How Claude decides which websites to cite

Claude surfaces a business in two different ways: recall from its training data, and live citations when its web search capability is switched on. Each path selects sources differently, and each needs different fixes. This guide explains exactly how both work, and what your pages need before Claude will quote them.

Key takeaway: Claude cites websites through two separate mechanisms. By default it answers from training data, where your brand’s historical footprint across the public web decides whether you are recalled. When web search is enabled (in claude.ai, the Anthropic API and Claude Code), Claude retrieves live pages and cites the ones it can reach, read and quote cleanly. You can influence the live path quickly; the training path is earned over time.

What are the two ways Claude cites a website?

Claude does not have a single index the way a search engine does. It can name your business in two quite different ways, and understanding the difference is the foundation of Claude visibility work.

Training data (the default). Claude answers primarily from what it learned up to its knowledge cutoff. If your brand appeared clearly and often across the public web before that date, Claude can recall and recommend you with no live lookup at all. There is no submit button and no way to edit this on demand: you cannot email Anthropic to add yourself. You earn a place in it over time through a distinct, well-referenced footprint.

Web search and tool use (the live path). In claude.ai, the Anthropic API and Claude Code, Claude has an optional capability to search the web, open pages and cite what it finds. When it is switched on, Claude can reach your current site and quote a passage back with a source link, even if it never saw you in training. This is the layer you can influence within weeks rather than years, but only if your pages are reachable, readable and cleanly structured.

A brand can win on one path and lose on the other. You might be recalled from training but never cited live because your current pages are unreadable to a crawler, or you might be absent from training yet pulled in live because your content answers the exact question being asked.

How does Claude’s training data decide which brands it recalls?

The training path rewards consistency and breadth. Claude learned about brands from the public web as it existed before its knowledge cutoff, so the question is not “how good is my website today?” but “how clearly and consistently did my brand appear across the web over time?”

The signals that shape training-data recall are the classic entity and authority signals:

• Third-party references. Mentions in industry publications, directories, review platforms and news coverage give the model repeated, independent evidence that your brand exists and what it does.
• Consistent naming. The same company name, category description and key facts everywhere they appear. Inconsistency fragments the entity the model builds.
• A distinct footprint. A brand that exists only on its own website is easy to overlook, and easy to confuse with a similarly named company.

None of this moves quickly. That is exactly why the live path matters more for most businesses working on Claude visibility right now.

How does Claude’s web search choose which pages to cite?

When Claude searches the web mid-conversation, the selection process looks much closer to the retrieval systems used by other AI engines. In practice, four filters decide whether your page makes it into a cited answer:

1. Can Anthropic’s crawlers reach the page?

Anthropic operates named crawlers, and every one of them checks your robots.txt first. ClaudeBot is the main web crawler gathering public content. anthropic-ai is a user agent associated with Anthropic’s web data collection. Claude-Web is the agent tied to Claude fetching pages from the web. Block any of them, deliberately or through a blanket “block AI scrapers” rule, and you take yourself out of the running on that path. SearchScore’s SAVI benchmark found 38.8% of sites block at least one major AI crawler in robots.txt, often through legacy rules nobody remembers adding.

2. Is the content actually in the HTML?

Crawlers do not reliably execute JavaScript. If your key content only exists after client-side rendering, Claude may fetch your page and find nothing usable. Server-rendered content is a baseline requirement.

3. Does the page answer the question directly?

Claude picks the source it can lift a clean, self-contained answer from. A page that states the answer plainly, near the top, under a heading that matches the question, is far more citable than a page where the same information is spread across five paragraphs of build-up. Across 850,000+ sites in the SAVI Report (April 2026 edition), the average on-page structure score is just 23.1/100: most pages simply do not contain a passage an AI engine can quote cleanly.

4. Can Claude resolve who you are?

Entity clarity matters. Consistent Organisation and Person schema, matching brand details across the web, and an unambiguous statement of what you do let Claude attach the citation to the right entity rather than conflating you with a similarly named brand.

Where does Claude actually surface businesses?

A large share of Claude usage never touches the claude.ai chat window. Claude is one of the most heavily used models among developers, reaching people through the Anthropic API, inside other companies’ apps, assistants and internal tools, and through Claude Code on engineers’ machines.

Many of those products run their own retrieval: they search the web or their own content, then hand the results to Claude to answer from. So your business can be surfaced by Claude inside a customer support bot or research tool you have never heard of. You cannot optimise for each app individually, and you do not need to. The same fundamentals decide all of them: reachable pages, liftable answers and a well-referenced entity.

What does Claude not use?

Several traditional SEO signals have little direct effect on whether Claude cites you:

• Google rankings. Claude’s web search does not read Google’s index, so your Google position does not carry over the way it does for Gemini or Google AI Overviews.
• Keyword density. Semantic relevance matters; keyword repetition does not.
• Backlink counts. Authority shows up as references and mentions the model has seen, not as a raw link total.

A practical checklist for getting cited by Claude

• ClaudeBot, anthropic-ai and Claude-Web are all allowed in robots.txt
• Key content is server-rendered, not JavaScript-only
• Each important page opens with a direct, self-contained answer
• Headings are written as the questions people actually ask
• Organisation and Person schema are present and consistent
• An llms.txt file at your domain root points to your most important pages
• Your brand name, category and details match everywhere they appear on the web

To see which of these you are missing today, run the free Claude Visibility Checker. It tests reachability for each Anthropic crawler separately, scores your citable structure, and returns a ranked fix list in about 60 seconds.

Related articles

• Claude SEO guide: the full playbook →
• Why your website isn’t showing up in Claude →
• How to check your Claude visibility →
• What is GEO? The complete guide →

Sources & Further Reading

• Anthropic – Does Anthropic crawl data from the web? (ClaudeBot)
• SearchScore SAVI Report, April 2026 (850,000+ sites audited)
• Academic research – GEO: Generative Engine Optimization (Aggarwal et al., arXiv)
• llmstxt.org – The llms.txt standard specification