Technical SEO
How to run a technical website audit that leads to better decisions
A useful audit is not a long list of warnings. It connects reliable evidence to business impact, makes the next action clear, and gives the team a way to verify the result.
What a good audit should deliver
The result should tell you whether important pages can be discovered, rendered, understood, trusted, and used comfortably. Every important finding needs evidence, severity, an affected URL or component, a practical recommendation, and a verification step.
1. Start with the purpose and the real page set
Define the outcome before opening an audit tool. A lead-generation site, an online store, and a logged-in application do not have the same critical journeys. Record the production hostname, languages, important templates, conversion paths, analytics boundaries, and any areas that must remain private.
- Choose representative URLs for the homepage, services, content, legal pages, forms, and each language or market.
- Separate public, indexable pages from checkout, account, search-result, parameter, staging, and internal URLs.
- Write down the primary conversion so technical severity reflects lost revenue or trust, not just a generic score.
2. Verify discovery and indexability as a system
Check status codes, redirects, robots directives, canonical URLs, internal links, sitemap entries, and language alternates together. A valid XML file cannot compensate for weak internal linking, conflicting canonicals, duplicate locale roots, or a page that returns an error to crawlers.
- Each indexable URL should return a stable 200 response and declare a canonical that resolves to the same preferred page.
- Multilingual pages need reciprocal hreflang mappings, consistent trailing-slash rules, and an intentional x-default destination.
- Keep only canonical, indexable URLs in the sitemap and use an accurate last modification date only when content materially changes.
3. Collect evidence from more than one layer
Combine server responses, rendered HTML, browser behavior, structured data, accessibility semantics, security headers, and performance measurements. Lab tests are useful for diagnosis; real-user field data shows what visitors experience across devices and networks. One run or one aggregate score is never the whole answer.
- Save the exact URL, response, element, request, or rule that supports each finding so another person can reproduce it.
- Test mobile and desktop, common templates, consent states, and at least one complete conversion journey.
- Distinguish confirmed defects from opportunities and from checks that require human or business validation.
4. Prioritize, implement, and retest
Rank work by reach, user or commercial impact, confidence, effort, and risk. Fix shared causes before isolated symptoms: a template-level canonical error matters more than polishing one page. After release, repeat the original check and watch field data, search visibility, conversions, and error logs for unintended effects.
- Use a short critical queue, a planned improvement queue, and a monitored backlog instead of labeling everything urgent.
- Give every task an owner, acceptance criteria, affected scope, and rollback or mitigation note when risk is meaningful.
- Close a finding only when the production result is verified—not when code is merely merged or a score moves once.
A compact audit checklist
- 01 Confirm the production scope, key templates, languages, critical journeys, and conversion goal.
- 02 Crawl from internal links and compare the discovered URLs with the sitemap and expected page inventory.
- 03 Review status codes, redirects, canonicals, robots controls, hreflang, titles, descriptions, and structured data.
- 04 Measure performance, accessibility, resilience, and security on representative mobile and desktop pages.
- 05 Group findings by shared root cause, then prioritize them by impact, reach, confidence, effort, and risk.
- 06 Retest the released change on production and monitor user, search, conversion, and operational signals.
The principle to remember
A technical audit earns its value after the scan: when its evidence is reproducible, its priorities match the website’s goals, and its fixes are verified in the environment where real people and crawlers use them.
Primary references
Continue with a related guide
These checks influence one another. Follow the next guide to verify the surrounding signals, not only one tag or score.