SEO case studies with real Semrush and Search Console evidence
Every study below comes from a site we can inspect: our own. Semrush and Google Search Console are the referees. We publish the before, the after, the numbers and the limits — not invented client logos or a screenshot of a traffic line.
Semrush Site AuditGoogle Search ConsoleUS and IndiaUpdated 31 October 2026
Flagship case study
Semrush case study: 641 errors to 1 in five fix passes.
We pointed Semrush Site Audit at guidedsuccessacademy.com, fixed what mattered over five passes, and published the before and after. Same site. Same campaign. The remaining 491 warnings are not hidden.


The library
All SEO case studies
Search visibility, sitewide audits, technical passes and local market studies. Each card states the window and the evidence boundary on the page. The index is generated from the case-study series taxonomy, so new studies appear here automatically.
Case-study series
US evidence
Dated US case studies from GSA’s own properties and US local search. Every study states its window, sample and limits.
Open the series hubGSC Audit: Reading Your Own Search Console Data
A GSC audit of our own Search Console data: 15,668 impressions, 42 clicks and the one bottleneck behind them. See the method, then run…
Read the studyContent Leak Audit: Impressions Without Clicks
Content leak audit on our own site: pages ranking on page 2 with impressions but no clicks — and the exact fixes. See the…
Read the studyGSA Search Console Then and Now: An Honest Report
An honest GSA Search Console case study comparing impressions, clicks, CTR, and position while accounting for domain and architecture changes.
Read the studyGSA Sitewide SEO Audit: A Clean, Dated Baseline
A GSA sitewide SEO audit case study covering 179 URLs, rendered-page checks, critical findings, internal links, pages that may be hard to discover, and…
Read the studyGear Sitewide SEO Audit: Clean Technical Evidence
A Gear sitewide SEO case study covering 19 published URLs, critical technical checks, internal links, pages that may be hard to discover, and GSC…
Read the studyPhoenix Local SEO Market Snapshot: Demand Is Not Selection
A dated Phoenix local SEO snapshot across plumbers, pest control and movers: customer demand, operator intent and local choice are different business questions.
Read the studyCase-study series
India evidence
Dated India-market evidence from public profiles, storefront performance and technical audits. Diagnosis is separated from measured outcomes.
Open the series hubDelhi HVAC Google Business Profile Snapshot: What Five Listings Show
An anonymised snapshot of five public Delhi HVAC Google Business Profiles: what profile completeness and website alignment can and cannot tell a ready customer.
Read the studySOVOR Shopify Performance and Core Web Vitals Case Study
A dated Shopify Core Web Vitals case study for sovor.store: desktop reached 97-100 on sampled URLs, while mobile LCP on product and COD pages…
Read the studySOVOR Sitewide SEO Audit: Evidence, Remediation, and Limits
A dated sitewide audit of sovor.store: 160 public surfaces, 47 initial failures reduced to zero, and one commercial page Google still returns as unknown.
Read the studyBy evidence type
Search Console, site audit and local SEO case studies
Google Search Console case studies
Impressions, clicks, CTR and position, read as a selection problem rather than a traffic trophy. See the GSC audit and the then-and-now study.
Semrush and site audit case studies
What a benchmark audit actually looks like before and after a fix pass. Start with the 641-to-1 Semrush study.
SEO audit case studies
What a dated sitewide audit looks like before the fix list, and what we separate from the warnings. Read the 176-URL sitewide audit.
How to read a GSA case study
The window
Every number has a date or a measurement window. If a study compares two periods, both periods are named.
The evidence
Search Console, Semrush or a live crawl. We show the source, not a designed dashboard that hides the raw view.
The limit
We say what the study cannot prove. A sitewide fix is not a controlled experiment, and a market snapshot is not a client result.
What we do not do: invent client logos, screenshot traffic charts, or promise rankings. The process guarantee is the product.
SEO case study questions
What is an SEO case study?
An SEO case study is a documented before-and-after record of a search problem, the work done and the measured result. A useful one names the window, the evidence source and the limit.
Are these client results?
Most are our own sites and our own data. We do not invent client logos or borrow someone else’s screenshot. Where a study is a market snapshot, we label it as a snapshot, not a client result.
Why do you publish your own weak numbers?
Because a case study that only shows wins is a sales page. Showing the real CTR, the page-2 rankings and the warnings we have not fixed is the only honest version.
Do you have India SEO case studies?
Yes. The India evidence library covers India-specific search and local work. The same rule applies: window, evidence and limit.
What is the Semrush case study?
We ran Semrush Site Audit on our own site. It found 641 errors. Five fix passes later it found 1 error, 0 broken pages and 94% site health. We left 491 warnings on the table on purpose.
Can I see the raw screenshots?
Yes. The Semrush case study shows the before and after screenshots. The Search Console studies link to the data window they use.
What is a Search Console case study?
A Search Console case study uses Google Search Console data — impressions, clicks, CTR and position — to show what changed for a site and what the data cannot prove.
What is a site audit case study?
A site audit case study documents a dated crawl: the errors, warnings and broken pages found, the fixes made and the result on the next scan.
Read the evidence in context
How to read a case study before you trust it
How to read an audit report
What a dated window, an evidence source and a stated limit look like in a real report.
Research and insights
Dated studies and market notes, with the source and the boundary stated.
Have a case study worth publishing?
We publish operator-level evidence, not guest-post filler. Pitch a guide.
How to use this hub with the cluster
This hub is the entry point for case studies; it is not the only page a reader needs. Move from the hub to the page that matches the market and the decision, then return to the hub when you need the broader view.
Keep the page, the market, the proof and the next action together. If one of those is missing, fix it before you add another URL. The cluster is easier to maintain when every page has one clear owner.
What this hub covers
A case study is useful when it shows the page, the date window, the observation, the limit and the next decision. This hub collects dated evidence without turning one result into a promise.
- Content Leak Audit: Impressions Without Clicks | GSA Growth explains the decision this page is built to support and the limit of the evidence.
- GSA Sitewide SEO Audit: A Clean, Dated Baseline explains the decision this page is built to support and the limit of the evidence.
- GSC Audit: Reading Your Own Search Console Data | GSA Growth explains the decision this page is built to support and the limit of the evidence.
- Semrush Site Audit: 641 Errors to 1 on Our Own Site explains the decision this page is built to support and the limit of the evidence.
- We Audited the 300 Most-Visited Websites (2026 Study) explains the decision this page is built to support and the limit of the evidence.
Who this is for
- A business owner choosing a page, a provider or a next action.
- A marketer who has to explain the evidence without overclaiming.
- A founder comparing a local, national or ecommerce decision.
- An operator who needs a dated check before spending more.
How to choose the next page
| Question | Start with | What it does not prove |
|---|---|---|
| Which page should own the query? | The page that answers the job, not the broadest page. | That one page will win every variation. |
| What proof can the business show? | A dated example, a real service area and a clear process. | That every buyer will trust the same proof. |
| What should be measured? | The page, the query, the date window and the next action. | That a movement was caused by one change. |
How to use this hub
- Name the reader. One owner, one market and one decision.
- Choose the page owner. One URL should answer the question.
- Check the proof. Show what the business can verify, not what it hopes.
- Set a review date. Compare the same page and window later.
What to check first
- Does the page name the service, the area and the next action?
- Can a buyer check the proof without a sales call?
- Does the profile, page and enquiry path agree?
- Is the page in the sitemap and reachable from the hub?
- Does the report separate observation, interpretation and unknown?
What this hub will not prove
It will not prove that a page will rank, that a provider is the best fit, or that a change will produce a lead. It can only make the decision and the evidence clearer. Public search data cannot see private enquiries, sales calls, margin or capacity.
Use this hub to choose the next inspection, then measure the same page and query after a fixed window. Do not treat a single result as a forecast.
Next useful step: read the dated 11 November 2026 self-audit for the method and limits, or use the Revenue-Leak Audit on your own property.
What a useful case study should let you check
A case study should show the baseline, the date window, the work completed and the limit. Ask what changed, what did not, and what the evidence cannot prove. A before-and-after screenshot without a method is a story, not a case study. Use the same questions on every entry in this hub.
Dated guidance. No ranking, traffic or revenue guarantee.