SEO & Organic Growth
Technical SEO audit
Your site crawled the way a machine sees it, reconciled against Google's own index data, and a fix list ordered by what each problem is costing you.
- From
- $250–$2,000
- Typical time
- 5–10 days
- Usually bought by
- Any site owner
Why a site with real pages gets no traffic
Almost everyone who asks for this arrives with one of two feelings. The first is confusion — the site exists, the pages look fine, money was spent, and nothing comes in. The second is doubt planted by somebody else, usually a sentence like "your site is technically broken", with no explanation of what that means or whether it is true.
Both feelings come from the same gap. A website has three separate states and they are routinely confused with each other. Can Google reach the page at all? Has Google decided to keep it? And where does it sit when somebody searches? Those are three different questions with three different answers, and a page can pass the first and fail the second, or pass both and sit on page four. The temptation is to jump straight to the third question, which is why the diagnosis so often goes wrong. An audit is the work of asking all three, in order, with evidence.
The commonest finding is not glamorous. A plugin setting quietly applied a noindex directive to two hundred pages. A sitemap lists sixty URLs when the site has three hundred. A theme update started returning the wrong status code. None of that is visible from the front end, which is exactly why the owner has been staring at the site for months without seeing it.
How the audit runs
- Access and baseline. Search Console, analytics and CMS access, then a full export of the last sixteen months of query and page data before anything is touched. Search Console keeps only sixteen months and then deletes it permanently, so day one is the only chance to capture the history. PageSpeed screenshots of the main templates go in the same folder. Half a day.
- Crawl the site the way a bot does. Screaming Frog across every reachable URL, saved as a crawl file so the state of the site on this date can be reopened later. If the site renders content with JavaScript — React, Vue, a modern Shopify theme — the crawl runs with JavaScript rendering switched on, which is dramatically slower and the only way to get a truthful result. Half a day to a day, longer while a large render crawl runs.
- Reconcile the crawl against Search Console. This is the step that separates a real audit from a tool export. The crawler shows what is reachable; Search Console shows what Google actually did with it, including the reasons — excluded by noindex, duplicate without user-selected canonical, crawled but currently not indexed. The answer is almost always in the gap between the two lists. One day.
- Verify every finding by hand, then rank it. Each flagged issue is opened in a browser and confirmed before it goes in the document, because crawlers report false positives. Surviving issues go into a priority table — issue, URLs affected, business impact, effort in hours, and who does it. P1 is this week, P2 is this month, P3 is when there is budget. One to two days.
- Write it, then walk you through it. An executive summary a non-technical owner can read, then one section per P1 and P2 issue with the evidence, the exact fix and how the fix will be verified. A short call to agree who does what. Half a day, plus the call.
Tools, so you know what you are buying — Screaming Frog for the crawl, Google Search Console for the truth about indexing, PageSpeed Insights for field data, the browser's own developer tools for confirmation, and the Rich Results Test for markup.
What moves the price
The range is $250–$2,000 over 5–10 days, and three things decide where a particular site lands inside it.
How many URLs there are. Five hundred pages and fifty thousand pages are not the same job. Past a few thousand URLs the crawl itself becomes a scheduling problem, sampling decisions have to be made and defended, and the reconciliation work grows with the site.
The platform. WordPress is the well-trodden case and the fixes are mostly known. A custom build with no plugin layer, or a large store where template changes have to be made in theme files, adds implementation time to every single item on the list.
Whether implementation is included. A report alone sits at the lower end. An audit where we apply the P1 and P2 fixes ourselves costs more than double, and it is the version that produces a result, because the failure mode of report-only work is that nothing ever gets applied.
What usually goes wrong
The tool's output gets forwarded as the report. A crawler produces three hundred flagged items on a typical site. Pasting all of them in makes the document look thorough and makes you freeze — the site looks doomed, nothing gets done, and the money is wasted. Ranking is the deliverable. A list is not.
The crawl runs without JavaScript rendering on a site that needs it. The crawler returns near-empty pages, the auditor concludes the content is thin, and every recommendation that follows is built on a false reading. The setting has to be switched on deliberately, and the crawl then takes hours rather than minutes, which is why it gets skipped.
A drop in impressions gets reported as a disaster. Search Console impressions can fall by half while clicks hold steady and average position appears to improve — that pattern usually means something changed in how results are counted, not that the site collapsed. Any drop gets dated and matched against a known event before it is called a problem, and branded queries are filtered out before anything is presented as a trend.
See where the site stands before you brief anyone.
If the site is already live, start from what it scores rather than from a guess. The audit reports what it checked, what it found, and — the part most tools leave out — what it could not check, and why.
Questions people ask before they commit.
- Do I get a report, or do the problems actually get fixed?
- Both are available and they are priced differently. A report-only audit is the cheaper end of the range. An audit with implementation costs more than double, and it is the one worth buying, because a fix list nobody applies changes nothing. Whichever you choose, the scope says exactly which items we apply and which go to your developer.
- My tool says I have 300 issues. Will your report cover all of them?
- No. A crawler will flag three hundred things on almost any site and most of them are noise. Our job is ranking, not listing. If the finished document has more than about forty items in it, we have handed you tool output instead of doing the work.
- How long before traffic moves?
- In a sequence, not on a date. The fixes themselves are our work and land inside the scope. Everything after that is Google's timing — the pages have to be crawled again, the indexing decision has to be revisited, and only once pages are being kept can non-branded clicks move. Each stage waits on the one before it, so traffic stays flat for a stretch after the work is finished. That gap is normal, and we say so at the start, because owners who are not told read it as failure. Anyone quoting you a date is describing a sales process, not a search engine.
- What access do you need before starting?
- Google Search Console as a full user, GA4 as a viewer, and a CMS login with enough rights to change titles and add markup. Hosting or server access only if speed and redirects are in scope. Every property should sit in your own account with us added as a user, never the other way round.
- What if you find nothing wrong?
- That is a result worth having, and it happens on well-built sites. In that case the document says the foundation is sound, shows the evidence, and points the budget at content or links instead. We would rather tell you that than invent work.
- Will you guarantee a ranking once the fixes are in?
- No. We guarantee the deliverables — the crawl, the reconciliation, the fix list, the applied fixes and the before-and-after evidence. Positions and traffic are goals we work towards, because the algorithm deciding them is not ours to control.
Often taken together.
Start with the brief, not the invoice.
Send what you are trying to achieve. You get a written scope, a price and a date — or an honest “this is not the right service for that”.
Talk about Technical SEO audit All SEO & Organic Growth services