AEO Audit for deliivo.com
Target: https://www.deliivo.com/
Score: 45 / 100
Generated: 2026-08-22T15:03:05.965Z
Pages crawled: 9
Findings: 51 pass · 113 warn · 7 fail · 0 unknown
1. Crawl Summary
- ✅ Fetched 9 of 9 pages successfully Target: https://www.deliivo.com
2. Data Found
| Data Point | Found? | Source | Notes |
|---|---|---|---|
| Pricing | No | — | — |
| Customer logos | No | — | — |
| Social proof | No | — | — |
| Recent launches | Yes | Press/news pages | https://www.deliivo.com/blog |
| Blog post activity | Yes | Blog | https://www.deliivo.com/blog |
| New hires | No | — | Often only on a /blog/team or LinkedIn page |
| Headline copy | Yes | Homepage | Carpool the Baltics and Beyond |
| Positioning | No | — | — |
| Executive team | No | Footer links | — |
| Product/service descriptions | Yes | Homepage | From meta description |
| Case studies or testimonials | No | — | — |
| Contact/demo/signup paths | Yes | Navigation links | — |
3. Homepage Audit
- ⚠️ Page load time: 1.83s Acceptable — consider optimizing for faster crawl times.
- ⚠️ Long meta description (238 chars) Snippets truncate around 160 chars. Tighten to keep the key sentence visible.
- ❌ Alt text coverage: 29% 2/7 images have alt text.
- ✅ Homepage fetched successfully HTTP 200 · 62383 bytes · 1828ms
- ✅ declared
- ✅ Single H1 Carpool the Baltics and Beyond
- ✅
<title>present (40 chars) - ✅ Canonical present https://deliivo.com/en
- ✅ Open Graph tags complete
- ✅ Twitter Card tags complete
- ✅ Critical content is server-rendered Raw and rendered text are within 16% of each other.
- ✅ Content volume: 316 words Substantive content — AI models have enough to summarize and recommend.
- ✅ Heading structure: 17 (h1:1, h2:4, h3:12) Multiple headings help AI chunk and outline your page.
- ✅ Internal links: 26 26 internal + 5 external links help crawlers navigate.
- ✅ Robots meta: "index, follow"
- ✅ hreflang: 6 alternate(s) Locales: en, et, lv, lt, ru, x-default
- ✅ Favicon declared
4. Content Quality
- ❌ Text-to-HTML ratio: 3.9% Very low text density. AI crawlers will struggle to find substantive content.
- ⚠️ 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 withrel="author". Strengthens E-E-A-T signals. - ✅ Heading levels are well-ordered 23 headings nested in order.
- ✅ Snippet-ready blocks: 4 (ul:4, ol:0, table:0) Lists and tables are extracted verbatim by AI answer engines.
- ✅ 2 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
- ⚠️ WebSite missing Adding WebSite 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.
- ⚠️ 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.
- ⚠️ Product / Offer JSON-LD not found Add Product / Offer 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: Organization
- ✅ Organization present
6. Links & Images
- ⚠️ Modern image formats: 0% (0/7 webp/avif) 0 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
- ❌ Explicit dimensions: 29% (2/7) Add width and height attributes on tags to prevent CLS.
- ✅ Lazy loading: 71% (5/7) Most below-the-fold images defer load — good for perf and crawl budgets.
- ✅ Responsive srcset: 7/7
- ✅ External nofollow: 0% (0/5) Healthy mix of follow and nofollow outbound links.
- ✅ No broken links in first 20 HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
7. Performance
- ❌ Response time: 1828ms Slow response. Check CDN/cache headers and origin latency.
- ⚠️ 1 render-blocking script(s) in Move non-critical scripts to end of or add
defer/async. - ✅ Page size: 61 KB Compact HTML payload — well within AI crawler limits.
- ✅ Resource requests: 24 (scripts:16, css:1, img:7) Reasonable request count.
- ✅ Inline JS+CSS bulk: 14 KB Inline payload is modest.
- ✅ Cache-Control set (CDN: Vercel) Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate CDN detected: Vercel
- ✅ Compression enabled (Brotli) Content-Encoding: br
- ✅ Lazy loading: 5/7 images
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. - ⚠️ X-Content-Type-Options missing Add
X-Content-Type-Options: nosniffto block MIME-type sniffing. - ⚠️ Referrer-Policy missing Add
Referrer-Policy: strict-origin-when-cross-originfor 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=63072000
9. robots.txt and sitemap.xml Audit
- ✅ robots.txt present 1244 chars
- ✅ robots.txt references sitemap(s)
- ✅ sitemap.xml present (2 URLs)
10. 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.
- ⚠️ /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 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 Carpool the Baltics and Beyond
- ✅ Contact / signup path discoverable
12. Missing or Hard-to-Find Information
- ❌ 7 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · 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.
⚠️ 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 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 IDAlso consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
⚠️ Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
⚠️ 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=….⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
⚠️ 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.
⚠️ Speed up homepage rendering AI crawlers commonly time out around 3s. Cache the HTML, ship less JS for the first paint, and pre-render the hero section server-side.
⚠️ 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 alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
⚠️ 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.
⚠️ 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⚠️ Eliminate render-blocking head scripts Add
deferorasyncto any<script src="…">in<head>, or move it to the end of<body>.⚠️ 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 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.
⚠️ 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.
⚠️ Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.
⚠️ Define a Content-Security-Policy Start with
Content-Security-Policy-Report-Onlyto learn safe sources, then enforce. Cuts XSS blast radius.⚠️ Declare an author byline Add
<meta name="author" content="Name">or a visible byline withrel="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.
⚠️ Add X-Frame-Options
X-Frame-Options: SAMEORIGIN(or CSPframe-ancestors) blocks clickjacking via iframe embeds.⚠️ Add X-Content-Type-Options
X-Content-Type-Options: nosniffprevents browsers from MIME-sniffing responses.⚠️ Set a Referrer-Policy
Referrer-Policy: strict-origin-when-cross-originis 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 — 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.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 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 /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
P2 — 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=….P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
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 — Speed up homepage rendering AI crawlers commonly time out around 3s. Cache the HTML, ship less JS for the first paint, and pre-render the hero section server-side.
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 — Add alt text to all meaningful images Decorative-only images can use empty alt='', but logos, screenshots, and product images need descriptive alt.
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.
Report by CrawlProof. Reusable after every major website change.