AI visibility FAQ

Yes, and it's load-bearing. Answer engines retrieve from the live indexed web, so crawl access, rendering and indexation gate everything. Google's own 2026 guidance (developers.google.com) states that optimizing for generative AI search is optimizing for the search experience, and is still SEO. What has changed is that ranking well no longer guarantees being cited — the overlap between top Google results and AI-cited sources has reportedly fallen from about 70% to under 20%.

Days to weeks for retrieval-based answers on already-indexed pages, because the engine is reading your live page. Months for anything that depends on model memory, which only updates with training. Recommendation share — being named rather than merely sourced — typically takes two to three quarters because it's an entity outcome.

Put a self-contained 40–60 word answer directly under a question-shaped heading near the top of your twenty highest-impression pages. It's cheap, it works on already-indexed content, and it addresses the most common failure mode: a page that is retrievable but never quotable.

It's optional and currently low-impact. Adoption sits around 10% of domains, major AI crawlers rarely request it, and Google has said on the record it doesn't support it. Publish one because it costs twenty minutes and hedges against agentic retrieval, not because it will move citations. The full evidence is here.

That's a business decision, not a technical one. Blocking reduces unlicensed use and also removes you from AI answers. Publishers with licensing deals often block deliberately. If visibility is your goal, blocking is self-defeating — and many sites block accidentally through CDN bot-management defaults.

No. Google's 2026 documentation states structured data isn't required for AI Overviews or AI Mode and that no special schema is needed. It's still worth implementing, for a different reason: it removes ambiguity about your entity for every system that does read it. Details here.

Not directly, and long content often performs worse. Because assistants decompose questions into narrow sub-queries, twelve focused pages compete for twelve sub-queries while one 4,000-word guide competes for one broad query. Extractability and specificity beat length.

Because citation and recommendation are different outcomes. Citation is driven by content structure and sourcing; recommendation is driven by entity strength — how firmly the model associates your brand with the category from third-party sources. The fix is entity work, not more content. Start here.

Yes, indirectly. Links feed the search indexes AI systems retrieve from, but the bigger effect is the accompanying description — being characterised by credible third parties is what builds entity association. An unlinked mention in a reputable publication can outperform a linked one in a low-quality directory.

Not for being AI-generated. What's penalised is scaled content abuse: high-volume pages produced primarily to manipulate rankings with no original value. The test is whether someone with the question would be glad they landed on the page. If the only reason it exists is to occupy a slot, production method is irrelevant — it's the abuse pattern.

None specifically. A 2026 Otterly.ai study (otterly.ai) found Claude and ChatGPT citing the same domains only about 13% of the time, and each engine reads a different slice of the web. Build one structurally excellent source of truth and make sure the reference-grade surfaces engines lean on — Wikipedia, Wikidata, industry databases — are accurate about you.

Three methods: a fixed prompt panel of 30–60 buyer questions run monthly in fresh logged-out sessions and scored for mention, citation and recommendation separately; server log analysis of AI crawler hits and status codes; and an AI referral segment in analytics. Full method here.

Generative engines are non-deterministic, personalise on session context, and re-retrieve as the web changes. Measure rates across repeated runs rather than treating any single response as a result. Run each prompt three times in a fresh session and record the proportion.

Google restricted FAQ rich results in search, so the visible SERP benefit largely went away. The markup remains useful for a different audience: explicit question-answer and step structures are unusually easy for retrieval systems to consume. Add them where the content is genuine.

Not with yourself at number one. A 2026 analysis by SEO researcher Lily Ray found brands publishing self-favouring “best of” lists were left out of the AI recommendation about 69% of the time. Engines appear to discount obviously self-interested comparisons. An honest comparison that sometimes points elsewhere performs better with both engines and buyers.

Yes, often faster than for national brands, because the competitive set is smaller. Consistent name-address-phone data, a complete Google Business Profile, LocalBusiness structured data and genuine local citations do most of the work. Content-wise the method is identical: answer local questions directly, on dedicated pages, with quotable specifics.

Fan-out is the step where an assistant decomposes a complex question into several narrower sub-queries and searches each separately. It matters because you only need to win one sub-query to enter the answer — which is the structural argument for narrow, focused pages over comprehensive omnibus guides.

Yes. Citation sets shift as competitors publish, content ages, and models update. This is why measurement is recurring rather than a one-time audit, and why freshness — genuinely reviewing and updating content, not just changing a date — is part of the ongoing work.

No. The word describes the outcome — taking a citation slot that currently belongs to someone else — not the method. Everything here is disclosed, reproducible and guideline-compliant. The rules we hold to are published in full.

Read what GEO Jacking is for the concept, then the stack for the map, then run week one of the playbook — which is mostly checking whether AI crawlers can reach you at all, and is where a surprising number of teams find their real problem.