Public share link

AEO Audit for feedbackminer.co

Target: https://feedbackminer.co/
Score: 32 / 100
Generated: 2026-08-22T22:22:07.976Z
Pages crawled: 9
Findings: 38 pass · 94 warn · 11 fail · 0 unknown

1. Crawl Summary

✅ Fetched 6 of 9 pages successfully Target: https://feedbackminer.co

2. Data Found

Data Point	Found?	Source	Notes
Pricing	Yes	Pricing page	https://feedbackminer.co/pricing
Customer logos	No	—	—
Social proof	No	—	—
Recent launches	No	—	—
Blog post activity	No	—	—
New hires	No	—	Often only on a /blog/team or LinkedIn page
Headline copy	Yes	Homepage	Customer interviews at survey scale
Positioning	No	—	—
Executive team	No	—	—
Product/service descriptions	Yes	Navigation links	https://feedbackminer.co/features
Case studies or testimonials	No	—	—
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

⚠️ Short <title> (14 chars) Aim for 30–60 chars. Lead with brand or product, then value prop.
⚠️ Long meta description (206 chars) Snippets truncate around 160 chars. Tighten to keep the key sentence visible.
⚠️ 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.
✅ Homepage fetched successfully HTTP 200 · 36612 bytes · 124ms
✅ Page load time: 0.12s Fast — well within AI crawler budgets.
✅ declared
✅ Single H1 Customer interviews at survey scale
✅ Critical content is server-rendered Raw and rendered text are within 57% of each other.
✅ Content volume: 664 words Substantive content — AI models have enough to summarize and recommend.
✅ Heading structure: 24 (h1:1, h2:6, h3:17) Multiple headings help AI chunk and outline your page.
✅ Internal links: 13 13 internal + 0 external links help crawlers navigate.
✅ Favicon declared

4. Content Quality

⚠️ 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.
✅ Heading levels are well-ordered 24 headings nested in order.
✅ Snippet-ready blocks: 11 (ul:8, ol:2, table:1) Lists and tables are extracted verbatim by AI answer engines.
✅ 1 definition list(s) present Definition lists give AI answer engines explicit term→meaning pairs.
✅ Text-to-HTML ratio: 12.3% 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

❌ 4 broken link(s) in first 9 · 404 — https://feedbackminer.co/terms · 404 — https://feedbackminer.co/privacy · 404 — https://feedbackminer.co/cookies · 404 — https://feedbackminer.co/sub-processors

7. Performance

✅ Page size: 36 KB Compact HTML payload — well within AI crawler limits.
✅ Resource requests: 6 (scripts:3, css:3, img:0) Reasonable request count.
✅ No render-blocking head scripts All head scripts use async or defer.
✅ Inline JS+CSS bulk: 4 KB Inline payload is modest.
✅ Response time: 124ms Fast first response.
✅ Cache-Control set (CDN: Cloudflare) Cache-Control: public, max-age=0, must-revalidate CDN detected: Cloudflare
✅ 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.
⚠️ Permissions-Policy missing Restrict browser features (camera, mic, geolocation) you don't use.
✅ Served over HTTPS
✅ No mixed content detected
✅ X-Frame-Options set DENY
✅ X-Content-Type-Options set nosniff
✅ Referrer-Policy set strict-origin-when-cross-origin

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 does not reference a Sitemap Add Sitemap: https://yoursite.com/sitemap.xml to robots.txt.
✅ robots.txt present 1859 chars

10. LLM / AI Crawler Accessibility

❌ GPTBot is blocked robots.txt disallows GPTBot from /. This bot cannot index your site.
❌ ClaudeBot is blocked robots.txt disallows ClaudeBot from /. This bot cannot index your site.
❌ Google-Extended is blocked robots.txt disallows Google-Extended from /. This bot cannot index your site.
❌ Applebot-Extended is blocked robots.txt disallows Applebot-Extended from /. This bot cannot index your site.
❌ CCBot is blocked robots.txt disallows CCBot from /. This bot cannot index your site.
⚠️ llms.txt missing Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
⚠️ PerplexityBot not explicitly addressed No User-agent: PerplexityBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ OAI-SearchBot not explicitly addressed No User-agent: OAI-SearchBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ 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 clear About/Team link Add an About or Team link in the nav or footer so LLMs can identify the company.
⚠️ 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 Customer interviews at survey scale
✅ Pricing path discoverable
✅ Contact / signup path discoverable

12. Missing or Hard-to-Find Information

❌ 8 data point(s) could not be found from public pages · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials

13. Recommended Fixes

⚠️ 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.

⚠️ Fix broken homepage links We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
⚠️ Allow GPTBot in robots.txt Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
⚠️ Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
⚠️ Allow Google-Extended in robots.txt Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
⚠️ Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
⚠️ Allow CCBot in robots.txt Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
⚠️ 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 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 /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.
⚠️ 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 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 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" />

⚠️ Allow PerplexityBot in robots.txt Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
⚠️ Allow OAI-SearchBot in robots.txt Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
⚠️ 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
```
⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
⚠️ Reference your sitemap in robots.txt Add Sitemap: https://yoursite.com/sitemap.xml so crawlers don't have to guess.
⚠️ 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.
⚠️ 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 — Fix broken homepage links We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
P1 — Allow GPTBot in robots.txt Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
P1 — Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
P1 — Allow Google-Extended in robots.txt Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
P1 — Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
P1 — Allow CCBot in robots.txt Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
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 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 /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.
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 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." />
```

Report by CrawlProof. Reusable after every major website change.

AEO audit

https://feedbackminer.co/

Completed 8/22/2026, 10:22:08 PM

/100

1. Crawl Summary

pass

Fetched 6 of 9 pages successfully

Target: https://feedbackminer.co

Evidence

{
  "pages": [
    {
      "url": "https://feedbackminer.co",
      "bytes": 36612,
      "status": 200,
      "fetchMs": 124
    },
    {
      "url": "https://feedbackminer.co/pricing",
      "bytes": 14316,
      "status": 200,
      "fetchMs": 79
    },
    {
      "url": "https://feedbackminer.co/features",
      "bytes": 23834,
      "status": 200,
      "fetchMs": 73
    },
    {
      "url": "https://feedbackminer.co/",
      "bytes": 36612,
      "status": 200,
      "fetchMs": 17
    },
    {
      "url": "https://feedbackminer.co/use-cases",
      "bytes": 15720,
      "status": 200,
      "fetchMs": 65
    },
    {
      "url": "https://feedbackminer.co/signup",
      "bytes": 12194,
      "status": 200,
      "fetchMs": 66
    },
    {
      "url": "https://feedbackminer.co/terms",
      "bytes": 7257,
      "status": 404,
      "fetchMs": 16
    },
    {
      "url": "https://feedbackminer.co/privacy",
      "bytes": 7257,
      "status": 404,
      "fetchMs": 16
    },
    {
      "url": "https://feedbackminer.co/cookies",
      "bytes": 7257,
      "status": 404,
      "fetchMs": 16
    }
  ],
  "origin": "https://feedbackminer.co",
  "target": "https://feedbackminer.co"
}

2. Data Found

Data Point	Found?	Source	Notes
Pricing	Yes	Pricing page	https://feedbackminer.co/pricing
Customer logos	No	—	—
Social proof	No	—	—
Recent launches	No	—	—
Blog post activity	No	—	—
New hires	No	—	Often only on a /blog/team or LinkedIn page
Headline copy	Yes	Homepage	Customer interviews at survey scale
Positioning	No	—	—
Executive team	No	—	—
Product/service descriptions	Yes	Navigation links	https://feedbackminer.co/features
Case studies or testimonials	No	—	—
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

warn
Short `<title>` (14 chars)
Aim for 30–60 chars. Lead with brand or product, then value prop.
Evidence
```
{
  "title": "Feedback Miner"
}
```
P3

warn

Long meta description (206 chars)

Snippets truncate around 160 chars. Tighten to keep the key sentence visible.

Evidence

{
  "description": "Feedback Miner runs a real 1:1 conversation with every one of your contacts over email, WhatsApp or SMS — asking follow-ups until it reaches the actual reason. You pick who to ask and what you want to know."
}

warn
Missing canonical link
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
P3
fail
Open Graph: missing title, description, image
P3
warn
No Twitter Card tags
Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces.
P3
pass
Favicon declared
Evidence
```
{
  "href": "/favicon.svg"
}
```
P5
pass
Internal links: 13
13 internal + 0 external links help crawlers navigate.
Evidence
```
{
  "external": 0,
  "internal": 13
}
```
P5
pass
Heading structure: 24 (h1:1, h2:6, h3:17)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 1,
  "h2": 6,
  "h3": 17
}
```
P5
pass
Content volume: 664 words
Substantive content — AI models have enough to summarize and recommend.
Evidence
```
{
  "wordCount": 664
}
```
P5
pass
Critical content is server-rendered
Raw and rendered text are within 57% of each other.
Evidence
```
{
  "ratio": 0.5736468999662429,
  "rawTextLen": 8887,
  "renderedTextLen": 5098
}
```
P5
pass
Single H1
Customer interviews at survey scale
Evidence
```
{
  "h1": "Customer interviews at survey scale"
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5
pass
Page load time: 0.12s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 124
}
```
P5
pass
Homepage fetched successfully
HTTP 200 · 36612 bytes · 124ms
Evidence
```
{
  "bytes": 36612,
  "status": 200,
  "fetchMs": 124
}
```
P5

4. Content Quality

warn
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.
P3
warn
No date signal found
Add <time datetime="…"> or article:published_time meta. AI ranking weights freshness.
P3
warn
No author byline found
Add `<meta name="author" content="Name">` or a visible byline with `rel="author"`. Strengthens E-E-A-T signals.
P4
pass
1 definition list(s) present
Definition lists give AI answer engines explicit term→meaning pairs.
P5
pass
Snippet-ready blocks: 11 (ul:8, ol:2, table:1)
Lists and tables are extracted verbatim by AI answer engines.
Evidence
```
{
  "ol": 2,
  "ul": 8,
  "tables": 1
}
```
P5

pass

Heading levels are well-ordered

24 headings nested in order.

Evidence

{
  "levels": [
    1,
    2,
    2,
    3,
    3,
    3,
    2,
    3,
    3,
    3,
    3,
    3,
    2,
    3,
    3,
    3,
    2,
    3,
    3,
    3,
    3,
    3,
    3,
    2
  ]
}

pass
Text-to-HTML ratio: 12.3%
Visible text density is healthy for AI extraction.
Evidence
```
{
  "ratio": 0.12305210782437531,
  "htmlBytes": 36578,
  "textChars": 4501
}
```
P5

5. Schema / Structured Data Audit

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

6. Links & Images

fail

4 broken link(s) in first 9

· 404 — https://feedbackminer.co/terms · 404 — https://feedbackminer.co/privacy · 404 — https://feedbackminer.co/cookies · 404 — https://feedbackminer.co/sub-processors

Evidence

{
  "broken": 4,
  "sampled": 9,
  "examples": [
    {
      "url": "https://feedbackminer.co/terms",
      "status": 404
    },
    {
      "url": "https://feedbackminer.co/privacy",
      "status": 404
    },
    {
      "url": "https://feedbackminer.co/cookies",
      "status": 404
    },
    {
      "url": "https://feedbackminer.co/sub-processors",
      "status": 404
    }
  ]
}

7. Performance

pass
Compression enabled (Brotli)
Content-Encoding: br
Evidence
```
{
  "encoding": "br"
}
```
P5
pass
Cache-Control set (CDN: Cloudflare)
Cache-Control: public, max-age=0, must-revalidate CDN detected: Cloudflare
Evidence
```
{
  "cdn": [
    "Cloudflare"
  ],
  "cacheControl": "public, max-age=0, must-revalidate"
}
```
P5
pass
Response time: 124ms
Fast first response.
Evidence
```
{
  "bytes": 36612,
  "fetchMs": 124
}
```
P5
pass
Inline JS+CSS bulk: 4 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 546,
  "inlineCssBytes": 3895
}
```
P5
pass
No render-blocking head scripts
All head scripts use async or defer.
P5

pass

Resource requests: 6 (scripts:3, css:3, img:0)

Reasonable request count.

Evidence

{
  "imgs": 0,
  "styles": 3,
  "scripts": 3,
  "inlineStyles": 2,
  "inlineScripts": 2
}

pass
Page size: 36 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 36612
}
```
P5

8. Security

warn
HSTS missing
Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you're confident in https.
P3
warn
Content-Security-Policy missing
Define a CSP to limit script sources — large reduction in XSS surface.
P3
warn
Permissions-Policy missing
Restrict browser features (camera, mic, geolocation) you don't use.
P4
pass
X-Content-Type-Options set
nosniff
Evidence
```
{
  "value": "nosniff"
}
```
P5
pass
Referrer-Policy set
strict-origin-when-cross-origin
Evidence
```
{
  "value": "strict-origin-when-cross-origin"
}
```
P5
pass
X-Frame-Options set
DENY
Evidence
```
{
  "value": "DENY"
}
```
P5
pass
No mixed content detected
P5

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://feedbackminer.co/"
}

9. robots.txt and sitemap.xml Audit

fail
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.
P1
warn
robots.txt does not reference a Sitemap
Add `Sitemap: https://yoursite.com/sitemap.xml` to robots.txt.
P3

pass

robots.txt present

1859 chars

Evidence

{
  "snippet": "# As a condition of accessing this website, you agree to abide by the following\n# content signals:\n\n# (a)  If a Content-Signal = yes, you may collect content for the corresponding\n#      use.\n# (b)  If a Content-Signal = no, you may not collect content for the\n#      corresponding use.\n# (c)  If the website operator does not include a Content-Signal for a\n#      corresponding use, the website operator neither grants nor restricts\n#      permission via Content-Signal with respect to the corresponding use.\n\n# The content signals and their meanings are:\n\n# search:   building a search index and providing search results (e.g., returning\n#           hyperlinks and short excerpts from your website's contents). Search does not\n#           include providing AI-generated search summaries.\n# ai-input"
}

10. LLM / AI Crawler Accessibility

fail
Google-Extended is blocked
robots.txt disallows Google-Extended from /. This bot cannot index your site.
P1
fail
Applebot-Extended is blocked
robots.txt disallows Applebot-Extended from /. This bot cannot index your site.
P1
fail
CCBot is blocked
robots.txt disallows CCBot from /. This bot cannot index your site.
P1
fail
GPTBot is blocked
robots.txt disallows GPTBot from /. This bot cannot index your site.
P1
fail
ClaudeBot is blocked
robots.txt disallows ClaudeBot from /. This bot cannot index your site.
P1
warn
llms.txt missing
Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
P2
warn
PerplexityBot not explicitly addressed
No User-agent: PerplexityBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
OAI-SearchBot not explicitly addressed
No User-agent: OAI-SearchBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
skill.md missing
Add /skill.md describing what your site lets agents do — speeds up agent task routing.
P3
warn
/.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.
P3
warn
/llms-full.txt missing
Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.
P3

11. Generative Engine Optimization (GEO)

fail
No llms.txt found
llms.txt tells generative AI systems what to read, index, and cite. Create /llms.txt following the llmstxt.org spec — include headings, page descriptions, and links to key resources.
P1
warn
No Organization schema — brand cannot be anchored in knowledge graphs
Add an Organization JSON-LD block with `sameAs` links to Wikipedia, Wikidata, LinkedIn, or Crunchbase. This resolves your brand as a distinct entity in AI knowledge graphs, significantly improving citation likelihood.
P2
warn
No AI agent integration files found
Add at least one: /.well-known/ai-plugin.json (ChatGPT plugin discovery), /.well-known/agent-card.json (A2A protocol), or /skill.md (Claude tool integration). These let AI agents interact with your site programmatically and signal that your site is AI-native.
P2
warn
Brand name not declared in structured data
Add a `name` field to your Organization (or SoftwareApplication) JSON-LD block. AI systems use this to recognise your brand as a distinct, citable entity rather than inferring it from page text.
P2
warn
No llms-full.txt found
llms-full.txt is an extended version of llms.txt that embeds the full text of every listed resource. Large-context models and RAG pipelines can ingest your entire site in one request — greatly improving citation coverage.
P3
warn
No outbound links to authoritative sources on the homepage
Generative AI systems cite pages that themselves cite credible sources. Link to Wikipedia, .gov, .edu, peer-reviewed research, or major news outlets to signal epistemic trustworthiness.
P3

12. Positioning Clarity

warn
No clear About/Team link
Add an About or Team link in the nav or footer so LLMs can identify the company.
P2
warn
Value-prop language not detected
Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
P3
pass
Pricing path discoverable
P5
pass
Contact / signup path discoverable
P5
pass
H1 communicates value
Customer interviews at survey scale
P5

13. Foundations

warn
No theme-color meta tag
Add <meta name="theme-color" content="#yourcolor"> to tint the browser chrome on mobile.
P4
warn
No feed announced
Add <link rel="alternate" type="application/rss+xml" href="/feed.xml"> so agents and readers can subscribe.
P4
pass
<!doctype html> declared
P5
pass
Meta viewport present
content="width=device-width, initial-scale=1"
Evidence
```
{
  "content": "width=device-width, initial-scale=1"
}
```
P5

14. Accessibility

warn
No skip navigation link found
Add a visible-on-focus skip link as the first focusable element: <a href="#main">Skip to main content</a>.
P3
pass
All semantic landmarks present (header/nav/main/footer)
Evidence
```
{
  "nav": 1,
  "main": 1,
  "footer": 1,
  "header": 1
}
```
P5

15. Well-Known URIs

warn
/.well-known/change-password missing
Redirect /.well-known/change-password to your password-change page so password managers can deep-link directly.
P4
warn
/.well-known/api-catalog missing
Publish a /.well-known/api-catalog (RFC 9727 Linkset) so agents can discover your API endpoints automatically.
P4
warn
/.well-known/agent-card.json missing
Publish an agent card at /.well-known/agent-card.json to enable agent-to-agent (A2A) discovery.
P4
warn
No HTTP Link header
Add a Link response header to advertise sitemap, llms.txt, and api-catalog to crawlers without requiring HTML parsing.
P4

16. Privacy

warn
2 third-party script(s) loaded
Each external script can read cookies and page data. Audit: https://www.googletagmanager.com/gtag/js?id=G-7LQ8FTY2XG, https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496
Evidence
```
{
  "scripts": [
    "https://www.googletagmanager.com/gtag/js?id=G-7LQ8FTY2XG",
    "https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496"
  ]
}
```
P4
pass
Privacy policy link found
/privacy
Evidence
```
{
  "href": "/privacy"
}
```
P5

17. Resilience

warn
No Web App Manifest found
Add <link rel="manifest" href="/manifest.json"> and a manifest.json with name, icons, start_url, and display.
P4

18. Website Specification

No findings.

19. Missing or Hard-to-Find Information

fail
8 data point(s) could not be found from public pages
· Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials
Evidence
```
{
  "missing": [
    "Customer logos",
    "Social proof",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Positioning",
    "Executive team",
    "Case studies or testimonials"
  ]
}
```
P1

20. Recommended Fixes

warn
Add JSON-LD structured data
Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.
Evidence
```
{
  "for": "schema.any"
}
```
P1
warn
Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
Evidence
```
{
  "for": "sitemap.exists"
}
```
P1
warn
Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.CCBot"
}
```
P1
warn
Allow Applebot-Extended in robots.txt
Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Applebot-Extended"
}
```
P1
warn
Allow Google-Extended in robots.txt
Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Google-Extended"
}
```
P1
warn
Allow ClaudeBot in robots.txt
Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.ClaudeBot"
}
```
P1
warn
Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.GPTBot"
}
```
P1
warn
Fix broken homepage links
We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
Evidence
```
{
  "for": "links.broken_sample"
}
```
P1
warn
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.
Evidence
```
{
  "for": "geo.llms_txt"
}
```
P1
warn
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.
Evidence
```
{
  "for": "positioning.who"
}
```
P2
warn
Add /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
Evidence
```
{
  "for": "llms_txt"
}
```
P2
warn
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.
Evidence
```
{
  "for": "geo.brand_entity"
}
```
P2
warn
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.
Evidence
```
{
  "for": "geo.agent_integration"
}
```
P2
warn
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.
Evidence
```
{
  "for": "geo.knowledge_graph"
}
```
P2
warn
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.
Evidence
```
{
  "for": "content.qa_headings"
}
```
P3
warn
Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "for": "content.date_signal"
}
```
P3
warn
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.
Evidence
```
{
  "for": "geo.llms_full_txt"
}
```
P3
warn
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.
Evidence
```
{
  "for": "geo.citation_signals"
}
```
P3
warn
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> ```
Evidence
```
{
  "for": "homepage.title"
}
```
P3
warn
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." /> ```
Evidence
```
{
  "for": "homepage.description"
}
```
P3
warn
Add a canonical link
Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html <link rel="canonical" href="https://yoursite.com/" /> ```
Evidence
```
{
  "for": "homepage.canonical"
}
```
P3
warn
Complete Open Graph tags
AI bots use OG for fast disambiguation. Add all four: ```html <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" /> ```
Evidence
```
{
  "for": "homepage.og"
}
```
P3
warn
Add Twitter Card meta tags
Used by social platforms and AI agents for richer previews. ```html <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" /> ```
Evidence
```
{
  "for": "homepage.twitter"
}
```
P3
warn
Allow PerplexityBot in robots.txt
Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.PerplexityBot"
}
```
P3
warn
Allow OAI-SearchBot in robots.txt
Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.OAI-SearchBot"
}
```
P3
warn
Add /skill.md
Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
Evidence
```
{
  "for": "skill_md"
}
```
P3
warn
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 ```
Evidence
```
{
  "for": "security_txt"
}
```
P3
warn
State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "for": "positioning.audience"
}
```
P3
warn
Reference your sitemap in robots.txt
Add `Sitemap: https://yoursite.com/sitemap.xml` so crawlers don't have to guess.
Evidence
```
{
  "for": "robots.sitemap_ref"
}
```
P3
warn
Enable HSTS
Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you're confident every subdomain is https-ready.
Evidence
```
{
  "for": "security.hsts"
}
```
P3
warn
Define a Content-Security-Policy
Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius.
Evidence
```
{
  "for": "security.csp"
}
```
P3
warn
Set a Permissions-Policy
Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`.
Evidence
```
{
  "for": "security.permissions"
}
```
P4
warn
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.
Evidence
```
{
  "for": "content.author"
}
```
P4

21. Priority To-Do List

warn
[ ] Add JSON-LD structured data
Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Fix broken homepage links
We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] 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.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Allow Applebot-Extended in robots.txt
Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Allow Google-Extended in robots.txt
Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Allow ClaudeBot in robots.txt
Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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> ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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." /> ```
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for feedbackminer.co

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Positioning Clarity

12. Missing or Hard-to-Find Information

13. Recommended Fixes

14. Priority To-Do List

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Generative Engine Optimization (GEO)

12. Positioning Clarity

13. Foundations

14. Accessibility

15. Well-Known URIs

16. Privacy

17. Resilience

18. Website Specification

19. Missing or Hard-to-Find Information

20. Recommended Fixes

21. Priority To-Do List

Track this site week over week

Your charts, not these.

Email yourself this report

Watch this URL