Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to get Claude to recommend your brand

Claude recommends brands it can read. Its live answers pull from the Brave search index, which reads pages as server-rendered HTML. If your product content only appears after JavaScript runs, Brave sees an empty page and Claude recommends a competitor with readable pages instead. The fix is making your site legible as plain HTML.

**One warning first:** there is no way to submit your brand to Claude. Anyone selling guaranteed placement is selling something they do not control.

## Why Claude skips your brand

Claude's failure modes are its own:

1.  JavaScript shells are invisible. Headless storefronts and heavy client-side rendering are the single most common reason Claude misses a brand. The crawler is not blocked; there is simply nothing to read.
2.  Three crawlers, three jobs. ClaudeBot feeds training data, Claude-SearchBot builds the search index, and Claude-User fetches pages live when someone asks a question. Most guides conflate them. Blocking ClaudeBot alone only opts you out of training; it is Claude-SearchBot and Claude-User that control whether you appear in answers.
3.  Thin pages lose. Brave rewards clear heading structure and text facts. Specs trapped in images, one-line product descriptions, and missing H1s all read as nothing.

## Step 1: Allow both crawlers

Check \[yourdomain.com\]/robots.txt, replacing yourdomain.com with your actual domain. If nothing loads, create the file at the root of your site. Then add near the top, before any broad disallow rules:

```
User-agent: ClaudeBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /
```

All three respect robots.txt, and they do different jobs: ClaudeBot trains the model, Claude-SearchBot builds the search index, Claude-User fetches your page at answer time. If you only allowlist the first two, Claude can know about you but can never re-check your current prices. Then check the edge, because the file is what you declare and the edge is what enforces: Cloudflare Bot Fight Mode and WAF bot rules block ClaudeBot even when robots.txt allows it. After a few days, verify in your logs:

```
grep -i "claudebot\|claude-searchbot\|claude-user" /var/log/nginx/access.log
```

## Step 2: Serve real HTML

This is the step that matters most for Claude and the one the ranking guides skip. View source on a product page: if the price, description, and specs are in the HTML, you are fine. If they only appear after JavaScript executes, Brave indexes an empty shell.

-   One clear H1 per page, with H2s that match the questions buyers ask. Claude rewrites queries behind the scenes; headings that mirror those questions get matched.
-   Price, materials, dimensions, and availability as text, never trapped in images.
-   Stable product URLs. Frequently changing URLs fragment your index presence.

You do not need to rebuild the site. Most platforms can serve pre-rendered HTML to crawlers without changing what shoppers see.

### A hypothetical, to make it concrete

Say you run a home-goods store on a headless storefront. The site looks beautiful and ranks on Google, which renders JavaScript. But Brave does not, so Claude's index holds empty shells of your product pages. A scan would flag it in one pass: ClaudeBot allowed, pages unreadable. The fix is server-side rendering on the product templates, not a redesign. After that, the same pages Claude could not see become citable.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •llms.txt: the file format, a complete sample, and per-platform publish steps, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •Product schema: the JSON-LD markup that lets Claude verify price and stock, see our [product schema guide for AI search](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •Every AI crawler in one reference table, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

## What this guide does not cover

Readability gets you into Claude's answers. Staying there takes monitoring: Brave re-indexes on its own schedule and your catalog drifts. And answers are not orders; the transaction layer is separate work.

For the ChatGPT version of this playbook, see our guide to getting ChatGPT to recommend your brand.

## Frequently Asked Questions

Does Claude use its own search index to find brands?

Claude relies heavily on Brave Search as its search provider rather than running its own universal index. Having strong visibility and clean indexation in Brave Search is critical for Claude recommendations.

Can Claude execute JavaScript to render my catalog pages?

No. Claude cannot execute JavaScript when fetching pages during web search. If your product descriptions or pricing require client-side hydration, Claude sees an empty shell.

Which crawler token should I allow in robots.txt for Claude?

You should address Claude-SearchBot for search indexing and Claude-User for real-time query retrieval. ClaudeBot handles training data collection and can be managed independently.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows exactly where Claude stands with your site: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)