Loading the report. A first-ever scan of a domain runs live against the site and takes about ten seconds.
ctpedia.org
scanned 8/3/2026, 10:24:59 PM · cached · refresh in 22h · rubric 2026.10.4
At risk
This is how AI agents (not browsers) experience ctpedia.org. The score weights five categories of machine-readability; the ticks on the arc are the 36 individual checks behind it.
Send this to whoever edits the site. The link shows the score and grade as a preview card, and it stays current: it re-reads the latest scan rather than freezing today’s number.
Top fixes
failSitemap present+5 ptsDiscoverabilityNo reachable sitemap.xml. Publish one and reference it in robots.txt.
Show me exactly what to do
What this means
A sitemap is a machine-readable list (sitemap.xml) of every page on your site. It is how crawlers find pages that aren’t linked from your homepage.
Why it matters
Agents discovering your site crawl outward from the pages they know. Without a sitemap, anything not linked from a top-level page (docs, older articles, product variants) may simply never be read, so it can’t be quoted or recommended.
Do this
- Most platforms generate one automatically: Next.js (app/sitemap.ts), WordPress (Yoast/Rank Math), Shopify and Wix (built in). Turn it on rather than hand-writing.
- Add a "Sitemap: https://yoursite.com/sitemap.xml" line to robots.txt so crawlers find it.
- Submit it once in Google Search Console and Bing Webmaster Tools for the search side.
Don’t lose this report
Get it in your inbox now, plus a heads-up whenever ctpedia.org’s agent-readiness score changes. Free, unsubscribe anytime.
Prefer we just watch it for you? Monitor rescans weekly and emails what changed, $29/mo. Start monitoring →
Fix it
Generated, ready-to-ship files for the gaps above. Copy them, or download and drop them into your repo.
This scan graded one page. Your site is more than one page.
This graded your homepage. Your pricing, docs, and checkout live on other pages: the ones assistants actually quote when they recommend you. A 49/100 here means agents are already missing things on the page you polish most. The $29 Deep Scan audits the whole site against all 36 checks, then emails a PDF with every failing check and its exact fix, ranked by what costs you the most visibility. One-time, delivered in minutes, no subscription.
What the agent receives
Show your score
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/ctpedia.org"><img src="https://agentspeed.com/badge/ctpedia.org" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when ctpedia.org’s agent-readiness actually changes: a check regressing, or the composite dropping.
Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.
Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.
This score says whether an AI agent could read ctpedia.org. AI traffic analytics says whether one actually came, and which pages turned it away.
Full breakdown
10 pass0 warn11 fail15 skip
Discoverability
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
pass
robots.txt allows AI agents
All 9 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
pass
llms.txt present
Found /llms.txt but missing H1 header and markdown links. Not scored.
100/100
fail
Sitemap present
No reachable sitemap.xml. Publish one and reference it in robots.txt.
0/100
fail
Link response headers
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
0/100
fail
Canonical URL
No <link rel="canonical"> tag in <head>. Agents use canonical URLs to dedupe and cite.
0/100
skip
MCP server cardemerging
Agent-protocol discovery was not probed for this scan.
—
skip
OAuth authorization metadataemerging
Agent-protocol discovery was not probed for this scan.
—
skip
OAuth resource metadataemerging
Agent-protocol discovery was not probed for this scan.
—
skip
API catalog / OpenAPIemerging
Agent-protocol discovery was not probed for this scan.
—
skip
Web Bot Authemerging
Agent-protocol discovery was not probed for this scan.
—
Readability
skip
Markdown negotiationemerging
Agent-protocol discovery was not probed for this scan.
—
fail
Text-to-markup ratio
Visible text is 0.7% of HTML weight (51/6993 bytes). 70% of the document is inline script, 6% is markup.
5/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
—
fail
Heading hierarchy
No headings found. Add at least an <h1>; structure helps agents summarise.
0/100
pass
Cookie wall blocks content
No common consent-modal markers detected.
100/100
pass
Declared language
Declared lang="en".
100/100
pass
Page title
A concise <title> is present (21 chars).
100/100
fail
Meta description
No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.
0/100
Structured data
fail
JSON-LD present
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
0/100
skip
Structured data validates
No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).
—
pass
Schema type coverage
Page intent unclear; no specific schema.org type expected.
100/100
Coherence: do your channels agree?
skip
JSON-LD price matches the visible priceemerging
No price declared in JSON-LD, so there is nothing to cross-check. (Whether a price SHOULD be declared is the structured-data checks’ question.)
—
skip
JSON-LD name appears on the pageemerging
No Product/Organization/Store name declared in JSON-LD, so nothing to cross-check.
—
skip
Declared language matches the contentemerging
Too little visible text (8 words) to classify a language honestly.
—
Actionability
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
skip
Agent Skills manifestemerging
Agent-protocol discovery was not probed for this scan.
—
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
fail
Primary action reachable
Page text too sparse to probe; agent has nothing to read.
0/100
pass
Reachability
HTTP 200.
100/100
skip
Primary action is clickableemerging
This page does not ask the reader to do anything, so there is no primary action to check. Informational pages are not penalised here.
—
skip
Filters reachable by URLemerging
This page does not offer to filter or sort a list, so there is nothing to address by URL. Pages without facets are not penalised here.
—
Performance
fail
Time to first byte
TTFB 4435ms. Slow. Agents time out aggressively.
20/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 7 KB.
100/100
Beyond the scan
Running AI agents of your own? AgentSpeed also monitors them in production: every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.