SEO for LLMs: How to Rank in AI Search in 2026
I have read most of what has been published on SEO for LLMs, and a lot of it is people repeating each other.
The same figures circulate. Fresh content gets cited 4.3 times more often. Three quarters of AI citations come from the top 10. Build an llms.txt file.
I went looking for the primary studies behind those claims. One of them does not exist. One was true last year and is false now. One scores dead last in the only evidence-weighted analysis anyone has published.
So this is not another tactics list. It is what the research supports, what it does not, and the order I would work in.
Every number below is attributed to the study it came from, with a date. Where studies disagree, I say so instead of picking the one I like. Where I could not verify something, I say that too.
TL;DR: What Works in LLM SEO
- Accessibility and rank anchor everything: Cyrus Shepard’s May 2026 meta-analysis of 54 studies scores URL accessibility 9.5 out of 10 and search rank 9.4. Nothing else comes close.
- Blocking the wrong crawler is the most expensive mistake: Training bots and search bots are separate agents. Rutgers and Wharton researchers found publishers blocking AI crawlers lost 23.1% of total traffic without reliably reducing citation rates.
- Brand mentions beat backlinks by roughly three times: Ahrefs studied 75,000 brands. Branded web mentions correlate 0.664 with AI Overview visibility, against 0.218 for backlink count.
- The top 10 matters far less than it did: Only 38% of AI Overview citations come from top 10 pages now. That was 76% in mid-2025, per Ahrefs.
- Editorial content does the work: BuzzStream found blog and content pages make up 53.46% of all AI citations. Syndicated press releases account for 0.04%.
- Skip llms.txt: It scores 2.0 out of 10, the lowest of all 23 factors, with no credible evidence it influences citations.
What SEO for LLMs Really Involves
There is a misunderstanding I want to clear up before anything else.
Most people assume LLMs answer from what they memorized in training. That is only one of three routes your content can take into an answer.
- Training data: The model absorbed your content during pre-training. You cannot influence this on any useful timeline, and you cannot verify it happened.
- Retrieval: The model runs a live search when it needs current information. Nearly all of your influence sits here.
- Grounding: The model reads what it retrieved and decides which pages to quote and cite.
SEO for LLMs is almost entirely about the second and third layers.
Those are two separate problems. Getting retrieved is a ranking and accessibility problem. Getting quoted once retrieved is a writing and structure problem.
Most guides collapse them into one. That is why their advice reads as a jumble of unrelated tips.
How LLMs Pick Which Sources to Cite
The mechanics changed in a way that has not filtered through to most advice yet.
An AI engine does not run your query and grab the top results. It expands your question into multiple sub-queries and retrieves across all of them. That expansion is called fan-out.
Search Engine Land reported an analysis in March 2026 covering 548,534 pages retrieved across 15,000 prompts. Nearly 90% of ChatGPT prompts trigger follow-up searches beyond the wording the user typed.
Roughly a third of cited pages get pulled in only through those follow-up queries. They never surface for the question the user typed.
The same analysis found ChatGPT cited only 15% of the pages it retrieved.
That figure reframes the whole exercise. Retrieval is necessary and nowhere near sufficient. Six of every seven retrieved pages get read and discarded.
What Fan-Out Looks Like in Practice
Say a buyer types this into ChatGPT.
“What’s the best help desk software for a 20 person support team that already uses Slack?”
The engine does not search that string. It breaks the question into something closer to this.
- best help desk software 2026
- help desk software for small teams
- help desk Slack integration
- Zendesk vs Freshdesk vs Intercom pricing
- help desk software pricing per agent
- help desk software reviews complaints
Six searches, maybe more. Each one returns its own results. The model reads across all of them, then writes one answer.
You do not need to win the original question. You need to appear in enough of those sub-searches that the model keeps running into you.
That is why a single strong page loses to a cluster of decent ones. It is also why the metric you should track is coverage across a topic, not position on a head term.
Why the Top 10 No Longer Decides Citations
Here is the figure I see quoted most often, and it is out of date.
You will read that 76% of AI Overview citations come from pages ranking in Google’s top 10. That was accurate in mid-2025.
Ahrefs analyzed 863,000 keywords and 4 million AI Overview URLs in March 2026. The share had fallen to 38%.
| Where the citation came from | Share of AI Overview citations |
|---|---|
| Top 10 organic results | 38% |
| Ranking 11 to 100 | 31.2% |
| Beyond rank 100 | 31.0% |
Source: Ahrefs, 863K keywords and 4M AI Overview URLs, March 2026.
Nearly two thirds of AI Overview citations now come from pages outside the top 10. Fan-out reaches deeper for each sub-query, so a page that would never win a head term can still be cited.
I treat this as the most consequential number in this article. It is the difference between a one-page strategy and a cluster strategy, and it is why “just rank higher” is no longer a complete answer.
The 23 Ranking Factors, Scored by Evidence
In May 2026, Cyrus Shepard of Zyppy published something this field badly needed. He synthesized 54 experiments, patents, and case studies across ChatGPT, Gemini, and Perplexity, then scored 23 factors on repeatability, evidence strength, and official platform support.
It is the only attempt I know of to weight GEO advice by evidence rather than by how confident the person sounds.
| Factor | Evidence score | What it means for you |
|---|---|---|
| URL accessibility | 9.5 | A blocked, paywalled, or erroring page cannot be cited at all |
| Search rank | 9.4 | Classic ranking is still the base layer |
| Fan-out rank | 9.3 | Ranking across the expanded sub-queries, not just the head term |
| Preview control | 9.2 | A nosnippet directive can suppress your citations entirely |
| Query-answer match | 9.2 | Answering the exact phrasing beats being topically adjacent |
| Topic cluster ranking | 8.9 | Depth across a topic makes you a repeated fan-out destination |
| Answer near the top | 8.8 | Lead each section with the answer |
| AI-ready structure | 8.6 | Headings and tables that make passages extractable |
| Self-contained passages | 8.0 | Each section should work as a complete answer on its own |
| Cites sources internally | 8.0 | Referencing primary data signals reliability |
| Freshness | 7.0 | Real but moderate, not the dominant factor |
| llms.txt | 2.0 | No credible evidence it influences citations |
Source: Zyppy AI Citation Ranking Factors, May 7, 2026.
Two findings stand out to me here.
The top four factors are technical accessibility, not content tactics. Most GEO advice starts at position five and never mentions the first four.
And preview control at 9.2 is the one almost nobody audits. Teams that added a nosnippet directive years ago for SERP reasons may be excluding themselves from AI answers without knowing it.
Step 1: Fix Accessibility Before Anything Else
This is the highest-scoring factor and the cheapest to fix. It is also where I find the most damage.
Know Which Crawler Does What
This is the part most teams get wrong, and it costs them the whole channel.
AI crawlers fall into three families. They look identical in your server logs and serve completely different purposes.
| Family | Examples | What it does | What blocking it costs you |
|---|---|---|---|
| Training crawlers | GPTBot, ClaudeBot, Google-Extended, CCBot, Applebot-Extended | Collects content to train foundation models | Your content is not used for training. Citations are unaffected. |
| Search crawlers | OAI-SearchBot, Claude-SearchBot, PerplexityBot | Indexes pages so assistants can cite them live | You disappear from ChatGPT, Claude, and Perplexity answers |
| User fetchers | ChatGPT-User, Claude-User, Perplexity-User | Fetches a page when a user asks the assistant to read it | Users cannot get your page summarized on request |
The distinction that matters: GPTBot is training, OAI-SearchBot is search. They need separate directives.
Blocking GPTBot keeps your content out of model training. Blocking OAI-SearchBot removes your brand from ChatGPT search results. A lot of teams blocked both in 2024 with one rule, meaning to opt out of training, and quietly deleted themselves from AI answers.
If you want to opt out of training while staying citable, the selective posture looks like this.
# Training crawlers: blocked
User-agent: GPTBot
Disallow: /
User-agent: Google-Extended
Disallow: /
User-agent: CCBot
Disallow: /
# Search crawlers: allowed, so you stay citable
User-agent: OAI-SearchBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
# User-triggered fetches: allowed
User-agent: ChatGPT-User
Allow: /
User-agent: Perplexity-User
Allow: /
# Never block this one
User-agent: Googlebot
Allow: /
Sitemap: https://example.com/sitemap.xml
Before you copy that, know what blocking training buys you.
Rutgers and Wharton researchers published work in December 2025 on publishers who blocked AI crawlers. Those publishers lost 23.1% of total traffic, and the block did not reliably reduce citation rates.
So the block cost them traffic and did not deliver the protection they wanted. I would default to allowing everything unless you have a specific licensing or legal reason not to.
Two honest caveats on robots.txt. Compliance is opt-in, so a directive only works if the bot honors it, and a spoofed user agent can claim to be anything. Real-time fetches triggered by a user asking an assistant to read a URL are also treated as user-directed access by some providers, so your crawl rules may not apply the way you expect.
Check the Four Faults That Silently Kill Citations
- Redirect chains: Search crawlers have lower tolerance than training crawlers. Reported limits sit around three to five hops by bot. One extra hop can be enough to drop the page from an answer. A chain of 301 to 302 to 200 that GPTBot digests without complaint can make OAI-SearchBot give up. Also note that 301 and 308 destinations get stored, while 302 and 307 trigger repeated recrawls.
- Status codes on archive pages: I have seen whole blog archives return a 302 to crawlers while looking fine in a browser. Nobody notices because the human experience is unaffected. Check status codes with a crawler user agent, not with your own browser.
- nosnippet and max-snippet directives: These score 9.2 in the Zyppy analysis. AI engines lean on snippet data during grounding, so suppressing previews can suppress citations. Search your templates for
nosnippet,max-snippet, anddata-nosnippetand confirm every instance is deliberate. - JavaScript rendering: If your main content only appears after client-side rendering, assume some crawlers will not see it. Load the substance server-side.
The One-Hour Audit
Run this on your 20 highest-value pages before you touch anything else.
- Fetch each URL with a search crawler user agent and confirm it returns a 200 with no redirect chain.
- Check robots.txt for any rule blocking OAI-SearchBot, Claude-SearchBot, or PerplexityBot.
- Search your templates and CMS for nosnippet and max-snippet directives.
- Confirm your CDN or WAF is not blocking AI user agents independently of robots.txt. This happens more often than robots.txt misconfiguration.
- View source with JavaScript disabled and confirm your main content is present.
- Check your server logs for which AI crawlers visited in the last 30 days. If a search crawler is absent, you have found your problem.
Point five and point four catch most of what I find. Hosting platforms and CMS defaults block AI crawlers more often than teams realize.
Step 2: Win Classic SEO First
Search rank scores 9.4 out of 10, second only to accessibility.
Shepard’s summary of his own findings is blunt: win SEO, win AI citations, most of the time, with extra steps.
The top 10 share fell to 38%. That changes where you put the effort, not whether ranking matters. A page ranking 15th for six related sub-queries beats a page ranking 3rd for one head term, because fan-out reaches all six.
So classic SEO is still the base layer. What changes is that you stop optimizing one page toward one keyword and start covering a question space.
Step 3: Build Brand Mentions, Not Just Backlinks
This is the finding that should move budget.
Ahrefs studied 75,000 brands using Spearman correlation, limited to domains with a Domain Rating above 40 and keywords with at least 800 monthly searches.
| Signal | Correlation with AI Overview visibility | Versus backlinks |
|---|---|---|
| Branded web mentions | 0.664 | 3.0x |
| Branded anchor texts | 0.527 | 2.4x |
| Branded search volume | 0.392 | 1.8x |
| Domain Rating | 0.326 | 1.5x |
| Number of backlinks | 0.218 | Baseline |
The three strongest signals are all off-site brand signals. Backlink count comes last.
The gap widens at the extremes. The top quartile of brands by mention volume averages 169 AI Overview mentions. The next quartile averages 14.
A separate Wellows analysis found Domain Authority’s correlation with citation likelihood has fallen to around r=0.18, down from r=0.43 before 2024. Two datasets, same direction.
I want to be careful here, because the study authors are careful. This is correlation, not causation.
Already-strong brands may simply earn both mentions and citations. Adding mentions to a weak brand may do nothing. Nobody has run the experiment that would separate those.
What I take from it is a priority order, not a guarantee.
- What earns mentions in practice: Podcast appearances. Guest analysis in industry newsletters. Original data other people quote. Answering questions in the communities your buyers read. Getting listed in the roundups and directories your category uses.
- What does not: BuzzStream found syndicated press releases account for 0.04% of all AI citations. The wire distribution playbook is close to invisible here.
Step 4: Replace Keyword Research With Prompt Research
Keyword tools were built for a world where people typed three words into a box.
Nobody talks to ChatGPT that way. Prompts are longer, conversational, and carry context a query never did.
So the research method changes shape. Here is the process I run.
- Harvest the real questions: Pull them from sales call recordings, support tickets, sales emails, and community threads. Write them in the exact words the buyer used. These have no search volume you can look up, and that is fine.
- Sort by buying stage: A prompt asking what a category is behaves differently from a prompt asking which vendor to pick. The second kind is where citation is worth money.
- Map the fan-out for each priority prompt: Write out the six to ten sub-questions an engine would need to answer it. For “best help desk software for a 20 person team using Slack,” that includes pricing per agent, Slack integration depth, alternatives to the market leader, complaints, setup time, and team size fit.
- Audit your coverage against that map: Most teams find they have one page covering the head term and nothing covering the sub-questions. That is precisely the gap fan-out punishes.
- Run the prompts and log what comes back: Take your top 20 prompts across ChatGPT, Perplexity, and Gemini in Google AI Mode. Record which brands are named, which sources are cited, and where you appear.
I still do step five manually more often than I would like to admit. Twenty prompts, three platforms, once a month, in a spreadsheet. Tools are improving, but the manual version teaches you more in the first month than any dashboard will.
Track two measures over time: how often you are mentioned at all, and how often you are mentioned when a competitor is. The second number tells you whether you are in the consideration set.
Step 5: Build for Fan-Out With Clusters
Fan-out rank scores 9.3 and topic cluster ranking scores 8.9. Those are the two highest content-strategy signals in the Zyppy study.
The practical translation is that one long page loses to six focused ones.
A cluster for a category looks roughly like this.
| Page type | The sub-query it answers |
|---|---|
| Best-of listicle | Which tools should I consider |
| Alternatives page | What else is there besides the leader |
| Head-to-head comparison | Should I pick A or B |
| Pricing explainer | What does this category cost |
| Use case page | Does this work for my situation |
| Integration page | Does it work with my stack |
| Limitations or complaints page | What goes wrong with these tools |
Each page answers one sub-question completely. Together they cover the fan-out for a buying decision.
That last row is the one most teams skip, and it is often the easiest citation to win because almost nobody writes it honestly.
Step 6: Write So Passages Can Be Extracted
Three factors here score 8.8, 8.6, and 8.0: answer near the top, AI-ready structure, and self-contained passages.
Position Digital reported that 44.2% of all LLM citations come from the first 30% of a text, and 31.1% from the middle.
That is a writing instruction, not a formatting one.
- Lead with the answer, then explain: Most writers build to a conclusion. For extraction you invert it.
Here is a paragraph written the usual way.
When evaluating help desk platforms, there are a number of factors worth weighing, including your team size, your existing stack, and the complexity of your support workflows. Once you have considered all of these, most teams find that per-agent pricing becomes the deciding factor, since costs scale directly with headcount.
Nothing in there can be lifted as an answer. Here is the same content rewritten.
Per-agent pricing is usually the deciding factor for support teams under 25 people. Costs scale directly with headcount, so a plan that looks cheap at five agents can double before you finish hiring. Team size, existing stack, and workflow complexity all matter, but they rarely override the per-agent math.
The answer is in the first sentence. The section stands alone without the paragraphs around it. A model can quote it without needing context.
- Make each section independently readable: If a passage starts with “this means that” or “as mentioned above,” it cannot be extracted. Repeat the subject instead of pronouns at the start of sections.
- Use tables for anything comparative: Tables are cleanly parseable, and comparison data is what buyer-stage prompts need.
- Cite your sources inside the content: This scores 8.0. Naming the study and date signals reliability, and it is what lets a model pass your claim along with attribution.
- Write short declarative sentences: Analysis of heavily cited text found simpler sentence structures and definite language perform better than hedged, complex prose.
Step 7: Build the Page Types That Get Cited
Content type determines what gets pulled once you are retrievable.
BuzzStream analyzed 4 million citations from 3,600 prompts across 10 industries.
| Content type | Share of AI citations |
|---|---|
| Blog and content pages | 53.46% |
| News | 14.09% |
| Social | 8.71% |
| Syndicated press releases | 0.04% |
With brand-owned queries excluded, earned editorial content accounted for roughly 80% of citations.
One caveat the authors give and I will repeat. That data was collected over a single week starting in late January 2026, so treat the percentages as directional rather than fixed.
On format specifically, Wix data from March 2026 found listicles at 21.9%, articles at 16.7%, and product pages at 13.7% of citations across AI Mode, ChatGPT, and Perplexity. Siege Media reported in June 2026 that comparison pages, alternatives pages, and best-of listicles correlate most strongly with AI search traffic.
For B2B SaaS specifically, Position Digital reported in August 2026 that listicles account for 18.8% of ChatGPT citations and product or service pages 18.6%.
The pattern is consistent across those datasets. Buyer-stage formats get cited because buyer-stage prompts are what people ask assistants.
Step 8: Measure It Properly
Most teams are measuring this badly, and the failure is usually attribution rather than effort.
- Fix the tracking first: Default GA4 setups bucket AI referrals as direct or referral. Build a channel group that catches chatgpt.com, openai.com, perplexity.ai, claude.ai, gemini.google.com, and copilot.microsoft.com so the traffic stops hiding.
- Watch your server logs for crawlers: If OAI-SearchBot has not visited in 30 days, no amount of content work will help until you find out why.
- Track prompt visibility on a fixed schedule: Same 20 prompts, same three platforms, same day each month. Log mention rate and competitor co-occurrence.
- Expect volume to be small: AI referrals sit around 1% of total traffic for most B2B sites. Do not build a business case that needs it to be 20%.
- Expect it to move in bursts: Referral volume shifts when platforms ship updates, not smoothly month over month. ChatGPT referral volume rose sharply after a May 2026 update that made brand links more prominent in answers. A team watching trailing averages will miss the week the numbers move.
The Numbers You Should Stop Repeating
Two claims circulate constantly and neither survives a source check.
“Fresh content gets cited 4.3 times more often.” I could not trace this to any primary study, and neither could the analysts who went looking. It does not appear in Shepard’s work, which scores freshness a moderate 7.0. It does not appear in the Ahrefs freshness study either. It shows up only on aggregation blogs with no published methodology or sample size.
The verified figure is more modest. Across 16.975 million cited URLs on seven platforms, Ahrefs found AI-cited content averages 1,064 days old against 1,432 days for organic top 10 results. That is a 25.7% freshness advantage. ChatGPT skews freshest at 958 days.
Real, replicable, worth acting on. Not a multiplier.
“Build an llms.txt file.” It scores 2.0 out of 10, the lowest of all 23 factors in the only evidence-weighted ranking published. No major platform has confirmed it reads the file.
I am not saying it will hurt you. I am saying it takes an afternoon that would be better spent auditing your nosnippet directives, which score 9.2.
Does Any of This Drive Traffic?
Here I have to be honest about a mess in the data.
Studies disagree sharply on what AI citations are worth, and the disagreement is not small.
Seer Interactive studied 53 brands across 5.47 million queries in April 2026 and found being cited in AI Overviews associated with 120% more organic clicks per impression than not being cited.
Other measurements point the other way. AI chat platforms send a low single-digit share of total referral traffic to most publishers, typically under 2%. Some publisher studies put click-through from AI answers below 1%.
On conversion the spread is wider still. Several 2026 studies report AI referral traffic converting multiples better than organic. Earlier peer-reviewed work in Marketing Science, covering 973 ecommerce sites and more than 50,000 ChatGPT-driven transactions between August 2024 and July 2025, found it converting worse.
I cannot reconcile those, and I would not trust anyone who says they can.
What I think is defensible: volume is small for most B2B sites, and the visitors who do arrive tend to be further along in their decision. Whether that nets out ahead of organic depends on your category and your measurement setup.
The stronger argument for doing this work is that it overlaps almost entirely with good SEO. Accessibility, rankings, brand presence, and topic depth all pay off in organic search regardless of what happens in AI answers. You are rarely trading one for the other.
A 90-Day Plan
- Days 1 to 14, stop the leaks: Run the one-hour audit on your top 20 pages. Fix redirect chains, remove unintended nosnippet directives, confirm search crawlers are allowed in robots.txt and at the CDN. Set up AI referral tracking in GA4.
- Days 15 to 30, find out where you stand: Build your prompt list from sales calls and support tickets. Run 20 prompts across three platforms and log the results. Map the fan-out for your five highest-value prompts and audit your coverage against it.
- Days 31 to 60, fill the cluster gaps: Build the pages your fan-out map says are missing. Comparison, alternatives, pricing, and limitations pages first, because those match buyer-stage prompts. Rewrite the intros of your existing top pages to lead with the answer.
- Days 61 to 90, build presence off your own domain: Pitch podcasts and newsletters. Publish one piece of original data worth quoting. Answer questions in the communities your buyers read. Re-run your prompt tracking and compare against the day 30 baseline.
Ninety days is enough to see accessibility and structure changes take effect. Brand presence and cluster depth take longer, and I would not judge those before month six.
Mistakes I See Most Often
- Blocking search crawlers while meaning to block training crawlers: The single most expensive error in this list, and it is usually a line of robots.txt written in 2024 that nobody has revisited.
- Optimizing one page for one prompt: Fan-out means the answer is assembled from many sources. Coverage beats perfection.
- Chasing freshness before fixing accessibility: Refreshing content is a 7.0 factor. Crawlability is a 9.5 factor. A constant refresh cadence on pages a search crawler cannot reach is wasted effort.
- Treating AI visibility as a separate program: It is mostly the same work as SEO with different priorities. Running it as a parallel track duplicates effort and splits budget.
- Building the business case on traffic volume: At around 1% of sessions, this channel does not justify itself on volume today. Justify it on overlap with organic and on presence in the consideration set.
- Quoting stats without checking them: The 4.3x figure spread because nobody traced it. If a number has no named study and date attached, do not put it in a deck.
Where I Would Start With SEO for LLMs
The 2026 data tells one story. AI engines cite pages they can reach, that already rank, that answer the exact question, and that come from brands with presence across the web.
My take is simple. This is not a new discipline. It is SEO with a reordered priority list, plus one new requirement: presence off your own domain.
Start with crawler access. It takes an hour and nothing else works until it is right.
Then fill the coverage gaps fan-out punishes, and build mentions rather than links.
One final point. Re-check every figure in this article before you build a plan on it, including mine. That is the lesson of the 4.3x myth.
FAQs About SEO for LLMs
1. Is SEO for LLMs different from regular SEO?
It is a layer on top rather than a replacement. Search rank scores 9.4 out of 10 as a citation factor, so classic SEO is still the base. You also need topic depth for fan-out, extractable structure, and off-site brand presence.
2. Should I block AI crawlers from my site?
Probably not. Rutgers and Wharton researchers found publishers who blocked AI crawlers lost 23.1% of total traffic without reliably reducing citation rates. If you want to opt out of training only, block GPTBot, Google-Extended, and CCBot while allowing OAI-SearchBot, Claude-SearchBot, and PerplexityBot.
3. What is the difference between GPTBot and OAI-SearchBot?
GPTBot collects content to train OpenAI’s models. OAI-SearchBot indexes pages so ChatGPT can find and link them in search answers. Blocking GPTBot stops training collection. Blocking OAI-SearchBot removes you from ChatGPT search results. They need separate directives.
4. Do I need an llms.txt file?
The evidence says no. It scores 2.0 out of 10 in Cyrus Shepard’s May 2026 meta-analysis, the lowest of all 23 factors, and no platform has confirmed it reads the file. Audit your nosnippet directives instead, which score 9.2.
5. Which content gets cited most by AI engines?
Blog and editorial content, by a wide margin. BuzzStream found blog and content pages make up 53.46% of all citations, rising to roughly 80% once brand-owned queries are excluded. Listicles, comparison pages, and alternatives pages correlate most strongly with AI search traffic.
6. Do backlinks still matter for AI citations?
They matter less than brand mentions. Ahrefs found backlink count correlates 0.218 with AI Overview visibility, against 0.664 for branded web mentions. Links still support the rankings that feed retrieval, so this is a reallocation rather than a reason to stop building them.
7. How do I track whether AI assistants mention my brand?
Run your priority buyer prompts across ChatGPT, Perplexity, and Gemini in Google AI Mode on a fixed schedule and log which brands appear. Twenty prompts checked monthly will teach you more in a quarter than most dashboards. Fix your GA4 attribution at the same time, because default setups bucket AI referrals as direct.
8. How long does it take to get cited?
There is no reliable published benchmark, and I would distrust anyone who gives you one. Accessibility fixes can take effect within a crawl cycle. Brand presence and cluster depth are quarters of work, not weeks.
9. Is AI search traffic worth chasing if the volume is small?
For most B2B sites AI referrals sit around 1% of total traffic, so it should not be your only channel. The case for doing the work is simple. Accessibility, rankings, brand mentions, and topic depth all help organic search too, so the effort is rarely wasted either way.
10. Does schema markup help with AI citations?
It does not appear among the highest-evidence factors in the Zyppy analysis, so I would not prioritize it over accessibility, rank, or structure. It remains worth having for traditional search features, and clean structured data does no harm to extraction.
