Home / Insights / Technical SEO Audit Checklist: Crawl, Index, Render and Measure
Technical SEO Audit Checklist: Crawl, Index, Render and Measure
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
- Check important URLs return the intended status code. Use 200 for canonical pages, 301 for permanent moves and 404/410 for genuinely removed pages.
- Find redirect chains, loops, soft 404s and internal links pointing to redirects.
- Choose one preferred hostname and protocol, then keep internal links and canonical tags consistent.
- Confirm trailing-slash behavior is consistent and does not create duplicate indexable versions.
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.
3. Make the sitemap a clean indexation guide
- Include only canonical, indexable, successful URLs that you want search engines to discover.
- Exclude redirects, noindex pages, error URLs, parameter duplicates and alternate canonical versions.
- Use absolute URLs and valid XML.
- Update the sitemap when meaningful pages are added, removed or changed.
- Submit it in Search Console and investigate processing errors; submission does not guarantee indexing.
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
- Give each important page a distinct title and clear primary heading.
- Match the page to one main search intent and its natural supporting questions.
- Explain the service, scope, process, deliverables, constraints and who it is for.
- Use examples, original diagrams, evidence and practical detail where available.
- Remove boilerplate and repeated sections that make sibling pages interchangeable.
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
- Export query and page data separately, with date range, country, device and search type clearly recorded.
- Segment branded and non-branded queries so brand demand does not hide service-page performance.
- Find high-impression, low-CTR queries and test clearer titles and descriptions.
- Find queries ranking around positions 5–20 and improve the matching page rather than creating a duplicate.
- Compare pages with similar queries to detect cannibalization.
- Inspect representative URLs when indexing status changes and verify the actual canonical Google selected.
9. Prioritize fixes by impact and confidence
| Priority | Examples | Response |
|---|---|---|
| Critical | Important page blocked, wrong canonical, 5xx errors, accidental noindex | Fix and validate immediately |
| High | Orphan commercial page, duplicate intent, broken internal links | Resolve in the next release |
| Medium | Weak title, thin unique content, missing relevant schema | Improve based on evidence |
| Low | Minor wording or cosmetic markup issues | Batch 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.