To run a technical SEO audit, inventory the URLs you want indexed, crawl the website, check robots.txt and noindex directives, inspect canonical tags and redirects, and review page performance. Prioritize broken pages, blocked content and incorrect canonical URLs before minor warnings. Verify each change with a repeat crawl and Google Search Console URL Inspection. This technical SEO audit checklist produces a documented fix list instead of an unexplained tool score.
How do you run a technical SEO audit?
Run a technical SEO audit in seven checks: URL inventory, crawl access, indexing directives, status codes, canonical URLs, internal discovery and rendered usability. Record the expected behavior before judging a finding. A deliberately excluded search archive should not be handled like a public article accidentally excluded from indexing.
- List public URLs and representative page templates.
- Check whether crawlers can request those URLs.
- Inspect indexing directives in headers and HTML.
- Follow status codes and redirects to their final destinations.
- Compare canonical tags with the intended preferred URLs.
- Check sitemap entries and incoming internal links.
- Test visible content, mobile controls and the repaired behavior.
Keep a reproducible example for every defect. Include the URL, the observation date, the response or screenshot and an acceptance test. This makes a technical SEO audit useful to the person implementing the fix.
Which URLs should a technical SEO audit include?
A technical SEO audit should include URLs from navigation, the CMS inventory, sitemaps and known historical links. These sources reveal different parts of the site. A crawler starting at the homepage cannot discover a page that has no path from that starting point.
- Sample an article, category, homepage and author archive.
- Include pagination and any filtered or parameterized URLs.
- Add old addresses that should redirect or remain available.
Choose a crawler that fits the audit, then save its settings with the export so another reviewer can repeat the run.
How do you check crawl access and indexability?
Check crawl access and indexability as separate controls. Inspect robots.txt rules, page-level robots tags and HTTP headers for the same URL. Our guide to robots.txt and noindex explains why blocking a request is different from requesting exclusion from search.
- Compare the observed directive with the page’s intended role.
- Check whether an environment-wide setting affects public templates.
- Record disagreements between page HTML and response headers.
For staging, intentional noindex is a correct result. For a production article intended for discovery, the same setting needs investigation.
How do you audit status codes and redirects?
Audit status codes by requesting each URL and following the full redirect path. Three outcomes need different handling: a useful page returning success, an intentional move returning a redirect and a genuinely missing page returning an error.
- Test HTTP and HTTPS versions of representative addresses.
- Check the preferred hostname and trailing-slash behavior.
- Record loops, unnecessary intermediate hops and irrelevant destinations.
Do not label every missing URL a critical failure. Investigate whether readers or meaningful links still point to it and whether a relevant replacement exists.
How do you check canonical URLs?
Check canonical URLs by comparing the declared destination with the page’s actual content and preferred address. A canonical pointing to another domain or an unrelated article deserves investigation. Follow the destination too; a tag pointing at a redirect can reveal inconsistent configuration.
- Confirm the canonical uses the intended production hostname.
- Compare equivalent URL variants for conflicting signals.
- Check that distinct articles have not inherited one shared canonical.
The canonical URL decision framework helps separate legitimate consolidation from an accidental template-wide error.
How do you audit XML sitemaps and internal links?
Audit XML sitemaps against the set of URLs you actually want discovered. Google’s sitemap documentation recommends including canonical URLs; sitemap submission does not itself guarantee indexing.
- Flag sitemap entries that redirect or return errors.
- Compare missing entries with the intended public inventory.
- Find useful articles without incoming crawlable internal links.
Check both directions: sitemap inclusion does not prove a reader can navigate to an article, and a navigation link does not prove the page’s canonical configuration is correct.
How do you test rendering and mobile usability?
Test rendering by opening the same template as a reader and comparing its visible content with the fetched HTML. Check two states where relevant: before and after scripts run. Text or navigation that appears only after an interaction requires closer inspection.
- Open menus and article controls at a narrow screen width.
- Confirm that important images and text actually load.
- Test whether forms report success and validation errors clearly.
A repeatable server delay belongs in the hosting evaluation; an oversized image or broken menu belongs to its own implementation owner.
How do you prioritize technical SEO fixes?
Prioritize technical SEO fixes by verified impact, affected scope and dependencies. A broken article template can affect an entire publication; a cosmetic warning on one excluded archive may require no action.
- Critical: public content is unavailable or unintentionally excluded.
- High: discovery, canonical signals or core navigation are inconsistent.
- Routine: isolated defects have a working reader path.
These are editorial triage labels, not a universal scoring formula. Add an owner and acceptance test to each accepted issue so severity leads to action.
How do you verify a technical SEO fix?
Verify a technical SEO fix by repeating the original failing request and checking adjacent templates for regressions. Store the before-and-after evidence with the task. The Technical SEO collection provides narrower troubleshooting paths when a finding needs more detail.
Is a crawl the same as a technical SEO audit?
A crawl is an input to an audit. The audit interprets results against intended behavior and produces decisions, owners and tests.
Should every crawler warning be fixed?
Every warning should be assessed, but an intentional exclusion or retired URL may need no change. Record why you accepted the behavior.
Does passing an audit guarantee indexing?
Passing an audit does not guarantee indexing. It shows that the checks performed found no remaining blockers within the tested scope.
Written by
Theo Bennett
Theo Bennett is an editorial pen name used by Approve SEO for technical SEO and measurement coverage. The byline focuses on crawler verification, website maintenance, analytics interpretation, software contracts and the limits of benchmark data. Articles attributed to Theo draw on official documentation and other identified primary sources, with practical checks that readers can reproduce on their own sites. Examples are labelled when they are illustrative rather than measured results. Theo represents an editorial function, not an individual specialist. The portrait is an original AI-generated illustration. Source suggestions and corrections are handled through Approve SEO’s editorial contact route.