# AEO Audit for clarity-cloud.com **Target:** https://www.clarity-cloud.com/ **Score:** 34 / 100 **Generated:** 2026-05-21T16:28:39.071Z **Pages crawled:** 1 **Findings:** 36 pass · 63 warn · 9 fail · 0 unknown --- ## 1. Crawl Summary - ✅ **Fetched 1 of 1 pages successfully** Target: https://www.clarity-cloud.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 | No | — | — | | Positioning | No | — | — | | Executive team | No | — | — | | Product/service descriptions | Yes | Homepage | From meta description | | Case studies or testimonials | No | — | — | | Contact/demo/signup paths | No | — | — | ## 3. Homepage Audit - ❌ **Missing H1** No `

` element found. LLMs use the H1 as the strongest signal of what the page is about. - ❌ Content volume: 0 words Very thin content. AI models need substantive text to understand and recommend your site. - ❌ Heading structure: 0 (h1:0, h2:0, h3:0) Few headings make it hard for AI to understand sectioning. Use h2/h3 to label each section. - ❌ Internal links: 0 Few internal links. Add a nav/footer with links to your key pages so AI crawlers can discover them. - ✅ Homepage fetched successfully HTTP 200 · 6560 bytes · 733ms - ✅ Page load time: 0.73s Fast — well within AI crawler budgets. - ✅ declared - ✅ `` present (47 chars) - ✅ Meta description present (151 chars) - ✅ Canonical present https://www.clarity-cloud.com/ - ✅ Open Graph tags complete - ✅ Twitter Card tags complete - ✅ Critical content is server-rendered Raw and rendered text are within 45% of each other. - ✅ Robots meta: "index, follow" - ✅ hreflang: 2 alternate(s) Locales: en, x-default - ✅ Favicon declared ## 4. Content Quality - ❌ Snippet-ready blocks: 0 (ul:0, ol:0, table:0) Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose. - ❌ Text-to-HTML ratio: 0.0% Very low text density. AI crawlers will struggle to find substantive content. - ⚠️ 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 <time datetime="…"> or article:published_time meta. AI ranking weights freshness. - ✅ Author byline declared ## 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 _No findings._ ## 7. Performance - ⚠️ 1 render-blocking script(s) in <head> Move non-critical scripts to end of <body> or add `defer`/`async`. - ⚠️ Response time: 733ms Slow response. Check CDN/cache headers and origin latency. - ✅ Page size: 6 KB Compact HTML payload — well within AI crawler limits. - ✅ Resource requests: 4 (scripts:2, css:2, img:0) Reasonable request count. - ✅ Inline JS+CSS bulk: 2 KB Inline payload is modest. - ✅ Cache-Control set (CDN: Cloudflare) Cache-Control: no-cache, must-revalidate, max-age=0 CDN detected: Cloudflare ## 8. Security - ⚠️ Content-Security-Policy missing Define a CSP to limit script sources — large reduction in XSS surface. - ⚠️ X-Frame-Options missing Add `X-Frame-Options: SAMEORIGIN` (or use CSP frame-ancestors) to prevent clickjacking. - ⚠️ 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-Content-Type-Options set nosniff - ✅ Referrer-Policy set strict-origin-when-cross-origin ## 9. robots.txt and sitemap.xml Audit - ✅ robots.txt present 923 chars - ✅ robots.txt references sitemap(s) - ✅ sitemap.xml present (29 URLs) ## 10. LLM / AI Crawler Accessibility - ⚠️ skill.md missing Add /skill.md describing what your site lets agents do — speeds up agent task routing. - ✅ GPTBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ ClaudeBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ PerplexityBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ Google-Extended has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ OAI-SearchBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ Applebot-Extended has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ CCBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed. - ✅ llms.txt present 6437 chars - ✅ /.well-known/security.txt present Security contact published — builds trust with crawlers and security researchers. ## 11. Positioning Clarity - ⚠️ H1 missing or too short to convey value Add a clear, single-sentence H1 like 'We help X do Y.' - ❌ No discoverable CTA Add a clearly-labeled Contact, Demo, or Sign up link to the nav or hero. - ⚠️ No clear About/Team link Add an About or Team link in the nav or footer so LLMs can identify the company. - ⚠️ No pricing/plans link found AI summaries commonly include pricing. Add a /pricing page even if pricing is custom. - ⚠️ Value-prop language not detected Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize. ## 12. Missing or Hard-to-Find Information - ❌ 11 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Headline copy · Positioning · Executive team · Case studies or testimonials · Contact/demo/signup paths ## 13. Recommended Fixes - ⚠️ Add a single, focused H1 to the homepage One `<h1>` per page. Write it as 'We help [audience] [do thing].' so an LLM can quote it verbatim. - ⚠️ 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. - ⚠️ Rewrite the homepage H1 to be self-evident Replace clever copy with literal copy. 'We help X do Y' beats 'Reimagine Y'. - ⚠️ Add a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label. - ⚠️ Add JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section. - ⚠️ Add lists or comparison tables Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage. - ⚠️ 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. - ⚠️ Make your About/Team page reachable Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site. - ⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers. - ⚠️ 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. - ⚠️ Add structured headings Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page. - ⚠️ Add internal navigation links Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site. - ⚠️ 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>`. - ⚠️ 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=…`. - ⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page. - ⚠️ Define a Content-Security-Policy Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius. - ⚠️ Add X-Frame-Options `X-Frame-Options: SAMEORIGIN` (or CSP `frame-ancestors`) blocks clickjacking via iframe embeds. - ⚠️ Set a Permissions-Policy Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`. ## 14. Priority To-Do List - [ ] P1 — Add a single, focused H1 to the homepage One `<h1>` per page. Write it as 'We help [audience] [do thing].' so an LLM can quote it verbatim. - [ ] P1 — Add more substantive homepage content AI models need 300+ words of visible body text to summarize and recommend a site. Add a value-prop paragraph, a short FAQ, and a 'how it works' section. - [ ] P1 — Rewrite the homepage H1 to be self-evident Replace clever copy with literal copy. 'We help X do Y' beats 'Reimagine Y'. - [ ] P1 — Add a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label. - [ ] P1 — Add JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section. - [ ] P2 — Add lists or comparison tables Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage. - [ ] P2 — 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 — Make your About/Team page reachable Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site. - [ ] P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers. - [ ] 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 — Add structured headings Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page. - [ ] P3 — Add internal navigation links Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site. - [ ] P3 — Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows. - [ ] P3 — Eliminate render-blocking head scripts Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`. - [ ] P3 — 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=…`. - [ ] P3 — State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page. - [ ] P3 — Define a Content-Security-Policy Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius. - [ ] P4 — Add X-Frame-Options `X-Frame-Options: SAMEORIGIN` (or CSP `frame-ancestors`) blocks clickjacking via iframe embeds. - [ ] P4 — Set a Permissions-Policy Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`. --- _Report by [CrawlProof](https://crawlproof.com). Reusable after every major website change._