Technical SEO Audit Checklist: Find and Fix Problems That Hurt Rankings

A technical SEO audit is a debugging exercise, not a hunt for a perfect score. The useful question is: what could stop a search engine from finding, understanding, selecting, or serving an important page? Google describes crawling, indexing, and serving as related but distinct systems. A page can be reachable but not indexed, indexed but canonicalised to another URL, or technically healthy while failing to satisfy the searcher.

This checklist follows that chain. Start with the highest-impact failure first, record the affected URLs, and tie every recommendation to an observed response, tag, or persisted measurement. For a broader audit structure, compare this guide with SiteNexis' technical SEO audit framework, which adds machine-readability and entity checks.

1. Confirm the site can be crawled

Fetch the homepage and a representative sample of templates as an anonymous user and as a crawler with JavaScript disabled. Check DNS, TLS, response time, redirects, and status codes. A page intended for search should normally return a successful 200 response, not a soft 404, an authentication wall, or a redirect chain. Inspect robots.txt for rules that block important paths, and make sure the robots file itself is reachable. Google's crawling and indexing documentation is the reference for how these controls interact.

What to record

• The final URL and every redirect hop
• HTTP status and cache behavior
• Robots.txt rules affecting important directories
• Whether the main content is present in the initial HTML or only after rendering
• Any intermittent 5xx response observed from more than one location

2. Test discovery, not just accessibility

A page that loads when you paste its URL into a browser may still be hard to discover. Crawl internal links from the homepage, navigation, category pages, and XML sitemaps. Look for orphan URLs, links hidden behind client-side interactions, and anchors whose destination changes after hydration. A sitemap is a discovery aid, not a substitute for a usable internal link graph. Compare sitemap URLs with canonical URLs and with the URLs you actually want indexed.

Pay attention to pagination, faceted navigation, search-result pages, and tracking parameters. These systems can create thousands of crawlable combinations with little unique value. Google explains that canonicalisation signals can be combined, but a canonical tag is a hint rather than a command; redirects and consistent internal links are stronger operational fixes. See the canonical URL documentation before choosing a remedy.

3. Inspect indexability and canonicalization

For every important template, check the robots meta tag, X-Robots-Tag response header, canonical link, status code, and whether the page is blocked by a parent rule. A noindex directive is different from a crawl block: crawlers need to access a page to see a noindex instruction. A canonical points search engines toward a preferred representative; it does not guarantee that URL will be selected.

1. 1Find accidental noindex on production templates.
2. 2Find canonical tags that point to redirects, non-equivalent pages, or the wrong host.
3. 3Compare canonical URLs with sitemap and internal-link destinations.
4. 4Check language or regional alternates for reciprocal, valid references.
5. 5Remove duplicate URL variants where a redirect is practical.

4. Check rendering and page content

JavaScript is not automatically an SEO problem. The problem is a mismatch between what the first response contains and what a crawler can render reliably. Compare source HTML with rendered HTML for the title, H1, main copy, links, canonical, structured data, and meaningful images. Look for client-side errors, blocked scripts, hydration failures, and content that appears only after an interaction a crawler will not perform. Google's JavaScript SEO basics recommends keeping important metadata and content available in a dependable rendered page.

5. Review titles, headings, and duplicate templates

Titles and headings do not rescue an inaccessible page, but they help searchers and crawlers understand the page that is available. Check that each indexable page has a descriptive, unique title and one clear H1. Flag templates that produce hundreds of near-identical titles, empty headings, or headings used only for visual sizing. A useful audit also compares title promises with visible content: a page titled “pricing” that contains only a lead form is a relevance problem, not a metadata formatting problem.

6. Measure page experience without turning it into a score chase

Review Core Web Vitals and the conditions that cause them. LCP concerns loading performance, INP concerns interaction responsiveness, and CLS concerns visual stability. Segment by template and device rather than hiding poor pages inside a site average. Then inspect the cause: oversized hero media, render-blocking resources, long main-thread tasks, third-party scripts, or dimensions missing from images and embeds. Use web.dev's Core Web Vitals guidance for definitions and diagnostics.

7. Validate structured data against visible facts

Structured data should describe the page, not add claims that the page does not support. Validate JSON-LD syntax, required properties for the chosen type, URLs, dates, author identity, and relationships between entities. Compare schema values with visible copy. An Article date that differs from the displayed date, or a review score with no visible review evidence, creates a trust and eligibility problem. SiteNexis' citation checklist is useful for a second pass on visible-to-machine alignment.

8. Turn findings into a repair queue

Prioritise by affected URL value, failure severity, and confidence in the fix. A blocked money page outranks a missing descriptive alt attribute on an archive thumbnail. A canonical mismatch affecting a whole template outranks a single title typo. Assign an owner, a verification method, and a date to every repair. Re-crawl the changed URLs, then watch Search Console for the relevant pages and queries rather than assuming a deployment equals an indexing change.

A checklist is the beginning of the work

Technical SEO protects the path between a page and a search result. It does not guarantee relevance, useful content, or conversions. Once the critical access and indexing failures are fixed, move to content quality and measurement. The companion guide on why a site may not be ranking is organised around those next diagnostic questions.