# AEO Audit for siena.agency
**Target:** https://www.siena.agency/
**Score:** 38 / 100
**Generated:** 2026-05-13T12:43:05.768Z
**Pages crawled:** 5
**Findings:** 18 pass · 45 warn · 4 fail · 0 unknown
---
## 1. Crawl Summary
- ✅ **Fetched 5 of 5 pages successfully**
Target: https://www.siena.agency
## 2. Data Found
| Data Point | Found? | Source | Notes |
|---|---:|---|---|
| Pricing | No | — | — |
| Customer logos | Yes | Homepage | trusted by |
| Social proof | Yes | Homepage | trusted by |
| Recent launches | No | — | — |
| Blog post activity | No | — | — |
| New hires | No | — | Often only on a /blog/team or LinkedIn page |
| Headline copy | Yes | Homepage | From empty calendars to booked pipeline. |
| Positioning | No | — | — |
| Executive team | No | — | — |
| Product/service descriptions | Yes | Homepage | From meta description |
| Case studies or testimonials | Yes | Navigation links | — |
| Contact/demo/signup paths | Yes | Navigation links | — |
## 3. Homepage Audit
- ⚠️ **Short `` (12 chars)**
Aim for 30–60 chars. Lead with brand or product, then value prop.
- ⚠️ **Short meta description (47 chars)**
Aim for 50–160 chars. Restate your value prop in plain language.
- ⚠️ **Missing canonical link**
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
- ❌ **Open Graph: missing title, description, image**
- ⚠️ **No Twitter Card tags**
Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces.
- ⚠️ **Content volume: 247 words**
Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
- ✅ **Homepage fetched successfully**
HTTP 200 · 32166 bytes · 199ms
- ✅ **Page load time: 0.20s**
Fast — well within AI crawler budgets.
- ✅ **<html lang="en"> declared**
- ✅ **Single H1**
From empty calendars to booked pipeline.
- ✅ **Critical content is server-rendered**
Raw and rendered text are within 11% of each other.
- ✅ **Alt text coverage: 100%**
3/3 images have alt text.
- ✅ **Heading structure: 9 (h1:1, h2:3, h3:5)**
Multiple headings help AI chunk and outline your page.
- ✅ **Internal links: 6**
6 internal + 12 external links help crawlers navigate.
## 4. 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.
## 5. robots.txt and sitemap.xml Audit
- ❌ **sitemap.xml not found**
Add /sitemap.xml — required for reliable AI/SERP discovery.
- ⚠️ **robots.txt not found**
No /robots.txt was reachable. Add one explicitly — silence is read differently by different crawlers, and you lose the chance to control AI bots.
## 6. LLM / AI Crawler Accessibility
- ⚠️ **llms.txt missing**
Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
- ⚠️ **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 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.
- ✅ **H1 communicates value**
From empty calendars to booked pipeline.
- ✅ **Value-prop language detected**
- ✅ **Contact / signup path discoverable**
## 8. Missing or Hard-to-Find Information
- ❌ **6 data point(s) could not be found from public pages**
· Pricing
· Recent launches
· Blog post activity
· New hires
· Positioning
· Executive team
## 9. Recommended Fixes
- ⚠️ **Publish a sitemap.xml**
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
- ⚠️ **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 /llms.txt**
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
- ⚠️ **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.
- ⚠️ **Create a robots.txt**
Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
- ⚠️ **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 a canonical link**
Prevents dup-content drift and tells AI crawlers which URL is authoritative.
```html
```
- ⚠️ **Complete Open Graph tags**
AI bots use OG for fast disambiguation. Add all four:
```html
```
- ⚠️ **Add Twitter Card meta tags**
Used by social platforms and AI agents for richer previews.
```html
```
- ⚠️ **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.
- ⚠️ **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
```
## 10. Priority To-Do List
- [ ] **P1** — Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
- [ ] **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 /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
- [ ] **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.
- [ ] **P2** — Create a robots.txt
Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
- [ ] **P3** — Set a meaningful ``
30–60 chars. Lead with the brand or product, then the value prop.
```html
<title>CrawlProof — AEO audits for AI crawlers
```
- [ ] **P3** — Add a meta description
50–160 chars. Repeat your core value prop in plain language; this often becomes the AI snippet.
```html
```
- [ ] **P3** — Add a canonical link
Prevents dup-content drift and tells AI crawlers which URL is authoritative.
```html
```
- [ ] **P3** — Complete Open Graph tags
AI bots use OG for fast disambiguation. Add all four:
```html
```
- [ ] **P3** — Add Twitter Card meta tags
Used by social platforms and AI agents for richer previews.
```html
```
- [ ] **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** — 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
```
---
_Report by [CrawlProof](https://crawlproof.com). Reusable after every major website change._