How to Get Your Brand Recommended by Claude

Updated · Citepoint · 5 min read

Short answer

Claude decides for each question whether to search the web. When it doesn't, it answers from training data, which you can't change quickly. When it does, it retrieves live pages and cites them. To be recommended, publish clear pages that Claude-SearchBot can read, get mentioned on the sources searches return, and be described consistently across the public web so that future training data knows you. Test both paths by asking Claude with and without search.

Key takeaways

  • Anthropic says Claude searches when a request depends on current or changing information, and answers directly when it draws on stable knowledge.
  • Without search, Claude answers from training data. What it knows about your brand was fixed before the model's training cutoff.
  • Anthropic runs three bots: ClaudeBot for training, Claude-User for user-requested fetches and Claude-SearchBot for search quality. Blocking the last two can reduce your visibility.
  • Citepoint asks Claude weekly through Anthropic's API with a fixed model and web search available, so Claude chooses whether to search, as it does in the app.

How does Claude decide whether to search the web?

Claude makes the call itself, question by question. Anthropic's help center says that when you ask about topics that benefit from current information, Claude invokes a search tool to ground its answer in content from the live web, and every response then includes citations. In the new Claude experience there is no web search toggle: Claude searches when it helps. You can force the issue by asking it to search the web, or tell it not to.

Anthropic's developer documentation is more specific. Claude searches when a request depends on information that is current, changing or outside its training data: recent events, current prices and statistics, information about specific organizations, people or products that might have changed, and explicit requests to look something up. It answers directly for stable knowledge such as math, science fundamentals, creative writing and analysis of content already in the conversation. Developers can steer how readily it searches through a system prompt.

Anthropic doesn't publish a rule for any particular question. "Best invoicing app for a two-person design studio" could be answered either way, so the only reliable approach is to test your own.

Does Claude recommend from memory or from search?

Claude answers from training data Claude answers with web search
What decides it What the model learned before its training cutoff The pages Claude retrieves and cites right now
How fast you can change it Only with a future model As soon as a page is crawled and relevant
What you can do Be consistently and widely described on the public web. Leave ClaudeBot allowed if you want future training to include your pages Allow Claude-SearchBot. Publish pages that answer the question. Get cited by the sources searches return
How to test Ask with web search switched off, or tell Claude not to search Ask it to search the web and read the citations

Anthropic lists a training data cutoff and a reliable-knowledge cutoff for each model in its documentation. Anything newer than the cutoff, Claude can only know by searching. Nobody outside Anthropic can say exactly what a model remembers about your brand, so ask it. If the answer is wrong or empty, that's your memory-path baseline.

Which Anthropic bots should you allow?

Anthropic uses three robots and says all of them honor robots.txt:

Bot What it does If you block it
ClaudeBot Collects web content that could contribute to training Signals that your future content should be excluded from training datasets
Claude-User Fetches a page when someone asks Claude a question Anthropic says it may reduce your visibility for user-directed web search
Claude-SearchBot Navigates the web to improve search result quality Anthropic says it may reduce your visibility and accuracy in user search results

Training is a business decision. Search and user fetches are how you get cited, so allow both unless you have a reason not to. Anthropic also warns that blocking by IP address may not work reliably, because it stops the bots reading your robots.txt. Use robots.txt rules instead, and check them with the free AI Crawler Checker. More in robots.txt for AI crawlers.

How do you get recommended when Claude searches?

The same fundamentals apply as on other engines:

  1. Answer the buyer question on a page of your own, in the first two sentences, with specifics: prices, limits, integrations, a date.
  2. Back claims with sources. In the research that named GEO, citing sources, adding quotations and adding statistics each raised visibility in generative answers by roughly 30 to 40% on its main metric. See what is generative engine optimization.
  3. Get mentioned where searches land. Ask Claude your questions with search on and note the pages it cites. Roundups, review sites and forum threads that name your category are the pages to be on.
  4. Keep facts consistent. If Claude finds three prices for your product, it has to choose.

How do you be remembered when Claude doesn't search?

You can't edit a model, but you can influence what future training data contains. Be described the same way across many reputable pages: your own site, directories and profiles, reviews, articles and forums. Make your name, category and what you do unambiguous. See entity SEO for AI. This is slow, there's no guarantee, and the payoff only arrives with a future model, so treat it as the long game and search as the near-term one.

How do you measure Claude visibility?

Ask each question several times, with search on and with search off, and count how often you're named. Variation is normal: in a 2026 study by SparkToro and Gumshoe, Claude was only slightly more likely than ChatGPT or Google's AI to repeat the same list of brands across 100 runs of one prompt, and even less likely to repeat the same order. Track a share across many answers, not one result.

Citepoint asks Claude once a week through Anthropic's API with a fixed model and web search available, so Claude decides whether to search, as it does in the app. Its answers show you both paths over time: when Claude searched, the sources it cited appear alongside the answer. Run the no-search test yourself now and then to see what the model remembers.

Frequently asked questions

Does Claude always search the web?

No. Anthropic says Claude determines when to search based on the request. It searches for current, changing or unfamiliar information and answers directly for stable knowledge.

How can I tell whether a Claude answer used search?

Claude shows an indicator while it searches, and answers that use search include citations to their sources. You can also ask it to search the web, or not to.

Should I block ClaudeBot?

That's a training decision. Anthropic says blocking ClaudeBot signals that your future content should be excluded from training datasets. Search runs through separate bots, Claude-SearchBot and Claude-User, so allow those if you want to be cited.

Can I make Claude remember my brand?

Not directly. What a model remembers is set by its training data, and Anthropic decides what goes in. The practical lever is being consistently described across many reputable pages, and that only pays off with a future model.

Why does Claude give a different answer each time?

Because answers are generated fresh each time, and lists of recommended brands rarely repeat exactly. In a 2026 study, Claude was only slightly more likely than other engines to repeat the same list. Measure the share of answers that name you over many runs.

Sources

  1. Claude Help Center: Enable and use web search
  2. Claude API docs: Web search tool
  3. Claude Help Center: Does Anthropic crawl data from the web, and how can site owners block the crawler?
  4. Claude API docs: Models overview
  5. SparkToro and Gumshoe: AIs are highly inconsistent when recommending brands or products
  6. Aggarwal et al., GEO: Generative Engine Optimization (arXiv:2311.09735)
  7. Citepoint: How we measure AI visibility (methodology)