The work, not the pitch
Three case studies with full write-ups, covering AI-search visibility, a core update recovery, and a ranking step change, then four further results with headline figures only. Every case-study number names its source and window.
What results has Khadija Zaman delivered?
At Wellows, Khadija Zaman took LLM referral sessions from 176 a month to roughly 9× in eight months with no paid spend and grew Search Console impressions from 680K to 3.78M (last three months against the previous three). For a confidential publisher she recovered average position from 32 to 8.2 after a core update, and for a separate confidential client she grew LLM referral traffic 22× over 12 months (GA4).
Case studies
AI visibility from near-zero: 9× LLM traffic in 8 months on $0 paid spend
Wellows had Google traffic but a small citation footprint inside AI answers: 176 LLM referral sessions a month. I built measurable AI-search presence (an entity model from Google patent research, retrieval-ready content, and structured signals LLMs treat as authoritative) with zero paid spend. From that baseline, LLM referral sessions reached roughly 9× over the eight months the case study covers.
Read the Wellows AI-visibility case study →
- AEO framework. Koray Tuğberk GÜBÜR's logic + Google's query fan-out patent for LLM retrieval.
- Citation experiments. Grounded vs. non-grounded tests tracking explicit and implicit AI visibility.
- Tool- & community-led. Three AI tools as LLM entry points; AEO across Reddit, Quora, G2; n8n + GA4 reporting.
Losing 70% of Organic Clicks, Then Recovering to Position 8.2
A high-volume publisher lost 70% of its organic clicks in four months. Five workstreams run together, not sequenced across separate vendors, took average position from 32 back to 8.2.
Stuck Near Position 55 for Two Months, Into the 20s in Days
Flat around position 55 from July into September. It was not declining, which is its own problem. A mid-September step change moved the property into the 20s within days, and it held there for eleven weeks.
Four more results, headline figures only
These four have no full write-up on this site. The figures are what I tracked in GA4 and Search Console while I owned the work; ask me for the source data in a conversation.
LLM referral growth for a confidential client
A separate engagement from the Wellows study above, measured in GA4 over 12 months. The client and the baseline are not published, so treat this as a headline figure, not a verified one.
Three SEO tools built at Wellows, zero paid
Query Fan-Out Generator, LLM Query Builder and AI Humanizer, built as LLM entry points. The counts are reconciled against Wellows’ live counter on the tools page. The LLM Query Builder’s Product Hunt launch post by Masab Gadit credits me by name.
Topic cluster architecture for an affiliate site
Sessions had plateaued at 8K a month despite regular publishing. Intent-mapped clusters, pillars around commercial queries and deliberate internal linking, with no technical overhaul. The method is written up in Topic Cluster Architecture That Actually Scales Organic Traffic.
KIVA launch: #1 U.S. rating on All About AI, all organic
Positioning, launch content, SEO-led distribution and influencer partnerships on zero paid budget.
How an AI-search program runs, stage by stage
Each stage depends on the one before it, and each ends on a condition you can check. The baseline at the start is what the results at the end are measured against.
01Baseline
- The work
- Set up or audit Search Console, GA4 and Bing Webmaster Tools, build an LLM referral segment in GA4, and record which AI engines cite or mention the brand today.
- You get
- A dated baseline per engine: LLM sessions, impressions, average position, and a BERAP read of what models recall about the brand.
- Why it's here
- Without a before, nobody can tell whether the work moved anything.
- Done when
- Every later number has a source and a window.
02Access
- The work
- Check that search and AI crawlers can fetch, render and index the pages that matter: robots.txt and CDN rules for OAI-SearchBot, Claude-SearchBot and PerplexityBot, key copy in the raw HTML, canonicals, noindex tags and redirects.
- You get
- Findings ranked P0 to P2 against my LLM technical SEO checklist, where P0 blocks indexing or AI access. This is R2A's Layer 1, Eligibility.
- Why it's here
- There's no point fixing schema on a page an AI crawler can't reach.
- Done when
- No P0 left open.
03Entities, queries and architecture
- The work
- Pin the central entity, run query fan-out on the core topics, then group pages into clusters with internal links that point authority where it's needed.
- You get
- An entity and attribute list, fan-out query sets from the generator, and a cluster map with missing pages marked.
- Why it's here
- Retrieval runs on sub-queries, and a site gets cited across a topic only when it covers the topic. How I structure clusters.
- Done when
- Every key page has a cluster and a job.
04Retrieval-ready pages
- The work
- Score key pages with R2A, rewrite chunks so each stands on its own, put direct answers in the raw HTML, and check that schema matches the visible copy.
- You get
- R2A scores per page, with an evidence grade on every fix.
- Why it's here
- Engines quote chunks, so each one has to make sense lifted out of the page.
- Done when
- Each new or changed URL clears a publish gate: final URL, self-canonical, in the sitemap, no staging noindex.
05Distribution and mentions
- The work
- Place answers where models read, such as Reddit, Quora and G2, earn mentions on sites the models already ingest, and ship free tools as LLM entry points.
- You get
- A placement list per engine, and the mentions earned against it.
- Why it's here
- An engine names a brand more readily when other sources already do.
- Done when
- The brand is named beyond its own domain.
06Automation and re-measurement
- The work
- Wire GA4 and Search Console into Python, BigQuery and n8n pipelines that segment LLM referrals, and re-run the per-engine citation check against the baseline.
- You get
- Auditable reports that arrive without anyone exporting a spreadsheet.
- Why it's here
- Manual reporting is the first thing to stop when a team gets busy.
- Done when
- Results compared with the stage 01 baseline, engine by engine.
Search Engine Land picked the tool I built at Wellows, and PipeRocket Digital had me on The Growth Show
After a 94-day query fan-out experiment we released the method as a free tool; Search Engine Land later used it in its guide to topic clusters for AI search. The article credits Wellows, not me by name; the public record of my hand in it is the COO’s LinkedIn post below.
“There are multiple query fan-out tools. For this tutorial, we’ll use Wellows.”Read Search Engine Land’s topic clusters for AI search guide →
Also listed in Search Engine Land’s query fan-out tools roundup →
- 923 → 2.12K clicks
- 62.9K → 626K impressions
Google Search Console, the fan-out experiment pages only, 11 Aug–12 Nov 2025 against the prior 94 days. A different scope from the site-wide Wellows figures in the case study above.
“How to Make Your B2B Brand Citable by AI, Not Just Rankable on Google”Watch the episode on YouTube →
PipeRocket’s announcement post → · post-show recap →
Need AI search visibility, or hiring for it?
Client project or in-house role, tell me what you're building. I reply within 48 hours with a direct read on your situation, not a pitch.

