# AEO Audit for bolapsd.xyz **Target:** https://www.bolapsd.xyz/ **Score:** 40 / 100 **Generated:** 2026-05-21T07:32:52.524Z **Pages crawled:** 7 **Findings:** 28 pass · 88 warn · 6 fail · 0 unknown --- ## 1. Crawl Summary - ✅ **Fetched 7 of 7 pages successfully** Target: https://www.bolapsd.xyz ## 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: 33 words** Very thin content. AI models need substantive text to understand and recommend your site. - ⚠️ **Short `` (7 chars)** Aim for 30–60 chars. Lead with brand or product, then value prop. - ⚠️ **Short meta description (27 chars)** Aim for 50–160 chars. Restate your value prop in plain language. - ⚠️ **Twitter Card: missing image** Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces. - ❌ **Alt text coverage: 0%** 0/2 images have alt text. - ⚠️ **Heading structure: 1 (h1:0, h2:0, h3:1)** Few headings make it hard for AI to understand sectioning. Use h2/h3 to label each section. - ✅ **Homepage fetched successfully** HTTP 200 · 73359 bytes · 273ms - ✅ **Page load time: 0.27s** Fast — well within AI crawler budgets. - ✅ **<html lang="en"> declared** - ✅ **Canonical present** https://www.bolapsd.xyz/ - ✅ **Open Graph tags complete** - ✅ **Critical content is server-rendered** Raw and rendered text are within 0% of each other. - ✅ **Internal links: 6** 6 internal + 5 external links help crawlers navigate. - ✅ **Favicon declared** ## 4. Content Quality - ❌ **Text-to-HTML ratio: 0.3%** 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. - ⚠️ **No author byline found** Add `<meta name="author" content="Name">` or a visible byline with `rel="author"`. Strengthens E-E-A-T signals. - ✅ **Snippet-ready blocks: 3 (ul:3, ol:0, table:0)** Lists and tables are extracted verbatim by AI answer engines. ## 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 - ⚠️ **Modern image formats: 0% (0/2 webp/avif)** 2 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF. - ⚠️ **1 broken link(s) in first 10** · 403 — https://tiktok.com/@bolapsd - ✅ **Explicit dimensions: 100% (2/2)** Most images have width/height — avoids layout shift. - ✅ **External nofollow: 20% (1/5)** Healthy mix of follow and nofollow outbound links. ## 7. Performance - ⚠️ **Inline JS+CSS bulk: 52 KB** Move large inline scripts/styles to external files to enable caching. - ⚠️ **No Cache-Control header** Add a Cache-Control header so CDNs and AI crawlers can revalidate efficiently. - ✅ **Page size: 72 KB** Compact HTML payload — well within AI crawler limits. - ✅ **Resource requests: 31 (scripts:16, css:13, img:2)** Reasonable request count. - ✅ **No render-blocking head scripts** All head scripts use async or defer. - ✅ **Response time: 273ms** Fast first response. ## 8. Security - ⚠️ **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=7889238 - ✅ **Content-Security-Policy set** block-all-mixed-content; frame-ancestors 'none'; upgrade-insecure-requests; - ✅ **X-Frame-Options set** DENY - ✅ **X-Content-Type-Options set** nosniff ## 9. robots.txt and sitemap.xml Audit - ✅ **robots.txt present** 3626 chars - ✅ **robots.txt references sitemap(s)** - ✅ **sitemap.xml present (5 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. - ⚠️ **/.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.txt present** 4157 chars ## 11. Positioning Clarity - ⚠️ **H1 missing or too short to convey value** Add a clear, single-sentence H1 like 'We help X do Y.' - ⚠️ **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. - ✅ **Contact / signup path discoverable** ## 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 JSON-LD structured data** Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section. - ⚠️ **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. - ⚠️ **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 ``` - ⚠️ **Add a meta description** 50–160 chars. Repeat your core value prop in plain language; this often becomes the AI snippet. ```html ``` - ⚠️ **Add Twitter Card meta tags** Used by social platforms and AI agents for richer previews. ```html ``` - ⚠️ **Add alt text to all meaningful images** Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt. - ⚠️ **Add structured headings** Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page. - ⚠️ **Use modern image formats** Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as fallbacks. - ⚠️ **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 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. - ⚠️ **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 ``` - ⚠️ **Externalize large inline JS/CSS** Inline blobs aren't cacheable. Move >50 KB inline payloads to versioned external files. - ⚠️ **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. - ⚠️ **Declare an author byline** Add `` or a visible byline with `rel="author"`. Combine with Person JSON-LD for E-E-A-T. - ⚠️ **Set a Referrer-Policy** `Referrer-Policy: strict-origin-when-cross-origin` is a safe default. - ⚠️ **Set a Permissions-Policy** Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`. ## 14. Priority To-Do List - [ ] **P1** — Add a single, focused H1 to the homepage One `

` 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 JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section. - [ ] **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 `