Ready with a few material gaps

80/ 100

B
Grade: 70
Agent readiness
Board average 77 Scanned 14 hours ago

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

Task

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

12 fetches8 found4 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 n8n.io over HTTPS in 84 ms and identified it from its title as “AI Workflow Automation Platform - n8n”. The copy is readable without JavaScript (103,575 chars of visible text, 29.4% of HTML). It found pricing and docs. It looked for 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.
4 / 4 passed
~
Core content is available
Useful content remains accessible without a fragile browser-only path.
1 / 2 passed
✓
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
2 / 2 passed
✓
Controls are understandable
Forms and interactive controls expose usable names and structure.
2 / 2 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
Meta description 50–160 charactersMetadata
Add a meta description between 50 and 160 characters.
+5 pts
03
Exactly one H1Metadata
Use one H1 that states the value proposition.
+4 pts
04
Semantic landmarks (main, single H1)Critical access
Wrap the content in <main> and keep one H1 so agents can find the primary content.
+3 pts
05
Favicon declaredMetadata
Add a favicon; it is what shows in tabs, bookmarks and directories.
+2 pts

Audit the checks behind the score

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

Crawlable5 of 5 passed · 19/19 pts›

✓Served over HTTPS5/5
https://n8n.io/
✓Responds in under 1.5s5/5
84 ms to first byte
✓robots.txt present2/2
User-agent: * Disallow: /cdn-cgi/ Sitemap: https://n8n.io/sitemap_index.xml
✓sitemap.xml present2/2
/sitemap.xml → 200
✓Homepage is indexable5/5
HTTP 200

Metadata4 of 7 passed · 13/24 pts›

✓Title tag 10–70 characters5/5
"AI Workflow Automation Platform - n8n" (37)
✕Meta description 50–160 characters0/5
"n8n is a workflow automation platform that uniquely combines AI capabilities with business process a…" (184)
→ Add a meta description between 50 and 160 characters.
✓Canonical URL set3/3
https://n8n.io/
✕Exactly one H10/4
no <h1>
→ Use one H1 that states the value proposition.
✓Mobile viewport set3/3
width=device-width, initial-scale=1.0, maximum-scale=2.0, user-scalable=1
✓Language declared2/2
<html lang="en">
✕Favicon declared0/2
no <link rel="icon">
→ Add a favicon; it is what shows in tabs, bookmarks and directories.

Shareable3 of 3 passed · 14/14 pts›

✓Open Graph title, description and image8/8
title, description, image
✓Twitter/X card type set3/3
twitter:card = summary
✓Links to X or LinkedIn3/3
12 social link(s)

Converts3 of 3 passed · 17/17 pts›

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

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready13 of 19 passed · 32/46 pts›

✓Structured data (JSON-LD)4/4
@type: Organization
✓Machine-readable pricing3/3
/pricing lists prices as text
✓llms.txt present1/1
/llms.txt → 200, 1154+ chars
✕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 → text/html; charset=utf-8
→ 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 homepage3/3
homepage links to docs / API
✓Content readable without JavaScript3/3
103,575 chars of visible text, 29.4% of HTML
✕Semantic landmarks (main, single H1)0/3
no <main>, 0 × <h1>
→ Wrap the content in <main> and keep one H1 so agents can find the primary content.
✓Images have alt text2/2
127/127 images have alt
—Form fields are labelledn/a
✓Descriptive link text2/2
0/90 links say "click here" / "learn more"
✓Agent-friendly 404s2/2
nonexistent path → HTTP 404
✓Trust pages (privacy, terms, security)2/2
found: /privacy, /terms, /security
◐Organization schema complete2/2
Organization has name, url, logo, sameAs
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
✓llms.txt says what you are and links out2/2
1154+ chars, has H1, has links
✓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

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-24T13:49:00.443Z.

← Back to the board