Skip to content
Good for Bots

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

kamero.ai scores 96 of 100: the whole readable base, 46 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 46 of the 50 agent-layer points below it.

96

2 prompts away

Copy them below ↓

4
Penalties0
How scoring works · current methodology →

3 prompts, 4 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

+2.5score from 96 to 99

Declare AI usage preferences

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

Read prompt

+1 capabilitybadge capabilities from 0 to 1

Publish an API catalog

No API catalog published.

Read prompt

Pro

10 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

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

Readable base

50 / 50

Passes.

3.6 of 3.6 points.

robots.txt is valid, with 10 user-agent groups.

Passes.

8.9 of 8.9 points.

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

Passes.

8.9 of 8.9 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, ImageObject, Person in valid schema.org JSON-LD.

Passes.

10.7 of 10.7 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.9 of 8.9 points.

11 of 11 assessed homepage navigation links expose usable destinations.

Passes.

4.5 of 4.5 points.

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

Not applicable.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

Passes.

2.7 of 2.7 points.

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

Passes.

1.8 of 1.8 points.

3 of 4 pages read pass; 1 partly. The page at /blog declares its canonical URL only in a <link> in the body; HTML head processing and Google's guidance expect it in the head.

Agent layer

46.3 / 50

Passes.

11.3 of 11.3 points.

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

Passes.

7.5 of 7.5 points.

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

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (13 KB).

Passes.

10 of 10 points.

All 4 pages read pass. The homepage serves markdown on `Accept: text/markdown`.

Passes.

5 of 5 points.

States a position on 8 AI crawlers, across 3 purposes (training, user-fetch, search).

Fails.

0 of 2.5 points.

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

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 1882 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 713 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.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

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://kamero.ai/

Declared crawling rules

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

Sources and scope: declared crawling rules

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.
Scanned

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.

Scan details

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

Scanned
6 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
4 MB
Took
51.8 s
Homepage
713 ms · direct
Pages read
4
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
  • /photography-website-builderarticle · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read

Also Excellent

brivoy.com

Community site where makers launch new products and early adopters discover them

Also Excellent

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 Excellent

contentspilot.com

AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations