A technical SEO audit should explain observed search problems, not generate a giant list of tool warnings. Start with site purpose and indexable page inventory, test how URLs are discovered and canonicalized, compare declarations with what the server returns, and connect each issue to affected templates and users.
Decision snapshot
| Decision | Practical approach | Watch for |
|---|---|---|
| Inventory first | Know which page types should and should not be indexed. | A crawl cannot judge duplicate or excluded URLs without intended state. |
| Test server truth | Inspect status, redirects, headers, HTML, rendering, and canonical signals. | A CMS setting or tool label may not match the public response. |
| Prioritize templates | Fix systemic defects affecting valuable page groups before isolated low-value URLs. | Issue counts alone exaggerate trivial problems. |
Define scope and intended index
List hosts, protocols, environments, languages, page templates, parameters, feeds, files, and the canonical URLs that deserve search visibility.
Audit discovery and crawl paths
Review navigation, contextual links, orphan candidates, sitemap membership, robots rules, status codes, redirect chains, pagination, and crawl traps using bounded crawls and server evidence.
Audit indexing and canonical signals
Compare canonical tags, redirects, sitemap URLs, internal links, robots meta and headers, duplicates, thin archives, rendered content, and Search Console indexing evidence.
Review page interpretation and experience
Check titles, headings, semantic HTML, structured data against visible content, mobile behavior, Core Web Vitals field data, JavaScript dependencies, images, and accessibility.
Prioritize, fix, and monitor
Group findings by root cause and template, estimate affected valuable pages, assign severity and owner, define acceptance tests, deploy safely, and monitor recrawl and business outcomes.
Action checklist
- Canonical page inventory and exclusion rules are documented
- Sitemap contains only canonical indexable successful URLs
- Robots, status, canonical, noindex, and internal links send consistent signals
- Important content and links exist in rendered output available to crawlers
- Structured data matches visible page content and supported types
- Fixes have affected templates, evidence, owner, acceptance test, and monitoring date
Working worksheet
Record these fields in the same working document so the decision can be reviewed and handed off:
- Finding and observed evidence
- Affected host, template, sample URLs, and approximate valuable-page impact
- Desired behavior and search/user consequence
- Root cause, fix owner, effort, risk, and priority
- Acceptance command or inspection, deploy date, and monitoring result
Common failure patterns
- Exporting every crawler warning as a priority without sampling URLs
- Blocking duplicate URLs in robots.txt before crawlers can see canonical or noindex signals
- Changing canonical, redirects, sitemap, and navigation simultaneously without a URL map
Connect this work
Sitemaps are one discovery and canonicalization input. Read diagnose sitemap-specific failures.
Robots rules should not be used as an indexing shortcut. Read review crawl controls carefully.
Technical quality includes measured user experience. Read turn performance evidence into fixes.