Skip to content
Good for Bots

TasteDir

tastedir.com

Curated directory of indie-made software tools, each reviewed by hand

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

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

Scanned

What is TasteDir?

TasteDir is a curated directory of software tools built by indie makers and small teams. According to the meta description, each tool is reviewed by hand, and the directory covers AI, developer, design, marketing and productivity tools. The homepage is a list of 28 tool entries, each with a name and a one-line description, linking to an individual listing page under /p/. The input does not say who the directory is for beyond browsing, or how tools are chosen, submitted or priced.

Through a bot’s eyes

“TasteDir is a curated directory of software tools built by indie makers and small teams, with each tool reviewed by hand, covering AI, developer, design, marketing and productivity tools.”

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 a list of 28 tool entries, each giving a product name and a short one-line description. Subjects covered include email platforms, analytics, form builders, developer utilities such as HTTP inspection and local email testing, design tools, notes and task apps, self-hosted AI chat and local models, workflow automation, and clipboard or shell history tools. Several entries say whether the tool is open source, free or self-hosted, and a few mention a free plan. The title and meta description add that the site is a curated directory of indie-made software with each tool reviewed by hand. The JSON-LD block only names the site as TasteDir with its URL, adding nothing beyond the title. No Markdown version or llms.txt was provided, so the homepage list is the only content. Company names, contact details and any description of how the reviews are done are not present as text.

What stays hidden

A model reading only this input cannot tell how tools get into the directory or what the hand review involves, whether the directory itself charges anything, or how to submit a tool or get in touch. Prices of the listed tools are not given, apart from occasional mentions of a free plan, so it cannot tell which listed tools are paid. The input does not say who the directory is intended for beyond browsing, or whether the site has other pages such as an about or contact page.

Good for Bots report

TasteDir scores 37 of 100: 37 of the 50 base points, none of the agent layer, no penalties.

Earned

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

37

Still open

Behind the checks below, with prompts in Pro.

29
Penalties0
How scoring works · current methodology →

For the owner of tastedir.com

3 prompts, 34 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.3 / 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 86 URLs.

Fails.

0 of 8.5 points.

2 of 4 pages read pass. The page at /c/ai publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Prompt in Pro →
Passes.

10.2 of 10.2 points.

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

Half passes.

4.2 of 8.5 points.

21 of 22 assessed homepage navigation links expose usable destinations.

Prompt in Pro →
Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

1.7 of 1.7 points.

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

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 327 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 182 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
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.

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

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

45th of 47 in Directories & Aggregators

  1. 1Brivoybrivoy.com
  2. 2IndieLaunchindielaunch.dev
  3. 45TasteDir · this reporttastedir.com

The prompts in the owner view would take TasteDir to 71, 15th in its category.

To the prompts →

Category average 62. 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
6 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
2.3 MB
Took
40.8 s
Homepage
182 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
  • /blog/postman-alternativesarticle · from the sitemap · read
  • /c/aicollection · linked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · from the sitemap · read

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