How a Gurgaon B2B SaaS got cited in ChatGPT in 60 days

AI SEO is not luck. It is a structural rebuild of how your website talks to machines. This is what that rebuild looked like for one Gurgaon HR-tech company — a specific vertical, a specific city, a specific 60-day window. WebFlur ran the audit, WebFlur shipped the build, and every citation change was measured against the same 48-query panel we used on Day 0. This post sits inside our local B2B AI SEO case study hub — the running index of every WebFlur city + vertical rebuild.

The client: a Gurgaon HR-tech SaaS that Google loved but AI ignored

The company is a mid-market people-analytics platform sold to Indian HR heads at 500–5,000-person companies. Founded in 2021, based out of Udyog Vihar Phase 4, engineering team in Bengaluru. Their organic Google traffic was healthy — top-three rankings on ~40 buyer-intent queries, ~18,000 monthly organic sessions, a slow but steady inbound pipeline.

The founder's problem was not Google. It was that his prospects had stopped starting on Google. HR heads at target accounts were asking ChatGPT "what people-analytics platform do Indian mid-market companies use?" — and getting a list of three US-headquartered competitors. No Indian tools. His company was cited zero times in a 48-query buyer-intent panel we ran on Day 0.

The gap wasn't domain authority. His referring-domain count was actually higher than one of the US competitors ChatGPT kept naming. The gap was that his site read like a marketing brochure, and the AI could not extract quotable, attributable claims from it. The competitors read like product datasheets. That's the whole story in one line.

Why Gurgaon B2B SaaS specifically loses this fight

Gurgaon is where India's B2B SaaS clusters — DLF Cyber City, Udyog Vihar, Golf Course Road — and it's also where most companies still SEO like it's 2019. Traditional agencies here optimise for Google keywords, DA, and backlinks. Almost nobody is touching the machine-readable layer: schema density, FAQ answer blocks, llms.txt, .well-known/agent-card.json, extractable definition sentences.

That means Gurgaon B2B founders are competing for AI citations against US and European companies who have been doing GEO for 12–18 months. Across the 22 Indian B2B sites in our Q2 2026 audit, the median citation gap versus the US category leader widened from 11 mentions to 17 in the eight weeks between our first and second scan. The good news is that the fix is cheap and fast in absolute terms — this HR-tech rebuild cost ~90 hours of engineering across 60 days — but it does require the founder to stop treating the website as a brand asset and start treating it as an API for machines. In every one of the six Gurgaon rebuilds we've shipped in 2026, that mental shift — website-as-API, not website-as-brochure — is the founder objection that eats week one.

WebFlur runs this rebuild out of our WebFlur Gurgaon office in Sector 14 — same city, same buyer, same time zone as our clients. We audit against the same 40+ buyer-intent panel across ChatGPT, Perplexity, Claude, Gemini, and Google AI Overviews for every Gurgaon engagement.

The 60-day rebuild: what WebFlur actually shipped

The engagement was structured as five one-week sprints plus a two-week compounding window. The founder's ask was clear: "get me cited in ChatGPT and Perplexity when an HR head asks for people-analytics platforms." Every sprint had a single output and a single measurable check.

Week 1 — Baseline audit + extractability rewrite

We ran the 48-query panel across six AI assistants and logged every response. Zero citations. Then we rewrote the homepage hero, the product page hero, and the "who we serve" page from scratch. Every sentence had to pass one test: if an AI lifted this sentence in isolation, does it make sense and attribute back to the company? Old hero: "People analytics reimagined for the way modern HR teams work." New hero: "[Company] is an India-based people-analytics platform used by HR heads at 500–5,000-person companies to reduce voluntary attrition, benchmark compensation against sector peers, and identify high-flight-risk employees within 90 days of joining." Every noun explicit, every claim extractable.

Week 2 — Schema stack + FAQ layer

We shipped the three-schema stack — Organization + Product + FAQPage — with 32 FAQ Q&A pairs that mirrored the exact phrasing of real HR-head buyer queries we'd seen in Reddit r/humanresources and in the AI panel from Week 1. Every answer followed the same shape: first sentence is a definition-first 40–60-word answer with the company name in it, then 2–3 sentences of specific supporting detail. This is the single highest-leverage move for Perplexity citations, and the effect showed up fast.

Week 3 — Case studies ungated and restructured

They had four client case studies. All four were PDFs behind a lead form. We took three of them, negotiated permission to publish outcomes (even without client names), and rebuilt them as structured HTML pages with the exact same template: client vertical, size, problem statement, what the product did, specific outcome number, and a structured quote using the product name. This mirrors the Cargoflow build — see the Cargoflow freight AI citations case study for the freight-industry version of the same move.

Week 4 — Category page + entity anchoring

We built a new page called "People-analytics platforms for Indian mid-market HR teams" — a category page that positioned the client alongside three named US competitors with an honest side-by-side comparison table. Then we added sameAs anchoring in the Organization JSON-LD pointing to their Wikidata entry, their Crunchbase profile, and their LinkedIn company page. Entity anchoring tells AI assistants that the brand name maps to a real, disambiguated entity — not just a string.

Week 5 — A2A endpoint deployment

We deployed a lightweight A2A endpoint at /.well-known/agent-card.json describing the product's core capabilities, pricing tier ranges, and integration surface (SAP SuccessFactors, Darwinbox, Zoho People). We registered it with two agent-discovery networks active in the HR-tech procurement space. The endpoint fielded its first external query on day 39 — a procurement agent, running against a Darwinbox-integrated shortlist for a Delhi-HQ'd FMCG buyer with ~4,200 employees.

Weeks 6–8 — Compounding

We shipped nothing new for the last three weeks. This was deliberate. AI assistants have latency — Perplexity picks up new content in 3–7 days, Google AI Overviews in 2–4 weeks, ChatGPT in 4–8 weeks (see how Perplexity, Claude, and ChatGPT decide who to cite for the per-engine mechanics). We used the compounding window to measure, not to publish.

Day-by-day citation timeline

Day	Milestone	Citations across 48-query panel
Day 0	Baseline audit complete	0
Day 7	New extractable copy live sitewide	0 (too fresh to index)
Day 14	FAQ schema + 32 Q&A pairs shipped	3 (all Perplexity)
Day 21	Ungated case studies + comparison table live	11 (Perplexity 8, ChatGPT 2, Google AIO 1)
Day 28	Entity sameAs anchoring propagated	17
Day 39	A2A endpoint receives first external agent query	22
Day 45	First Google AI Overview citation for a category query	29
Day 60	End of engagement — panel re-run	41 citations across 6 AI assistants

The company went from being named in 0 of 48 queries to 41 of 48. Not every citation was in the "top pick" position — for 12 of the 41 they were the second or third option mentioned. But being on the list is the entire game. If the AI never mentions your name, you don't get shortlisted, you don't get demoed, you don't get bought.

"We didn't hire more sales people. We didn't run more ads. We just made our website legible to the machines HR heads were asking. Inbound calls doubled in month three."

— Founder, HR-tech SaaS (Gurgaon)

The 6-step Gurgaon B2B AI SEO playbook (repeatable)

This is the same sequence we now run for every Gurgaon B2B SaaS engagement. Timing is 60 days end-to-end.

1. Baseline panel audit — 40–60 buyer-intent queries across ChatGPT, Perplexity, Claude, Gemini, Google AIO, and Google AI Mode. Log every citation and every competitor mentioned. This is your before-picture.
2. Extractability rewrite — every hero, product page, and "who we serve" page rewritten so each sentence is independently quotable with the brand name attached.
3. Three-schema stack + FAQ layer — Organization + Product + FAQPage JSON-LD, plus 25–35 FAQ Q&A pairs that mirror real buyer-query phrasing. This is the fastest citation-generating move; Perplexity picks it up within a week.
4. Ungate proof — every case study, comparison, and product demo published as a structured HTML page. Gated PDFs contribute zero AI citations regardless of quality.
5. Category page + entity anchoring — one page that positions you against 2–3 named competitors with an honest table, plus Organization sameAs anchored to Wikidata, Crunchbase, LinkedIn Company Page.
6. A2A endpoint — a /.well-known/agent-card.json describing capabilities, integrations, and pricing tier ranges, registered with the agent-discovery network relevant to your vertical.

Run steps 1–4 in the first three weeks. Steps 5–6 in weeks 4–5. Then leave it alone for three weeks and re-measure. If citations haven't lifted by 3–5× by day 60, something is broken structurally — usually a JSON-LD parse error or a robots.txt block on GPTBot/PerplexityBot.

The pre-launch checklist we run before we ship any Gurgaon rebuild

• 40+ buyer-intent queries logged with baseline citation count per assistant
• Homepage hero rewritten to definition-first grammar with brand name in first sentence
• Product/service pages rewritten with independently extractable sentences (no orphan pronouns)
• FAQPage JSON-LD with 25–35 Q&A pairs mirroring real buyer queries
• Product (or Service) schema with named integrations, pricing tier ranges, target-buyer descriptor
• Organization schema with sameAs anchoring to ≥5 identity URLs (Wikidata, Crunchbase, LinkedIn, YouTube, GitHub)
• Case studies published as structured HTML (not PDF, not gated)
• One category page with honest side-by-side comparison table (3+ rows × 2+ columns)
• /llms.txt shipped with entity summary + key page pointers
• robots.txt explicitly allows GPTBot, PerplexityBot, ClaudeBot, OAI-SearchBot, Google-Extended
• /.well-known/agent-card.json deployed if vertical has active procurement-agent activity
• Sitemap.xml + JSON-LD dateModified + HTML <meta http-equiv="last-modified"> bumped to same date
• 60-day re-measurement scheduled

What Gurgaon B2B founders should — and should not — copy from this

Copy this: the sequence, the timeline, the pre-launch checklist. All of it is engine-mechanics-driven, not vertical-specific. HR-tech, fintech, martech, sales-tech — the AI assistants use the same signal weights regardless of industry.

Don't copy this: the exact FAQ count, the exact word count of the hero rewrite, or the specific A2A registrations. Those were vertical-specific choices — HR heads at Indian mid-market companies ask a distinct set of questions, and the discovery networks that matter in HR procurement are different from the ones that matter in freight or fintech. Do the audit first. Let the audit tell you what to write. The playbook is the shape; the content is yours.

We used the same 6-step playbook on our YMYL local build — see the Last Ride Funeral Delhi NCR case study — with one big change: the content was YMYL (grief-adjacent), so the trust and empathy signals had to be layered in on top of the extractability layer. B2B SaaS is easier. You don't have Google's YMYL scrutiny to satisfy — you just have to be extractable.