Question 1

How long does an audit take?

Accepted Answer

Typically 1–2 weeks from kick-off to finished report, depending on the site's size, complexity and how much access I get to Search Console, GA4 and any dev environment. A smaller B2B site with 50 key pages can be done in a week; an international store with 15,000 products and five language versions typically takes 3.

The work splits roughly: week one goes to data collection and crawl (Screaming Frog, log file analysis, Search Console exports, Core Web Vitals measurements). Week two goes to interpretation and prioritisation — that's where the difference between an auto-generated audit and a real audit lives.

I always deliver a preliminary 'quick wins' list along the way if we find serious issues that shouldn't wait for the full audit. There's no reason to live with a broken canonical implementation for two weeks when it can be fixed the same day I find it.

Question 2

Do I get a report?

Accepted Answer

Yes, but the most valuable part of the audit isn't the report itself — it's the prioritised action plan and the walkthrough afterwards, where I explain *why*, not just *what*.

The report is structured as an action plan, not an academic analysis. Every issue gets a priority (P0/P1/P2), a clear description (what's the problem, where does it happen, how many pages are affected), a recommended fix (concrete, not 'we should consider…'), and a verification criterion (how do we confirm the fix worked after deploy).

After delivery we walk through the report together — either a 1-hour meeting or a Loom recording if you prefer async. This walkthrough is often the most valuable part: you get the context, can ask questions, and the team gets shared alignment on where the priority sits.

Question 3

Can you also execute?

Accepted Answer

Yes, and I do for most clients. After the audit is delivered, I can either handle execution myself (technical implementation directly in the theme, collaboration with your developers, content production, link building) or act as an ongoing sparring partner while your own team executes.

The model adapts to your capacity. If you have a mature marketing and dev team, it usually makes best sense that I stay on the strategy and verification side while they execute. If you have a small team or are mid-way through another project, I can take it over fully for a period and gradually hand back when it's stable.

I generally prefer longer engagements where we can measure the impact of each fix and adjust the plan continuously — SEO moves in quarters, not weeks, and an audit is rarely a one-off deliverable.

SEO Audit

Technical review

Content and on-page

Authority and competitors

Frequently asked questions

Follow my SEO insights