What this site covers, and what it does not yet
One central entity, AI search visibility, decomposed into entity and attribute pairs. The core is the commercial half a hiring manager judges; the outer section is the trust that makes the core checkable. Every node says whether a page exists. The unbuilt ones are the roadmap.
What is the central entity of khadijazaman.com?
The central entity of khadijazaman.com is AI search visibility: getting a brand found on Google and cited inside ChatGPT, Gemini, Perplexity and AI Overviews, run with SEO, content architecture and measurement as one system. The site covers 26 entity-attribute pairs, 19 of them with a page behind them, split 65% commercial core to 35% trust-building outer section.
Source context. Khadija Zaman, AI Search Manager at Wellows, publishing what she has measured, built and been wrong about, so a hiring manager or client can check the work. Definition. Getting a brand found on Google and cited inside ChatGPT, Gemini, Perplexity and AI Overviews, run with SEO, content architecture and measurement as one system.
Core: what the work produces
The commercial half. Each pair here is something a hiring manager or client is judging: a result with a source, a method that can be repeated, or a tool that exists.
AI search visibility
-
built
LLM referral growth, measured9× in 8 months from 176/month, GA4
- built
-
built
Query fan-out as the expansion modelFree explorer, plus the Wellows generator used by Search Engine Land
- built
-
not yet
Grounded vs non-grounded citation experiments, the methodDescribed inside the Wellows case study; needs its own write-up with the protocol
-
not yet
Distribution on the surfaces models read (Reddit, Quora, G2)Named in the case study; no page shows the placement method or its measurement
-
not yet
LLM referral segmentation in GA4, the setupWhich sources count, how the segment is built, how it is reported
SEO management
-
built
Core update recovery, five workstreams run togetherPosition 32 → 8.2, Search Console
-
built
AI Overview absorption, read from position vs CTRLabelled as an inference on the page
-
not yet
Technical SEO: crawl, indexation, schema, Core Web VitalsClaimed on the homepage; no page shows an audit or a fix
-
built
Internal linking, AI-assistedOpen-source Internal Link System; no case or post yet
Content architecture
- built
-
built
Ranking step change that heldPosition 55 → 20s, held 11 weeks
-
not yet
Semantic SEO framework (Koray Tuğberk's model) appliedA credential on the About page; no page shows it applied to a site
Measurement and automation
- built
-
not yet
Reporting pipeline: n8n, GA4, BigQuery, LookerNamed in the case study; the pipeline itself is not shown
- built
Outer: what makes the core believable
The trust half. Definitions, studies, corrections and context. Wider than deep on purpose; each pair exists so the core can be checked, not so it can be sold.
Definitions
- built
- built
-
not yet
Glossary of AI search terms (citation, grounding, entity, retrieval)
Studies and corrections
-
built
Cross-engine citation study, re-tested against a permutation nullTwo findings retracted
-
built
The original citation overlap studyOn the Wellows blog
-
built
The 94-day query fan-out experimentPosted publicly by Wellows' COO
Who is behind it
- built
- built
-
built
How to cite this site, and what it offers machinesllms.txt, answers.json, agents.json, markdown twins
Every post and case study on this site carries a core or outer badge that matches this map. The map is a data file in the site's source, so a new page is added here in the same commit that creates it. Machine-readable interfaces, including this site's answer index and provenance registry, are declared at /.well-known/agents.json.