Technical SEO Audit Checklist for Ecommerce, Lead Gen and Publisher Sites

Overview

A strong technical SEO audit is not a single pass through a crawler report. It is a way to confirm that search engines can discover your important URLs, understand their relationships, render key content, and reach the pages that deserve to rank without wasting crawl effort on duplicates, faceted combinations, thin archives or broken journeys.

The reason many audits fail is simple: they treat every website as if it has the same technical priorities. In practice, an ecommerce catalogue, a lead gen site and a publisher platform tend to break in different places.

Use this checklist in two layers:

• Layer 1: universal technical checks that apply to almost any site.
• Layer 2: scenario-specific checks based on how the website earns traffic and revenue.

Before you begin, collect a basic audit set:

• Access to Google Search Console and analytics.
• A site crawl from your preferred crawler.
• XML sitemap files and robots.txt.
• A sample of server logs if available.
• A list of priority templates and revenue-driving URLs.
• Knowledge of recent migrations, plugin changes, tracking updates or design releases.

If you work through the checklist in order, start with indexation and crawl control first. There is little value in refining page speed or schema on pages that are accidentally blocked, canonicalised away or buried too deeply in the site structure.

Universal technical SEO audit checklist

• HTTP status codes: confirm priority pages return 200 status codes and that redirects are intentional, direct and clean.
• Indexation controls: review noindex tags, x-robots directives, canonical tags, robots.txt rules and password protection.
• XML sitemaps: include only canonical, indexable URLs and keep them current.
• Internal linking: make sure key pages are reachable through crawlable links and not only search functions or scripts.
• Duplicate URLs: check parameters, uppercase and lowercase variants, trailing slash differences, filtered views and alternate paths.
• JavaScript rendering: verify that important content, links and metadata are available without rendering failures.
• Core page experience basics: assess layout stability, image handling, script weight, caching and unnecessary third-party tags.
• Mobile usability: confirm content parity, navigational access and template consistency on mobile devices.
• Structured data: validate that markup matches page intent and visible content.
• Pagination and archives: ensure long lists are crawlable and do not trap authority in weak pages.
• International and regional handling: where relevant, review URL structure, duplicate regional pages and hreflang implementation.
• Orphan pages: identify URLs in sitemaps or analytics that are not linked internally.
• Broken assets: check images, JavaScript and CSS files that fail to load and affect rendering.

For a companion content-layer review, it helps to pair this with an on-page SEO checklist for UK small business websites. Technical SEO and on-page SEO usually fail together, not separately.

Checklist by scenario

This section breaks the audit into three site types so you can prioritise what is most likely to affect performance.

Ecommerce sites

An SEO audit for ecommerce should focus heavily on duplication, crawl waste and template consistency. Large product and category sets create more indexation risk than most other website models.

• Category pages: confirm they are indexable, linked from primary navigation and not diluted by duplicate category paths.
• Facet and filter handling: review whether filtered URLs create low-value indexable combinations. Decide which combinations deserve crawl access and which should remain non-indexable.
• Pagination: ensure product lists remain crawlable and products are not hidden behind interactions search engines struggle to follow.
• Canonical tags: test products with variants, sort orders and parameters. Canonicals should reflect the preferred commercial URL, not a convenient default that removes key pages from the index.
• Out-of-stock and discontinued products: define a consistent policy. Avoid serving dead-end pages with no alternatives or relevance.
• Internal linking to revenue pages: use merchandising modules, related products and category hubs to support priority ranges.
• Duplicate product descriptions: while often seen as a content issue, they also create technical ambiguity when variants and duplicate product URLs exist.
• Site search pages: check whether internal search results are indexable by accident.
• Image optimisation: review file size, modern formats, descriptive filenames and lazy loading that does not block key content.
• Structured data: validate product, offer, breadcrumb and review markup where appropriate. Keep it aligned with visible content.
• Variant logic: make sure size, colour or style options do not produce unmanaged URL sprawl.
• Merchant platform quirks: audit platform-generated duplicate collections, tags, parameter URLs or app-created pages.

For ecommerce, the highest-value question is often: Are search engines spending time on URLs that can never rank or convert while important category and product pages remain weakly linked?

Lead generation sites

Lead gen websites are usually smaller, but technical issues can have an outsized impact because the site relies on a limited set of service pages, local landing pages and conversion templates.

• Primary service pages: confirm they are indexable, self-canonical and linked prominently from the main navigation and supporting content.
• Location pages: review template uniqueness, internal links, crawl depth and duplication across towns or service-area variants.
• Thin utility pages: identify thank-you pages, campaign pages, old test pages and duplicate quote forms that may be getting indexed.
• JavaScript forms and CTAs: make sure forms, phone links and conversion elements do not break layout or slow the template excessively.
• Local business signals: align address, service-area information and local schema where relevant.
• Service silos: check that related services link logically to each other and to the main conversion page.
• Redirect hygiene: lead gen sites often change service names or page URLs during redesigns. Audit for redirect chains and internal links pointing to old locations.
• Index bloat: tag pages, media attachments, archived landing pages and duplicate blog category pages can dilute a small site's authority.
• Core Web Vitals fixes: pay close attention to heavyweight hero sections, embedded maps, chat widgets and third-party booking tools.
• Structured data: validate organisation, local business, service and FAQ markup where it genuinely reflects visible content.

For local and service-led websites, technical SEO should support clearer topical architecture and stronger local intent, not just cleaner crawl reports. If local visibility is part of your strategy, combine this work with your Google Business Profile optimisation and local landing page review.

Publisher sites

Publisher and media-style sites usually struggle with scale, freshness and archive management. The core technical question is whether the site helps search engines find valuable articles quickly without getting lost in tag archives, duplicate feeds or low-value pagination.

• Section hubs and topic pages: verify they are indexable, well linked and clearly differentiated.
• Tag and category archives: decide which archive types deserve indexation and which should be noindexed or consolidated.
• Pagination and infinite scroll: ensure older articles remain reachable to crawlers.
• Publication and update dates: keep template signals clear and consistent where freshness matters.
• Article schema: validate structured data and avoid markup that overstates authorship, reviews or page type.
• Media handling: optimise image dimensions, lazy loading and ad placements that shift layout.
• Internal recirculation: related articles, topic hubs and evergreen resource centres should support deeper crawling.
• Canonical discipline: review syndicated, republished or printer-friendly URLs.
• Feed, search and author pages: confirm low-value archive types are not crowding the index.
• Advertisement and script load: assess render-blocking impact and template weight, especially on mobile.

Publisher audits often reveal a simple pattern: too many URLs are technically available, but too few are strategically important. Technical SEO should narrow that gap.

If your content model is evolving because of AI-assisted editorial workflows, it is worth reviewing human-in-the-loop workflows and how to make listicles trustworthy again so technical changes support better editorial quality rather than just faster publishing.

What to double-check

These are the areas most likely to produce false confidence during a technical SEO audit checklist review. They deserve a second pass before you sign off recommendations.

1. Pages that are crawlable but not truly indexable

A URL may return 200 and appear in a sitemap, yet still be suppressed by canonicals, thin duplication, soft redirects or inconsistent internal signals. Check whether the same page is:

• linked internally as the preferred version,
• listed in XML sitemaps,
• self-canonical,
• free of noindex directives,
• not duplicated across parameters or alternate paths.

2. JavaScript-dependent content

If navigation, product information, FAQs or internal links depend on delayed rendering, test what is available in raw HTML versus rendered output. This matters for crawl issues SEO investigations because some pages look complete in a browser but remain weakly understood by crawlers.

3. Internal linking depth

Important pages should not sit four or five clicks away from any useful hub. Crawl depth is not a perfect metric, but it is a useful warning sign. Review whether high-value URLs are linked from navigation, contextual copy, breadcrumbs and parent hubs.

4. Conflicting directives

One of the most common audit problems is mixed messaging:

• blocked in robots.txt but listed in XML sitemaps,
• canonicalised to one URL but internally linked to another,
• noindexed while still treated as a core landing page,
• redirected but still present in navigation and canonicals.

Search engines can handle many imperfections, but they respond better when your strongest signals agree.

5. Site migrations and template releases

Even a small redesign can alter heading structure, internal links, render paths, image loading, canonical logic or crawlable navigation. Double-check any release that touched templates, plugins, frameworks or CMS output. On WordPress sites, plugin updates often create issues that look like content losses but are actually technical regressions.

Structured data changes deserve careful review as well. For a deeper schema-focused companion, see Structured Data for AEO.

Common mistakes

Most failed audits do not fail because the analyst missed an obscure edge case. They fail because the recommendations are disconnected from site type, business value or implementation reality.

• Treating every error as urgent: hundreds of low-value 404s are not automatically more important than one canonical error on your main category page.
• Optimising crawl reports without business context: fix the pages that drive revenue, leads or strategic visibility first.
• Ignoring index bloat: more indexable URLs rarely means more SEO value.
• Overlooking template-level causes: if one product page is broken, review the template before fixing isolated URLs.
• Confusing UX fixes with SEO fixes: there is overlap, but not every design complaint is an organic search problem.
• Publishing new content while important pages remain blocked or diluted: this is a common reason teams feel SEO is not working.
• Using broad noindex or disallow rules too aggressively: quick clean-up moves can remove pages you actually need.
• Neglecting logs and real crawl behaviour: a theoretical architecture is less useful than evidence of what bots actually request.
• Auditing once and assuming the site is stable: technical SEO decays quietly through releases, plugins, tracking scripts and content operations.

There is also a newer layer to consider: how technical setup affects visibility beyond classic web search. If your brand is thinking about AI retrieval, crawl governance and entity clarity, related reading on LLMs.txt, robots and the new bot economy and cross-engine brand hygiene can help frame those decisions without confusing them with core indexation work.

When to revisit

The most useful indexing checklist is the one your team returns to before issues become expensive. Treat technical SEO as a recurring operating review, not a one-off project.

Revisit this audit:

• Before seasonal planning cycles when traffic demand, inventory, campaign landing pages or editorial schedules are about to change.
• When workflows or tools change including CMS updates, theme releases, app installs, tracking revisions and JavaScript-heavy redesigns.
• After migrations such as domain changes, HTTPS changes, URL restructuring or platform moves.
• When rankings drop without a clear content cause especially if affected pages span templates rather than isolated URLs.
• When indexation patterns shift such as rising excluded URLs, sudden spikes in crawled but not indexed pages or unexplained sitemap inconsistencies.
• When page speed or rendering regresses after adding experiments, scripts, embeds or ad technology.

A practical revisit routine

1. Monthly: review Search Console coverage, sitemap health, crawl anomalies, core templates and recent releases.
2. Quarterly: run a fuller crawl, review internal linking, duplicate URL patterns and site architecture drift.
3. Before major campaigns: test landing page indexability, render performance, canonicals, mobile UX and analytics tracking.
4. After deployments: spot-check page source, headings, metadata, structured data, canonical output and status codes.

If you need a simple rule for prioritisation, use this sequence:

1. Fix what blocks crawling or indexation.
2. Fix what weakens important templates at scale.
3. Fix what wastes crawl budget on low-value URLs.
4. Fix what slows or destabilises the user experience on key pages.
5. Then refine enhancements such as secondary schema or low-impact clean-up tasks.

A good technical SEO audit is not a document to file away. It is a working checklist that helps your team preserve search visibility as the website grows, changes platform, adds content and accumulates technical debt. If the site changes, the audit should change with it.