[INSERT CASE STUDY 1]An audit client: site size, the highest-impact finding, what changed after implementation, and how it was verified.
A deliverable, not a retainer
Technical SEO Audit Service
A fixed-scope audit that ends with a document your developers can actually work from, in about fifteen working days.
[INSERT TRUST BAR]Client logos, years in operation, or a verified results figure.
Most audits are a tool export with a logo on the front
The common deliverable is two hundred pages generated by a crawler, sorted by the tool's own severity scoring, listing every missing alt attribute alongside the one redirect chain that is actually costing money. It is technically accurate and practically unusable, and it usually ends up unread in a shared drive.
The test of an audit is not how much it found. It is whether a developer can pick it up, understand why each item matters, reproduce the problem, fix it, and know when it is done. Almost nothing sold as an audit passes that test, which is why so many of them are bought and never actioned.
What you actually receive
A defined deliverable with a defined turnaround, not a month of unspecified work.
01
A prioritised issue register
Every finding ranked by likely revenue impact against effort to fix, not by a tool's red-amber-green. The first five items are the ones worth doing this month, and we say why in plain language.
02
Reproduction steps for each issue
The URL, the request, what happens and what should happen. A developer should never have to guess what you meant, and should never have to re-derive the problem from scratch.
03
Acceptance criteria
How to tell the fix worked. This is the part almost every audit omits, and it is why fixes get marked done without being done.
04
Crawl, index and rendering analysis
What can be reached, what is indexed, what is being spent on pages that should not exist, and whether your content survives JavaScript rendering. Crawl budget waste on large sites is routinely the biggest single finding.
05
Core Web Vitals with named causes
Field data where available, and the specific resource or layout cause behind each number, rather than a score and a recommendation to be faster.
06
Architecture, internal linking and schema
How authority moves through the site, which important pages are stranded, and whether structured data is valid and matches the visible content.
07
A working session with your developers
We walk the register with the people who will implement it and answer questions live. Handing over a document and leaving is how audits die.
How the audit runs
- 01 Scope and access Site size, platform, and read access to Search Console and analytics. We agree the page count the fee is based on before starting. Day 1-2
- 02 Crawl and data collection Full crawl, log files where you can supply them, index coverage, field performance data and rendering checks. Day 3-6
- 03 Analysis and prioritisation The slow part, and the part that is actually worth paying for. Findings are triaged by impact and effort, and anything we cannot justify commercially is cut rather than padded in. Day 7-12
- 04 Delivery and walkthrough The register, the summary for whoever signs off, and a live session with your developers. Day 13-15
- 05 Verification, if you want it After you implement, we re-test against the acceptance criteria and confirm what actually landed. Priced separately and entirely optional. On request
Results, with the working shown
Every number here comes with the client name, the timeframe and the method. If we cannot show you how it was measured, we do not publish it.
[INSERT CASE STUDY 2]An audit client: site size, the highest-impact finding, what changed after implementation, and how it was verified.
How the audit is priced
This is a fixed-scope deliverable with a fixed turnaround, so the quote is firm rather than an estimate that drifts.
01
Number of URLs
Crawling and analysing five hundred pages and five hundred thousand are different jobs. This is the main driver and we agree the count up front.
02
Platform complexity
A standard WordPress site is quicker to assess than a headless build, a multi-store setup, or anything with heavy client-side rendering.
03
International and multi-site scope
Multiple country versions or several domains mean hreflang validation and cross-site analysis on top of the base audit.
04
Log file access
Where you can supply server logs, the analysis is materially better. It also adds work. Optional, and worth it on large sites.
05
Whether you want verification
The post-implementation re-test is a separate, smaller piece of work.
What you are committing to
Fixed fee, agreed before start
About fifteen working days
Developer walkthrough included
One-off, no retainer required
There is no obligation to retain us afterwards. Plenty of clients take the register to their own developers and we do not hear from them again, which is a legitimate outcome and how the deliverable is designed.
Questions buyers actually ask
It is a fixed fee agreed before we start, driven mainly by how many URLs are in scope and how complex the platform is. We quote it on a short call once we know the site size, and the quote does not move afterwards unless the scope does.
About fifteen working days from access being granted for a typical site. Very large or heavily international sites take longer, and we will say so when quoting rather than discovering it halfway through.
The audit is a diagnosis. Most clients hand it to their own developers, which is what it is built for. If you want us to implement, that is a separate conversation and a separate engagement, and we would rather you chose that after seeing the audit than as a condition of buying one.
This is a one-off product with a fixed scope, a fixed price and an end date. The technical SEO service is an ongoing engagement where we monitor, implement and maintain over time. Different moment, different buyer. Many clients start here and never need the other.
Read access to Google Search Console and your analytics, and ideally server log files. We can produce a useful audit without logs, but on a large site they are where the crawl budget findings come from.
Sometimes. If the cause is technical, an audit will usually surface it. If the cause was an algorithm update, a competitor improving, or seasonality, a technical audit will not find it because it is not there. We will tell you which situation you are in rather than producing findings to justify the fee.
Yes, and pre-launch is the cheapest time to find these problems. A staging audit before a migration is one of the highest-return things you can buy in this discipline, because the alternative is finding out in production.
An audit against a tool export
What you are comparing
A typical SEO audit
MyInscribe
What it is
A crawler export, reformatted
A triaged register with reasoning
Prioritisation
The tool's severity score
Revenue impact against effort
Usable by a developer
Needs translating first
Reproduction steps and acceptance criteria
Handover
Emailed as a PDF
Walked through live with your team
What happens next
A retainer pitch
Yours to implement however you like
Get the audit scoped
Tell us the site and roughly how many pages it has, and we will come back with a fixed fee and a delivery date. No retainer, no obligation afterwards.
hello@myinscribe.com
· replies within a working day