Live SEO Case Study: This Site, Measured in Public
Client results sit under NDA, so a buyer has to take them on trust. This one doesn’t need trust. It is a live SEO case study on suroliamarketing.com: the real starting numbers on 27 September 2026, every change I made, and dated updates at 30, 60 and 90 days, good or bad.
Why I run my own site in public
Every consultant says their results are real. A hospital buyer can’t check that, because client names and dashboards sit under NDA. I asked ChatGPT and Perplexity why someone should not hire me, and the first answer was exactly that: the numbers can’t be verified from the outside.
So this page is the proof you can check. My own site is a healthcare SEO business competing for healthcare SEO searches, and I publish its numbers from the day I rebuilt it. You can compare the numbers here with the site itself, with Google, and with what AI tools say about me when you ask them.
Day 0: where the site started
These are the numbers on 27 September 2026, the day the rebuilt site went live. Nothing is rounded up.
| Measure | Day 0 | Source and period |
|---|---|---|
| Google clicks | 18 | Search Console, 4 Feb to 24 Sep 2026 |
| Google impressions | 714 | Search Console, same period |
| Average position | 14 | Search Console, same period |
| Click-through rate | 2.5% | Search Console, same period |
| Pages indexed by Google | 7 (6 not indexed) | Search Console page indexing |
| Bing impressions | 20, with 0 clicks | Bing Webmaster Tools, 13 Jul to 24 Sep 2026 |
| Named by ChatGPT in buyer questions | 0 of 7 | Temporary chat, personalisation off, 27 Sep 2026 |
| Server response time | 1.5 to 20 seconds | My own checks before the rebuild |
The search data told its own story. The queries with the most impressions were for orthopedic SEO, which came from one old page, and a company name that has nothing to do with me. Healthcare buyers searching for a consultant were not finding the site at all.
What an AI audit said about me
Before fixing anything I asked ChatGPT, in a temporary chat with personalisation off, to act as a US hospital group and list every reason not to hire me. It was useful, and some of it stung. This is what it found and what I did.
| Red flag it raised | What I did |
|---|---|
| One certificate showed another certificate’s credential ID | Corrected it from the certificate itself: the Azure Administrator ID is 860C0E2B361B7FB3 |
| Two Microsoft Azure certificates expired in August 2026 but were shown as current | Chose not to renew them. They now read as training earned in 2025, and they are out of my structured data |
| The orthopedic case study was a representative model but read as a client result | Relabelled it as a sample engagement plan everywhere it appears |
| Results can’t be verified from the outside | Published this live case study, and references are available on a call |
| A 2025 article discussed grey-hat tactics without a clear stance | Added a plain statement: I describe these tactics so clients can spot them, and I don’t use them |
| Old copies of the site still say six years and quote retired figures | Removed them from the live site and pinged Bing and Google to recrawl |
None of these were hard to fix. All of them were costing trust before anyone booked a call. Most healthcare sites I audit have the same kind of problem: small, visible inconsistencies that a careful buyer, or an AI model reading on their behalf, notices first.
What I changed, and why
- Speed. Page caching and a clean server setup took the server response from 1.5 to 20 seconds to around 0.4 seconds on a cached page. Slow pages lose patients before they read a word.
- One version of every page. All traffic now goes to one secure address, and every page names itself as the original with a canonical tag.
- A clean index. The sitemap went from 70 URLs to 51. Tag, category and author archives were thin pages competing with real ones, so they are now kept out of the index.
- Structure. Separate pages for each sector and each service, each owning one search phrase, linked the way a buyer moves from problem to proof to call.
- Machine-readable facts. One connected schema graph for the business, the person and every page, plus an llms.txt file that tells AI tools what each page is for.
- Content with sources. Fourteen guides on the questions healthcare buyers actually ask, each regulatory claim linked to its primary source, and one piece of original research on 30 lab websites.
- Discovery. Sitemap submitted to Google, the six most important pages sent for indexing, and all 51 pages sent to Bing through IndexNow.
- Email you can trust. SPF, DKIM and a new DMARC record, so replies to enquiries reach an inbox rather than a spam folder.
How I will report it
Every update uses the same measures and the same sources, so the numbers can be compared. If something goes down, it stays on the page with the reason.
| Date | Report |
|---|---|
| 27 September 2026 | Day 0 baseline (this page) |
| 27 October 2026 | Day 30: indexing, impressions, first non-branded queries |
| 26 November 2026 | Day 60: clicks, average position for target phrases, AI answers |
| 26 December 2026 | Day 90: all of the above, plus enquiries through the contact form |
What I won’t do is promise rankings. A new site in a competitive niche takes months, and my site is a consultancy, not a clinic. The point of this page is to show you the method and the honesty of the reporting, which is exactly what you would get as a client.
What this means for your practice
The same audit works on any healthcare site: pull the real baseline, ask AI tools the hard questions a buyer or patient would ask, fix what they find, and report on fixed dates. If you want to see how your site looks through that lens, book a free strategy call and I will run the same checks before we speak.
Questions I get asked
Why not just show client results?
Client names and dashboards are confidential. I share them on a call, under NDA. This page is the part anyone can check without an NDA.
Will you publish the numbers if they go down?
Yes. The measures and sources stay the same at every update, and any fall stays on the page with the reason.
How did you ask ChatGPT without it knowing it was me?
I used a temporary chat with memory and personalisation turned off, and asked as a US hospital group would.
Sources
- Google Search Console Help: Performance report
- IndexNow protocol
- The /llms.txt file proposal, llmstxt.org
Written by Bhagyashree Surolia and checked against the sources above on the date shown. Read my editorial policy.
Want a second pair of eyes on your site?
A free 30-minute strategy call. I review your search footprint, local visibility and AI search presence before we speak, and tell you plainly what is achievable.
- You speak with me directly, always
- Your data stays private, never put into AI tools
- If SEO isn’t your bottleneck, I’ll say so