Skip to content
Good for Bots
Good for Bots: Fair, 48 of 100Get this badge →

On your homepage, it turns this report’s link to brivoy.com dofollow.

Scanned

Good for Bots report

brivoy.com scores 48 of 100: 29 of the 50 base points, 19 of the 50 agent-layer points, no penalties.

Earned

29 of the 50 base points above the line, 19 of the 50 agent-layer points below it.

48

Still open

Behind the checks below, with prompts in Pro.

19
Penalties0
How scoring works · current methodology →

For the owner of brivoy.com

3 prompts, 32 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

28.8 / 50

Passes.

3.4 of 3.4 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.5 of 8.5 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

Fails.

0 of 8.5 points.

None of the 3 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Prompt in Pro →
Fails.

0 of 10.2 points.

None of the 3 pages read pass. The homepage is barely structured: No <main> element and nothing carrying role="main".

Passes.

8.5 of 8.5 points.

8 of 8 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

356 of 356 assessed homepage links and buttons have a nonempty accessible name.

Fails.

0 of 2.5 points.

0 of 1 assessed homepage form fields meet the static naming and field-semantics checks.

Prompt in Pro →
Passes.

2.5 of 2.5 points.

360 of 360 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 3 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

18.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 79 links across 6 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 91% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 3 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1364 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 721 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

The ACP discovery document could not be read, so support is unknown.

Not applicable.

Adds +1 to the badge when found.

The UCP discovery document could not be read, so support is unknown.

Not applicable.

Adds +1 to the badge when found.

AMP discovery could not be established from the public documents we could read. Support is unknown.

Site profile

Login
Detected
A sign-in or sign-up link
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://brivoy.com/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://brivoy.com/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://brivoy.com/

    https://brivoy.com/robots.txt

    User-agent: *

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
7 Nov 2026
Rubric
0.9.0
Requests
22
Fetched
763.4 KB
Took
17.2 s
Homepage
721 ms · direct
Pages read
3
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /product/submitproduct · linked from the homepage · not read: robots.txt disallows it
  • /blogcollection · linked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · from the sitemap · read

Also Fair

volanea.com

Transactional email, campaigns, and automation API with AI agent support

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Fair

opensourcefeed.org

Gallery and news updates for open-source operating systems and desktop environments

Also Fair

launchy.tools

Curated weekly product launch platform and directory

Do you run brivoy.com? Open the owner view → Removing the listing is free. Remove →