Same category
submityourstartup.now
Free weekly launch directory where early-stage founders list startups and are ranked by votes
Startup launch directory with permanent pages and daily rankings
bunny.directory is a startup directory that provides permanent product pages for newly launched projects. Aimed at founders, builders, and developers, it offers free listings where products climb daily rankings based on community engagement and carrots. The directory features a ranked launch feed, category browsing, builder leaderboards, and free tools such as an llms.txt generator and a startup launch checklist. Listings include do-follow links to the submitted products under the condition that a site badge is displayed on the target website.
“bunny.directory is a startup directory where founders can launch products for free, maintain a permanent page, and climb daily rankings through community engagement.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model reading this input learns about a startup launch directory and its submission guidelines. The homepage markdown details current product rankings, categories like AI and SaaS, top builders, a FAQ section explaining the ranking and streak mechanics, and free guides. The provided llms.txt file adds concrete technical instructions for submitting via an MCP client at a specific API endpoint, along with direct URLs for RSS feeds and site pages. Facts such as pricing are explicitly covered by stating that launching is free. Contact details and legal terms are absent, but submission requirements, badge conditions, and API connection pathways are fully outlined in the text.
The input does not state who owns or operates bunny.directory, nor does it provide direct contact information or support email addresses for the directory itself.
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 53 URLs.
Content is marked up so a reader can find it. 3 of 4 pages read pass; 1 partly. The page at /blog is partly structured: The outline jumps from h1 to h3, which the standard forbids.
Navigation links expose usable destinations. 7 of 7 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 296 of 296 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 297 of 297 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. Both pages read pass. The homepage has 4 section links, and every one reaches an element on the page.
Describes itself to machines with schema.org JSON-LD. 2 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa. +8.3 with its prompt.
llms.txt is present and well formed. /llms.txt is well formed: 15 links across 2 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is partly descriptive: only 47% of links carry a description. Every description follows the link with something other than ":", the separator the format specifies (`- [name](url): notes`). +3.8 with its prompt in Pro.
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 in Pro.
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
42 of the 50 base points above the line, 15 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 bunny.directory
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
41.7 / 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 53 URLs.
0 of 8.3 points.
2 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
10 of 10 points.
3 of 4 pages read pass; 1 partly. The page at /blog is partly structured: The outline jumps from h1 to h3, which the standard forbids.
4.2 of 4.2 points.
296 of 296 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
1 of 1 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
297 of 297 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.
Both pages read pass. The homepage has 4 section links, and every one reaches an element on the page.
Agent layer
15 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 15 links across 2 sections.
3.8 of 7.5 points.
/llms.txt is partly descriptive: only 47% of links carry a description. Every description 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 990 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 186 ms.
Agent capabilities
0 of 10 · 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.
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://bunny.directory/
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://bunny.directory/
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://bunny.directory/
https://bunny.directory/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://bunny.directory
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://bunny.directory/
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://bunny.directory/
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://bunny.directory/
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://bunny.directory/
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://bunny.directory/
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://bunny.directory/
In its category
The prompts in the owner view would take bunny.directory to 88, 4th in its category.
To the prompts →Category average 62. 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 bunny.directory:Directories & AggregatorsWeb DevelopmentOpen Data & APIsStartups
Same category
submityourstartup.now
Free weekly launch directory where early-stage founders list startups and are ranked by votes
Same category
saascubes.com
Curated SaaS directory offering permanent do-follow backlinks for modern software products
Same category
brivoy.com
Community site where makers launch new products and early adopters discover them
Also Web Development
volanea.com
Transactional email, campaigns, and automation API with AI agent support
Also Fair
talhabashir.com
Free online calculators and tools for US taxes, mortgages, business and personal finance
Also Fair
interviewace.online
Real-time AI answer suggestions for job candidates during live video interviews
Do you run bunny.directory? Open the owner view → Removing the listing is free. Remove →