Diagnostic · Vadodara
SEO audit
A paid diagnostic with evidence, severity and acceptance criteria — not a 200-point export, and not a free turnaround promise.
Fit
Who this is for
A fit
- Teams who need to know what is actually wrong before they hire a retainer or a rebuild.
- Sites with stalled or declining organic that nobody can explain in a sentence they would defend.
- Stakeholders who need a document developers and content can execute, not a sales PDF.
Not a fit
- A free audit in 24 hours. I do not offer that, and a document produced on that timetable is not an audit.
- A Lighthouse or crawler dump restated as a 200-point checklist.
- Anyone who has already decided on a 12-month retainer and wants the audit only as theatre to justify it.
Problems
What I diagnose
No shared picture of the site. Search Console, analytics, the CMS and the live HTML often tell three different stories. An audit starts by reconciling those, or every later recommendation is an argument about whose export is true.
Findings without a decision. A list of 80 issues is not a diagnosis. If nothing is ranked by impact, effort and confidence, the team will pick the familiar items and leave the ones that would have mattered.
Fixes nobody can accept as done. “Improve internal linking” is not a task. Without an acceptance check — which templates, which anchors, what must appear in the rendered HTML — the finding comes back next quarter unchanged.
Scope that pretends to be exhaustive. No honest audit covers every URL and every competitor. The useful document says what was examined, at what depth, and what was explicitly left out.
Delivered
What you actually get
Scoped diagnostic document
A written audit against an agreed crawl depth, template set and commercial URL list — not an unbounded “whole internet of your site” promise.
Prioritised backlog
Each finding carries severity, effort, confidence and a suggested owner. You get a sequence, not a guilt pile.
Acceptance criteria per High finding
What “fixed” looks like in HTML, headers, Search Console or the live template, so QA is not a vibe.
Walkthrough
A conversation through the document. The file is not the whole delivery; unexplained PDFs are how audits die in inboxes.
Explicit exclusions
What I did not look at, and why. If you need those areas next, that is a follow-on scope, not a surprise.
The walkthrough is part of the deliverable. A PDF without a conversation is a dump.
Sample
Deliverable sample outline
This is the shape of the document, not a fictional filled example. Your audit follows this outline; the contents are yours.
Scope and access
Properties used (Search Console, analytics if granted, crawl), environments, date of crawl, and URL lists in scope.
How the site makes money
The commercial paths that have to work in search. Recommendations are judged against these, not against vanity queries.
Crawl, render and index
Where the chain breaks, with example URLs. Includes robots, sitemaps, status codes, canonicals and rendering where they affect the in-scope templates.
Architecture and templates
URL design, duplication, internal links, and template-level indexation rules. Grouped by system so developers can estimate.
On-page structure on commercial URLs
Intent match, heading structure, and content gaps on the URLs that should win demand — not a copy rewrite of the whole site.
SERP notes, only where they change priority
Competitor and results-page observations that alter what to do first. Not a gallery of screenshots for their own sake.
Backlog and 30 / 60 / 90 sequence
A suggested order. Dates are planning aids, not promises that Google will move on a calendar.
Exclusions and next decisions
What was out of scope, and whether the honest next engagement is technical implementation, consulting, or something else.
Done when
Acceptance criteria
The audit is complete when all of the following are true. If a vendor cannot meet these, it is not this product.
Every High finding includes at least one affected URL or template, a piece of evidence (crawl row, header, screenshot of the live HTML, or Search Console excerpt), and a proposed change.
Every recommended High fix includes an acceptance check that a third party could verify without me in the room.
Exclusions are listed in the document. The audit does not claim to have covered what it did not.
A walkthrough is scheduled as part of delivery. Sending a file is not sufficient on its own.
The document contains no ranking guarantee, no traffic forecast dressed as a fact, and no “free extra” used to upsell a retainer you did not ask for.
Method
How the work runs
Scope
Agree what is in, what is out, which commercial URLs matter, and what access I will have. The fee follows this, not a menu of page counts.
Evidence
Crawl, Search Console, rendered HTML, and the live templates. I collect before I opine.
Severity
Rank by impact, effort and confidence. Uncertainty is labelled as uncertainty.
Brief
Write the document in the outline above, with acceptance checks on the High items.
Walkthrough
Go through it with the people who will ship. Then you decide whether implementation, consulting, or a pause is the honest next step.
Proof
Examples in progress
No redacted audit excerpt is on this site yet. Publishing one requires a client who agrees to show the shape of the findings without pretending the numbers are yours.
When an example lands, it will show the outline above filled in at a depth you can judge — including the exclusions — not a highlight reel of “issues found”.
Until then, judge the product by this page: the outline, the acceptance criteria, and a conversation on your site.
Questions
Common questions
Is there a free audit in 24 hours?
No. A useful diagnostic needs access, a crawl, and time to write acceptance criteria. Anything advertised as free and overnight is a lead magnet, not this product. I will look at a URL in a consultation and tell you whether an audit is even the right next step.
How long does an audit take?
It depends on the size of the site, the stack, and how quickly access arrives. I will give you a range when we scope — not a universal number. Large catalogues and JavaScript-heavy templates take longer because the evidence takes longer to collect.
What do I receive as a file?
A written document following the outline on this page, plus the walkthrough. Format is whatever your team can actually use (usually a structured doc, not a 200-slide deck). Tickets can be copied out of the High findings.
What happens after the audit?
You are not signed up to a retainer by buying the diagnostic. The document should make the next decision obvious: a technical project, a consulting cadence, implementation help, or no SEO engagement if search is the wrong lever.
Request an audit against a real scope
Send the URL, what you think is wrong, and whether developers can ship. I will tell you if this diagnostic is the right product, what access I need, and how I would bound the work.