A B2B software client in the legal-tech space got their first Claude citation last December and called me almost suspicious about it. "We just got mentioned in a Claude answer about contract review software. We don't think we did anything different — what happened?" I dug in. The answer turned out to be: someone had edited the Wikipedia article on "AI-assisted legal research" three months earlier and included them in a paragraph about contract analysis vendors. That was it. One Wikipedia edit, three months of dormancy, and Claude started citing them. It hasn't stopped since.

That story tells you almost everything you need to know about Claude. It's the most conservative of the major AI models in terms of which sources it'll quote. It loves Wikipedia, official documentation, well-known publications, and academic sources. It is deeply skeptical of marketing-language content from sites it hasn't heard of. If you want to win in Claude, you don't optimize your site harder. You build the kind of off-site authority that makes Anthropic's models comfortable putting your name in an answer.

Let's get into how.

Why Claude is different

Anthropic trained Claude using a technique they call Constitutional AI. The short version: instead of just rewarding the model for helpful answers, they trained it to be cautious about claims it can't verify, to defer to authoritative sources when there's uncertainty, and to be transparent about its confidence level. This trickles all the way down into citation behavior.

In practice, what this means for you:

  • Claude is more likely to write a long, hedged, careful answer than a punchy direct one.
  • When it does cite a source, it heavily favors sources with clear pedigree — major publications, official documentation, Wikipedia, government sites, academic institutions.
  • It rarely cites brand-new domains or single-author blogs unless they're specifically about a niche where they happen to be the canonical source.
  • It will sometimes refuse to make a confident statement at all if the source material isn't strong enough, where ChatGPT might just paraphrase and go.

This isn't a flaw in Claude. It's a deliberate design choice. And it dictates the entire strategy.

The three Anthropic crawlers

Anthropic runs three different web agents you need to know about:

ClaudeBot is the training crawler. Like GPTBot, it ingests open-web content to build training datasets for future Claude versions. Crawled today, used in training months from now.

Claude-Web is the live web search agent. When Claude.ai or the Anthropic API is used with web search enabled and a user asks something current, this is the bot that goes out and fetches pages in real time. Newer than ClaudeBot — Claude's live web search rolled out widely in late 2024.

anthropic-ai is the older general-purpose agent that some Anthropic services still use. You'll occasionally see it in logs. Treat it as a third member of the Anthropic family and allow it.

Your robots.txt should explicitly allow all three:

User-agent: ClaudeBot
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: anthropic-ai
Allow: /

Same caveat as with the ChatGPT playbook: if you're behind Cloudflare or any aggressive WAF, double-check that none of these are being blocked at the edge. The "permissive robots.txt but blocked at the firewall" pattern is sneaky and costs people visibility they don't know they're losing.

Wikipedia is the highest-leverage move (and almost no one does it right)

Here's an uncomfortable truth: a single notable Wikipedia mention will do more for your Claude visibility than six months of blogging on your own site. I have seen this play out repeatedly. The model treats Wikipedia as a primary trust source, and being included in a relevant Wikipedia article is the closest thing to a "verified" badge that exists in the AI world.

But Wikipedia is also where most companies embarrass themselves. The article you're not allowed to write is the one about your own company. Wikipedia's notability and conflict-of-interest policies are strict, and they should be — there's a real reason the encyclopedia is still trusted after 25 years. So your job is not to create a Wikipedia article about yourself. Your job is to become so visibly relevant in your space that you naturally get added to existing articles by neutral editors.

What actually works:

  • Find Wikipedia articles in your industry that should mention you but don't. Industry overview articles ("Software-as-a-service", "Drain cleaning", "Contract management"), category lists ("List of legal tech companies"), event or trend pieces.
  • Build the case for inclusion based on third-party coverage. You need at least 2–3 mentions in reliable secondary sources (real news, industry publications, books) before any editor will add you in good faith.
  • If you have those mentions, request inclusion on the article's Talk page, not by editing directly. Be transparent about your conflict of interest. Provide the sources. Let a neutral editor make the call.
  • If your company has its own article and it's wrong (factually incorrect, outdated, contains promotional language an editor would flag), again — talk page, not direct edit. Provide sources for the corrections.

This is slow. It can take months. You will sometimes get nothing. But the payoff is permanent. A well-placed Wikipedia mention compounds for years, and it's the single most durable AI-visibility asset you can build.

What other sources Claude trusts

Beyond Wikipedia, the other sources I've observed Claude leaning on heavily:

Official documentation. If your company has a docs site (docs.yourcompany.com, help.yourcompany.com), Claude treats it as primary source material — especially for technical and procedural questions. Invest in your docs. Treat them like flagship content, not afterthought. This is one of the highest-ROI uses of writer time for any B2B company I work with.

Major publications. A profile in The Verge, TechCrunch, your industry's flagship trade publication, NYT, WSJ — Claude weights these heavily. Even a single mention can establish you as a real entity in the model's "this is a thing I should consider citing" bucket.

Government and academic sources. If you're in regulated industries (healthcare, finance, legal), being mentioned in agency guidance documents or academic literature carries enormous weight. This is one of those things you can't manufacture — you have to actually be doing work that matters enough for those sources to notice.

Long-running independent blogs with established authors. Patrick McKenzie's blog, Ben Thompson at Stratechery, Marques Brownlee's videos — these are individuals with enough longevity and authority that Claude treats them as credible sources. Getting mentioned in one is a real signal.

Reddit threads with high vote counts on established subreddits. Reddit shows up in Claude's citations more than you'd expect, but only the older, well-moderated subreddits with substantive discussion. A 4-year-old r/sysadmin thread with 800 upvotes is treated very differently than a brand-new post.

Notice what's missing: random small blogs, LinkedIn posts, your own marketing pages. Claude reads them. It just doesn't quote them.

The content shape Claude prefers

When Claude does cite from a smaller site (it does happen — the long tail of cited sources is bigger than people think), there are patterns to what wins. They are not the same as ChatGPT's preferences.

Long-form, structured, sourced. Claude is more comfortable quoting from a 3,000-word piece with 12 internal section headings and inline citations than from a punchy 600-word "10 tips" listicle. The model treats length and structure as a proxy for thoroughness.

Explicit citations and methodology. If your piece says "according to a 2024 study by McKinsey, X is true (link)," Claude is far more likely to use it than the same claim made without attribution. Anthropic's models specifically learned to value explicit sourcing during training.

Honest hedging. Claude likes content that admits uncertainty appropriately. "We saw a 28% improvement in our specific use case, but results vary widely depending on team size" is more quotable than "Our customers see a 28% improvement." This is counterintuitive for marketing — we're trained to be bold — but Claude rewards the qualified version.

Step-by-step procedural content with screenshots/code. Particularly relevant for technical content. A how-to guide with 11 numbered steps, screenshots, and code samples gets quoted more often than a glossy overview.

Author bios with credentials. An article by "Dr. Sarah Chen, infectious disease epidemiologist at Johns Hopkins" gets cited more than one by "the Acme Pharma team." Claude is pulling on the author's name and credentials, not just the article body. Make sure your authors have real bios with real credentials and real schema markup.

The developer-tool lane (a major opportunity)

Claude is the dominant LLM inside developer tools right now. Cursor, the AI code editor that's exploded in 2025, uses Claude as its default brain. Many of the popular Slack AI integrations use Claude. The Anthropic API powers a long list of internal "AI assistants" at companies that don't make their tooling public.

This means there's a specific lane that's underexploited: getting your technical content cited inside developer workflows. If you make a developer tool, library, or API, your docs being well-structured and accessible to ClaudeBot directly affects how often developers building with Claude end up using your product.

Specific tactical implications:

  • Publish a clean /llms.txt at the root of your docs site. Specifically point Claude at your most important reference pages. Most docs sites still don't have this.
  • Make sure your API reference pages render server-side. A docs site that requires JavaScript to render is a docs site that Claude can't index.
  • Include working code examples in standard languages (Python, TypeScript, Go) on every API endpoint page. Claude will quote them verbatim into a developer's IDE if they ask about your API.
  • Maintain a public changelog with dates. Claude uses this to figure out what version of your API it's talking about.

If you sell to developers, this is probably the single highest-ROI work you can do this year.

Schema and structured data for Claude

Claude respects standard schema.org markup, but it cares about different fields than ChatGPT does.

Strong author + Person objects. Bylines matter. Credentials matter. sameAs links to verifiable profiles (LinkedIn, university faculty page, official company role page) help a lot. Anonymous content gets discounted hard.

citation field on Article markup. If your piece cites studies, papers, books — add them to the citation field. This is rare on the web and Claude appears to give it real weight when present.

Organization with sameAs. Verify your company's identity by linking out to your LinkedIn, Crunchbase, official company filings, etc. Helps Claude confirm you're a real entity worth citing.

FAQPage. Same as ChatGPT and Gemini — Claude eats this format.

What I'd skip: speakable schema, video object schema (unless it's specifically a how-to video that should be marked up), product schema (unless you're e-commerce, where it's table-stakes).

The honest answer about timeline

Claude is the slowest of the three to start citing you. ChatGPT can pick up changes within days because OAI-SearchBot is aggressive. Gemini moves on roughly weekly cycles. Claude tends to lag — I've seen new sites take 8–12 weeks to start appearing in citations even after they've done everything right.

The reason: Claude's web search is more conservative about source selection, and the "trust signal accumulation" takes time. Wikipedia mentions need to age. Industry coverage needs to be cross-referenced. Author credentials need to be verifiable through multiple sources.

This is frustrating in the short term but valuable in the long term. Sites that win Claude citations tend to keep them. The model doesn't randomly drop them like search-engine rankings sometimes do. Once you're in, you're in for a while.

How to actually track Claude visibility

Tracking Claude is the hardest of the three. Anthropic has not shipped any equivalent of Google Search Console, OpenAI doesn't expose much through ChatGPT yet, but Anthropic exposes basically nothing. You're flying mostly blind. Here's what I do anyway.

Server logs are your only direct signal. Look for hits from ClaudeBot, Claude-Web, and anthropic-ai user agents. Claude-Web hits are the most interesting because they're live — they happen when an actual user asks Claude a question and Claude fetches your page to answer it. If you see a Claude-Web hit, someone just got cited content from your page in a conversation with Claude. Track which URLs get hit most. That's your real ranking signal.

Manual queries, weekly. Open Claude.ai with web search enabled. Run 10 queries you should rank for given your industry and content. Note which sources Claude cites. If you're not in them, note who is. That's your gap analysis. Do this every Friday for two months and you'll have a real picture of where Claude is and isn't placing you.

Wikipedia and citation tracking. If you have or could plausibly have Wikipedia mentions, set up Google Alerts for your brand name on site:en.wikipedia.org. Any time you get added or removed, you'll know. This is the leading indicator for Claude citation changes — Wikipedia moves first, Claude follows.

Backlink monitoring. Use Ahrefs, Semrush, or even Google Search Console's links report to watch for new mentions on authoritative domains. New high-authority backlinks are the second-best predictor of Claude citation lift after Wikipedia.

Be patient with this data. Where ChatGPT shows you wins or losses within a week, Claude reveals itself over a quarter. The good news is that the wins you see are the wins you keep.

The Claude.ai vs API distinction nobody talks about

One more thing worth knowing. "Claude" is actually a family of models accessed through three different surfaces, and the citation behavior is meaningfully different across them.

Claude.ai is the consumer chat product. Web search is opt-in. When it's on, Claude cites with linked sources. This is the surface most people mean when they say "Claude."

The Anthropic API is what developers call directly to build their own products. By default, no web search. The model answers from training only. This means "showing up in the Claude API" really means showing up in the training data — the long-horizon game.

Claude in third-party tools (Cursor, Slack apps, Notion AI in some configurations) varies wildly. Some enable web search via Anthropic's tools, some don't. Some bring their own retrieval over your docs. You can win the tool's specific retrieval lane independent of winning Claude.ai.

The tactical takeaway: optimize for Claude.ai if you want fast feedback, optimize for training data (the slow, durable work) if you want long-term reach across all three surfaces. Most clients I work with do both, weighted toward training.

The 30-day Claude plan

Same format as the other playbooks. Here's the exact order I'd attack this in.

Week one — access and identity. Allow ClaudeBot, Claude-Web, and anthropic-ai in robots.txt. Check your firewall isn't silently blocking them. Add or strengthen the Organization schema on your site with sameAs links to LinkedIn, Crunchbase, and your official social profiles. Make sure every blog post has a real author byline with a Person schema and credentials.

Week two — Wikipedia and authority. Identify the 3–5 Wikipedia articles where you should be mentioned and aren't. Assess whether you have the third-party coverage to support inclusion. If yes, draft a Talk page request. If no, identify the 3–5 publications you could realistically pitch and start that process. This is the long game — start it now.

Week three — content depth. Pick your three highest-traffic pages. Rewrite each to be longer, more sourced, and more honestly hedged. Add inline citations to real third-party sources. Add a 6–10 question FAQ at the bottom of each. Make sure the author has a real bio block.

Week four — developer surface (if relevant). If you have any developer-facing content, publish an llms.txt at the root of your docs site pointing Claude at your most important reference pages. Verify your docs render server-side. Make sure your changelog is public with dates.

Then wait. Claude citations take longer than the others. Run manual queries every few weeks. Be patient.

The closing argument

I'll be honest with you. If you came to AI search optimization expecting quick wins, ChatGPT is your easiest target. Gemini is the second easiest if your Google SEO is already strong. Claude is the hardest — but it rewards the kind of work that doesn't go out of fashion, doesn't get penalized by algorithm updates, and doesn't require ongoing content treadmills.

You can't game your way into Claude citations. The model is specifically designed to resist that. The only thing that works is becoming the kind of source it makes sense to cite — which is, conveniently, also the kind of business that does well in any market in any decade. Wikipedia entries, real authors with real credentials, careful sourced content, mentions in trusted publications, accurate docs.

It's old-fashioned. It compounds. It's worth it.

Start with the robots.txt additions and the author bios this week. Start the Wikipedia and publication process this month. Check back in three months and see what's moved.

This piece will be kept up to date as Anthropic ships new Claude features and citation behavior changes. Last updated May 21, 2026.