Claude is the engine almost nobody works and the one you talk to more than you think. It's Anthropic's AI, and it carries an oddity that changes the game: most people don't talk to it on claude.ai — they talk to it inside other products (code editors, company assistants, work tools) that run Claude underneath through its API. So «showing up in Claude» isn't one surface. On top of that, Claude searches the web only when the question calls for it, cites its sources one by one, and is one of the strictest engines about the quality of what it cites. It answers two ways. Here's the map.
Why Claude isn't an app: it's a model reaching thousands of products through its API
Every other engine you've worked, you mostly use in its own house: ChatGPT in its app, Gemini in Google, Perplexity in theirs. Claude is a different picture: its biggest surface isn't claude.ai, it's the API. Thousands of products — from code editors to internal company assistants — answer their users with Claude underneath without those users ever typing into claude.ai. The consequence for you is the one of a model that's distributed: what Claude knows about your category travels to every product that runs it.
Translated to your work: the layer that weighs most in Claude is trained knowledge, because it's the one that reaches all those surfaces at once. If the model knows you as a clear, well-described entity — who you are, what you do, why you're a reference — that signal doesn't show up in one place: it shows up in every tool where Claude answers.
The two ways Claude answers (and how to get into each)
Claude answers in two ways, and each is worked differently.
- By default, from what it knows. Like ChatGPT, its first deck is the knowledge it learned in training. There's no live link here: either you're in what the model learned, or you're not. You get in by being a recognizable entity corroborated off your own site — press, Wikipedia, reviews, forums — so the model learned you well.
- With search on, from the live web. Claude has a search tool it decides to use itself when the question needs fresh or out-of-training data; it retrieves results — leaning on Brave Search — and cites them with inline notes the user can verify. Here you do compete to be retrievable: answer up front, fresh content, sourced data.
The difference from other engines is that Claude doesn't search on every question: it does it only when it needs to. So some of your answers will come from the trained layer even though search exists. Work both.
The strictest engine: why Claude penalizes unsourced content
If there's one engine that rewards work done well and punishes filler, it's this one. When Claude cites, it tends to be conservative: it favors solid, corroborated sources and down-weights affiliate-aggregator content, substance-free SEO listicles and unsourced claims. Where another engine swallows a well-optimized empty text, Claude discards it. What rises is the opposite: a clear claim, the why right behind it, and the proof — a data point, a source, a quote — next.
The levers that actually get you into Claude's answers
With the two decks and the strictness in mind, the game is five things.
- Be a clear, corroborated entity. It's lever number one, because it feeds the trained layer that reaches every product running Claude, and because Claude leans heavily on what's said about you off your site. Make sure who you are and what you do reads the same on and off your site.
- Answer up front, with data and quotes. Front-load the answer in the first lines of each section and back it. It's what lifts visibility most and the only thing that survives Claude's filter against unsourced content.
- Break it into short, focused blocks. Claude cites by blocks: the smaller and more self-contained each block is, the easier it is for it to clip and quote you verbatim. One paragraph, one idea.
- Let the right crawlers in. Check that your robots.txt doesn't block Claude-User (the fetch when a user asks) or Claude-SearchBot (the one that indexes for its answers). Those are separate decisions from ClaudeBot, the training one.
- Be retrievable and fresh for search mode. Visible date, updated content, crawl access. The second deck is won by being among the most solid and recent it finds.
Measure it and check your robots.txt: Claude doesn't have one crawler, it has three
Like every other engine, Claude gives you no citation dashboard. The method is the usual one: define 15 to 25 questions your customers would ask it, run them once a month — some that force search and some that don't, because they're two decks — and note whether you show up in the text or among the sources. The trend over months is what counts.
And the technical detail almost nobody controls: Anthropic documents three named crawlers, controlled separately in your robots.txt. ClaudeBot collects content to train the model; Claude-User goes to fetch a page when a user asks a question that needs it; Claude-SearchBot indexes content to improve search answers. The trap: blocking one doesn't block the others, and blocking the wrong one — thinking you're shutting off training — can lock you out of the very layer that cites you. Check which you allow and which you don't.