# AI readiness of pipcorn.com

> Measured on the home page. Overall grade: Fair.

Score 51/100, grade Fair. Measured 2026-09-10T19:02:21.657+00:00, engine axrush-engine@6.0.0.

## Checks

### Content — 29/100

#### Content Negotiation — 0/100

- **FAIL** Homepage does not serve Markdown via content negotiation
  Got text/html (HTTP 200) for "Accept: text/markdown"
  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.
  https://axrush.com/guides/content-negotiation#not-supported
- **WARN** 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.
  https://axrush.com/guides/content-negotiation#no-alternate

#### Structured Data — 0/100

- **FAIL** 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.
  https://axrush.com/guides/structured-data#not-found

#### HTML Rendering — 15/100

- **FAIL** 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.
  https://axrush.com/guides/html-rendering#js-shell
- **WARN** Low text-to-markup ratio (0.0%)
  Recommended minimum: 5% of structural markup (script/style bodies and svg interiors excluded)
  A very low text-to-markup ratio is a typical SPA-shell symptom. Inline more content directly into the HTML response.
  https://axrush.com/guides/html-rendering#low-ratio
- **WARN** 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.
  https://axrush.com/guides/html-rendering#no-landmarks
- **WARN** No <h1> heading found
  Add a single <h1> describing the page. Agents and search engines treat the H1 as the primary topic indicator.
  https://axrush.com/guides/html-rendering#no-h1

#### SEO Basics — 25/100

- **FAIL** <title> is missing or empty
  Add a <title> in <head> describing the page in 20-70 characters. Agents quote it as the document name.
  https://axrush.com/guides/seo-basics#no-title
- **FAIL** <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.
  https://axrush.com/guides/seo-basics#no-description
- **WARN** 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.
  https://axrush.com/guides/seo-basics#no-canonical
- **WARN** <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.
  https://axrush.com/guides/seo-basics#no-lang
- **WARN** 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.
  https://axrush.com/guides/seo-basics#no-charset
- **WARN** Missing or incomplete viewport meta tag
  Add <meta name="viewport" content="width=device-width, initial-scale=1">. Helps mobile agents render the page correctly.
  https://axrush.com/guides/seo-basics#no-viewport

#### Agent Operability — 95/100

- **WARN** No lang attribute on <html>
  Agents route, translate and pick a voice from this. Add lang="en" or whichever applies.
  https://axrush.com/guides/agent-operability#no-lang
- **PASS** Method note: this reads markup, not a rendered accessibility tree
  Labels attached by script and roles computed at runtime are invisible here, so treat low proportions as a prompt to check the real tree rather than as a count. Every finding is also a plain accessibility defect.

### Access — 85/100

#### TLS / HTTPS — 70/100

- **PASS** Site is served over HTTPS
- **FAIL** HTTP request did not redirect to HTTPS
  Final URL: http://pipcorn.com/
  Configure your server to 301-redirect every http:// request to https://. Otherwise agents may cache the insecure variant.
  https://axrush.com/guides/tls-https#no-redirect
- **WARN** 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.
  https://axrush.com/guides/tls-https#no-hsts

#### Agent Access — 100/100

- **PASS** All 10 core AI crawler user-agents receive the same page as a regular client

#### HTTP Hygiene — 60/100

- **FAIL** A nonexistent path returns HTTP 200
  /ax-audit-probe-uf5b2rgu → 200 (0 chars of visible text)
  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.
  https://axrush.com/guides/http-hygiene#soft-404
- **PASS** Homepage answers without a redirect
- **PASS** HEAD requests are supported
- **WARN** 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.
  https://axrush.com/guides/http-hygiene#no-charset

#### Crawl Efficiency — 40/100

- **WARN** Response is not compressed
  No Content-Encoding header
  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.
  https://axrush.com/guides/crawl-efficiency#no-compression
- **WARN** 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.
  https://axrush.com/guides/crawl-efficiency#no-validators
- **PASS** Homepage size is reasonable (114 B decompressed)
- **WARN** Roughly 0 tokens of content in 29 tokens of response (100% markup)
  Estimated at four characters per token.
  An agent pays to receive the markup and then discards it. Serving Markdown on Accept negotiation is the direct fix.
  https://axrush.com/guides/crawl-efficiency#markup-overhead
- **PASS** Homepage responded in 348ms

#### AI Directives — 100/100

- **PASS** Homepage is indexable
- **PASS** No directive restricts how AI assistants may use this page

### Discovery — 59/100

#### LLMs.txt — 55/100

- **PASS** /llms.txt exists
- **PASS** /llms.txt Content-Type OK (text/plain)
- **WARN** 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
  https://axrush.com/guides/llms-txt#missing-h1
- **WARN** No blockquote description found ("> ...")
  Add a blockquote description after the H1 heading, e.g.: > A brief summary of your site for AI agents.
  https://axrush.com/guides/llms-txt#missing-blockquote
- **WARN** No section headings found (## ...)
  Organize your llms.txt content with ## section headings (e.g., ## About, ## API, ## Documentation).
  https://axrush.com/guides/llms-txt#missing-sections
- **WARN** No Markdown links found
  Add Markdown links to relevant pages: [Page Title](https://example.com/page). This helps AI agents navigate your site.
  https://axrush.com/guides/llms-txt#no-links
- **WARN** Content appears minimal (< 100 characters)
  Expand your llms.txt with more descriptive content about your site, its purpose, and available resources.
  https://axrush.com/guides/llms-txt#minimal-content
- **PASS** /llms-full.txt also available (bonus)
- **WARN** 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.
  https://axrush.com/guides/llms-txt#no-describedby
- **WARN** No per-page Markdown mirror found
  Tried /index.md and /index.html.md.
  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.
  https://axrush.com/guides/llms-txt#no-markdown-mirror
- **PASS** Consumer note: llms.txt is read by coding agents, not by search
  Google has stated that Search ignores llms.txt, and adoption studies find most published files are never fetched by an AI search crawler. Claude Code, Cursor and OpenCode do fetch it. Treat it as developer tooling, not as a search-visibility signal.

#### Robots.txt — 60/100

- **PASS** /robots.txt exists
- **FAIL** No core AI crawlers explicitly configured
  Expected: GPTBot, ClaudeBot, Meta-ExternalAgent, Google-Extended, Applebot-Extended, Amazonbot, Bytespider, CCBot, OAI-SearchBot, Claude-SearchBot, PerplexityBot, ChatGPT-User
  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.
  https://axrush.com/guides/robots-txt#no-core-crawlers
- **PASS** Sitemap directive present
- **WARN** 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.
  https://axrush.com/guides/robots-txt#missing-content-signals
- **WARN** 0/57 known AI crawlers have explicit rules
  Add explicit User-agent entries for more AI crawlers to maximize discoverability.
  https://axrush.com/guides/robots-txt#low-coverage

#### Sitemap — 95/100

- **PASS** Sitemap located: https://pipcorn.com/sitemap.xml
- **PASS** Content-Type is XML (application/xml)
- **PASS** 1 URL(s) declared
- **WARN** 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.
  https://axrush.com/guides/sitemap#low-lastmod

#### Meta Tags — 36/100

- **WARN** 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">.
  https://axrush.com/guides/meta-tags#no-ai-meta
- **WARN** 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">
  https://axrush.com/guides/meta-tags#no-llms-alternate
- **WARN** 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">
  https://axrush.com/guides/meta-tags#no-agent-alternate
- **WARN** 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">.
  https://axrush.com/guides/meta-tags#no-rel-me
- **WARN** 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.
  https://axrush.com/guides/meta-tags#no-opengraph
- **WARN** 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.
  https://axrush.com/guides/meta-tags#no-twitter

#### HTTP Headers — 50/100

- **FAIL** Missing critical header: Strict-Transport-Security
  Add the Strict-Transport-Security response header to your server configuration. This is a critical security header.
  https://axrush.com/guides/http-headers#missing-critical-header
- **FAIL** 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.
  https://axrush.com/guides/http-headers#missing-critical-header
- **WARN** 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.
  https://axrush.com/guides/http-headers#low-security-headers
- **WARN** 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"
  https://axrush.com/guides/http-headers#no-link-header
- **WARN** 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.
  https://axrush.com/guides/http-headers#no-cors
- **WARN** No machine-readable discovery relations beyond llms.txt and the Agent Card
  describedby — llms.txt v2 uses this relation to point a page at the llms.txt that covers it.
api-catalog — RFC 9727: the catalog of APIs this publisher offers.
service-desc — RFC 8631: a machine-readable API description.
service-doc — RFC 8631: human documentation for the API.
ai-catalog — Draft: the AI catalog listing agent cards and MCP server cards.
c2pa-manifest — C2PA 2.4: content provenance for media on the page.
license — RSL and other machine-readable licensing terms.
  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.
  https://axrush.com/guides/http-headers#discovery-relations

### Protocols — 0/100

#### Agent Card (A2A) — N/A

- **PASS** No agent-facing surface — an Agent Card does not apply to this site
  No API, MCP server or existing card was found. An Agent Card advertises capabilities another agent can invoke; a site that offers none has nothing to put in it. Run with --profile agent to audit as though it did.

#### OpenAPI Spec — N/A

- **WARN** /.well-known/api-catalog served as "text/html"
  RFC 9727 requires support for application/linkset+json.
  Serve the catalog as application/linkset+json.
  https://axrush.com/guides/api-discovery#catalog-content-type
- **PASS** No API surface — API discovery does not apply to this site
  No description, catalog, service-desc relation or developer area was found. Run with --profile api to audit as though the site offered one.

#### MCP (Model Context Protocol) — N/A

- **PASS** No MCP server — MCP discovery does not apply to this site
  A server card describes an MCP server so agents can find it. A site that runs none has nothing to advertise. Run with --profile mcp to audit as though it did.

#### AI Catalog — 0/100 (reports, does not score)

- **WARN** No agent resource catalog found
  Checked robots.txt Agentmap: directive, Link header rel="ai-catalog", <link rel="ai-catalog">, well-known path and /.well-known/ai-catalog.json, /.well-known/ard.json. Both specifications are drafts.
  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.
  https://axrush.com/guides/ai-catalog#not-found

#### Agent Skills — 0/100

- **WARN** No Agent Skills published
  Checked /.well-known/agent-skills/index.json, /.well-known/skills/index.json, /skill.md, /SKILL.md. Draft specification — the path may still change. Cloudflare RFC v0.2.0 (2026-03-12). Not registered; a competing shorter path (/.well-known/skills/) also ships.
  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.
  https://axrush.com/guides/agent-skills#not-found

#### Commerce Discovery — N/A

- **PASS** No commerce surface — agentic-commerce discovery does not apply to this site
  No Product or Offer structured data, cart links, or product price tags found.

#### Auth Discovery — N/A

- **PASS** Nothing on this site requires authorization — auth discovery does not apply
  No API description, API catalog, MCP server card or commerce profile found.

#### WebMCP — N/A

- **PASS** No forms and no WebMCP code — nothing here for an agent to invoke as a tool

### Policy — 33/100

#### Security.txt — 45/100

- **PASS** /.well-known/security.txt exists
- **FAIL** 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
  https://axrush.com/guides/security-txt#missing-field
- **FAIL** 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
  https://axrush.com/guides/security-txt#missing-field
- **WARN** 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).
  https://axrush.com/guides/security-txt#missing-optional

#### RSL License — 0/100

- **FAIL** No RSL license discovery found
  Checked robots.txt License directive, Link header, and <link rel="license" type="application/rsl+xml">
  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.
  https://axrush.com/guides/rsl#not-found

#### Usage Policy — 40/100

- **WARN** No machine-readable usage policy declared
  Checked robots.txt Content-Signal and Content-Usage, the Content-Usage and content-signal response headers, an RSL licence, TDMRep, and the noai meta directive.
  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.
  https://axrush.com/guides/usage-policy#no-policy

---

Markdown representation of https://axrush.com/report/pipcorn.com
