Skip to content
Good for Bots

Curated directory of online tools for productivity, creative work, development and AI

Good for Bots: Poor, 38 of 100Get this badge →

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

Scanned

What is HoTools?

HoTools is a directory of online tools. Its homepage presents a curated collection of listings grouped under headings such as Featured, Latest, Other, Chatbot, AI Detector and Open source. Each listing gives a tool name, a short description and tags such as Text to image, Code Assistant, Web and Freemium. The site describes its audience as people looking for productivity boosters, creative utilities or business solutions, and it offers a newsletter with weekly updates on online tools. The listed tools include AI image, video, music and voice generators, coding agents, an SEO platform and a fan wiki for a browser game.

Through a bot’s eyes

“HoTools is an online directory of tools, with listings for AI agents, chatbots, image and video generators, coding assistants and productivity apps, each with a short description and tags. The input gives no pricing, operator or submission details.”

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 text a model reads is almost entirely a list of tool listings. Each entry has a name, a one- or two-sentence description and tag links. Subjects covered include AI agents and chatbots, image, video, voice and music generation, coding assistants, APIs, SEO, email newsletters, web scraping and browser games. The page states that the directory is updated daily and offers a weekly newsletter. Some descriptions include concrete facts, such as a free trial for one image generator, a unified API for over 450 AI models for another, and pay-as-you-go billing for a third. The text does not say what the directory itself costs, who runs it, or how a tool gets listed. No contact details, company name or about text appear in the captured content. Several listings repeat across sections, and the capture was truncated, so later entries were not read.

What stays hidden

The input does not say how tools are chosen or whether listings are paid, sponsored or reviewed, and it gives no way to submit a tool. It does not explain what the directory charges visitors or whether the newsletter costs anything. Contact details and the operator's identity are absent. Because the capture was cut off, the total number of listings and the remaining sections are unknown. Figures inside listings, such as the user numbers given for one chat search site, are the listing authors' own statements and are not checked here.

Good for Bots report

HoTools scores 38 of 100: 38 of the 50 base points, none of the agent layer, no penalties.

Earned

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

38

Still open

Behind the checks below, with prompts in Pro.

28
Penalties0
How scoring works · current methodology →

For the owner of hotools.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

37.7 / 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 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Prompt in Pro →
Passes.

10.2 of 10.2 points.

3 of 4 pages read pass; 1 partly. The page at /about is partly structured: No <h1>, so nothing says what the page is about.

Passes.

8.5 of 8.5 points.

4 of 4 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Fails.

0 of 2.5 points.

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

Prompt in Pro →
Half passes.

1.3 of 2.5 points.

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

Prompt in Pro →
Passes.

1.7 of 1.7 points.

3 of 4 pages read pass. The page at /about declares no canonical URL, in a Link header or a <link> element.

Agent layer

0 / 50

Fails.

0 of 11.3 points.

/llms.txt returns an HTML page rather than markdown.

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 2383 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 800 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 answers with a web page, the way a site answers a path it does not implement, so no API catalog is established.

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 returns an HTML page rather than an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

/.well-known/agent-card.json returns an HTML page rather than an A2A Agent Card.

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 returns an HTML page rather than a key directory.

Not applicable.

Adds +1 to the badge when found.

/.well-known/x402 returns an HTML page rather than an x402 manifest, and no 402 payment challenge was seen.

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 button in the page header
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://hotools.com/

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
0
Refusing training would not change 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
, 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 trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

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

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

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

    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

48th of 51 in Directories & Aggregators

  1. 1Brivoybrivoy.com
  2. 2IndieLaunchindielaunch.dev
  3. 48HoTools · this reporthotools.com

The prompts in the owner view would take HoTools to 71, 17th in its category.

To the prompts →

Category average 63. 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
22 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
3.9 MB
Took
27.5 s
Homepage
800 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
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read
  • /aboutabout · from the sitemap · read

More like HoTools:Directories & AggregatorsProductivityAI & Machine LearningDevelopers

Same category

saascubes.com

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

Same category

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes

Same category

brivoy.com

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

Also AI & Machine Learning

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

Also AI & Machine Learning

dolaai.pro

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

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