agentability

← AI-Readiness Index

comingsoon.net

15/100   F

Audited October 14, 2026 from public surfaces only. Can AI agents discover, read, and act on comingsoon.net? Check by check:

GPTBot: allowed ClaudeBot: allowed Claude-User: allowed PerplexityBot: allowed Google-Extended: allowed CCBot: allowed

CheckFindingPointsResult
A1 llms.txt for AI readers
No /llms.txt found — AI readers get no curated entry point.
0/15 fail
A2 AI crawler access policy
robots.txt allows the major AI crawlers and agents.
15/15 pass
A3 Content readable without a browser
A bot challenge page blocks plain fetches — agents see a wall, not your content.
0/25 fail
A4 Structured data (schema.org JSON-LD)
No machine-readable entity markup on the homepage.
0/15 fail
A5 Sitemap discoverable
No sitemap found.
0/10 fail
A6 Everyday agent tasks reachable from the homepage
None of pricing, support, docs, or legal are linked from the homepage.
0/20 fail
B1 MCP server advertised
No MCP advertisement (bonus check — most sites skip this).
0/5 skip
B2 OpenAPI description published
No OpenAPI document (bonus check — only relevant for APIs).
0/5 skip

What comingsoon.net would have to change

5 checks cost comingsoon.net points. Each one below is the specific remedy for what we measured, not general advice.

  1. llms.txt for AI readers0/15

    Serve a plain-text file at https://comingsoon.net/llms.txt listing the pages an agent most often needs — pricing, docs, support, account management — each as a one-line description and an absolute URL. It is read by an agent arriving cold with no idea of your structure. Fifteen points, and most teams ship it in an afternoon.

  2. Content readable without a browser0/25

    A bot challenge page blocks plain fetches — agents see a wall, not your content. An agent fetches the page and reads what comes back; it does not run your JavaScript. Server-render the main content, or serve the same text to a plain request. This is the heaviest check on the board at 25 points, and the one that most often decides whether an agent can use a site at all.

  3. Structured data (schema.org JSON-LD)0/15

    Add schema.org JSON-LD to the homepage — Organization at minimum, plus Product or Article where they apply. It is how an agent learns what comingsoon.net is without inferring it from prose.

  4. Sitemap discoverable0/10

    Serve https://comingsoon.net/sitemap.xml and point to it from robots.txt. Without it an agent has to guess your URL structure from whatever the homepage happens to link.

  5. Everyday agent tasks reachable from the homepage0/20

    An agent could not reach pricing, support/contact, docs/api, legal/privacy from the comingsoon.net homepage. These are what agents are sent to find most often. Each needs a plain link an agent can follow from the homepage in one hop — not behind a menu that only appears once JavaScript runs, and not solely in a logged-in view.

  6. MCP server advertised0/5

    Optional, and rare — only a handful of the sites we track run one. An MCP server lets an agent act on comingsoon.net through a defined interface instead of scraping it. Advertise it at /.well-known/mcp/server-card.json.

  7. OpenAPI description published0/5

    Optional. If comingsoon.net has a public API, publishing an OpenAPI document at /openapi.json lets an agent call it correctly without a human reading your docs first.

Put this score on your site

The badge reads live from this page, so it updates itself when the score changes. Free, no attribution required beyond the link it already carries.

AI-Ready 15 out of 100 for comingsoon.net

HTML

Markdown

Work on comingsoon.net? Each failed check maps to a concrete fix in the methodology — most ship in under an hour. Scores refresh weekly; request a re-run after you deploy.