CrawlProof

Public share link

Post on XLinkedIn

AEO Audit for example.com

Target: https://example.com/
Score: 37 / 100
Generated: 2026-08-29T03:59:40.078Z
Pages crawled: 1
Findings: 22 pass · 106 warn · 9 fail · 0 unknown

1. Crawl Summary

2. Data Found

Data PointFound?SourceNotes
PricingNo——
Customer logosNo——
Social proofNo——
Recent launchesNo——
Blog post activityNo——
New hiresNo—Often only on a /blog/team or LinkedIn page
Headline copyYesHomepageExample Domain
PositioningNo——
Executive teamNo——
Product/service descriptionsNo——
Case studies or testimonialsNo——
Contact/demo/signup pathsNo——

3. Homepage Audit

  • ❌ Content volume: 17 words Very thin content. AI models need substantive text to understand and recommend your site.
  • ⚠️ Missing meta description Add a <meta name="description"> to control the snippet AI/SERP show.
  • ⚠️ Short <title> (14 chars) Aim for 30–60 chars. Lead with brand or product, then value prop.
  • ⚠️ Missing canonical link Add <link rel="canonical" href="https://your-domain"> to prevent dup-content confusion.
  • ❌ Open Graph: missing title, description, image
  • ⚠️ No Twitter Card tags Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces.
  • ⚠️ Heading structure: 1 (h1:1, h2:0, h3:0) Few headings make it hard for AI to understand sectioning. Use h2/h3 to label each section.
  • ❌ Internal links: 0 Few internal links. Add a nav/footer with links to your key pages so AI crawlers can discover them.
  • ⚠️ Charset not declared Add <meta charset="utf-8"> as the first child of .
  • ✅ Homepage fetched successfully HTTP 200 · 559 bytes · 37ms
  • ✅ Page load time: 0.04s Fast — well within AI crawler budgets.
  • ✅ declared
  • ✅ Single H1 Example Domain
  • ✅ Critical content is server-rendered Raw and rendered text are within 45% of each other.
  • ✅ Favicon declared

4. Content Quality

  • ❌ Snippet-ready blocks: 0 (ul:0, ol:0, table:0) Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
  • ⚠️ No question-style headings found Phrase at least one heading as a user question (e.g. 'How does pricing work?') to match conversational AI queries.
  • ⚠️ No date signal found Add or article:published_time meta. AI ranking weights freshness.
  • ⚠️ No author byline found Add <meta name="author" content="Name"> or a visible byline with rel="author". Strengthens E-E-A-T signals.
  • ✅ Text-to-HTML ratio: 22.4% Visible text density is healthy for AI extraction.

5. Schema / Structured Data Audit

  • ❌ No JSON-LD structured data found Add JSON-LD blocks (Organization, SoftwareApplication, FAQPage, BreadcrumbList) so AI answer engines can ingest your data without guessing.

6. Links & Images

  • ✅ External nofollow: 0% (0/1) Healthy mix of follow and nofollow outbound links.
  • ✅ No broken links in first 1 HEAD-probed the first 20 unique homepage links — all 2xx/3xx.

7. Performance

  • ⚠️ No Cache-Control header Add a Cache-Control header so CDNs and AI crawlers can revalidate efficiently.
  • ✅ Page size: 1 KB Compact HTML payload — well within AI crawler limits.
  • ✅ Resource requests: 0 (scripts:0, css:0, img:0) Reasonable request count.
  • ✅ No render-blocking head scripts All head scripts use async or defer.
  • ✅ Response time: 37ms Fast first response.
  • ✅ Compression enabled (Brotli) Content-Encoding: br

8. Security

  • ⚠️ HSTS missing Add Strict-Transport-Security: max-age=31536000; includeSubDomains once you're confident in https.
  • ⚠️ Content-Security-Policy missing Define a CSP to limit script sources — large reduction in XSS surface.
  • ⚠️ X-Frame-Options missing Add X-Frame-Options: SAMEORIGIN (or use CSP frame-ancestors) to prevent clickjacking.
  • ⚠️ X-Content-Type-Options missing Add X-Content-Type-Options: nosniff to block MIME-type sniffing.
  • ⚠️ Referrer-Policy missing Add Referrer-Policy: strict-origin-when-cross-origin for safer referrers.
  • ⚠️ Permissions-Policy missing Restrict browser features (camera, mic, geolocation) you don't use.
  • ✅ Served over HTTPS
  • ✅ No mixed content detected

9. robots.txt and sitemap.xml Audit

  • ❌ sitemap.xml not found No /sitemap.xml was reachable and robots.txt has no Sitemap: directive. Add /sitemap.xml — required for reliable AI/SERP discovery.
  • ⚠️ robots.txt not found No /robots.txt was reachable. Add one explicitly — silence is read differently by different crawlers, and you lose the chance to control AI bots.

10. LLM / AI Crawler Accessibility

  • ⚠️ llms.txt missing Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
  • ⚠️ skill.md missing Add /skill.md describing what your site lets agents do — speeds up agent task routing.
  • ⚠️ /.well-known/security.txt missing Publish a /.well-known/security.txt with at least a Contact: line. Crawlers and security researchers expect it; AI systems use it as a trust signal.
  • ⚠️ /llms-full.txt missing Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.

11. Positioning Clarity

  • ❌ No discoverable CTA Add a clearly-labeled Contact, Demo, or Sign up link to the nav or hero.
  • ⚠️ No clear About/Team link Add an About or Team link in the nav or footer so LLMs can identify the company.
  • ⚠️ No pricing/plans link found AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
  • ⚠️ Value-prop language not detected Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
  • ✅ H1 communicates value Example Domain

12. Missing or Hard-to-Find Information

  • ❌ 11 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Product/service descriptions · Case studies or testimonials · Contact/demo/signup paths

  • ⚠️ Create or enrich /llms.txt Follow the llmstxt.org spec:

    # Your Brand

> One-line description of your site.

## Docs

- [Getting Started](https://yoursite.com/docs/start): How to get up and running.
- [API Reference](https://yoursite.com/docs/api): Full API details.

## About

- [About us](https://yoursite.com/about): Mission and team.

    Include at least 2 section headings, 3+ linked resources, and a brief description per link. A rich llms.txt dramatically increases how often generative AI systems cite your content.

  • ⚠️ Add more substantive homepage content AI models need 300+ words of visible body text to summarize and recommend a site. Add a value-prop paragraph, a short FAQ, and a 'how it works' section.

  • ⚠️ Add a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.

  • ⚠️ Publish a sitemap.xml Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.

  • ⚠️ Add JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.

  • ⚠️ Add lists or comparison tables Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.

  • ⚠️ Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

    {
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}

    These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

  • ⚠️ Add an AI agent integration file At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API:

    # Your Brand Skill

API endpoint: https://yoursite.com/api
Auth: Bearer token

## Tools

- search: Search the knowledge base
- get_article: Retrieve a full article by ID

    Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.

  • ⚠️ Declare your brand name in Organization JSON-LD Add "name": "Your Brand" to your Organization or SoftwareApplication schema block. AI systems match structured-data names against training data to resolve your brand as a distinct entity. Without it, mentions of your brand may not be attributed to you.

  • ⚠️ Add a meta description 50–160 chars. Repeat your core value prop in plain language; this often becomes the AI snippet.

    <meta name="description" content="CrawlProof shows you exactly how AI crawlers see your site, then tells you what to fix." />

  • ⚠️ Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.

  • ⚠️ Make your About/Team page reachable Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site.

  • ⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.

  • ⚠️ Create a robots.txt Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.

  • ⚠️ Phrase a heading as a user question Use headings like 'How does pricing work?' or 'Who is this for?' — they map directly to conversational AI queries.

  • ⚠️ Publish a date signal Add <time datetime="2026-05-17"> or <meta property="article:published_time">. AI ranking heavily weights freshness.

  • ⚠️ Generate /llms-full.txt for RAG pipelines llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root:

    # Your Brand — Full Content

## Getting Started
<full markdown content of /docs/start>

## API Reference
<full markdown content of /docs/api>

    Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.

  • ⚠️ Add outbound links to authoritative sources Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood.

    Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.

  • ⚠️ Set a meaningful <title> 30–60 chars. Lead with the brand or product, then the value prop.

    <title>CrawlProof — AEO audits for AI crawlers</title>

  • ⚠️ Add a canonical link Prevents dup-content drift and tells AI crawlers which URL is authoritative.

    <link rel="canonical" href="https://yoursite.com/" />

  • ⚠️ Complete Open Graph tags AI bots use OG for fast disambiguation. Add all four:

    <meta property="og:title" content="Your Page Title" />
<meta property="og:description" content="50–160 char description of this page." />
<meta property="og:image" content="https://yoursite.com/og-image.jpg" />
<meta property="og:url" content="https://yoursite.com/" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="YourSite" />

  • ⚠️ Add Twitter Card meta tags Used by social platforms and AI agents for richer previews.

    <meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="Your Page Title" />
<meta name="twitter:description" content="50–160 char description." />
<meta name="twitter:image" content="https://yoursite.com/og-image.jpg" />

  • ⚠️ Add structured headings Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page.

  • ⚠️ Add internal navigation links Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.

  • ⚠️ Declare charset Add <meta charset="utf-8"> as the first child of so non-ASCII content is parsed reliably.

  • ⚠️ Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.

  • ⚠️ Publish /.well-known/security.txt A security contact builds trust with crawlers and researchers. Minimal example:

    Contact: mailto:security@yourdomain.com
Expires: 2027-01-01T00:00:00.000Z
Preferred-Languages: en

  • ⚠️ Set a Cache-Control header Add Cache-Control: public, max-age=300, s-maxage=3600 (or similar) so CDNs and AI crawlers can revalidate cheaply.

  • ⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.

  • ⚠️ Enable HSTS Add Strict-Transport-Security: max-age=31536000; includeSubDomains once you're confident every subdomain is https-ready.

  • ⚠️ Define a Content-Security-Policy Start with Content-Security-Policy-Report-Only to learn safe sources, then enforce. Cuts XSS blast radius.

  • ⚠️ Declare an author byline Add <meta name="author" content="Name"> or a visible byline with rel="author". Combine with Person JSON-LD for E-E-A-T.

  • ⚠️ Add X-Frame-Options X-Frame-Options: SAMEORIGIN (or CSP frame-ancestors) blocks clickjacking via iframe embeds.

  • ⚠️ Add X-Content-Type-Options X-Content-Type-Options: nosniff prevents browsers from MIME-sniffing responses.

  • ⚠️ Set a Referrer-Policy Referrer-Policy: strict-origin-when-cross-origin is a safe default.

  • ⚠️ Set a Permissions-Policy Restrict browser features you don't use, e.g. Permissions-Policy: camera=(), microphone=(), geolocation=().

14. Priority To-Do List

  • P1 — Create or enrich /llms.txt Follow the llmstxt.org spec:

    ```
# Your Brand

> One-line description of your site.

## Docs

- [Getting Started](https://yoursite.com/docs/start): How to get up and running.
- [API Reference](https://yoursite.com/docs/api): Full API details.

## About

- [About us](https://yoursite.com/about): Mission and team.
```

Include at least 2 section headings, 3+ linked resources, and a brief description per link. A rich llms.txt dramatically increases how often generative AI systems cite your content.

  • P1 — Add more substantive homepage content AI models need 300+ words of visible body text to summarize and recommend a site. Add a value-prop paragraph, a short FAQ, and a 'how it works' section.

  • P1 — Add a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.

  • P1 — Publish a sitemap.xml Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.

  • P1 — Add JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.

  • P2 — Add lists or comparison tables Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.

  • P2 — Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

    ```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}
```

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

  • P2 — Add an AI agent integration file At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API:

    ```markdown
# Your Brand Skill

API endpoint: https://yoursite.com/api
Auth: Bearer token

## Tools

- search: Search the knowledge base
- get_article: Retrieve a full article by ID
```

Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.

  • P2 — Declare your brand name in Organization JSON-LD Add "name": "Your Brand" to your Organization or SoftwareApplication schema block. AI systems match structured-data names against training data to resolve your brand as a distinct entity. Without it, mentions of your brand may not be attributed to you.

  • P2 — Add a meta description 50–160 chars. Repeat your core value prop in plain language; this often becomes the AI snippet.

    ```html
<meta name="description" content="CrawlProof shows you exactly how AI crawlers see your site, then tells you what to fix." />
```

  • P2 — Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.

  • P2 — Make your About/Team page reachable Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site.

  • P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.

  • P2 — Create a robots.txt Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.

  • P3 — Phrase a heading as a user question Use headings like 'How does pricing work?' or 'Who is this for?' — they map directly to conversational AI queries.

  • P3 — Publish a date signal Add <time datetime="2026-05-17"> or <meta property="article:published_time">. AI ranking heavily weights freshness.

  • P3 — Generate /llms-full.txt for RAG pipelines llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root:

    ```
# Your Brand — Full Content

## Getting Started
<full markdown content of /docs/start>

## API Reference
<full markdown content of /docs/api>
```

Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.

  • P3 — Add outbound links to authoritative sources Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood.

    Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.

  • P3 — Set a meaningful <title> 30–60 chars. Lead with the brand or product, then the value prop.

    ```html
<title>CrawlProof — AEO audits for AI crawlers</title>
```

  • P3 — Add a canonical link Prevents dup-content drift and tells AI crawlers which URL is authoritative.

    ```html
<link rel="canonical" href="https://yoursite.com/" />
```

Report by CrawlProof. Reusable after every major website change.

Email yourself this report

Get a PDF copy of this audit in your inbox — handy for sharing with a client, dev, or teammate.

Watch this URL

We'll re-scan example.com and email you when its AEO Score actually moves — not on a schedule, only when something changes.

Re-scan

Free. We email you to confirm first, and every message has a one-click stop link.