Rapporto del sito: 1 pagina misurata. Valutazione complessiva: Discreto.
Punteggio del sito · apnews.com
Combina l'origine e 1 pagina misurata. Il report qui sotto dettaglia soltanto la pagina di origine.
Porta i risultati a chi può risolverli. Copia un riepilogo pronto per Slack, Teams o la prossima riunione.
Questo rapporto è pubblico. Il team può aprirlo senza un account.
C'è sostanza che un agente possa leggere?
Homepage does not serve Markdown via content negotiation
Serve a Markdown representation of your pages when agents request "Accept: text/markdown". Agents like Claude Code and Cursor ask for it, and Markdown cuts token usage by roughly 80% against HTML. Cloudflare ("Markdown for Agents") and Vercel can enable this without code changes.
No <link rel="alternate" type="text/markdown"> fallback found on the homepage
If you cannot enable content negotiation, advertise a Markdown version with <link rel="alternate" type="text/markdown" href="/index.md"> so agents can discover it.
1792/1803 interactive elements have an accessible name
2/4 form controls have no label
An unlabelled box is one the agent has to guess the meaning of, which is how an email address ends up in a search field. Use <label for>, wrap the control in a label, or add aria-label.
59 link(s) lead nowhere without JavaScript
A link with no destination cannot be followed by a fetch-only agent and cannot be opened in a new tab by a browsing one. Give it a real href, or make it a <button> if it is an action rather than a destination.
1/2 iframes have no title
An untitled frame is an opaque region. A title tells an agent whether it is worth entering.
1 obstacle(s) on the entry page
A CAPTCHA or a meta refresh on the landing page stops an agent before it reaches any content. If bot protection is needed, apply it to the actions that need it, not to reading a page.
Method note: this reads markup, not a rendered accessibility tree
Server-rendered content detected (9729 words, 62109 chars of visible text)
Low text-to-markup ratio (2.5%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Semantic landmarks present (main, footer, nav)
No <h1> heading found
Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
Only 49/92 <img> tags have alt attributes
Add descriptive alt="" to every <img>. Agents use alt text to understand images they cannot process visually.
2 JSON-LD block(s) found
@context references schema.org
No @graph array (single-entity only)
Use an @graph array to define multiple entities in one JSON-LD block: { "@context": "https://schema.org", "@graph": [...] }
Key types found: Organization, WebSite
No BreadcrumbList found
Add a BreadcrumbList entity to help AI agents understand your site navigation hierarchy.
No author declared in structured data
An assistant deciding whether to cite a page weighs where it came from. Add author as a Person or Organization, not a bare string.
6 sameAs link(s) tie your entity to external identifiers
No dateModified or datePublished in structured data
Assistants weigh recency when they answer time-sensitive questions, and a page with no date cannot be weighed at all. Add dateModified to anything that changes.
Structured-data headings appear in the visible text
<title> is too long (75 chars)
Shorten the title to 20-70 characters. Many agents and search engines truncate beyond ~70.
Meta description length 148 chars
Canonical URL: https://apnews.com/
<html lang="en">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1.0, minimum-scale=1.0 user-scalable=yes"
2 hreflang alternate(s) including x-default
Un agente riesce a recuperarla?
Homepage is indexable
noarchive excludes this page from Microsoft Copilot grounding
Microsoft documents that noarchive means a page is not included in Copilot answers and not linked from them. nocache is the lighter option: Copilot may use the URL, title and snippet but not the body.
GPTBot receives a Cloudflare challenge instead of the page
Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
ClaudeBot blocked at the server — consistent with its robots.txt Disallow
Meta-ExternalAgent receives a Cloudflare challenge instead of the page
Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
Amazonbot receives a Cloudflare challenge instead of the page
Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
Bytespider is allowed in robots.txt but its User-Agent is refused
Collects training data for ByteDance models. Compliance with robots.txt is disputed. Your firewall rejects this crawler token even though robots.txt permits it — the block is invisible to you but fatal for the agent. Check your firewall rules and AI-bot toggles (for example Cloudflare "Block AI Crawlers").
CCBot blocked at the server — consistent with its robots.txt Disallow
OAI-SearchBot receives a Cloudflare challenge instead of the page
Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
Claude-SearchBot blocked at the server — consistent with its robots.txt Disallow
PerplexityBot blocked at the server — consistent with its robots.txt Disallow
ChatGPT-User receives a Cloudflare challenge instead of the page
Challenge pages require running JavaScript. Crawlers that only fetch HTML — which is most of them — never get past one, so the page is effectively unavailable to them even though nothing is "blocked". Add a bot-management exception for verified AI crawlers. ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
5 crawler probe(s) could not be settled from outside
ax-audit sends this user agent from its own network without a Web Bot Auth signature, so an edge that verifies crawlers by IP range or signature will reject the probe while admitting the real crawler. Confirm against your WAF logs before changing any rule.
Response compressed with Brotli (br)
Cache validator present (Last-Modified)
Conditional request returns 304 Not Modified
Homepage is very large (2.4 MB decompressed)
Large documents inflate crawl cost and token usage. Trim inlined data, split content, or serve a Markdown representation to agents (see the content-negotiation check).
Roughly 15,527 tokens of content in 624,737 tokens of response (98% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 190ms
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=31536000
HSTS includes subdomains
HSTS lacks the preload directive
Add preload (and ensure max-age >= 31536000 + includeSubDomains) and submit the domain at https://hstspreload.org for browser-built-in HTTPS enforcement.
Could not test 404 handling — the probe was challenged
Bot management answered a plain GET with an interstitial, so status-code honesty could not be verified from outside.
Homepage answers without a redirect
HEAD requests are supported
Content-Type: text/html with charset
Un agente trova ciò che pubblichi?
/llms.txt not found
Create a /llms.txt file at your site root following the llmstxt.org specification. It should be a Markdown file starting with "# Your Site Name" and include a description, sections, and links.
No AI meta tags (ai:*) found
Add AI meta tags to your HTML <head>: <meta name="ai:summary" content="Brief description">, <meta name="ai:content_type" content="website">, <meta name="ai:author" content="Your Name">.
No rel="alternate" link to llms.txt in HTML
Add to your <head>: <link rel="alternate" type="text/plain" href="/llms.txt" title="LLM-optimized content">
No rel="alternate" link to the Agent Card in HTML
Add to your <head>: <link rel="alternate" type="application/json" href="/.well-known/agent-card.json" title="Agent Card">
No rel="me" identity links found
Add rel="me" links to verify your identity across platforms: <link rel="me" href="https://github.com/yourname">, <link rel="me" href="https://twitter.com/yourname">.
OpenGraph required tags present (og:title, og:description, og:url, og:type)
Twitter Card required tags present (twitter:card, twitter:title, twitter:description)
Twitter Card recommended tags missing: twitter:image
Add twitter:image for richer previews.
/robots.txt exists
7/12 core AI crawlers configured
Add explicit User-agent entries for the missing crawlers with Allow: / for each one.
9 AI crawler(s) explicitly blocked
These crawlers have "Disallow: /" rules. If you want AI agents to access your site, change to "Allow: /" for each blocked crawler.
2 assistant search crawler(s) blocked — your site cannot be cited by those assistants
Search crawlers build the index an assistant cites from; they are separate from the training crawlers. If the intent was to opt out of training only, allow these and block the training tokens instead.
6 training crawler(s) blocked — recorded as a deliberate policy choice
3 robots.txt rule(s) target a retired or non-existent crawler token
These rules have no effect. Remove them so the file reflects your actual policy.
Sitemap directive present
No Content-Signal directive found (optional)
Declare how crawlers may use your content after access with the Content Signals Policy, e.g.: Content-Signal: search=yes, ai-train=no. Known signals: search, ai-input, ai-train, plus the optional use=immediate|reference|full. Generate yours at contentsignals.org.
9/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
Missing critical header: X-Content-Type-Options
Add the X-Content-Type-Options response header to your server configuration. This is a critical security header.
Only 2/7 security headers present
Add security headers like Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to your server response.
No Link header for AI discovery (llms.txt, Agent Card)
Add a Link response header pointing to your AI discovery files: Link: </llms.txt>; rel="alternate"; type="text/plain", </.well-known/agent-card.json>; rel="alternate"; type="application/json"
No machine-readable discovery relations beyond llms.txt and the Agent Card
Advertise what you publish with Link relations so agents stop guessing paths. Add the ones that apply, for example: Link: </llms.txt>; rel="describedby", </.well-known/api-catalog>; rel="api-catalog". Informational in 3.x: this does not affect your score.
Sitemap located: https://apnews.com/ap-sitemap.xml
Content-Type is XML (text/xml)
Sitemap-index references 230 child sitemap(s)
3/3 sample child sitemap(s) reachable
Sample yielded 3 URL(s) across 3 child(ren)
Newest <lastmod> is 569 days old
Refresh <lastmod> on URLs that have changed. A stale sitemap signals to crawlers that nothing on the site has updated.
Che cosa può chiamare un agente?
/.well-known/agent-card.json not found
This site offers something an agent could call, but nothing tells an agent what. Publish an A2A Agent Card at /.well-known/agent-card.json. A minimal 1.0 card needs name, description, version, capabilities, supportedInterfaces, defaultInputModes, defaultOutputModes and skills. Spec: https://a2a-protocol.org/latest/specification/
API surface present but no machine-readable description found
The API exists; nothing describes it in a form an agent can read, so using it requires a human to read your documentation first. Serve an OpenAPI description at /openapi.json and advertise it with Link: </openapi.json>; rel="service-desc". For several APIs, publish an RFC 9727 catalog.
No agent resource catalog found
A catalog is one document listing everything an agent can call here — agent cards, MCP servers, APIs, skills — so a client stops probing four conventions to find out. Worth publishing once you have more than one of those. Informational: both ai-catalog.json and ard.json are still drafts, so this never affects your score.
Site sells something but publishes no agent-readable commerce profile
Publish a Universal Commerce Protocol profile at /.well-known/ucp so an agent can find your catalog, cart and checkout without a human. Note that the alternatives are not discoverable by design: the OpenAI and Stripe Agentic Commerce Protocol defines no manifest, and AP2 advertises itself through an A2A card extension.
4 form(s) on the page, none declared as agent tools
A declared form is called by an agent rather than driven pixel by pixel. Add toolname and tooldescription to the forms worth automating — search, filter, subscribe — and toolparamdescription to each field.
No MCP server — MCP discovery does not apply to this site
No developer-facing surface — skills do not apply to this site
Nothing on this site requires authorization — auth discovery does not apply
Quali diritti d'uso sono dichiarati?
/.well-known/security.txt not found
Create a /.well-known/security.txt file per RFC 9116. At minimum, include Contact: and Expires: fields. See https://securitytxt.org/ for a generator.
No RSL license discovery found
Declare machine-readable licensing terms for your content with Really Simple Licensing. Add to robots.txt: License: https://your-site.com/license.xml — then publish the RSL document. See https://rslstandard.org.
No machine-readable usage policy declared
State your terms where they can be read without a lawyer. The lowest-effort option is a Content-Signal line in robots.txt: Content-Signal: search=yes, ai-input=yes, ai-train=no. Absence is neutral, not permission — but it also gives you nothing to point at.
Dai al team rapporti completi, correzioni prioritarie e monitoraggio per mantenere i miglioramenti dopo ogni rilascio.