Site report: 1 measured page. Overall grade: Fair.
Site score · pipcorn.com
Blended across the origin and 1 measured page. The report below details the origin page alone.
Bring the findings to the people who can fix them. Copy a ready-to-send summary for Slack, Teams or your next planning meeting.
This is a public report. Your team can open it without an account.
Is there substance an agent can read?
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.
No visible text content in static HTML
Your homepage appears to be a JavaScript-only shell. Add server-side rendering (Next.js SSR/SSG, Astro, Remix, or a static prerender) so AI agents that do not execute JS can read your content.
Low text-to-markup ratio (0.0%)
A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
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 missing or empty
Add a <title> in <head> describing the page in 20-70 characters. Agents quote it as the document name.
<meta name="description"> is missing
Add <meta name="description" content="..."> in <head> with a 70-160 character summary. Agents use this as the canonical short description.
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="..."> is missing
Set the document language: <html lang="en">. Multilingual agents rely on this to pick the right summarization model and avoid mixed-language ranking.
No UTF-8 charset declaration in HTML head
Add <meta charset="utf-8"> as the first child of <head>. Without it, agents can mis-decode non-ASCII content.
Missing or incomplete viewport meta tag
Add <meta name="viewport" content="width=device-width, initial-scale=1">. Helps mobile agents render the page correctly.
No lang attribute on <html>
Agents route, translate and pick a voice from this. Add lang="en" or whichever applies.
Method note: this reads markup, not a rendered accessibility tree
Can an agent retrieve it at all?
Response is not compressed
Enable Brotli or gzip for text responses. Compression cuts bytes transferred by ~70–80% and reduces crawl cost for every agent and bot that fetches your pages.
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 (114 B decompressed)
Roughly 0 tokens of content in 29 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 348ms
A nonexistent path returns HTTP 200
An agent has no way to see that this page is an apology. It stores the text as the answer, or retries a URL that will never work. Return 404 for missing pages and 410 for removed ones.
Homepage answers without a redirect
HEAD requests are supported
No character encoding declared in the header or the document
Without a charset, non-ASCII text is decoded by guesswork and quoted back with replacement characters. Add charset=utf-8.
Site is served over HTTPS
HTTP request did not redirect to HTTPS
Configure your server to 301-redirect every http:// request to https://. Otherwise agents may cache the insecure variant.
No Strict-Transport-Security header
Add: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload. This locks browsers and many agents to HTTPS for 1 year.
All 10 core AI crawler user-agents receive the same page as a regular client
Homepage is indexable
No directive restricts how AI assistants may use this page
Can an agent find what you publish?
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">.
No OpenGraph meta tags found
Add at minimum og:title, og:description, og:url, og:type, and og:image. Agents and link previews depend on these.
No Twitter Card meta tags found
Add twitter:card, twitter:title, twitter:description, and twitter:image so X / Threads / Bluesky / Discord agents render link previews correctly.
Missing critical header: Strict-Transport-Security
Add the Strict-Transport-Security response header to your server configuration. This is a critical security header.
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 0/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 CORS headers on .well-known resources
Add Access-Control-Allow-Origin: * to responses from /.well-known/* so AI agents from other domains can fetch your discovery files.
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.
/llms.txt exists
/llms.txt Content-Type OK (text/plain)
Missing H1 heading (first line should start with "# ")
Add an H1 heading as the first line of your llms.txt file, e.g.: # Your Site Name
No blockquote description found ("> ...")
Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
No section headings found (## ...)
Organize your llms.txt content with ## section headings (e.g., ## About, ## API, ## Documentation).
No Markdown links found
Add Markdown links to relevant pages: [Page Title](https://example.com/page). This helps AI agents navigate your site.
Content appears minimal (< 100 characters)
Expand your llms.txt with more descriptive content about your site, its purpose, and available resources.
/llms-full.txt also available (bonus)
No rel="describedby" link to llms.txt
llms.txt v2 uses this relation so a page can name the file that covers it. Add <link rel="describedby" href="/llms.txt"> or the equivalent Link header, so an agent that landed on a deep page does not have to guess that an index exists.
No per-page Markdown mirror found
llms.txt v2 documents appending .md to a URL for its Markdown version. The index tells an agent which pages exist; the mirrors are what make reading them cheap.
Consumer note: llms.txt is read by coding agents, not by search
/robots.txt exists
No core AI crawlers explicitly configured
Add User-agent entries for core AI crawlers in your robots.txt. For each crawler, add: User-agent: <name> followed by Allow: / on the next line.
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.
0/57 known AI crawlers have explicit rules
Add explicit User-agent entries for more AI crawlers to maximize discoverability.
Sitemap located: https://pipcorn.com/sitemap.xml
Content-Type is XML (application/xml)
1 URL(s) declared
Only 0% of URLs have <lastmod>
Add a <lastmod>YYYY-MM-DD</lastmod> child to each <url>. AI agents use lastmod to prioritize re-fetching.
What can an agent call?
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 Skills published
This site has documentation, so it has procedures worth teaching. A skill is a SKILL.md an agent installs and follows: setup steps, argument shapes, the mistakes to avoid. Publish one per task at /.well-known/agent-skills/{name}/SKILL.md and list them in /.well-known/agent-skills/index.json.
No agent-facing surface — an Agent Card does not apply to this site
/.well-known/api-catalog served as "text/html"
Serve the catalog as application/linkset+json.
No API surface — API discovery does not apply to this site
No MCP server — MCP discovery does 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
What usage rights are declared?
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.
/.well-known/security.txt exists
Required field "Contact" missing (RFC 9116)
Add "Contact:" to your security.txt. Use a mailto: or https: URI, e.g., Contact: mailto:security@example.com
Required field "Expires" missing (RFC 9116)
Add "Expires:" to your security.txt. Use an ISO 8601 date, e.g., Expires: 2026-12-31T23:59:59.000Z
No optional fields (Canonical, Preferred-Languages, Policy, etc.)
Consider adding Canonical: (canonical URL), Preferred-Languages: (e.g., en), and Policy: (link to your security policy).
Give your team full reports, prioritized fixes and monitoring, so improvements last beyond the next release.