Rapporto del sito: 1 pagina misurata. Valutazione complessiva: Discreto.
Punteggio del sito · omsom.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.
No JSON-LD structured data found
Add a <script type="application/ld+json"> block in your HTML <head> with schema.org structured data describing your site, organization, or person.
Sparse server-rendered content (1 words, 5 chars)
Render at least the main page content server-side. Many AI crawlers (GPTBot, ClaudeBot, CCBot) do not execute JavaScript and will see only the static HTML.
Low text-to-markup ratio (2.9%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
Empty SPA mount point detected: #root
The static HTML contains an empty SPA mount node, which means content is rendered only client-side. Enable SSR/SSG so the initial HTML response includes meaningful content.
No semantic HTML landmarks found
Replace generic <div> structures with semantic tags: <main>, <article>, <header>, <nav>, <footer>. Agents use these to identify the primary content region.
No <h1> heading found
Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
<title> is too short (5 chars): "Omsom"
Lengthen the title to 20-70 characters with a clear topic indicator.
Meta description length 131 chars
No <link rel="canonical"> found
Add <link rel="canonical" href="https://your-site.com/page"> so agents have an unambiguous URL to cite even when crawled via a redirect or query-string variant.
<html lang="en">
UTF-8 charset declared
Viewport meta present: "width=device-width, initial-scale=1"
Method note: this reads markup, not a rendered accessibility tree
Un agente riesce a recuperarla?
Response compressed with Brotli (br)
No ETag or Last-Modified header — conditional requests unsupported
Send an ETag or Last-Modified header so crawlers can revalidate with If-None-Match / If-Modified-Since and receive a cheap 304 Not Modified instead of the full body.
Homepage size is reasonable (58.7 KB decompressed)
Roughly 1 tokens of content in 15,028 tokens of response (100% markup)
An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
Homepage responded in 52ms
Site is served over HTTPS
HTTP requests redirect to HTTPS
HSTS max-age=31536000
HSTS does not include subdomains
Add includeSubDomains to apply HSTS across api., docs., etc. Required for preload list submission.
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.
All 10 core AI crawler user-agents receive the same page as a regular client
Missing pages return 404
Homepage answers without a redirect
HEAD requests are supported
Character encoding declared in the document (not in the Content-Type header)
Homepage is indexable
No directive restricts how AI assistants may use this page
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.
/robots.txt not found
Create a /robots.txt file at your site root. Add User-agent entries for AI crawlers (GPTBot, ClaudeBot, etc.) with Allow: / to grant access.
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 missing: og:url
Add these meta tags: <meta property="og:url" content="...">.
Twitter Card required tags missing: twitter:card, twitter:title
Add these meta tags: <meta name="twitter:card" content="...">, <meta name="twitter:title" content="...">.
6/7 security headers present
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://omsom.com/sitemap.xml
Content-Type is XML (application/xml)
1 URL(s) declared
100% of URLs have <lastmod>
Newest <lastmod> is 416 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?
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.
No agent-facing surface — an Agent Card does not apply to this site
No API surface — API discovery does not apply to this site
No MCP server — MCP discovery does not apply to this site
No developer-facing surface — skills do not apply to this site
No commerce surface — agentic-commerce discovery does not apply to this site
Nothing on this site requires authorization — auth discovery does not apply
No forms and no WebMCP code — nothing here for an agent to invoke as a tool
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.