Public share link

AEO Audit for planqr.com

Target: https://planqr.com/
Score: 49 / 100
Generated: 2026-09-02T20:27:30.698Z
Pages crawled: 9
Findings: 46 pass · 113 warn · 4 fail · 0 unknown

1. Crawl Summary

✅ Fetched 9 of 9 pages successfully Target: https://planqr.com

2. Data Found

Data Point	Found?	Source	Notes
Pricing	No	—	—
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	QR code management for businesses and designers.
Positioning	No	—	—
Executive team	Yes	About/team page	https://planqr.com/about
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	No	—	—
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

⚠️ Alt text coverage: 50% 1/2 images have alt text.
⚠️ Content volume: 288 words Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
✅ Homepage fetched successfully HTTP 200 · 127805 bytes · 630ms
✅ Page load time: 0.63s Fast — well within AI crawler budgets.
✅ declared
✅ Single H1 QR code management for businesses and designers.
✅ <title> present (40 chars)
✅ Meta description present (104 chars)
✅ Canonical present https://planqr.com/
✅ Open Graph tags complete
✅ Twitter Card tags complete
✅ Critical content is server-rendered Raw and rendered text are within 2% of each other.
✅ Heading structure: 11 (h1:1, h2:5, h3:5) Multiple headings help AI chunk and outline your page.
✅ Internal links: 12 12 internal + 3 external links help crawlers navigate.
✅ Favicon declared

4. Content Quality

❌ Text-to-HTML ratio: 1.3% Very low text density. AI crawlers will struggle to find substantive content.
⚠️ Snippet-ready blocks: 1 (ul:1, ol:0, table:0) Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
⚠️ 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 11 headings nested in order.
✅ 1 question-style heading(s) Questions in headings map cleanly to user queries. Pair with FAQPage JSON-LD for max lift.

5. Schema / Structured Data Audit

⚠️ Organization missing Adding Organization JSON-LD helps LLMs identify your entity.
⚠️ WebSite missing Adding WebSite JSON-LD helps LLMs identify your entity.
⚠️ FAQPage JSON-LD missing Add an FAQPage block on pages that answer common questions — high-value for AI summaries.
⚠️ Article / BlogPosting JSON-LD not found Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
⚠️ BreadcrumbList JSON-LD not found Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
⚠️ LocalBusiness JSON-LD not found Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
⚠️ Person (author / founder) JSON-LD not found Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
⚠️ HowTo JSON-LD not found Add HowTo where applicable so AI answer engines can resolve the entity precisely.
⚠️ VideoObject JSON-LD not found Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
✅ 1 JSON-LD block(s) found Types: SoftwareApplication
✅ SoftwareApplication present

6. Links & Images

⚠️ Modern image formats: 0% (0/2 webp/avif) 0 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
❌ Explicit dimensions: 0% (0/2) Add width and height attributes on tags to prevent CLS.
✅ External nofollow: 0% (0/3) Healthy mix of follow and nofollow outbound links.
✅ No broken links in first 13 HEAD-probed the first 20 unique homepage links — all 2xx/3xx.

7. Performance

⚠️ 1 render-blocking script(s) in Move non-critical scripts to end of or add defer/async.
⚠️ Inline JS+CSS bulk: 72 KB Move large inline scripts/styles to external files to enable caching.
⚠️ Response time: 630ms Slow response. Check CDN/cache headers and origin latency.
⚠️ No Cache-Control header Add a Cache-Control header so CDNs and AI crawlers can revalidate efficiently.
✅ Page size: 125 KB Compact HTML payload — well within AI crawler limits.
✅ Resource requests: 4 (scripts:2, css:0, img:2) Reasonable request count.
✅ Compression enabled (Brotli) Content-Encoding: br
✅ Lazy loading: 1/2 images

8. Security

⚠️ Content-Security-Policy missing Define a CSP to limit script sources — large reduction in XSS surface.
⚠️ 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
✅ HSTS set max-age=31536000; includeSubDomains
✅ X-Frame-Options set SAMEORIGIN
✅ X-Content-Type-Options set nosniff

9. robots.txt and sitemap.xml Audit

✅ robots.txt present 65 chars
✅ robots.txt references sitemap(s)
✅ sitemap.xml present (4 URLs)

10. LLM / AI Crawler Accessibility

⚠️ GPTBot not explicitly addressed No User-agent: GPTBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ ClaudeBot not explicitly addressed No User-agent: ClaudeBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ 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.
⚠️ Google-Extended not explicitly addressed No User-agent: Google-Extended 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.
⚠️ Applebot-Extended not explicitly addressed No User-agent: Applebot-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
⚠️ CCBot not explicitly addressed No User-agent: CCBot 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.
⚠️ /llms-full.txt missing Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.
✅ llms.txt present 1195 chars
✅ /.well-known/security.txt present Security contact published — builds trust with crawlers and security researchers.

11. Positioning Clarity

⚠️ 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.
✅ About/Team path discoverable
✅ H1 communicates value QR code management for businesses and designers.
✅ Contact / signup path discoverable

12. Missing or Hard-to-Find Information

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

13. Recommended Fixes

⚠️ Raise your text-to-HTML ratio Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.

⚠️ 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.
⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
⚠️ Add Organization JSON-LD Include name, url, logo, sameAs (your social profiles). LLMs use this to resolve your brand entity.
⚠️ 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.
⚠️ 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.
⚠️ Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
⚠️ 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.
⚠️ Use modern image formats Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as fallbacks.
⚠️ Set width/height on images Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
⚠️ 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 PerplexityBot in robots.txt Add an explicit User-agent: PerplexityBot 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 OAI-SearchBot in robots.txt Add an explicit User-agent: OAI-SearchBot 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.
⚠️ Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
⚠️ Eliminate render-blocking head scripts Add defer or async to any <script src="…"> in <head>, or move it to the end of <body>.
⚠️ Externalize large inline JS/CSS Inline blobs aren't cacheable. Move >50 KB inline payloads to versioned external files.
⚠️ Reduce response time Push static HTML to a CDN edge cache. If you must server-render per-request, profile DB/template work and add Cache-Control: s-maxage=….
⚠️ 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.
⚠️ Add WebSite JSON-LD Helps engines understand the root site and enables sitelinks-search-box features.
⚠️ Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
⚠️ Add Article / BlogPosting JSON-LD On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
⚠️ Add BreadcrumbList JSON-LD Helps AI engines understand site hierarchy and improves citation context.
⚠️ 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 LocalBusiness JSON-LD (if you have a physical location) Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
⚠️ Add Person JSON-LD for authors / founders Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
⚠️ Add HowTo JSON-LD for step-by-step content For any 'how to' page, wrap the steps in HowTo JSON-LD. AI step-by-step answers cite these heavily.
⚠️ Add VideoObject JSON-LD For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.
⚠️ 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

P2 — Raise your text-to-HTML ratio Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.

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 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
P2 — Add Organization JSON-LD Include name, url, logo, sameAs (your social profiles). LLMs use this to resolve your brand entity.
P3 — 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.
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 — Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
P3 — 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.
P3 — Use modern image formats Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as fallbacks.
P3 — Set width/height on images Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
P3 — Allow GPTBot in robots.txt Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
P3 — Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
P3 — Allow PerplexityBot in robots.txt Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
P3 — Allow Google-Extended in robots.txt Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
P3 — Allow OAI-SearchBot in robots.txt Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
P3 — Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
P3 — Allow CCBot in robots.txt Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.

Report by CrawlProof. Reusable after every major website change.

AEO audit

https://planqr.com/

Completed 9/2/2026, 8:27:31 PM

/100

1. Crawl Summary

pass

Fetched 9 of 9 pages successfully

Target: https://planqr.com

Evidence

{
  "pages": [
    {
      "url": "https://planqr.com",
      "bytes": 127805,
      "status": 200,
      "fetchMs": 630
    },
    {
      "url": "https://planqr.com/about",
      "bytes": 5028,
      "status": 200,
      "fetchMs": 171
    },
    {
      "url": "https://planqr.com/",
      "bytes": 127805,
      "status": 200,
      "fetchMs": 88
    },
    {
      "url": "https://planqr.com/login",
      "bytes": 6064,
      "status": 200,
      "fetchMs": 185
    },
    {
      "url": "https://planqr.com/signup",
      "bytes": 6073,
      "status": 200,
      "fetchMs": 654
    },
    {
      "url": "https://planqr.com/emoji-qr-code",
      "bytes": 52311,
      "status": 200,
      "fetchMs": 135
    },
    {
      "url": "https://planqr.com/svg-qr-code",
      "bytes": 52251,
      "status": 200,
      "fetchMs": 118
    },
    {
      "url": "https://planqr.com/legal",
      "bytes": 35418,
      "status": 200,
      "fetchMs": 115
    },
    {
      "url": "https://planqr.com/licenses",
      "bytes": 5502,
      "status": 200,
      "fetchMs": 297
    }
  ],
  "origin": "https://planqr.com",
  "target": "https://planqr.com"
}

2. Data Found

Data Point	Found?	Source	Notes
Pricing	No	—	—
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	QR code management for businesses and designers.
Positioning	No	—	—
Executive team	Yes	About/team page	https://planqr.com/about
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	No	—	—
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

warn
Alt text coverage: 50%
1/2 images have alt text.
P3
warn
Content volume: 288 words
Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
Evidence
```
{
  "wordCount": 288
}
```
P3
pass
Page load time: 0.63s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 630
}
```
P5
pass
Critical content is server-rendered
Raw and rendered text are within 2% of each other.
Evidence
```
{
  "ratio": 0.01707691281435528,
  "rawTextLen": 74955,
  "renderedTextLen": 1280
}
```
P5

pass

Twitter Card tags complete

Evidence

{
  "card": "summary_large_image",
  "image": "https://planqr.com/og-image.png",
  "title": "PlanQR - Professional QR Code Management",
  "description": "Professional QR code management: unlimited codes and scans, vector exports, and privacy-first analytics."
}

pass
Homepage fetched successfully
HTTP 200 · 127805 bytes · 630ms
Evidence
```
{
  "bytes": 127805,
  "status": 200,
  "fetchMs": 630
}
```
P5
pass
Favicon declared
Evidence
```
{
  "href": "/favicon.svg"
}
```
P5
pass
Internal links: 12
12 internal + 3 external links help crawlers navigate.
Evidence
```
{
  "external": 3,
  "internal": 12
}
```
P5

pass

Open Graph tags complete

Evidence

{
  "image": "https://planqr.com/og-image.png",
  "title": "PlanQR - Professional QR Code Management",
  "description": "Professional QR code management: unlimited codes and scans, vector exports, and privacy-first analytics."
}

pass
Canonical present
https://planqr.com/
Evidence
```
{
  "canonical": "https://planqr.com/"
}
```
P5
pass
Heading structure: 11 (h1:1, h2:5, h3:5)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 1,
  "h2": 5,
  "h3": 5
}
```
P5

pass

Meta description present (104 chars)

Evidence

{
  "description": "Professional QR code management: unlimited codes and scans, vector exports, and privacy-first analytics."
}

pass

`<title>` present (40 chars)

Evidence

{
  "title": "PlanQR - Professional QR Code Management"
}

pass
Single H1
QR code management for businesses and designers.
Evidence
```
{
  "h1": "QR code management for businesses and designers."
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5

4. Content Quality

fail
Text-to-HTML ratio: 1.3%
Very low text density. AI crawlers will struggle to find substantive content.
Evidence
```
{
  "ratio": 0.013404490073791209,
  "htmlBytes": 127793,
  "textChars": 1713
}
```
P2
warn
Snippet-ready blocks: 1 (ul:1, ol:0, table:0)
Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
Evidence
```
{
  "ol": 0,
  "ul": 1,
  "tables": 0
}
```
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 question-style heading(s)
Questions in headings map cleanly to user queries. Pair with FAQPage JSON-LD for max lift.
Evidence
```
{
  "samples": [
    "Questions?"
  ]
}
```
P5

pass

Heading levels are well-ordered

11 headings nested in order.

Evidence

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

5. Schema / Structured Data Audit

warn
Organization missing
Adding Organization JSON-LD helps LLMs identify your entity.
P2
warn
WebSite missing
Adding WebSite JSON-LD helps LLMs identify your entity.
P3
warn
FAQPage JSON-LD missing
Add an FAQPage block on pages that answer common questions — high-value for AI summaries.
P3
warn
Article / BlogPosting JSON-LD not found
Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
P3
warn
BreadcrumbList JSON-LD not found
Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
P3
warn
LocalBusiness JSON-LD not found
Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
P4
warn
Person (author / founder) JSON-LD not found
Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
P4
warn
HowTo JSON-LD not found
Add HowTo where applicable so AI answer engines can resolve the entity precisely.
P4
warn
VideoObject JSON-LD not found
Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
P4
pass
1 JSON-LD block(s) found
Types: SoftwareApplication
Evidence
```
{
  "types": [
    "SoftwareApplication"
  ],
  "blocks": 1
}
```
P5
pass
SoftwareApplication present
P5

6. Links & Images

warn
Modern image formats: 0% (0/2 webp/avif)
0 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
Evidence
```
{
  "total": 2,
  "legacy": 0,
  "modern": 0
}
```
P3
fail
Explicit dimensions: 0% (0/2)
Add width and height attributes on <img> tags to prevent CLS.
Evidence
```
{
  "total": 2,
  "withDims": 0
}
```
P3
pass
External nofollow: 0% (0/3)
Healthy mix of follow and nofollow outbound links.
P5
pass
No broken links in first 13
HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
Evidence
```
{
  "broken": 0,
  "sampled": 13,
  "examples": []
}
```
P5

7. Performance

warn
1 render-blocking script(s) in <head>
Move non-critical scripts to end of <body> or add `defer`/`async`.
P3
warn
Inline JS+CSS bulk: 72 KB
Move large inline scripts/styles to external files to enable caching.
Evidence
```
{
  "inlineJsBytes": 694,
  "inlineCssBytes": 72682
}
```
P3
warn
Response time: 630ms
Slow response. Check CDN/cache headers and origin latency.
Evidence
```
{
  "bytes": 127805,
  "fetchMs": 630
}
```
P3
warn
No Cache-Control header
Add a Cache-Control header so CDNs and AI crawlers can revalidate efficiently.
Evidence
```
{
  "cdn": [
    "Cloudflare"
  ]
}
```
P3
pass
Compression enabled (Brotli)
Content-Encoding: br
Evidence
```
{
  "encoding": "br"
}
```
P5
pass
Lazy loading: 1/2 images
P5
pass
Page size: 125 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 127805
}
```
P5

pass

Resource requests: 4 (scripts:2, css:0, img:2)

Reasonable request count.

Evidence

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

8. Security

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

9. robots.txt and sitemap.xml Audit

pass

sitemap.xml present (4 URLs)

Evidence

{
  "snippet": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://planqr.com/</loc>\n  </url>\n  <url>\n    <loc>https://planqr.com/about</loc>\n  </url>\n  <url>\n    <loc>https://planqr.com/emoji-qr-code</loc>\n  </url>\n  <url>\n    <loc>https://planqr.com/svg-qr-code</loc>\n  </url>\n</urlset>\n",
  "urlCount": 4
}

pass

robots.txt present

65 chars

Evidence

{
  "snippet": "User-agent: *\nDisallow:\n\nSitemap: https://planqr.com/sitemap.xml\n"
}

pass

robots.txt references sitemap(s)

Evidence

{
  "sitemaps": [
    "https://planqr.com/sitemap.xml"
  ]
}

10. LLM / AI Crawler Accessibility

warn
GPTBot not explicitly addressed
No User-agent: GPTBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
ClaudeBot not explicitly addressed
No User-agent: ClaudeBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
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
Google-Extended not explicitly addressed
No User-agent: Google-Extended 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
Applebot-Extended not explicitly addressed
No User-agent: Applebot-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
CCBot not explicitly addressed
No User-agent: CCBot 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
/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

pass

llms.txt present

1195 chars

Evidence

{
  "snippet": "# PlanQR\n\n> QR code management for businesses and designers. Flat-rate. No gotchas.\n\nComing in 2026.\n\nPlanQR is a QR code management platform built for businesses and designers who need reliable, scalable QR code generation with professional print output.\n\nTry the free, no-signup QR code generator right on the homepage—no account required.\n\n## Features\n\n- **Unlimited Everything**: Unlimited codes "
}

pass
/.well-known/security.txt present
Security contact published — builds trust with crawlers and security researchers.
P5

11. Generative Engine Optimization (GEO)

warn
Organization schema has no knowledge graph sameAs links
Add `sameAs` pointing to Wikipedia, Wikidata, LinkedIn, or Crunchbase. AI systems use these links to resolve your brand name as a known entity rather than an ambiguous string.
Evidence
```
{
  "existingSameAs": []
}
```
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
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

pass

llms.txt present with meaningful content

4 section(s), 4 linked resource(s), 156 words.

Evidence

{
  "words": 156,
  "snippet": "# PlanQR\n\n> QR code management for businesses and designers. Flat-rate. No gotchas.\n\nComing in 2026.\n\nPlanQR is a QR code management platform built for businesses and designers who need reliable, scalable QR code generation with professional print output.\n\nTry the free, no-signup QR code generator right on the homepage—no account required.\n\n## Features\n\n- **Unlimited Everything**: Unlimited codes ",
  "headings": 4,
  "urlLines": 4
}

pass
Brand entity declared: "PlanQR"
AI systems can resolve "PlanQR" as a distinct entity. Ensure this name is used consistently in titles, H1s, and social profiles.
Evidence
```
{
  "schemaName": "PlanQR"
}
```
P5

12. Positioning Clarity

warn
No pricing/plans link found
AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
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
About/Team path discoverable
P5
pass
H1 communicates value
QR code management for businesses and designers.
P5
pass
Contact / signup path discoverable
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
Meta viewport present
content="width=device-width, initial-scale=1.0"
Evidence
```
{
  "content": "width=device-width, initial-scale=1.0"
}
```
P5
pass
<!doctype html> declared
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
warn
Missing landmark(s): <header>
Semantic landmarks help screen readers and AI agents navigate page structure.
Evidence
```
{
  "nav": 2,
  "main": 1,
  "footer": 1,
  "header": 0
}
```
P3
fail
Form label coverage: 14% (6/44)
Each form input needs a <label for=…>, aria-label, or aria-labelledby for screen readers.
P3

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
1 third-party script(s) loaded
Each external script can read cookies and page data. Audit: https://static.cloudflareinsights.com/beacon.min.js/v3d52b47920f24c319d37e2661827c42b1787588026925
Evidence
```
{
  "scripts": [
    "https://static.cloudflareinsights.com/beacon.min.js/v3d52b47920f24c319d37e2661827c42b1787588026925"
  ]
}
```
P4
pass
Privacy policy link found
/legal#privacy
Evidence
```
{
  "href": "/legal#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
· Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Case studies or testimonials
Evidence
```
{
  "missing": [
    "Pricing",
    "Customer logos",
    "Social proof",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Positioning",
    "Case studies or testimonials"
  ]
}
```
P1

20. Recommended Fixes

warn
Add Organization JSON-LD
Include name, url, logo, sameAs (your social profiles). LLMs use this to resolve your brand entity.
Evidence
```
{
  "for": "schema.org"
}
```
P2
warn
Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "for": "positioning.pricing"
}
```
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
Raise your text-to-HTML ratio
Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
Evidence
```
{
  "for": "content.text_ratio"
}
```
P2
warn
Reduce response time
Push static HTML to a CDN edge cache. If you must server-render per-request, profile DB/template work and add `Cache-Control: s-maxage=…`.
Evidence
```
{
  "for": "perf.response_time"
}
```
P3
warn
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.
Evidence
```
{
  "for": "perf.caching"
}
```
P3
warn
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.
Evidence
```
{
  "for": "content.snippet_blocks"
}
```
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
Add alt text to all meaningful images
Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
Evidence
```
{
  "for": "homepage.alt_text"
}
```
P3
warn
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.
Evidence
```
{
  "for": "homepage.word_count"
}
```
P3
warn
Use modern image formats
Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as <picture> fallbacks.
Evidence
```
{
  "for": "images.format"
}
```
P3
warn
Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "for": "images.dimensions"
}
```
P3
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"
}
```
P3
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"
}
```
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 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"
}
```
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
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"
}
```
P3
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"
}
```
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
Eliminate render-blocking head scripts
Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`.
Evidence
```
{
  "for": "perf.render_blocking"
}
```
P3
warn
Externalize large inline JS/CSS
Inline blobs aren't cacheable. Move >50 KB inline payloads to versioned external files.
Evidence
```
{
  "for": "perf.inline_bulk"
}
```
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
Add WebSite JSON-LD
Helps engines understand the root site and enables sitelinks-search-box features.
Evidence
```
{
  "for": "schema.web"
}
```
P3
warn
Add FAQPage JSON-LD
Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
Evidence
```
{
  "for": "schema.faq"
}
```
P3
warn
Add Article / BlogPosting JSON-LD
On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
Evidence
```
{
  "for": "schema.article"
}
```
P3
warn
Add BreadcrumbList JSON-LD
Helps AI engines understand site hierarchy and improves citation context.
Evidence
```
{
  "for": "schema.breadcrumb"
}
```
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 Referrer-Policy
`Referrer-Policy: strict-origin-when-cross-origin` is a safe default.
Evidence
```
{
  "for": "security.referrer"
}
```
P4
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
Add HowTo JSON-LD for step-by-step content
For any 'how to' page, wrap the steps in HowTo JSON-LD. AI step-by-step answers cite these heavily.
Evidence
```
{
  "for": "schema.howto"
}
```
P4
warn
Add VideoObject JSON-LD
For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.
Evidence
```
{
  "for": "schema.video"
}
```
P4
warn
Add Person JSON-LD for authors / founders
Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
Evidence
```
{
  "for": "schema.person"
}
```
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
warn
Add LocalBusiness JSON-LD (if you have a physical location)
Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
Evidence
```
{
  "for": "schema.local_business"
}
```
P4

21. Priority To-Do List

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
[ ] 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
[ ] Raise your text-to-HTML ratio
Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add Organization JSON-LD
Include name, url, logo, sameAs (your social profiles). LLMs use this to resolve your brand entity.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
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
[ ] Add alt text to all meaningful images
Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Use modern image formats
Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as <picture> fallbacks.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow ClaudeBot in robots.txt
Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow PerplexityBot in robots.txt
Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
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": 3
}
```
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
```
{
  "priority": 3
}
```
P3
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": 3
}
```
P3
warn
[ ] Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for planqr.com

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