Technical SEO Audit

What Gets Crawled

The crawler follows internal links from your starting URL the way a search engine does, requesting each page and recording what came back. It checks status codes and redirect chains, canonical tags, indexability directives, page titles and descriptions, heading structure, image attributes, structured data, and internal link depth.

The reason to crawl rather than check pages one at a time is that technical problems are almost never isolated. A template change breaks a canonical on every page using that template. A bulk slug edit breaks every link pointing at the old URLs. Checking one page finds one instance and tells you nothing about scale.

Reading the Output

CRAWLED       412 pages, 1,940 links

BLOCKING INDEXATION            PAGES
  noindex on live pages           14
  canonical points elsewhere      31
  blocked in robots.txt            6

BROKEN
  internal 404s                   22
  redirect chains 2+ hops         48

DUPLICATE OR MISSING
  duplicate titles                67
  missing descriptions            89
  missing H1                      12

STRUCTURE
  pages 4+ clicks from home      103
  orphan pages                     7

Read the top block first and ignore the rest until it is clear. Fourteen live pages carrying a noindex directive and thirty-one pointing their canonical somewhere else means forty-five pages that cannot rank regardless of anything else on this list. Sixty-seven duplicate titles is a real problem and it is a smaller one, because those pages are at least eligible.

The structure block is the one people skip. A hundred and three pages sitting four or more clicks from the home page are being told, by your own linking, that they do not matter much. Seven orphan pages have no internal links at all and exist only because something else pointed at them once.

What an Audit Will Not Tell You

It will not tell you why traffic fell. Technical health is a floor, not a lever: fixing forty-five blocked pages lets them compete, and whether they win is a separate question about content and demand.

It also will not find problems that need a browser. Anything rendered by JavaScript after load, anything behind a login, and anything that only breaks on a specific device is outside what a crawl sees. A clean report means the crawler found nothing wrong, not that nothing is wrong.

Questions