Loading the report. A first-ever scan of a domain runs live against the site and takes about ten seconds.
anglepage.com
scanned 8/5/2026, 2:16:36 PM · cached · refresh in 23h · rubric 2026.10.4
Built with Webflow
At risk
This is how AI agents (not browsers) experience anglepage.com. 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
failJSON-LD present+8 ptsStructured dataNo JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
Show me exactly what to do
What this means
JSON-LD is a small block of structured facts (name, what you sell, prices) embedded invisibly in your page’s HTML, written in a vocabulary (schema.org) that machines share. Think of it as the machine-readable caption for the page humans see.
Why it matters
An agent reading prose has to guess which number is the price and which name is the brand. JSON-LD removes the guessing: typed facts it can quote directly. Pages without it get summarised from inference, which is where wrong prices and wrong names come from.
Do this
- Webflow: Add JSON-LD in Page Settings → Custom Code (inside <head>) for the page’s type.
- Add an Organization block (name, url, logo) site-wide, in <head>.
- On product pages add Product with offers (price, currency, availability); on articles add Article; on FAQs add FAQPage.
- A starter block generated for this site is in the Fix it section below. Copy it, then extend per page type.
- On WordPress, Yoast or Rank Math emits this automatically. Shopify themes usually include Product markup already, so check for gaps rather than adding a duplicate.
Don’t lose this report
Get it in your inbox now, plus a heads-up whenever anglepage.com’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 65/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/anglepage.com"><img src="https://agentspeed.com/badge/anglepage.com" alt="AgentSpeed agent-readiness score" height="56"></a>Track this score
Get this report by email, then a heads-up when anglepage.com’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 anglepage.com. AI traffic analytics says whether one actually came, and which pages turned it away.
Full breakdown
15 pass6 warn10 fail5 skip
Discoverability
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
warn
robots.txt allows AI agents
1 access agent(s) blocked: Amazonbot. These keep your site out of AI answers. 7 training-data crawler(s) blocked (GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, Bytespider, CCBot, Meta-ExternalAgent), a licensing choice, not scored.
89/100
pass
Content-Signal directivesemerging
Content-Signal directives are advertised, declaring fine-grained AI usage preferences.
100/100
pass
llms.txt present
Found /llms.txt but missing H1 header and markdown links. Not scored.
100/100
warn
Sitemap present
sitemap.xml reachable but not referenced from robots.txt, so agents may miss it.
70/100
warn
Link response headers
A Link: header is present but carries none of canonical/alternate/describedby, the relations agents consume.
60/100
pass
Canonical URL
Canonical points to self: https://anglepage.com/.
100/100
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
fail
OAuth authorization metadataemerging
No RFC 8414 metadata at /.well-known/oauth-authorization-server. Agents that act on behalf of users need this to discover your authorization endpoints.
0/100
fail
OAuth resource metadataemerging
No RFC 9728 metadata at /.well-known/oauth-protected-resource. Publish it so agents can discover required scopes without hand-coded credentials.
0/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Readability
fail
Markdown negotiationemerging
Accept: text/markdown returns HTML, not markdown. Serve a markdown variant of primary content when requested; agents summarize and cite it more reliably.
0/100
warn
Text-to-markup ratio
Visible text is 11.2% of HTML weight (6039/53787 bytes). 5% of the document is inline script, 84% is markup.
69/100
pass
Content without JavaScript
Primary content is present in the initial HTML — agents without JS can read it. (Measured statically; a rendered comparison was not run because the static reading sufficed.)
90/100
pass
Heading hierarchy
Hierarchy is well-formed (1 H1, no skipped levels, 24 headings total).
100/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 (55 chars).
100/100
warn
Meta description
Meta description is 210 characters; aim for 50–200 so it's neither thin nor truncated.
60/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).
—
fail
Schema type coverage
Page looks like Product / FAQPage; missing JSON-LD type(s): Product, FAQPage.
0/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.
—
pass
Declared language matches the contentemerging
Declared lang="en" matches the detected content language (en).
100/100
Actionability
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
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
pass
Primary action reachable
A primary offering and a price or call to action were both identifiable from the served HTML, so an agent can tell what this page sells and what it costs without running scripts.
100/100
pass
Reachability
HTTP 200.
100/100
pass
Primary action is clickableemerging
4 clickable element(s) carry an action an agent can take: <a> announcing "get started", <a> announcing "get started", <a> announcing "get started". An agent driving the page has something real to click.
100/100
skip
Filters reachable by URLemerging
The words "refine" appear on this page, but there is no filter control and no filter link in the served HTML, and no label a control would carry. That reads as a page discussing filtering rather than offering it, so this is not scored either way.
—
Performance
warn
Time to first byte
TTFB 533ms. Acceptable.
60/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
—
pass
Page weight
Initial document is a lean 53 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.