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

Free tested startup directories with an MCP server, API and planner for founders
Where to Submit Your Startup is a directory and toolset for founders looking for places to post their startup. It offers a free public list of 949 directories, launch sites, communities, and editorial sites, with real submission results based on personal testing. The platform provides a planner, bundles, a JSON API, and an MCP server and skill for AI assistants like Claude, ChatGPT, Cursor, and Codex. It is designed for startup founders and developers seeking to distribute their products across various web directories and launch platforms.
“Where to Submit Your Startup is a tool and directory providing a tested list of 949 places to submit a startup, alongside an MCP server, JSON API, and planner for founders and AI agents.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model reading this input learns about a public directory containing 949 startup submission sites. The llms.txt file details the available developer integrations, including an MCP server, a JSON API, and agent skills, along with documentation links and the MIT license. The JSON-LD block provides structured list items with specific directory names, URLs, and submission requirements such as prices, wait times, and error conditions. The homepage text primarily consists of a long list of outbound links to various directory websites. All core facts about what is offered, developer interfaces, documentation, and data access are present as text.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing 19 URLs.
Describes itself to machines with schema.org JSON-LD. All 4 pages read pass. The homepage describes itself to machines as CollectionPage, ItemList, ListItem in valid schema.org JSON-LD.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 5 of 5 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 349 of 349 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 53 of 53 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 407 of 407 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. All 4 pages read pass. The homepage has 2 section links, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 15 links across 3 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 100% of links. 1 of 15 descriptions follows the link with something other than ":", the separator the format specifies (`- [name](url): notes`).
Serves markdown at its own URL. No /llms-full.txt and no markdown versions linked from llms.txt. +12.5 with its prompt.
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt in Pro.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
The whole readable base above the line, 19 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of submitmystartup.com
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
50 / 50
3.3 of 3.3 points.
robots.txt is valid, with 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing 19 URLs.
8.3 of 8.3 points.
All 4 pages read pass. The homepage describes itself to machines as CollectionPage, ItemList, ListItem in valid schema.org JSON-LD.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.2 of 4.2 points.
349 of 349 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
53 of 53 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
407 of 407 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
All 4 pages read pass. The homepage has 2 section links, and every one reaches an element on the page.
Agent layer
18.8 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 15 links across 3 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 100% of links. 1 of 15 descriptions follows the link with something other than ":", the separator the format specifies (`- [name](url): notes`).
0 of 12.5 points.
No /llms-full.txt and no markdown versions linked from llms.txt.
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 3611 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 18 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
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.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://submitmystartup.com/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://submitmystartup.com/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://submitmystartup.com/
https://submitmystartup.com/robots.txt
User-agent: * allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
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://submitmystartup.com
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://submitmystartup.com/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://submitmystartup.com/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://submitmystartup.com/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://submitmystartup.com/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://submitmystartup.com/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://submitmystartup.com/
In its category
The prompts in the owner view would take Where to Submit Your Startup to 96, 2nd in its category.
To the prompts →Category average 59. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
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.
More like Where to Submit Your Startup:Directories & AggregatorsMarketingOpen Data & APIsStartups
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Same category
productperch.com
Free product launch platform with a daily schedule for indie makers and open-source projects
Same category
bunny.directory
Startup launch directory with permanent pages and daily rankings
Same category
rankcert.com
Product launch board ranking items on verified domain control rather than upvotes
Same category
mydentify.com
Weekly product leaderboard and directory for discovering indie software by job
Same category
builtbyme.io
Curated product directory and weekly leaderboard for indie makers and solo founders
Do you run submitmystartup.com? Open the owner view → Removing the listing is free. Remove →