Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
Preparing the stored Is Agentic score
coolset-website-preview.vercel.app
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Needs work
Weighted across 16 applicable checks
Needs work
Weighted across 12 applicable checks
Ready with gaps
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist - it must print 404.
On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.
Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
Checks are grouped by relevance for Business sites.
2241 chars, semantic headings (1 H1 + 4 H2s + 9 H3s), 7.2% content ratio
Site accessible to 6 AI agent user-agents
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
Not acceptmarkdown.com compliant: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch")
How to pass
On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.
Nonexistent paths return a real HTTP 404. For full credit, include a short markdown body (site map links, where to look next) so agents can recover.
How to pass
Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist - it must print 404.
"Coolset" search returned 9 results but domain did not appear - brand may be too generic or not indexed
How to pass
Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.
Valid sitemap found at https://coolset-website-preview.vercel.app/sitemap.xml with 242 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block)
3/4 metadata signals present - missing: canonical URL
How to pass
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Organization schema found but missing: contactPoint, address
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
All trust anchor pages verified: About, Contact, Privacy
All 6 measured pages fit an agent context budget (largest ~4K tokens)
Name search surfaced no pages on coolset-website-preview.vercel.app, although developer resources exist on the site (API docs, OpenAPI spec) - weak search indexing or transient search noise
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
NPM package found: vercel - "The command-line interface for Vercel"
Found in ChatGPT app directory: "Vercel"
88% of 242 sampled sitemap entries carry lastmod; newest is 28 day(s) old
Found the llms.txt at https://coolset-website-preview.vercel.app/llms.txt.
The llms.txt is well-formatted: 22 lines with markdown links, 2,066 characters in total.
Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub)
How to pass
Add sameAs links in your JSON-LD structured data pointing to your Wikipedia page, Wikidata entry, GitHub org, and social profiles. This helps AI disambiguate your brand from similarly named entities.
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://coolset-website-preview.vercel.app/api/content/csrd-reporting-best-practices/markdown serves markdown
Code fences balanced across 1 markdown document
OpenAPI spec found at https://coolset-website-preview.vercel.app/openapi.json (version: 3.1.0)
RFC 9727 api-catalog with 1 API link(s) and rfc9727 profile
REST API documentation found at https://coolset-website-preview.vercel.app/api/content. Best-of-protocols score: 7/7.
Onboarding signals described but not verified live: zero-auth access
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
First-party MCP server published by product org (npm, @vercel/mcp-adapter, 42488 score). Add live handshake at /.well-known/mcp for full credit.
How to pass
Build an MCP (Model Context Protocol) server exposing your API as tools. Use Streamable HTTP transport for full score. This lets Claude, ChatGPT, and other AI agents call your product natively.
OpenAPI defines a typed error schema in components.schemas and 4xx/5xx responses reference it
Offset/page-based pagination found in OpenAPI spec - consider migrating to cursor-based pagination for agent friendliness
How to pass
Use a consistent, documented pagination shape on your list endpoints (cursor-based preferred) and define the pagination fields in your OpenAPI response schemas, so agents can page through results without guessing the shape.
CLI tool found on PyPI: vercel-cli
SDK package found only in npm
How to pass
Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json repository/homepage, PyPI Home-Page or project_urls, RubyGems homepage_uri) - this is how agents verify the package is your official SDK.
100% of operations define typed response schemas, 67% use application/json
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
60 native controls, 1 non-native div-soup affordances (98% native).
60/60 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (3 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 3/3 ops with IDs, 3/3 with typed schemas
What does coolset-website-preview.vercel.app do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does coolset-website-preview.vercel.app do and who is it for? Explain it back to me.