Mostly invisible to buyers and agents

59/ 100

D
Grade: 27
Agent readiness
Board average 77 Scanned 17 hours ago

Every outstanding fix in one prompt for your coding agent. Rescan →

Task

What does mentions.so do and how do I use it? A fetch-only agent finds out.

12 fetches4 found8 missing

⋯home

/robots.txt⋯/sitemap.xml
/llms.txt⋯/llms-full.txt
/pricing
/docs
/openapi.json
mcp.json⋯MCP initialize
/privacy · /terms

⋯404 probe

every path the scanner fetched · replayed deterministically, no LLM

Evaluator notes

A fetch-only agent reached mentions.so over HTTPS, though the response was slow and identified it from its title as “Mentions - Get Your Brand Mentioned on Top AIs”. Little of the page survives without JavaScript, so a fetch-only agent sees mostly an empty shell. It found pricing. It looked for docs, an OpenAPI spec and an MCP server and found none.

Critical access needs attention

Whether an ordinary agent can enter, read, and operate the public site.

~
Agents can reach the site
Crawler access and bot defenses.
3 / 4 passed
~
Core content is available
Useful content remains accessible without a fragile browser-only path.
0 / 2 passed
~
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
1 / 2 passed
~
Controls are understandable
Forms and interactive controls expose usable names and structure.
2 / 3 passed

Fix these gaps first

Critical access gaps come first, then the biggest remaining points.

01
OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts
02
Responds in under 1.5sCritical access
Cache the homepage at the edge; aim for under 500 ms.
+5 pts
03
Exactly one H1Metadata
Use one H1 that states the value proposition.
+4 pts
04
Structured data (JSON-LD)Agent-ready
Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
+4 pts
05
Canonical URL setCritical access
Add a canonical link so www/non-www and query variants consolidate.
+3 pts

Audit the checks behind the score

Grouped by what they measure. Not-applicable checks are excluded from scoring.

Crawlable3 of 5 passed · 12/19 pts›

✓Served over HTTPS5/5
https://mentions.so/
✕Responds in under 1.5s0/5
7044 ms to first byte
→ Cache the homepage at the edge; aim for under 500 ms.
✓robots.txt present2/2
User-Agent: * Allow: / Disallow: /api/ Disallow: /visibility-waitlist-data Sitem…
✕sitemap.xml present0/2
no /sitemap.xml
→ Generate a sitemap and reference it from robots.txt.
✓Homepage is indexable5/5
HTTP 200

Metadata5 of 7 passed · 17/24 pts›

✓Title tag 10–70 characters5/5
"Mentions - Get Your Brand Mentioned on Top AIs" (46)
✓Meta description 50–160 characters5/5
"Mentions helps your Brand get recognised by AI Platforms and Increases your Reach." (82)
✕Canonical URL set0/3
no <link rel="canonical">
→ Add a canonical link so www/non-www and query variants consolidate.
✕Exactly one H10/4
3 × <h1>: "Get Your Brand Mentionedon |"
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
width=device-width, initial-scale=1
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
/favicon.ico

Shareable2 of 3 passed · 11/14 pts›

✓Open Graph title, description and image8/8
title, description, image
✓Twitter/X card type set3/3
twitter:card = summary_large_image
✕Links to X or LinkedIn0/3
no X / LinkedIn links found
→ Link your X and LinkedIn so visitors can follow and verify you.

Converts3 of 3 passed · 17/17 pts›

✓Clear call to action8/8
10 CTA(s), e.g. "Get Started"
✓Pricing page linked6/6
→ /#pricing
✓HTML under 2 MB3/3
514 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready6 of 20 passed · 13/48 pts›

✕Structured data (JSON-LD)0/4
no JSON-LD
→ Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
✕Machine-readable pricing0/3
no /pricing page and no Offer JSON-LD
→ Publish prices as text on /pricing (not in images) and add an Offer to your JSON-LD.
✕llms.txt present0/1
no /llms.txt
→ Publish /llms.txt: a short markdown summary of the product, pricing and docs links for AI agents.
✕llms-full.txt present0/1
no /llms-full.txt
→ Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.
✓AI crawlers allowed in robots.txt2/2
none of 9 known AI crawlers blocked
✓No noai / TDM reservation2/2
no opt-out signals
✕Serves markdown on request0/1
Accept: text/markdown → no response
→ Return text/markdown when the Accept header asks for it; agents skip the HTML entirely.
✕OpenAPI spec discoverable0/7
no /openapi.json or /.well-known/openapi.json
→ Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
✕Agent manifest (MCP, A2A or ai-plugin)0/2
no manifest at /.well-known/{mcp,agent,ai-plugin}.json
→ Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
✕Docs or API link from the homepage0/3
no docs / API link and no /docs
→ Link Docs or API from the homepage nav; it is the first thing an integrating agent looks for.
✕Content readable without JavaScript0/3
34,571 chars of visible text, 6.6% of HTML
→ Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
✕Semantic landmarks (main, single H1)0/3
<main> present, 3 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
87/87 images have alt
◐Form fields are labelled1/2
1/2 fields have a label, name or aria-label
→ Give every input a name and a label; an agent filling the form needs both.
✓Descriptive link text2/2
0/18 links say "click here" / "learn more"
✓Agent-friendly 404s2/2
nonexistent path → HTTP 404
✕Trust pages (privacy, terms, security)0/2
none of /privacy, /terms, /security respond
→ Serve /privacy and /terms at those paths; agents deciding whether to use you look for them.
✕Organization schema complete0/2
no Organization in JSON-LD
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
✕llms.txt says what you are and links out0/2
no /llms.txt
→ Start llms.txt with an H1 and one-paragraph summary, then link docs, pricing and API.
✓Contact route discoverable2/2
mailto:, /contact or /support link found

APIn/a›

—Spec parses and declares a versionn/a
—Operations have summaries and operationIdsn/a
—Error responses documentedn/a
—Auth scheme declaredn/a
—Versioned paths or serversn/a
—Spec within a model context budgetn/a

MCPn/a›

—Server answers initializen/a
—Tools listedn/a
—Tools carry descriptionsn/a
—Tool parameters have schemasn/a

Score history

59 17 hours ago
60 yesterday
60 yesterday
70 yesterday

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-24T08:17:22.565Z.

← Back to the board