Public share link

AEO Audit for mavomedia.net

Target: https://mavomedia.net/
Score: 38 / 100
Generated: 2026-06-04T13:44:42.956Z
Pages crawled: 1
Findings: 35 pass · 118 warn · 10 fail · 0 unknown

1. Crawl Summary

✅ Fetched 1 of 1 pages successfully Target: https://mavomedia.net

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	No	—	—
Positioning	Yes	Homepage	we help
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 <h1> element found. LLMs use the H1 as the strongest signal of what the page is about.
❌ Important content appears to be JavaScript-rendered Raw HTML contains 2725 chars of text; rendered DOM contains 15877 (5.8× more). LLM crawlers like GPTBot generally do not run JavaScript — they will miss most of your content.
❌ Content volume: 0 words Very thin content. AI models need substantive text to understand and recommend your site.
❌ Heading structure: 0 (h1:0, h2:0, h3:0) Few headings make it hard for AI to understand sectioning. Use h2/h3 to label each section.
❌ Internal links: 0 Few internal links. Add a nav/footer with links to your key pages so AI crawlers can discover them.
✅ Homepage fetched successfully HTTP 200 · 6240 bytes · 700ms
✅ Page load time: 0.70s Fast — well within AI crawler budgets.
✅ declared
✅ <title> present (56 chars)
✅ Meta description present (151 chars)
✅ Canonical present https://mavomedia.net/
✅ Open Graph tags complete
✅ Twitter Card tags complete
✅ Robots meta: "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1"
✅ Favicon declared

4. Content Quality

❌ Snippet-ready blocks: 0 (ul:0, ol:0, table:0) Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
❌ Text-to-HTML ratio: 0.0% 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 or article:published_time meta. AI ranking weights freshness.
✅ Author byline declared

5. Schema / Structured Data Audit

⚠️ 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.
✅ 3 JSON-LD block(s) found Types: Organization, WebSite, ProfessionalService
✅ Organization present
✅ WebSite present

6. Links & Images

No findings.

7. Performance

⚠️ 1 render-blocking script(s) in Move non-critical scripts to end of or add defer/async.
⚠️ Response time: 700ms Slow response. Check CDN/cache headers and origin latency.
✅ Page size: 6 KB Compact HTML payload — well within AI crawler limits.
✅ Resource requests: 2 (scripts:1, css:1, img:0) Reasonable request count.
✅ Inline JS+CSS bulk: 2 KB Inline payload is modest.
✅ Cache-Control set (CDN: Netlify) Cache-Control: public,max-age=0,must-revalidate CDN detected: Netlify
✅ Compression enabled (Brotli) Content-Encoding: br

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: nosniff to block MIME-type sniffing.
⚠️ 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=31536000

9. robots.txt and sitemap.xml Audit

✅ robots.txt present 203 chars
✅ robots.txt references sitemap(s)
✅ sitemap.xml present (17 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

⚠️ H1 missing or too short to convey value Add a clear, single-sentence H1 like 'We help X do Y.'
❌ No discoverable CTA Add a clearly-labeled Contact, Demo, or Sign up link to the nav or hero.
⚠️ 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 detected

12. Missing or Hard-to-Find Information

❌ 8 data point(s) could not be found from public pages · Pricing · Recent launches · Blog post activity · New hires · Headline copy · Executive team · Case studies or testimonials · Contact/demo/signup paths

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.

⚠️ 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.
⚠️ Server-render critical homepage content Move the headline, sub-headline, pricing summary, and CTA into server-rendered HTML. Most LLM bots do not execute JS.
⚠️ 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 a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
⚠️ Add lists or comparison tables Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
⚠️ 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 sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

⚠️ 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 ID
```
Also 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.
⚠️ 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.
⚠️ 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.
⚠️ Add structured headings Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page.
⚠️ Add internal navigation links Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.
⚠️ 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 defer or async to any <script src="…"> in <head>, or move it to the end of <body>.
⚠️ 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 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-Only to learn safe sources, then enforce. Cuts XSS blast radius.
⚠️ 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 CSP frame-ancestors) blocks clickjacking via iframe embeds.
⚠️ Add X-Content-Type-Options X-Content-Type-Options: nosniff prevents browsers from MIME-sniffing responses.
⚠️ 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 — 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.

P1 — 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.
P1 — Server-render critical homepage content Move the headline, sub-headline, pricing summary, and CTA into server-rendered HTML. Most LLM bots do not execute JS.
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 a discoverable CTA Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
P2 — Add lists or comparison tables Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
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 sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}
```

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

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 — 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 <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 — Add structured headings Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page.
P3 — Add internal navigation links Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.
P3 — Allow GPTBot in robots.txt Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.

Report by CrawlProof. Reusable after every major website change.

AEO audit

https://mavomedia.net/

Completed 6/4/2026, 1:44:43 PM

/100

1. Crawl Summary

pass

Fetched 1 of 1 pages successfully

Target: https://mavomedia.net

Evidence

{
  "pages": [
    {
      "url": "https://mavomedia.net",
      "bytes": 6240,
      "status": 200,
      "fetchMs": 700
    }
  ],
  "origin": "https://mavomedia.net",
  "target": "https://mavomedia.net"
}

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	No	—	—
Positioning	Yes	Homepage	we help
Executive team	No	—	—
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	No	—	—
Contact/demo/signup paths	No	—	—

3. Homepage Audit

fail
Missing H1
No `<h1>` element found. LLMs use the H1 as the strongest signal of what the page is about.
P1
fail
Important content appears to be JavaScript-rendered
Raw HTML contains 2725 chars of text; rendered DOM contains 15877 (5.8× more). LLM crawlers like GPTBot generally do not run JavaScript — they will miss most of your content.
Evidence
```
{
  "ratio": 5.826422018348624,
  "rawTextLen": 2725,
  "renderedTextLen": 15877
}
```
P1
fail
Content volume: 0 words
Very thin content. AI models need substantive text to understand and recommend your site.
Evidence
```
{
  "wordCount": 0
}
```
P1
fail
Heading structure: 0 (h1:0, h2:0, h3:0)
Few headings make it hard for AI to understand sectioning. Use h2/h3 to label each section.
Evidence
```
{
  "h1": 0,
  "h2": 0,
  "h3": 0
}
```
P3
fail
Internal links: 0
Few internal links. Add a nav/footer with links to your key pages so AI crawlers can discover them.
Evidence
```
{
  "external": 0,
  "internal": 0
}
```
P3
pass
Homepage fetched successfully
HTTP 200 · 6240 bytes · 700ms
Evidence
```
{
  "bytes": 6240,
  "status": 200,
  "fetchMs": 700
}
```
P5
pass
Page load time: 0.70s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 700
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5

pass

`<title>` present (56 chars)

Evidence

{
  "title": "MavoMedia — Gaming Marketing Agency | Roblox & Minecraft"
}

pass

Meta description present (151 chars)

Evidence

{
  "description": "MavoMedia is a gaming marketing agency specialising in Roblox, Minecraft, Discord ads, influencer marketing, UGC, and paid ads. $1M+ revenue generated."
}

pass
Canonical present
https://mavomedia.net/
Evidence
```
{
  "canonical": "https://mavomedia.net/"
}
```
P5

pass

Open Graph tags complete

Evidence

{
  "image": "https://mavomedia.net/og-image.jpg",
  "title": "MavoMedia — Gaming Marketing Agency | Roblox & Minecraft",
  "description": "MavoMedia is a gaming marketing agency specialising in Roblox, Minecraft, Discord ads, influencer marketing, UGC, and paid ads. $1M+ revenue generated."
}

pass

Twitter Card tags complete

Evidence

{
  "card": "summary_large_image",
  "image": "https://mavomedia.net/og-image.jpg",
  "title": "MavoMedia — Gaming Marketing Agency | Roblox & Minecraft",
  "description": "MavoMedia is a gaming marketing agency specialising in Roblox, Minecraft, Discord ads, influencer marketing, UGC, and paid ads. $1M+ revenue generated."
}

pass
Robots meta: "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1"
Evidence
```
{
  "content": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1"
}
```
P5
pass
Favicon declared
Evidence
```
{
  "href": "/favicon.png"
}
```
P5

4. Content Quality

fail
Snippet-ready blocks: 0 (ul:0, ol:0, table:0)
Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
Evidence
```
{
  "ol": 0,
  "ul": 0,
  "tables": 0
}
```
P2
fail
Text-to-HTML ratio: 0.0%
Very low text density. AI crawlers will struggle to find substantive content.
Evidence
```
{
  "ratio": 0,
  "htmlBytes": 6230,
  "textChars": 0
}
```
P2
warn
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.
P3
warn
No date signal found
Add <time datetime="…"> or article:published_time meta. AI ranking weights freshness.
P3
pass
Author byline declared
P5

5. Schema / Structured Data Audit

warn
SoftwareApplication missing
Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
P3
warn
FAQPage JSON-LD missing
Add an FAQPage block on pages that answer common questions — high-value for AI summaries.
P3
warn
Article / BlogPosting JSON-LD not found
Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
P3
warn
BreadcrumbList JSON-LD not found
Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
P3
warn
Product / Offer JSON-LD not found
Add Product / Offer where applicable so AI answer engines can resolve the entity precisely.
P3
warn
LocalBusiness JSON-LD not found
Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
P4
warn
Person (author / founder) JSON-LD not found
Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
P4
warn
HowTo JSON-LD not found
Add HowTo where applicable so AI answer engines can resolve the entity precisely.
P4
warn
VideoObject JSON-LD not found
Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
P4

pass

3 JSON-LD block(s) found

Types: Organization, WebSite, ProfessionalService

Evidence

{
  "types": [
    "Organization",
    "WebSite",
    "ProfessionalService"
  ],
  "blocks": 3
}

pass
Organization present
P5
pass
WebSite present
P5

6. Links & Images

No findings.

7. Performance

warn
1 render-blocking script(s) in <head>
Move non-critical scripts to end of <body> or add `defer`/`async`.
P3
warn
Response time: 700ms
Slow response. Check CDN/cache headers and origin latency.
Evidence
```
{
  "bytes": 6240,
  "fetchMs": 700
}
```
P3
pass
Page size: 6 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 6240
}
```
P5

pass

Resource requests: 2 (scripts:1, css:1, img:0)

Reasonable request count.

Evidence

{
  "imgs": 0,
  "styles": 1,
  "scripts": 1,
  "inlineStyles": 0,
  "inlineScripts": 3
}

pass
Inline JS+CSS bulk: 2 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 1958,
  "inlineCssBytes": 0
}
```
P5
pass
Cache-Control set (CDN: Netlify)
Cache-Control: public,max-age=0,must-revalidate CDN detected: Netlify
Evidence
```
{
  "cdn": [
    "Netlify"
  ],
  "cacheControl": "public,max-age=0,must-revalidate"
}
```
P5
pass
Compression enabled (Brotli)
Content-Encoding: br
Evidence
```
{
  "encoding": "br"
}
```
P5

8. Security

warn
Content-Security-Policy missing
Define a CSP to limit script sources — large reduction in XSS surface.
P3
warn
X-Frame-Options missing
Add `X-Frame-Options: SAMEORIGIN` (or use CSP frame-ancestors) to prevent clickjacking.
P4
warn
X-Content-Type-Options missing
Add `X-Content-Type-Options: nosniff` to block MIME-type sniffing.
P4
warn
Referrer-Policy missing
Add `Referrer-Policy: strict-origin-when-cross-origin` for safer referrers.
P4
warn
Permissions-Policy missing
Restrict browser features (camera, mic, geolocation) you don't use.
P4

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://mavomedia.net/"
}

pass
No mixed content detected
P5
pass
HSTS set
max-age=31536000
Evidence
```
{
  "value": "max-age=31536000"
}
```
P5

9. robots.txt and sitemap.xml Audit

pass

robots.txt present

203 chars

Evidence

{
  "snippet": "User-agent: Googlebot\nAllow: /\n\nUser-agent: Bingbot\nAllow: /\n\nUser-agent: Twitterbot\nAllow: /\n\nUser-agent: facebookexternalhit\nAllow: /\n\nUser-agent: *\nAllow: /\n\nSitemap: https://mavomedia.net/sitemap.xml"
}

pass

robots.txt references sitemap(s)

Evidence

{
  "sitemaps": [
    "https://mavomedia.net/sitemap.xml"
  ]
}

pass

sitemap.xml present (17 URLs)

Evidence

{
  "snippet": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://mavomedia.net/</loc>\n    <lastmod>2026-05-04</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>1.0</priority>\n  </url>\n  <url>\n    <loc>https://mavomedia.net/services</loc>\n    <lastmod>2026-05-04</lastmod>\n    <changefreq>monthly</changefreq>\n    <priority>0.8</priority>\n  </url>\n  <url>\n    <loc>https://mavomedia.net/free-tools</loc>\n    <lastmod>2026-05-04</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.8</priority>\n  </url>\n  <url><loc>https://mavomedia.net/free-tools/audit</loc><lastmod>2026-05-04</lastmod><changefreq>monthly</changefreq><priority>0.6</priority></url>\n  <url><loc>https://mavomedia.net/free-tools/growth</loc><lastmod>2026-",
  "urlCount": 17
}

10. 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
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.
P3
warn
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.
P3
warn
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.
P3
warn
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.
P3
warn
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.
P3
warn
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.
P3
warn
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.
P3
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
warn
/llms-full.txt missing
Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.
P3

11. Generative Engine Optimization (GEO)

fail
No llms.txt found
llms.txt tells generative AI systems what to read, index, and cite. Create /llms.txt following the llmstxt.org spec — include headings, page descriptions, and links to key resources.
P1
warn
Organization schema has no knowledge graph sameAs links
Add `sameAs` pointing to Wikipedia, Wikidata, LinkedIn, or Crunchbase. AI systems use these links to resolve your brand name as a known entity rather than an ambiguous string.
Evidence
```
{
  "existingSameAs": [
    "https://discord.gg/YR4JyD9NMQ",
    "https://x.com/realafros",
    "https://www.youtube.com/@AfrosHD"
  ]
}
```
P2
warn
No AI agent integration files found
Add at least one: /.well-known/ai-plugin.json (ChatGPT plugin discovery), /.well-known/agent-card.json (A2A protocol), or /skill.md (Claude tool integration). These let AI agents interact with your site programmatically and signal that your site is AI-native.
P2
warn
No llms-full.txt found
llms-full.txt is an extended version of llms.txt that embeds the full text of every listed resource. Large-context models and RAG pipelines can ingest your entire site in one request — greatly improving citation coverage.
P3
warn
No outbound links to authoritative sources on the homepage
Generative AI systems cite pages that themselves cite credible sources. Link to Wikipedia, .gov, .edu, peer-reviewed research, or major news outlets to signal epistemic trustworthiness.
P3
pass
Brand entity declared: "MavoMedia"
AI systems can resolve "MavoMedia" as a distinct entity. Ensure this name is used consistently in titles, H1s, and social profiles.
Evidence
```
{
  "schemaName": "MavoMedia"
}
```
P5

12. Positioning Clarity

warn
H1 missing or too short to convey value
Add a clear, single-sentence H1 like 'We help X do Y.'
P1
fail
No discoverable CTA
Add a clearly-labeled Contact, Demo, or Sign up link to the nav or hero.
P1
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
Value-prop language detected
P5

13. Foundations

warn
No theme-color meta tag
Add <meta name="theme-color" content="#yourcolor"> to tint the browser chrome on mobile.
P4
warn
No feed announced
Add <link rel="alternate" type="application/rss+xml" href="/feed.xml"> so agents and readers can subscribe.
P4
pass
<!doctype html> declared
P5
pass
Meta viewport present
content="width=device-width, initial-scale=1.0"
Evidence
```
{
  "content": "width=device-width, initial-scale=1.0"
}
```
P5

14. Accessibility

warn
No skip navigation link found
Add a visible-on-focus skip link as the first focusable element: <a href="#main">Skip to main content</a>.
P3
warn
Missing landmark(s): <header>, <nav>, <main>, <footer>
Semantic landmarks help screen readers and AI agents navigate page structure.
Evidence
```
{
  "nav": 0,
  "main": 0,
  "footer": 0,
  "header": 0
}
```
P3

15. Well-Known URIs

warn
/.well-known/change-password missing
Redirect /.well-known/change-password to your password-change page so password managers can deep-link directly.
P4
warn
/.well-known/api-catalog missing
Publish a /.well-known/api-catalog (RFC 9727 Linkset) so agents can discover your API endpoints automatically.
P4
warn
/.well-known/agent-card.json missing
Publish an agent card at /.well-known/agent-card.json to enable agent-to-agent (A2A) discovery.
P4
warn
No HTTP Link header
Add a Link response header to advertise sitemap, llms.txt, and api-catalog to crawlers without requiring HTML parsing.
P4

16. Privacy

warn
No privacy policy link found
Add a visible link to your privacy policy. Required by GDPR, CCPA, and expected by AI agents assessing trustworthiness.
P2
pass
No third-party scripts detected
P5

17. Resilience

warn
No Web App Manifest found
Add <link rel="manifest" href="/manifest.json"> and a manifest.json with name, icons, start_url, and display.
P4

18. Website Specification

No findings.

19. Missing or Hard-to-Find Information

fail
8 data point(s) could not be found from public pages
· Pricing · Recent launches · Blog post activity · New hires · Headline copy · Executive team · Case studies or testimonials · Contact/demo/signup paths
Evidence
```
{
  "missing": [
    "Pricing",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Headline copy",
    "Executive team",
    "Case studies or testimonials",
    "Contact/demo/signup paths"
  ]
}
```
P1

20. Recommended Fixes

warn
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.
Evidence
```
{
  "for": "geo.llms_txt"
}
```
P1
warn
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.
Evidence
```
{
  "for": "homepage.h1"
}
```
P1
warn
Server-render critical homepage content
Move the headline, sub-headline, pricing summary, and CTA into server-rendered HTML. Most LLM bots do not execute JS.
Evidence
```
{
  "for": "homepage.js_rendered"
}
```
P1
warn
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.
Evidence
```
{
  "for": "homepage.word_count"
}
```
P1
warn
Rewrite the homepage H1 to be self-evident
Replace clever copy with literal copy. 'We help X do Y' beats 'Reimagine Y'.
Evidence
```
{
  "for": "positioning.what"
}
```
P1
warn
Add a discoverable CTA
Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
Evidence
```
{
  "for": "positioning.cta"
}
```
P1
warn
Add lists or comparison tables
Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
Evidence
```
{
  "for": "content.snippet_blocks"
}
```
P2
warn
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.
Evidence
```
{
  "for": "content.text_ratio"
}
```
P2
warn
Add sameAs knowledge graph links to Organization schema
Extend your Organization JSON-LD to include `sameAs` pointing to authoritative directories: ```json { "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://yoursite.com", "sameAs": [ "https://en.wikipedia.org/wiki/Your_Brand", "https://www.wikidata.org/wiki/Q12345678", "https://www.linkedin.com/company/your-brand", "https://www.crunchbase.com/organization/your-brand" ] } ``` These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.
Evidence
```
{
  "for": "geo.knowledge_graph"
}
```
P2
warn
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.
Evidence
```
{
  "for": "geo.agent_integration"
}
```
P2
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
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.
Evidence
```
{
  "for": "content.qa_headings"
}
```
P3
warn
Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "for": "content.date_signal"
}
```
P3
warn
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.
Evidence
```
{
  "for": "geo.llms_full_txt"
}
```
P3
warn
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.
Evidence
```
{
  "for": "geo.citation_signals"
}
```
P3
warn
Add structured headings
Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page.
Evidence
```
{
  "for": "homepage.heading_structure"
}
```
P3
warn
Add internal navigation links
Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.
Evidence
```
{
  "for": "homepage.internal_links"
}
```
P3
warn
Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.GPTBot"
}
```
P3
warn
Allow ClaudeBot in robots.txt
Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.ClaudeBot"
}
```
P3
warn
Allow PerplexityBot in robots.txt
Add an explicit User-agent: PerplexityBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.PerplexityBot"
}
```
P3
warn
Allow Google-Extended in robots.txt
Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Google-Extended"
}
```
P3
warn
Allow OAI-SearchBot in robots.txt
Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.OAI-SearchBot"
}
```
P3
warn
Allow Applebot-Extended in robots.txt
Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Applebot-Extended"
}
```
P3
warn
Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.CCBot"
}
```
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
warn
Eliminate render-blocking head scripts
Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`.
Evidence
```
{
  "for": "perf.render_blocking"
}
```
P3
warn
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=…`.
Evidence
```
{
  "for": "perf.response_time"
}
```
P3
warn
Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "for": "schema.product"
}
```
P3
warn
Add FAQPage JSON-LD
Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
Evidence
```
{
  "for": "schema.faq"
}
```
P3
warn
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.
Evidence
```
{
  "for": "schema.article"
}
```
P3
warn
Add BreadcrumbList JSON-LD
Helps AI engines understand site hierarchy and improves citation context.
Evidence
```
{
  "for": "schema.breadcrumb"
}
```
P3
warn
Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "for": "schema.product"
}
```
P3
warn
Define a Content-Security-Policy
Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius.
Evidence
```
{
  "for": "security.csp"
}
```
P3
warn
Add X-Frame-Options
`X-Frame-Options: SAMEORIGIN` (or CSP `frame-ancestors`) blocks clickjacking via iframe embeds.
Evidence
```
{
  "for": "security.xfo"
}
```
P4
warn
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.
Evidence
```
{
  "for": "schema.local_business"
}
```
P4
warn
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.
Evidence
```
{
  "for": "schema.person"
}
```
P4
warn
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.
Evidence
```
{
  "for": "schema.howto"
}
```
P4
warn
Add VideoObject JSON-LD
For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.
Evidence
```
{
  "for": "schema.video"
}
```
P4
warn
Add X-Content-Type-Options
`X-Content-Type-Options: nosniff` prevents browsers from MIME-sniffing responses.
Evidence
```
{
  "for": "security.xcto"
}
```
P4
warn
Set a Referrer-Policy
`Referrer-Policy: strict-origin-when-cross-origin` is a safe default.
Evidence
```
{
  "for": "security.referrer"
}
```
P4
warn
Set a Permissions-Policy
Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`.
Evidence
```
{
  "for": "security.permissions"
}
```
P4

21. Priority To-Do List

warn
[ ] 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.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] 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.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Server-render critical homepage content
Move the headline, sub-headline, pricing summary, and CTA into server-rendered HTML. Most LLM bots do not execute JS.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] 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.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Rewrite the homepage H1 to be self-evident
Replace clever copy with literal copy. 'We help X do Y' beats 'Reimagine Y'.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Add a discoverable CTA
Place 'Contact sales' or 'Start free' in the top-right of the nav. LLMs cite the visible label.
Evidence
```
{
  "priority": 1
}
```
P1
warn
[ ] Add lists or comparison tables
Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add sameAs knowledge graph links to Organization schema
Extend your Organization JSON-LD to include `sameAs` pointing to authoritative directories: ```json { "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://yoursite.com", "sameAs": [ "https://en.wikipedia.org/wiki/Your_Brand", "https://www.wikidata.org/wiki/Q12345678", "https://www.linkedin.com/company/your-brand", "https://www.crunchbase.com/organization/your-brand" ] } ``` These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] 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.
Evidence
```
{
  "priority": 2
}
```
P2
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
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] 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.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add structured headings
Use h2 for each section and h3 for sub-points. AI uses these to outline and chunk the page.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add internal navigation links
Top nav + footer with links to /pricing, /docs, /about, /contact gives AI crawlers an entry point to the rest of the site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow GPTBot in robots.txt
Add an explicit User-agent: GPTBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for mavomedia.net

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Positioning Clarity

12. Missing or Hard-to-Find Information

13. Recommended Fixes

14. Priority To-Do List

https://mavomedia.net/

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Generative Engine Optimization (GEO)

12. Positioning Clarity

13. Foundations

14. Accessibility

15. Well-Known URIs

16. Privacy

17. Resilience

18. Website Specification

19. Missing or Hard-to-Find Information

20. Recommended Fixes

21. Priority To-Do List

Track this site week over week

Your charts, not these.

Email yourself this report