# AEO Audit for codewow.nl **Target:** https://codewow.nl/ **Score:** 49 / 100 **Generated:** 2026-05-13T18:45:04.492Z **Pages crawled:** 9 **Findings:** 21 pass · 69 warn · 1 fail · 0 unknown --- ## 1. Crawl Summary - ✅ **Fetched 9 of 9 pages successfully** Target: https://codewow.nl ## 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 | Wij zijn Code WOW! | | Positioning | No | — | — | | Executive team | No | — | — | | Product/service descriptions | Yes | Homepage | From meta description | | Case studies or testimonials | No | — | — | | Contact/demo/signup paths | Yes | Navigation links | — | ## 3. Homepage Audit - ⚠️ **Multiple H1s found** 2 `

` tags. Prefer one focused H1 per page. - ⚠️ Long meta description (201 chars) Snippets truncate around 160 chars. Tighten to keep the key sentence visible. - ⚠️ Open Graph: missing image - ⚠️ 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: 88% 58/66 images have alt text. - ✅ Homepage fetched successfully HTTP 200 · 123340 bytes · 737ms - ✅ Page load time: 0.74s Fast — well within AI crawler budgets. - ✅ declared - ✅ `` present (67 chars) - ✅ Canonical present https://codewow.nl - ✅ Critical content is server-rendered Raw and rendered text are within 33% of each other. - ✅ Content volume: 495 words Substantive content — AI models have enough to summarize and recommend. - ✅ Heading structure: 16 (h1:2, h2:13, h3:1) Multiple headings help AI chunk and outline your page. - ✅ Internal links: 63 63 internal + 3 external links help crawlers navigate. ## 4. Schema / Structured Data Audit - ⚠️ Organization missing Adding Organization JSON-LD helps LLMs identify your entity. - ⚠️ SoftwareApplication missing Adding SoftwareApplication 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. - ✅ 4 JSON-LD block(s) found Types: WebSite, ProfessionalService, WebPage, ItemList - ✅ WebSite present ## 5. robots.txt and sitemap.xml Audit - ✅ robots.txt present 277 chars - ✅ robots.txt references sitemap(s) - ✅ sitemap.xml present (46 URLs) ## 6. LLM / AI Crawler Accessibility - ⚠️ llms.txt missing Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site. - ⚠️ 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. ## 7. 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 Wij zijn Code WOW! - ✅ Contact / signup path discoverable ## 8. Missing or Hard-to-Find Information - ❌ 9 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials ## 9. Recommended Fixes - ⚠️ Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary. - ⚠️ 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 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 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." /> ``` - ⚠️ 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" /> ``` - ⚠️ 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" /> ``` - ⚠️ Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt. - ⚠️ 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 ``` - ⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page. - ⚠️ Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory. - ⚠️ Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion. ## 10. Priority To-Do List - [ ] 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 — 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 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. - [ ] 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." /> ``` - [ ] P3 — 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" /> ``` - [ ] P3 — 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" /> ``` - [ ] 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 — 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. - [ ] 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 — 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 ``` - [ ] P3 — State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page. - [ ] P3 — Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory. - [ ] P3 — Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion. --- _Report by [CrawlProof](https://crawlproof.com). Reusable after every major website change._