Same category
saascubes.com
Curated SaaS directory offering permanent do-follow backlinks for modern software products

Directory where makers launch new products and people upvote and review them
Launchef is a website where new products launch. Makers post what they built, and people try it, upvote, rate and review it. The most upvoted launches lead a weekly leaderboard, and the homepage also shows top launches for the last week and last month. Each launch has its own page with a description, screenshots, topics, ratings, comments and the team behind it. The site is aimed at makers who want to launch a product and at people looking for new products. According to the input, launching is free, and a signed-in account is needed to upvote, comment, rate or launch. Launchef also lists member deals and a directory of topics.
“Launchef is a site where makers post new products and people upvote, rate and review them, with the most upvoted launches leading a weekly leaderboard. Launching there is free.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
The homepage text is mostly navigation labels and placeholder entries. The top-launch lists show 'Sample launch' with the line 'A short line that says what the product does' and zero counts, so the raw page names no real products. It does say the site is a launch platform, with weekly, last-week and last-month leaderboards, a trending list, active discussions, a sponsor slot and a list of 28 sites that feature Launchef. The Markdown version and llms.txt add the actual content: a plain statement of what Launchef is, notes for AI agents, five leading launches with taglines and upvote counts, a list of 20 topics with launch counts, and links to an MCP server, a JSON API, a sitemap and RSS feeds. The JSON-LD adds an organization description, the support email [email protected] and a contact page URL. The statement that launching is free appears only in the Markdown and llms.txt versions.
A model reading only this input cannot tell which products are listed beyond the five leading launches in the Markdown version, nor what any of them costs or does in detail, because the homepage launch entries are placeholders. Member deal terms and any discount amounts are not given. Individual product reception beyond upvote counts is not stated, and the total number of launches is not given on the homepage. Who each launch is for depends on the maker's own description, which is not in the input.
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 at least 200 URLs.
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. 34 of 34 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 118 of 118 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. 124 of 124 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. 3 of 4 pages read pass; 1 partly. The page at /products/1password declares its canonical URL only in a <link> in the body; HTML head processing and Google's guidance expect it in the head.
Section links reach an element on the page. All 4 pages read pass. The homepage has 1 section link, 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 page at /topics 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: 41 links across 5 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 93% of links.
Serves markdown at its own URL. /llms-full.txt serves the site's content as markdown (at least 64 KB).
Serves markdown when asked for it. 3 of 4 pages read pass. Asking the page at /about for markdown still returns text/html.
Declares AI usage preferences. Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.
Advertises machine-readable resources with typed links. All 4 pages read pass. The homepage advertises 2 machine-readable resources: describedby, api-catalog.
States a position on AI crawlers. robots.txt states AI usage preferences, but names no AI crawler individually. +5 with its prompt.
Earned
42 of the 50 base points above the line, 45 of the 50 agent-layer points below it.
2 prompts away
For the owner of launchef.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
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 at least 200 URLs.
0 of 8.3 points.
2 of 4 pages read pass. The page at /topics publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
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.
118 of 118 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.
124 of 124 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
3 of 4 pages read pass; 1 partly. The page at /products/1password declares its canonical URL only in a <link> in the body; HTML head processing and Google's guidance expect it in the head.
0.8 of 0.8 points.
All 4 pages read pass. The homepage has 1 section link, and every one reaches an element on the page.
Agent layer
45 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 41 links across 5 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 93% of links.
12.5 of 12.5 points.
/llms-full.txt serves the site's content as markdown (at least 64 KB).
10 of 10 points.
3 of 4 pages read pass. Asking the page at /about for markdown still returns text/html.
0 of 5 points.
robots.txt states AI usage preferences, but names no AI crawler individually.
2.5 of 2.5 points.
Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.
1.3 of 1.3 points.
All 4 pages read pass. The homepage advertises 2 machine-readable resources: describedby, api-catalog.
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 353 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 246 ms.
Agent capabilities
1 of 11 · no points
Each one found adds +1 to the badge.
+1 on the badge.
Publishes an API catalog describing 6 APIs.
Adds +1 to the badge when found.
/auth.md is published but links neither OAuth protected-resource nor authorization-server metadata, so an agent cannot discover where to authenticate.
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://launchef.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://launchef.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://launchef.com/
https://launchef.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://launchef.com
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://launchef.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://launchef.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://launchef.com/
A preference allowing this use applies to at least one listed identity.
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://launchef.com/
Declared allow · Content-Signal
The applicable crawler group declares these Content Signals. They are separate from permission to fetch and from AIPREF.
Purpose: search; applicable crawler group for https://launchef.com/
https://launchef.com/robots.txt
Content-Signal: search=yes, ai-input=yes, ai-train=yes
A preference allowing this use applies to at least one listed identity.
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://launchef.com/
Declared allow · Content-Signal
The applicable crawler group declares these Content Signals. They are separate from permission to fetch and from AIPREF.
Purpose: ai-use; applicable crawler group for https://launchef.com/
https://launchef.com/robots.txt
Content-Signal: search=yes, ai-input=yes, ai-train=yes
A preference allowing this use applies to at least one listed identity.
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://launchef.com/
Declared allow · Content-Signal
The applicable crawler group declares these Content Signals. They are separate from permission to fetch and from AIPREF.
Purpose: train-ai; applicable crawler group for https://launchef.com/
https://launchef.com/robots.txt
Content-Signal: search=yes, ai-input=yes, ai-train=yes
In its category
The prompts in the owner view would take Launchef to 100, first 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 Launchef:Directories & AggregatorsStartupsCreators
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 Creators
contentspilot.com
AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style
Also Good
dolaai.pro
AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor
Also Good
vouchgeo.com
Tracks how AI assistants mention a brand across multi-question buying conversations
Do you run launchef.com? Open the owner view → Removing the listing is free. Remove →