Skip to content
Good for Bots

Searchable directory of AI tools, SaaS products and productivity apps organised by category

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

AiToolsList.Tools scores 81 of 100: the whole readable base, 31 of the 50 agent-layer points, no penalties.

Earned

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

81

3 prompts away

Copy them below ↓

19
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“AiToolsList.Tools is a directory of about 2,900 AI tools, SaaS products and productivity apps, organised by category and including tool detail pages and a search page.”

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

The homepage text covers a large set of AI and software topics: image and video generators, chatbots, writing and copywriting tools, automation platforms, speech and translation tools, SEO and marketing software, and bookkeeping software. Most of the text is a list of individual tool cards, each with a name, a short one-line description and a category label. Several descriptions include concrete details, such as a per-clip price of $4.99, a starting price of $9.90 and a free tier, but these belong to listed tools rather than to the directory itself. The directory's own pricing, how listings are chosen or who runs the site are not described on the homepage. The llms.txt file adds a short site summary, a list of main pages, a section on how to use the site and a contact email address. The JSON-LD blocks give a WebSite and an Organization entry with the name, URL, description, language and logo. The homepage text itself is cut off before the list ends.

What stays hidden

A model reading this input cannot find out who operates the directory, how tools are selected or ranked, or whether listings are paid placements, since the homepage presents no editorial statement and the llms.txt points to About pages that were not read. It also cannot tell what the Featured tools have in common or how often the directory is updated. The text does not say what the directory itself costs to use.

What is AiToolsList.Tools?

Tools is a website that presents itself as a curated directory of AI tools, SaaS products and productivity apps. The homepage states that it lists 2,914 tools and that it is organised into categories such as Chat, Productivity, Generative Art, Generative Video, Copywriting, Research, Marketing and Finance.

Read more →

txt file, the site is meant for discovering, browsing and comparing software, and it links to individual tool detail pages under /tool/ and to a search page. The homepage also includes a Submit a Tool link, so the site accepts listings from others. Its audience is not stated beyond users who want to find software for writing, automation, images, video, research and business workflows.

3 prompts, 19 points

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

+10score from 81 to 91

Serve Markdown when asked for it

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

Read prompt

+7.5score from 91 to 99

Add descriptions to llms.txt

/llms.txt is a bare link list: 0 of 19 links have a description.

Read prompt

Pro

11 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 →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for AiToolsList.Tools from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

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

Readable base

50 / 50

Passes.

4.3 of 4.3 points.

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

Passes.

10.9 of 10.9 points.

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

Passes.

10.9 of 10.9 points.

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

Passes.

13 of 13 points.

3 of 4 pages read pass; 1 partly. The homepage is partly structured: Only one landmark (complementary) outside the content root.

Not applicable.

0 of 0 points.

No applicable navigation links were observed in the homepage HTML.

Passes.

5.4 of 5.4 points.

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

3.3 of 3.3 points.

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

Passes.

2.2 of 2.2 points.

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

Agent layer

31.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 19 links across 3 sections.

Fails.

0 of 7.5 points.

/llms.txt is a bare link list: 0 of 19 links have a description.

Passes.

12.5 of 12.5 points.

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

Fails.

0 of 10 points.

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

Passes.

5 of 5 points.

States a position on 9 AI crawlers, covering 9 crawlers.

Passes.

2.5 of 2.5 points.

Declares AI usage preferences via Content-Signal (robots.txt): ai-train, search.

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 2237 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 413 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.

/.well-known/api-catalog could not be read, so whether the site publishes an API catalog is unknown.

Not applicable.

Adds +1 to the badge when found.

/auth.md returns an HTML page rather than a markdown document.

Not applicable.

Adds +1 to the badge when found.

/.well-known/ai-catalog.json could not be read, so whether it lists an MCP server card is unknown.

Not applicable.

Adds +1 to the badge when found.

/.well-known/agent-card.json could not be read, so whether the site publishes an A2A Agent Card there is unknown.

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.

/.well-known/http-message-signatures-directory could not be read, so whether the site publishes a Web Bot Auth key directory is unknown.

Not applicable.

Adds +1 to the badge when found.

/.well-known/x402 could not be read, and no 402 payment challenge was seen.

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.

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://aitoolslist.tools/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
9
GPTBot, ClaudeBot, MistralAI-Training and 6 more. Refusing training never changes the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
DiffbotDiffbotSearchRefusedNot scoredUser-agent: diffbot Disallow: /
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingRefusedNone: training opt-outs are neutralUser-agent: gptbot Disallow: /
ClaudeBotAnthropicAI trainingRefusedNone: training opt-outs are neutralUser-agent: claudebot Disallow: /
MistralAI-TrainingMistralAI trainingRefusedNone: training opt-outs are neutralUser-agent: mistralai-training Disallow: /
KimiBotMoonshot AIAI trainingRefusedNone: training opt-outs are neutralUser-agent: kimibot Disallow: /
Applebot-ExtendedAppleAI trainingRefusedNone: training opt-outs are neutralUser-agent: applebot-extended Disallow: /
Google-ExtendedGoogleAI training, GroundingRefusedNone: training opt-outs are neutralUser-agent: google-extended Disallow: /
Meta-ExternalAgentMetaAI training, Product improvementRefusedNone: training opt-outs are neutralUser-agent: meta-externalagent Disallow: /
AmazonbotAmazonAI training, Product improvementRefusedNone: training opt-outs are neutralUser-agent: amazonbot Disallow: /
CCBotCommon CrawlOpen dataset, AI trainingRefusedNone: training opt-outs are neutralUser-agent: ccbot Disallow: /
, all allowed
Agents, extraction and others
bytespiderUnspecifiedNot establishedRefusedNot scoredUser-agent: bytespider Disallow: /
omgiliUnspecifiedNot establishedRefusedNot scoredUser-agent: omgili Disallow: /
anthropic-aiUnspecifiedNot establishedRefusedNot scoredUser-agent: anthropic-ai Disallow: /
claude-webUnspecifiedNot establishedRefusedNot scoredUser-agent: claude-web Disallow: /
cohere-aiUnspecifiedNot establishedRefusedNot scoredUser-agent: cohere-ai Disallow: /
googleotherUnspecifiedNot establishedRefusedNot scoredUser-agent: googleother Disallow: /
baiduspiderUnspecifiedNot establishedRefusedNot scoredUser-agent: baiduspider Disallow: /
petalbotUnspecifiedNot establishedRefusedNot scoredUser-agent: petalbot Disallow: /
awariosmartbotUnspecifiedNot establishedRefusedNot scoredUser-agent: awariosmartbot User-agent: awariorssbot Disallow: /
awariorssbotUnspecifiedNot establishedRefusedNot scoredUser-agent: awariosmartbot User-agent: awariorssbot Disallow: /
Google-CloudVertexBotGoogleExtractionRefusedNot scoredUser-agent: google-cloudvertexbot Disallow: /
qualifiedbotUnspecifiedNot establishedRefusedNot scoredUser-agent: qualifiedbot Disallow: /
cotoyogiUnspecifiedNot establishedRefusedNot scoredUser-agent: cotoyogi Disallow: /
icc-crawlerUnspecifiedNot establishedRefusedNot scoredUser-agent: icc-crawler Disallow: /
atlassian-botUnspecifiedNot establishedRefusedNot scoredUser-agent: atlassian-bot Disallow: /
fishbotUnspecifiedNot establishedRefusedNot scoredUser-agent: fishbot Disallow: /
borderxbotUnspecifiedNot establishedRefusedNot scoredUser-agent: borderxbot Disallow: /
navubotUnspecifiedNot establishedRefusedNot scoredUser-agent: navubot Disallow: /
semrushbot-swaUnspecifiedNot establishedRefusedNot scoredUser-agent: semrushbot-swa Disallow: /
wardbotUnspecifiedNot establishedRefusedNot scoredUser-agent: wardbot Disallow: /
magpie-crawlerUnspecifiedNot establishedRefusedNot scoredUser-agent: magpie-crawler Disallow: /
citibotsitecrawlerUnspecifiedNot establishedRefusedNot scoredUser-agent: citibotsitecrawler Disallow: /
, all allowed

The robots.txt groups behind this table

User-agent: gptbot
Disallow: /

User-agent: claudebot
Disallow: /

User-agent: mistralai-training
Disallow: /

User-agent: kimibot
Disallow: /

User-agent: applebot-extended
Disallow: /

User-agent: google-extended
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: amazonbot
Disallow: /

User-agent: ccbot
Disallow: /

User-agent: bytespider
Disallow: /

User-agent: diffbot
Disallow: /

User-agent: omgili
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: claude-web
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: googleother
Disallow: /

User-agent: baiduspider
Disallow: /

User-agent: petalbot
Disallow: /

User-agent: awariosmartbot
User-agent: awariorssbot
Disallow: /

User-agent: google-cloudvertexbot
Disallow: /

User-agent: qualifiedbot
Disallow: /

User-agent: cotoyogi
Disallow: /

User-agent: icc-crawler
Disallow: /

User-agent: atlassian-bot
Disallow: /

User-agent: fishbot
Disallow: /

User-agent: borderxbot
Disallow: /

User-agent: navubot
Disallow: /

User-agent: semrushbot-swa
Disallow: /

User-agent: wardbot
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: citibotsitecrawler
Disallow: /

User-agent: *
Allow: /
Allow: /

https://aitoolslist.tools/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • 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://aitoolslist.tools/

    robots.txt is present and valid

  • Observed · Direct request

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

    Our request received HTTP 200. A status alone does not identify a WAF.

    Our recorded direct transport attempt; intermediate attempt URLs are not retained

    https://aitoolslist.tools

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

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

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://aitoolslist.tools/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

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

8th of 47 in Directories & Aggregators

  1. 1Brivoybrivoy.com
  2. 2IndieLaunchindielaunch.dev
  3. 8AiToolsList.Tools · this reportaitoolslist.tools

The prompts above would take AiToolsList.Tools to 100, first in its category.

To the prompts ↑

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

Scanned

Site profile

Login
Not established
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
16 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
14.5 MB
Took
16.5 s
Homepage
413 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
  • /pricing/pricing · linked from the homepage · from the sitemap · read
  • /blog/collection · linked from the homepage · from the sitemap · read
  • /about/about · linked from the homepage · from the sitemap · read