1. Crawl Summary

pass

Fetched 9 of 9 pages successfully

Target: https://flutter.dev

Evidence

{
  "pages": [
    {
      "url": "https://flutter.dev",
      "bytes": 69946,
      "status": 200,
      "fetchMs": 136
    },
    {
      "url": "https://flutter.dev/",
      "bytes": 69946,
      "status": 200,
      "fetchMs": 11
    },
    {
      "url": "https://flutter.dev/development",
      "bytes": 54912,
      "status": 200,
      "fetchMs": 10
    },
    {
      "url": "https://flutter.dev/development/mobile",
      "bytes": 68040,
      "status": 200,
      "fetchMs": 10
    },
    {
      "url": "https://flutter.dev/development/ios",
      "bytes": 62696,
      "status": 200,
      "fetchMs": 15
    },
    {
      "url": "https://flutter.dev/development/web",
      "bytes": 54297,
      "status": 200,
      "fetchMs": 12
    },
    {
      "url": "https://flutter.dev/development/desktop",
      "bytes": 52913,
      "status": 200,
      "fetchMs": 16
    },
    {
      "url": "https://flutter.dev/development/embedded",
      "bytes": 50629,
      "status": 200,
      "fetchMs": 20
    },
    {
      "url": "https://flutter.dev/ai",
      "bytes": 56204,
      "status": 200,
      "fetchMs": 15
    }
  ],
  "origin": "https://flutter.dev",
  "target": "https://flutter.dev"
}

P5

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	Navigation links	—
Blog post activity	No	Navigation links	—
New hires	No	—	Often only on a /blog/team or LinkedIn page
Headline copy	Yes	Homepage	Build for any screen
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

warn
Missing canonical link
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
P3
warn
Twitter Card: missing title, description, image
Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces.
Evidence
```
{
  "card": "summary_large_image"
}
```
P3
pass
Homepage fetched successfully
HTTP 200 · 69946 bytes · 136ms
Evidence
```
{
  "bytes": 69946,
  "status": 200,
  "fetchMs": 136
}
```
P5
pass
Page load time: 0.14s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 136
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5
pass
Single H1
Build for any screen
Evidence
```
{
  "h1": "Build for any screen"
}
```
P5

pass

`<title>` present (35 chars)

Evidence

{
  "title": "Flutter - Build apps for any screen"
}

P5

pass

Meta description present (152 chars)

Evidence

{
  "description": "Flutter transforms the entire app development process. Build, test, and deploy beautiful mobile, web, desktop, and embedded apps from a single codebase."
}

P5

pass

Open Graph tags complete

Evidence

{
  "image": "/assets/flutter-logo-sharing.d744440971931f937269e060e720f5a7.png",
  "title": "Flutter - Build apps for any screen",
  "description": "Flutter transforms the entire app development process. Build, test, and deploy beautiful mobile, web, desktop, and embedded apps from a single codebase."
}

P5

pass
Critical content is server-rendered
Raw and rendered text are within 69% of each other.
Evidence
```
{
  "ratio": 0.6926292629262927,
  "rawTextLen": 4545,
  "renderedTextLen": 3148
}
```
P5
pass
Alt text coverage: 100%
43/43 images have alt text.
P5
pass
Content volume: 526 words
Substantive content — AI models have enough to summarize and recommend.
Evidence
```
{
  "wordCount": 526
}
```
P5
pass
Heading structure: 17 (h1:1, h2:5, h3:11)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 1,
  "h2": 5,
  "h3": 11
}
```
P5
pass
Internal links: 35
35 internal + 63 external links help crawlers navigate.
Evidence
```
{
  "external": 63,
  "internal": 35
}
```
P5

4. Schema / Structured Data Audit

fail
No JSON-LD structured data found
Add JSON-LD blocks (Organization, SoftwareApplication, FAQPage, BreadcrumbList) so AI answer engines can ingest your data without guessing.
P1

5. robots.txt and sitemap.xml Audit

fail
sitemap.xml not found
Add /sitemap.xml — required for reliable AI/SERP discovery.
P1
warn
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.
P2

6. LLM / AI Crawler Accessibility

warn
llms.txt missing
Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
P2
warn
skill.md missing
Add /skill.md describing what your site lets agents do — speeds up agent task routing.
P3
warn
/.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.
P3

7. Positioning Clarity

warn
No clear About/Team link
Add an About or Team link in the nav or footer so LLMs can identify the company.
P2
warn
No pricing/plans link found
AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
P2
pass
H1 communicates value
Build for any screen
P5
pass
Value-prop language detected
P5
pass
Contact / signup path discoverable
P5

8. Missing or Hard-to-Find Information

fail
7 data point(s) could not be found from public pages
· Pricing · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials
Evidence
```
{
  "missing": [
    "Pricing",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Positioning",
    "Executive team",
    "Case studies or testimonials"
  ]
}
```
P1

9. Recommended Fixes

warn
Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
Evidence
```
{
  "for": "sitemap.exists"
}
```
P1
warn
Add JSON-LD structured data
Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.
Evidence
```
{
  "for": "schema.any"
}
```
P1
warn
Add /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
Evidence
```
{
  "for": "llms_txt"
}
```
P2
warn
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.
Evidence
```
{
  "for": "positioning.who"
}
```
P2
warn
Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "for": "positioning.pricing"
}
```
P2
warn
Create a robots.txt
Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
Evidence
```
{
  "for": "robots.exists"
}
```
P2
warn
Add a canonical link
Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html <link rel="canonical" href="https://yoursite.com/" /> ```
Evidence
```
{
  "for": "homepage.canonical"
}
```
P3
warn
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" /> ```
Evidence
```
{
  "for": "homepage.twitter"
}
```
P3
warn
Add /skill.md
Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
Evidence
```
{
  "for": "skill_md"
}
```
P3
warn
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 ```
Evidence
```
{
  "for": "security_txt"
}
```
P3

10. Priority To-Do List

warn
[ ] Publish a sitemap.xml
Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Add JSON-LD structured data
Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Add /llms.txt
A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Create a robots.txt
Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add a canonical link
Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html <link rel="canonical" href="https://yoursite.com/" /> ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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" /> ```
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add /skill.md
Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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 ```
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for flutter.dev

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Schema / Structured Data Audit

5. robots.txt and sitemap.xml Audit

6. LLM / AI Crawler Accessibility

7. Positioning Clarity

8. Missing or Hard-to-Find Information

9. Recommended Fixes

10. Priority To-Do List

https://flutter.dev/

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Schema / Structured Data Audit

5. robots.txt and sitemap.xml Audit

6. LLM / AI Crawler Accessibility

7. Positioning Clarity

8. Missing or Hard-to-Find Information

9. Recommended Fixes

10. Priority To-Do List

Track this site week over week

Your charts, not these.