Get cited by AIClaude
How to get cited by Claude
Claude reaches your page through named Anthropic crawlers that honor robots.txt and work from your raw HTML, so being cited starts with being fetchable, allowed, and readable without JavaScript.
To be cited by Claude, your page has to be reachable and readable by Anthropic's crawlers first. Citation is never guaranteed, but a page Claude cannot fetch or parse is never a candidate.
Anthropic uses several named crawler tokens, and each works from the HTML your server returns. Like most AI crawlers, these fetchers read that raw markup rather than a fully scripted browser render, so content injected client-side, allowed only for other user agents, or buried in non-semantic markup can reach Claude as less than a visitor sees. This page covers what it takes to be readable and allowed, which is the part you control.
What it takes, in short
- Make the page fetch cleanly
- Allow the Anthropic tokens in robots.txt
- Serve your content in the raw HTML
- Give the content a machine-readable structure
- Publish substantive, specific content
- ClaudeBot Training. Collects public web content that may train Anthropic's models.
- Claude-SearchBot Search. Crawls to build and improve Claude's search index.
- Claude-User User fetch. Handles requests such as asking Claude to read a specific page.
- anthropic-ai Training. A robots-only token with no user agent to probe.
How Claude reads the web
Anthropic operates named crawler tokens including ClaudeBot, Claude-SearchBot, and Claude-User. Per Anthropic's documentation, ClaudeBot collects public web content that may be used to train Anthropic's models, Claude-SearchBot crawls pages to build and improve Claude's search index, and Claude-User handles user-initiated requests, such as when someone asks Claude to read a specific page. Anthropic publishes these user-agent tokens and states that all of them honor robots.txt. Like most AI crawlers, these fetchers work from the raw HTML your server returns; text that appears only after client-side JavaScript runs is at risk of not reaching them. Claude draws on what it can fetch and read, through live fetches and its search index, so being fetched and parsed is a prerequisite for being referenced and not a guarantee of it.
What it takes to be readable and citable
-
Make the page fetch cleanly
Claude's crawlers need a clean HTTP response. Return a 200 status, avoid long redirect chains, and keep the page from timing out or blocking on size. Lantad's Retrievability check fetches your URL the way a crawler does and reports the status, redirects, and response size, so you can see whether the page is even reachable before anything else.
-
Returns HTMLBlocking A 4xx or 5xx ends the scan. Nothing downstream is measurable. -
Crawler allowedBlocking robots.txt and the live server both have to permit the token. -
Readable without JSBlocking Most AI crawlers do not execute JavaScript. -
StructuredImproves Headings and schema make the content extractable. -
CitedNot promised The engine decides. No configuration can guarantee it.
The order a page has to pass. Failing an earlier rung makes the later ones irrelevant. -
-
Allow the Anthropic tokens in robots.txt
robots.txt controls whether a given crawler may fetch your pages, and vendors use different tokens. Check that your rules do not block ClaudeBot, Claude-SearchBot, or Claude-User, whether by a named Disallow or an overly broad wildcard. Lantad's Access check reads your robots.txt and the live server response and reports the exact rule that applies to each Anthropic token.
-
Claude-SearchBotCosts you You are absent from the index Claude searches. -
Claude-UserCosts you A direct request to read your page returns nothing. -
ClaudeBotYour choice Training opt-out. Not penalised by Lantad. -
anthropic-aiYour choice Also training, and robots-only so there is nothing to probe.
What each Anthropic token costs if you block it. -
-
Serve your content in the raw HTML
Because these fetchers work from the HTML your server returns, text rendered only in the browser can reach them as an empty shell. Server-render or statically generate the words that matter so they appear in the raw markup. Lantad measures this as Prose Parity: it compares the text in a raw HTTP fetch against a full browser render and reports how much of the human-visible content a crawler actually receives. High parity means Claude sees closer to what your visitors see.
Sample Illustrative, not a measurement of any real site.
What the crawler gets
- <div id="root"></div>
- a script bundle
- no product copy
- nothing to quote
What the visitor gets
- the full copy
- headings and prose
- assembled in the browser
- invisible on the left
Sample illustration of a client-rendered page as each side receives it. -
Give the content a machine-readable structure
Semantic HTML and a clear heading hierarchy give your content an outline a machine can follow. Use real headings, lists, and landmarks instead of styled div elements. Add structured data (schema.org / JSON-LD) to label what the page is about. Lantad scores Structure and Schema separately so you can see whether your outline and your labeling are legible to a crawler.
- One h1, then ordered h2s A machine reads the outline before it reads the prose.
- Semantic containers main, article and section, rather than nested unlabelled divs.
- A recognised business type in JSON-LD Organization, LocalBusiness, SoftwareApplication and similar.
- Server-rendered, not injected JSON-LD added by JavaScript is not in the HTML a crawler receives.
What the structure and schema checks look for. Together they are 25% of the score. -
Publish substantive, specific content
Readable and allowed gets you into the candidate set; substance is what makes a page worth referencing. Answer the question directly, state facts plainly, and keep the useful content in the fetchable HTML rather than behind interactions. Lantad cannot promise a citation, and neither can anyone else, but it can confirm that the substance you wrote is present in what Claude receives.
What you control
- whether the page fetches
- whether the token is allowed
- whether the text is in the HTML
- whether it is structured
What you do not
- whether Claude cites you
- how sources are selected
- what the model already knows
- no tool can promise this
The honest boundary of what any of this achieves.
Lantad
Common questions
Does allowing ClaudeBot guarantee that Claude will cite my page?
No. Being fetchable, allowed, and readable makes your page a candidate for retrieval and use, but no tool or vendor can guarantee a citation. Lantad measures the prerequisites you control and does not claim to influence how Claude selects sources.
What is the difference between ClaudeBot, Claude-SearchBot, and Claude-User?
Per Anthropic's documentation, ClaudeBot collects public web content that may be used to train Anthropic's models, Claude-SearchBot crawls pages to build and improve Claude's search index, and Claude-User handles user-initiated requests, such as when someone asks Claude to read a specific URL. Your robots.txt can set rules for each token by name, and Lantad reports the rule that applies to each.
My page looks fine in a browser. Why would Claude see something different?
Most AI crawlers work from the HTML your server returns and often do not run JavaScript. If your text is injected in the browser after load, a crawler can receive an empty shell instead. Lantad's Prose Parity check shows the gap between a raw fetch and a full render so you can see exactly what is missing.
See what Claude can read on your site
Run a free scan: paste a URL and see exactly what AI crawlers can and cannot read, with a graded report and ranked fixes.