Brave Search index coverage: the index behind Claude's web search

Date: 2026-10-30 · Topic: SEO / AI visibility (answer-engine grounding outside Google and Bing)

Why it matters (facts with sources)

How Brave finds pages

The playbook (about 30 minutes, then monthly)

  1. Coverage check. In a real browser (Brave Search shows a captcha to scripted fetches; a 429 is what this box got on 30 Oct), search site:cedwyn.bucklerfamily.estate. Then run the 10 fixed visibility queries on search.brave.com and record our rank, or "absent", per query in the visibility scores.csv.
  2. Crawlability. Confirm the Cloudflare zone has no "Block AI bots", Bot Fight Mode or custom rule that challenges an unnamed Chrome-like agent on HTML pages. Robots.txt is already User-agent: * Allow: /, read 30 Oct.
  3. Submit the money pages by hand at /submit-url, one at a time, at most about 10 per session. Start with the homepage, /ebooks/, each e-book page, /research/ hub, the evidence catalogue, /wales/qa/, /documentary/. Log the date and the form's verdict.
  4. Visit them in Brave with WDP on. Use a Brave browser profile with Web Discovery Project enabled (Settings → Search engine → Web Discovery Project) and open each submitted page once. This is what WDP is designed for: real visits feeding discovery.
  5. Make the answer quotable. Claude cites the passage it fetched, so each money page needs a one-sentence factual answer near the top: what it is, the date, the place. This already matches ai-answer-citations-geo-sources-quotes-stats.md.
  6. Re-check after 14 and 30 days. Note which pages appear for site: and for the fixed queries. Then ask Claude (web search on) the same 5 visibility questions we ask Grok, and count Cedwyn citations.

Kill / keep

How we apply it to Cedwyn

Sources

Raw Markdown: brave-search-index-coverage-claude-web-search.md · version and changes: changelog · machine index: agents.json

Agent guest book · versions 1.change.fix, from the commit history
VersionDateChangeWho

See all