Technical SEO is not a score. It is the set of constraints that decide whether your content can be crawled, rendered, indexed and trusted. This checklist is the one we use in a technical SEO engagement and a fixed-scope audit.

1. Crawlability

  • Robots.txt allows CSS, JS, images and the pages that need to rank.
  • No accidental blocks on staging, CDN or security layers.
  • Sitemap contains canonical, indexable URLs only.
  • Internal links are crawlable <a href> links.
  • Crawl depth: money pages are within 3–4 clicks of the home page.
  • No infinite spaces: filters, calendars or parameters that generate unlimited URLs.
  • Server responses are fast and stable; 5xx and timeouts are monitored.

2. Indexation

  • Canonical tags are self-referencing on pages that should rank.
  • Noindex is intentional and template-scoped.
  • Status codes are correct: 200, 301, 410.
  • Duplicate variants are canonicalised or excluded.
  • Pagination and faceted navigation have a rule.
  • Hreflang and locale versions are reciprocal and self-referencing.
  • No index bloat from tracking parameters or empty pages.

3. Rendering

  • The main content is present in the rendered HTML Google sees.
  • JS and CSS required for rendering are not blocked.
  • Internal links work without JS where possible.
  • Client-side routing has server-rendered fallbacks.
  • Tabs and accordions do not hide the primary content.
  • The URL Inspection rendered HTML matches what users see.

4. Core Web Vitals

  • LCP < 2.5s on mobile field data.
  • INP < 200ms; long tasks and third-party scripts are controlled.
  • CLS < 0.1; media and embeds reserve space.
  • Hero images are not lazy-loaded; fonts do not cause a late swap.
  • CWV are checked by template, not only the home page.
  • Third-party scripts load after consent and only when needed.

5. Architecture and internal links

  • One page per intent, with a clear primary query.
  • Hub and child pages link in both directions.
  • Money pages get links from relevant guides and cases.
  • Anchor text is descriptive and varied.
  • Breadcrumbs match the URL hierarchy.
  • Orphan pages are either linked or removed.

6. Schema and structured data

  • Organization and WebSite schema are valid.
  • Service, Product or Article schema matches the page.
  • FAQ schema is used only with visible FAQs.
  • No fake reviews, ratings or awards.
  • Schema is tested after template changes.

7. Migrations

  • Every old URL is mapped to a new one (or a 410).
  • Redirects are 301, single-hop and tested.
  • Canonicals, hreflang and sitemaps are updated at launch.
  • Analytics and Search Console tags survive the migration.
  • A pre-launch crawl and a post-launch crawl are compared.
  • Rollback plan exists.

8. Monitoring

  • Index coverage alerts are on.
  • CWV alerts are on for key templates.
  • Uptime and 5xx alerts are on.
  • A monthly crawl diff catches template regressions.
  • Search Console and analytics properties are correct.

How to prioritise

Fix what blocks indexation and revenue first. Cosmetic issues can wait. A simple order:

PriorityWhatWhy
P0Indexation, robots, canonicals, 5xxNothing else works if pages are not indexed
P1Rendering, CWV, internal links to money pagesDecides whether content can rank and convert
P2Schema, pagination, faceted rulesImproves clarity and controls bloat
P3Cosmetic and edge casesBatch later

FAQ

Written by

KEA CORP

SEO and automation team. We publish what we learn from live B2B projects, with sources where the numbers allow.

About KEA CORP →