Skip to content
Good for Bots

ToolRoots

toolroots.com

Directory of local software alternatives organized by country and region

Good for Bots: Fair, 49 of 100Get this badge →

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

Scanned
Tags
B2BB2CStartups

What is ToolRoots?

ToolRoots is a directory that lists local alternatives to widely used software tools. It organizes products by their country of origin and hosting region. Visitors can browse software categorized by countries such as France, Germany, the United States, and the United Kingdom, or search for substitutes to specific platforms like QuickBooks, Stripe, AWS, and Mailchimp. The site provides submission options for tool creators, offering a free listing tier tied to a homepage badge installation as well as a premium tier.

Through a bot’s eyes

“ToolRoots is a directory of local software alternatives categorized by country of origin and hosting region.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns that ToolRoots is a platform for discovering regional software alternatives. The text provides a list of featured tools with their countries of origin and hosting locations, browsing categories by country and hosting region, and alternative groupings for popular platforms. Contact details including an email address are found within the provided JSON-LD blocks. While the homepage outlines submission steps and free versus premium options, exact numerical pricing figures are omitted from the text input. The provided JSON-LD schema adds organization data, a website description, an item list of recent tools, and truncated FAQ entries about finding and listing tools.

What stays hidden

The input does not state the exact monetary cost of the premium tier or provide full answers to the frequently asked questions regarding listing details due to truncation in the JSON-LD block.

Good for Bots report

ToolRoots scores 49 of 100: 49 of the 50 base points, none of the agent layer, no penalties.

Earned

49 of the 50 base points above the line, none of the agent layer below it.

49

Still open

Behind the checks below, with prompts in Pro.

17
Penalties0
How scoring works · current methodology →

For the owner of toolroots.com

3 prompts, 33 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

48.7 / 50

Passes.

3.5 of 3.5 points.

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

Passes.

8.8 of 8.8 points.

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

Passes.

8.8 of 8.8 points.

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

Passes.

10.5 of 10.5 points.

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

Passes.

8.8 of 8.8 points.

22 of 22 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

227 of 227 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.

Half passes.

1.3 of 2.6 points.

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

Prompt in Pro →
Passes.

1.8 of 1.8 points.

3 of 4 pages read pass; 1 partly. The page at /browse 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

0 / 50

Fails.

0 of 11.3 points.

No /llms.txt on this site.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
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 4 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 421 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 199 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.

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://toolroots.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://toolroots.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://toolroots.com/

    https://toolroots.com/robots.txt

    User-agent: *
    allow: /

    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.

In its category

16th of 24 in Directories & Aggregators

  1. 1SwipeToLaunchswipetolaunch.com
  2. 2SaaS Cubessaascubes.com
  3. 16ToolRoots · this reporttoolroots.com

The prompts in the owner view would take ToolRoots to 82, 3rd in its category.

To the prompts →

Category average 59. The percentile appears once the catalogue holds a few hundred sites.

Scan details

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

Scanned
24 Oct 2026
Rubric
0.9.0
Requests
23
Fetched
4.5 MB
Took
14.9 s
Homepage
199 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
  • /browsecollection · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · read
  • /aboutabout · linked from the homepage · read

More like ToolRoots:Directories & AggregatorsB2BB2CStartups

goodforbots.com

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

Same category

submityourstartup.now

Open launch directory for early-stage founders to submit startups and get discovered

Same category

remoteornothing.com

Fully remote job board with region and salary filters sourced from employer career pages

Same category

websoftreview.com

Curated software reviews and daily launches of web tools and SaaS products

Same category

launchy.tools

Curated weekly product launch platform and directory

Same category

shipboost.io

Weekly launch boards and listings for bootstrapped SaaS founders

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