Home / Insights / Technical SEO Audit Checklist: Crawl, Index, Render and Measure

Search visibility playbook

Technical SEO Audit Checklist: Crawl, Index, Render and Measure

Published 18 November 2026 · Dominion Fortress

A technical SEO audit should answer four questions: can search engines fetch the page, should the page be indexed, can they understand the page, and does the page earn useful visibility? This checklist follows that sequence so teams fix causes instead of repeatedly changing titles.

1. Start with URL and HTTP hygiene

2. Check indexability—not just crawlability

A page can be crawlable but intentionally or accidentally excluded from indexing. Inspect robots.txt, meta robots, X-Robots-Tag response headers, canonical tags and the rendered page. Do not block a URL in robots.txt if Google needs to fetch it to see a noindex directive.

Important distinction: robots.txt controls crawling; noindex controls eligibility for indexing when the crawler can access the page. A canonical is a signal about preferred duplicates, not a guaranteed redirect or indexing command.

3. Make the sitemap a clean indexation guide

4. Audit internal discovery paths

Every important commercial page should be reachable through ordinary crawlable links. Link from relevant category pages, guides, tool results and related service pages using descriptive anchor text. Look for orphan pages and avoid relying on site search or JavaScript-only interactions as the only discovery route.

5. Improve page-level relevance

6. Validate structured data

Use only schema types that accurately describe visible page content. Organization, WebSite, BreadcrumbList and relevant Service or Article markup can clarify entities and page relationships. Validate JSON-LD syntax and eligibility, but do not expect markup alone to improve rankings or guarantee rich results. Never add fabricated reviews, awards, addresses, prices or credentials.

7. Check rendering, mobile and performance

Verify that the main content and important links are present in the rendered HTML, not hidden behind inaccessible interactions. Test mobile layouts, image dimensions, lazy-loading behavior, font loading and layout stability. Use field Core Web Vitals when available; a single lab test is useful for debugging but does not represent every visitor.

8. Use Search Console as a diagnostic system

9. Prioritize fixes by impact and confidence

PriorityExamplesResponse
CriticalImportant page blocked, wrong canonical, 5xx errors, accidental noindexFix and validate immediately
HighOrphan commercial page, duplicate intent, broken internal linksResolve in the next release
MediumWeak title, thin unique content, missing relevant schemaImprove based on evidence
LowMinor wording or cosmetic markup issuesBatch with normal maintenance

10. Measure outcomes without confusing correlation

Track clicks, impressions, CTR and average position by query and landing page. Add analytics events for meaningful enquiries, not just page views. Annotate deployments and content changes. Compare equivalent periods and countries, and remember that search demand, seasonality, competition and algorithm changes can affect results independently of your changes.

Useful official documentation

Read Google's SEO Starter Guide, robots.txt documentation, sitemap guidance and AI features guidance.

Want implementation, not just an audit?

Dominion Fortress provides technical SEO audits and implementation covering crawlability, indexation, internal architecture, structured data and Search Console diagnostics. Scope is confirmed against your platform and available access.

Technical SEO servicesRun a free SEO checkRequest a review

Related: AI search visibility · Website audit tool · AI search readiness tool

This guide is general educational information. Project decisions should be based on the specific systems, risks, permissions and requirements involved.