Technical SEO audit

Most audit reports are a tool export with a logo on it: four hundred warnings, sorted by color, with no idea which three matter. My audits start from your question, such as "why did product traffic fall in March?", and end with the answer, the evidence behind it, and the order to fix things in.

Who it's for

• Sites whose organic traffic dropped and nobody can say why.
• Sites that have plateaued despite steady publishing.
• New owners, marketing leads, or agencies inheriting a site and wanting a baseline before they change anything.
• Teams planning a redesign or replatform who want to know what to protect.

What I examine

Crawling

A full crawl with Screaming Frog in both text-only and JavaScript rendering modes, so I can compare what the server sends with what a browser builds. Robots rules, XML sitemaps, status codes, redirect chains, internal link depth, and orphaned pages.

Indexing

The Page indexing report in Search Console, broken down by reason and by template; URL Inspection on representative pages; and the equivalent reports in Bing Webmaster Tools, which often confirm or contradict what Google shows.

Rendering

Raw HTML, rendered DOM, and the text a crawler actually extracts, compared on the same URLs. This is where the expensive surprises live: tabs, accordions, lazy sections, and consent tools that leave content invisible to bots.

Signals on the page

Titles, meta descriptions, headings, canonicals, hreflang, structured data, and internal anchor text, checked for duplication and conflicts at the template level.

Performance

Core Web Vitals from field data where it exists, lab tests where it doesn't, and the server and CDN configuration behind them.

History

What changed and when: deployments, plugin updates, migrations, Google updates, and backlink spikes, lined up against the traffic curve.

How I keep findings honest

Traffic losses rarely have a single cause, and the most dangerous move is to tell one tidy story about two unrelated problems. I keep separate problems on separate tracks, attach evidence to each finding, and say how confident I am. When the data can't settle a question, the report says what would.

What you receive

• A findings report: the question, the cause or causes, the evidence, and confidence for each.
• A ranked fix list, P0 to P3, with an owner and an effort estimate per item.
• Developer tickets with exact steps and acceptance criteria.
• A one-page summary in plain English for leadership.
• A walkthrough call, if you want one.

After the audit

Many clients have me implement the fixes I can reach, such as metadata, redirects, schema, and plugin or Cloudflare settings, and then verify the developer's work against the acceptance criteria. Others take the report to their own team. Either way the report stands on its own. Scope, timeline, and price are agreed before the audit starts. See Hire Me, or read what a technical SEO audit should give you.

Updated October 6, 2026