Las Vegas SEO Logo
Book a Call

Resources

Technical SEO Checklist

Resource · Technical & On-Page

Technical SEO Checklist: A Practical Website Audit Checklist

For each item, mark Pass, Needs attention, or Not applicable. Record affected URLs, evidence, severity, owner, deadline, and a retest method.

Checklist resource

Reviewed October 17, 2026

Las Vegas SEO Agency

Validate tool warnings before treating them as confirmed defects. A long list of resolved warnings is not the same as a healthier website.

On this page

  1. 1. Baseline and Access
  2. 2. Crawlability and Discovery
  3. 3. Robots and Indexing Directives
  4. 4. Status Codes and Redirects
  5. 5. Canonicalization and Duplicate URLs
  6. 6. URL Structure
  7. 7. Rendering and JavaScript
  8. 8. Mobile Usability and Accessibility
  9. 9. Performance and Core Web Vitals
  10. 10. Structured Data
  11. 11. HTTPS and Security
  12. 12. Analytics and Conversion Tracking
  13. 13. Migration and Deployment
  14. 14. Monitoring
  15. 15. Prioritization
  16. 16. Issue Tracking Template
  17. Conclusion

1. Baseline and Access

  • Confirm the correct production domain and preferred hostname.
  • Confirm access to Search Console and analytics where available.
  • Record CMS, framework, hosting, CDN, and major plugins.
  • Identify important page templates and URL groups.
  • Save a baseline crawl and sitemap copy.
  • Record recent migrations, redesigns, and releases.
  • Confirm a safe staging and deployment process.

2. Crawlability and Discovery

  • Important pages are linked from crawlable internal links.
  • Navigation links work without inaccessible interactions.
  • Important pages are not orphaned unintentionally.
  • XML sitemap is accessible.
  • Sitemap contains intended canonical, indexable URLs.
  • Sitemap excludes redirects, errors, and intentionally noindexed URLs.
  • Low-value parameter URLs do not create uncontrolled URL growth.
  • Internal links do not point unnecessarily to redirects.
  • Important pages are reachable without excessive click depth.

3. Robots and Indexing Directives

  • Robots.txt returns successfully and contains intended rules.
  • No important page paths are blocked accidentally.
  • Required resources are not blocked unnecessarily.
  • Meta robots directives are correct.
  • HTTP X-Robots-Tag headers are reviewed where used.
  • No unintended noindex rules exist.
  • Blocked URLs are not being relied on to communicate a noindex directive.
  • Representative URL groups are tested after changes.

4. Status Codes and Redirects

  • Important pages return the expected successful status.
  • Deleted pages return an appropriate 404 or 410 when no replacement exists.
  • Permanent moves use appropriate permanent redirects.
  • Temporary redirects are used only when the move is temporary.
  • Redirect chains are minimized.
  • Redirect loops are absent.
  • Redirect destinations match the original intent.
  • HTTP and HTTPS behavior is consistent.
  • Hostname and trailing-slash rules are consistent.
  • Internal links point directly to final destinations.

5. Canonicalization and Duplicate URLs

  • Important pages have appropriate canonical tags.
  • Canonicals point to accessible, appropriate destinations.
  • Canonicals do not point unnecessarily to redirects or errors.
  • Sitemap URLs align with canonical choices.
  • Internal links align with preferred URLs.
  • Parameter and filter URLs are reviewed.
  • HTTP/HTTPS, hostname, and slash variants are handled consistently.
  • Duplicate content is consolidated where appropriate.
  • Canonical tags are not being used as a substitute for necessary redirects.

6. URL Structure

  • URLs are readable and stable.
  • Duplicate paths are avoided.
  • Tracking parameters do not create unnecessary indexable duplicates.
  • Sorting and filtering behavior is understood.
  • Session IDs are not needlessly exposed in URLs.
  • URL casing is consistent.
  • Old URLs are mapped during migrations.
  • URLs are not changed solely to insert extra keywords.

7. Rendering and JavaScript

  • Important content appears in rendered output.
  • Important links are discoverable.
  • Titles and metadata render correctly.
  • Navigation works.
  • Resources required for rendering are accessible.
  • Console and server errors are investigated.
  • Content does not require an inaccessible interaction to appear.
  • Important pages do not require authentication unless intended.
  • Representative templates are tested with rendered-page tools.

8. Mobile Usability and Accessibility

  • Navigation works on small screens.
  • Text is readable without unnecessary zooming.
  • Tap targets have practical spacing.
  • Forms and validation work.
  • Phone and booking links are functional.
  • Sticky elements do not hide important content.
  • Images, tables, and embedded media fit the viewport.
  • Keyboard navigation is considered.
  • Focus states and labels are usable.
  • Accessibility issues affecting core tasks are addressed.

9. Performance and Core Web Vitals

  • Field performance data is reviewed where available.
  • LCP bottlenecks are investigated.
  • INP and long JavaScript tasks are reviewed.
  • CLS causes are identified.
  • Images are appropriately sized and compressed.
  • Fonts are loaded efficiently.
  • Unnecessary JavaScript and CSS are reduced where practical.
  • Caching and server response are reviewed.
  • Third-party scripts are evaluated.
  • Lab tests are not treated as a replacement for field data.
  • Performance is retested after changes.

The Core Web Vitals guide covers diagnosis for each metric.

10. Structured Data

  • Markup matches visible page content.
  • Schema type fits the page and entity.
  • Required properties are present where applicable.
  • URLs and entity references are correct.
  • Conflicting duplicate markup is reviewed.
  • Unsupported or misleading claims are absent.
  • Validation errors are reviewed.
  • Eligibility for intended search features is checked against current guidance.
  • No rich-result guarantee is made based on markup alone.

11. HTTPS and Security

  • TLS certificate is valid.
  • HTTP redirects to the preferred HTTPS version.
  • Mixed content is addressed.
  • Canonicals use the preferred secure URLs.
  • Important forms are protected.
  • CMS, plugins, and dependencies are maintained.
  • Backups and restoration procedures are tested.
  • Unauthorized changes and suspicious URL generation are monitored.
  • Error pages do not expose sensitive information.

12. Analytics and Conversion Tracking

  • Analytics loads on intended pages.
  • Key events are defined consistently.
  • Form success is measured, not only button clicks.
  • Phone and booking events are tested where tracked.
  • Duplicate events are investigated.
  • Consent and privacy requirements are respected.
  • Tracking survives releases and template changes.
  • CRM lead statuses align with reporting definitions.
  • Test conversions are clearly identified.

13. Migration and Deployment

  • Old URLs are crawled before migration.
  • Important URLs are mapped to relevant new destinations.
  • Redirects are tested in staging.
  • Canonicals, robots directives, and sitemaps are checked.
  • Titles and important content are preserved or deliberately updated.
  • Forms and analytics are tested.
  • Rollback plan is available.
  • New site is crawled after launch.
  • Redirect chains and broken internal links are fixed.
  • Indexing and traffic trends are monitored with context.

14. Monitoring

  • Server errors are monitored.
  • Important URLs are checked for availability.
  • Indexing changes are reviewed.
  • Sitemap errors are checked.
  • Broken links and redirects are audited.
  • Robots and canonical changes are monitored.
  • Performance trends are reviewed.
  • Structured data errors are checked.
  • Conversion events are tested periodically.
  • Deployments and major changes are logged.

15. Prioritization

LevelWhat belongs here
CriticalImportant pages unintentionally noindexed, widespread server failures, a broken primary site, security compromise, or a migration without essential redirects.
HighBroken internal navigation, important canonical errors, widespread rendering problems, failed forms, or important pages inaccessible to crawlers.
MediumDuplicate URL patterns, performance bottlenecks, internal-link gaps, or inconsistent structured data.
LowerHarmless warnings on pages that do not need indexing, cosmetic issues with no user impact, or speculative optimizations without evidence.

Priority depends on the number and importance of affected URLs and the impact on users.

16. Issue Tracking Template

URL or templateFindingEvidenceImpactPriorityFixOwnerRetest
        
        
        

Conclusion

A technical SEO checklist is most useful when it links each finding to a real URL, evidence, user or search impact, and a verified fix. Focus on important pages and confirmed issues rather than maximizing the number of warnings resolved.

FAQ

Frequently Asked Questions

Which warnings matter, and how often to re-run the checks.

Still have a question?

Ask Our Team
Does every warning need fixing?

No. Confirm the issue and its impact before assigning work.

No. Some utility, duplicate, or low-value URLs should not be indexed.

No. Performance tests help diagnose usability bottlenecks but do not guarantee rankings.

Crawl after major changes and on a cadence appropriate to site size and release frequency.

Keep Going

The rest of the Google Business Profile library

Six companion resources, each covering one job: setting up, checking, choosing, photographing, appealing and diagnosing.

Technical SEO Guide

The full framework behind every item on this list.

Open the guide

Crawlability Guide

How URLs get discovered, and how to fix what blocks them.

Open the guide

Core Web Vitals Guide

Diagnose LCP, INP and CLS with field data, not score chasing.

Open the guide

On-Page SEO Guide

Intent, titles, headings, content and conversion on a single page.

Open the guide

Schema Markup Guide

Choose the right type, validate it, and avoid misleading markup.

Open the guide

Internal Linking Guide

Architecture, anchors, orphan pages and crawl paths.

Open the guide

Las Vegas SEO Agency

Want this run against your site?

We work the checklist on the templates that carry your traffic and leads, attach evidence to every finding, and retest after each fix rather than closing it on trust.

Book a Free Strategy Call
Profile Management Services

Explore next: Local SEO · Google Business Profile Management · All Resources · Pricing