1. Crawl Summary

pass

Fetched 1 of 1 pages successfully

Target: https://junwatu.com

Evidence

{
  "pages": [
    {
      "url": "https://junwatu.com",
      "bytes": 931,
      "status": 200,
      "fetchMs": 497
    }
  ],
  "origin": "https://junwatu.com",
  "target": "https://junwatu.com"
}

P5

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	No	—	—
Positioning	No	—	—
Executive team	No	—	—
Product/service descriptions	No	—	—
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 43 chars of text; rendered DOM contains 1696 (39.4× more). LLM crawlers like GPTBot generally do not run JavaScript — they will miss most of your content.
Evidence
```
{
  "ratio": 39.44186046511628,
  "rawTextLen": 43,
  "renderedTextLen": 1696
}
```
P1
fail
Content volume: 0 words
Very thin content. AI models need substantive text to understand and recommend your site.
Evidence
```
{
  "wordCount": 0
}
```
P1
warn
Missing meta description
Add a `<meta name="description">` to control the snippet AI/SERP show.
P2
warn
Missing canonical link
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
P3
fail
Open Graph: missing title, description, image
P3
warn
No Twitter Card tags
Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces.
P3
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 · 931 bytes · 497ms
Evidence
```
{
  "bytes": 931,
  "status": 200,
  "fetchMs": 497
}
```
P5
pass
Page load time: 0.50s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 497
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5

pass

`<title>` present (43 chars)

Evidence

{
  "title": "Building the Future with AI-Driven Products"
}

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": 931,
  "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
warn
No author byline found
Add `<meta name="author" content="Name">` or a visible byline with `rel="author"`. Strengthens E-E-A-T signals.
P4

5. 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

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
pass
Response time: 497ms
Fast first response.
Evidence
```
{
  "bytes": 931,
  "fetchMs": 497
}
```
P5
pass
Cache-Control set (CDN: Vercel)
Cache-Control: public, max-age=0, must-revalidate CDN detected: Vercel
Evidence
```
{
  "cdn": [
    "Vercel"
  ],
  "cacheControl": "public, max-age=0, must-revalidate"
}
```
P5
pass
Page size: 1 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 931
}
```
P5

pass

Resource requests: 4 (scripts:1, css:3, img:0)

Reasonable request count.

Evidence

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

P5

8. Security

warn
Content-Security-Policy missing
Define a CSP to limit script sources — large reduction in XSS surface.
P3
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
HSTS set
max-age=63072000
Evidence
```
{
  "value": "max-age=63072000"
}
```
P5
pass
X-Frame-Options set
DENY
Evidence
```
{
  "value": "DENY"
}
```
P5
pass
X-Content-Type-Options set
nosniff
Evidence
```
{
  "value": "nosniff"
}
```
P5

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://www.junwatu.com/"
}

P5

pass
No mixed content detected
P5

9. robots.txt and sitemap.xml Audit

warn
Sitemap is empty
No <loc> entries found. Sitemap should list canonical URLs.
P2
warn
robots.txt does not reference a Sitemap
Add `Sitemap: https://yoursite.com/sitemap.xml` to robots.txt.
P3

pass

robots.txt present

58 chars

Evidence

{
  "snippet": "User-agent: *\nAllow: /\nDisallow: /admin\nDisallow: /admin/\n"
}

P5

pass

sitemap.xml present (0 URLs)

Evidence

{
  "snippet": "<!doctype html>\n<html lang=\"en\">\n\n<head>\n  <meta charset=\"UTF-8\" />\n  <link rel=\"icon\" href=\"/favicon.png\" />\n  <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\" />\n  <title>Building the Future with AI-Driven Products</title>\n  <link rel=\"me\" href=\"https://www.threads.com/@equan_p\" />\n  <link rel=\"preconnect\" href=\"https://fonts.googleapis.com\" />\n  <link rel=\"preconnect\" href=\"https://fonts.gstatic.com\" crossorigin />\n  <link rel=\"stylesheet\" href=\"https://fonts.googleapis.com/css2?family=Inter:ital,opsz,wght@0,14..32,100..900;1,14..32,100..900&display=swap\" />\n  <link rel=\"stylesheet\" href=\"https://fonts.googleapis.com/css2?family=JetBrains+Mono:ital,wght@0,100..800;1,100..800&display=swap\" />\n  <script type=\"module\" crossorigin src=\"/assets/index-D9z_ADIG.js\"></scrip",
  "urlCount": 0
}

P5

10. LLM / AI Crawler Accessibility

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

pass

llms.txt present

931 chars

Evidence

{
  "snippet": "<!doctype html>\n<html lang=\"en\">\n\n<head>\n  <meta charset=\"UTF-8\" />\n  <link rel=\"icon\" href=\"/favicon.png\" />\n  <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\" />\n  <title>Building the Future with AI-Driven Products</title>\n  <link rel=\"me\" href=\"https://www.threads.com/@equan_p\" />\n  <link rel=\"preconnect\" href=\"https://fonts.googleapis.com\" />\n  <link rel=\"preconnect\" href="
}

P5

pass
skill.md present
P5
pass
/.well-known/ai-plugin.json present
P5
pass
/.well-known/security.txt present
Security contact published — builds trust with crawlers and security researchers.
P5

11. 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
warn
Value-prop language not detected
Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
P3

12. Missing or Hard-to-Find Information

fail

12 data point(s) could not be found from public pages

· Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Headline copy · Positioning · Executive team · Product/service descriptions · Case studies or testimonials · Contact/demo/signup paths

Evidence

{
  "missing": [
    "Pricing",
    "Customer logos",
    "Social proof",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Headline copy",
    "Positioning",
    "Executive team",
    "Product/service descriptions",
    "Case studies or testimonials",
    "Contact/demo/signup paths"
  ]
}

P1

13. Recommended Fixes

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 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 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 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." /> ```
Evidence
```
{
  "for": "homepage.description"
}
```
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
Populate your sitemap with canonical URLs
The sitemap must list `<loc>` entries — empty sitemaps are worse than none.
Evidence
```
{
  "for": "sitemap.empty"
}
```
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
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
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" /> ```
Evidence
```
{
  "for": "homepage.og"
}
```
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 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
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
State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "for": "positioning.audience"
}
```
P3
warn
Reference your sitemap in robots.txt
Add `Sitemap: https://yoursite.com/sitemap.xml` so crawlers don't have to guess.
Evidence
```
{
  "for": "robots.sitemap_ref"
}
```
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
Declare an author byline
Add `<meta name="author" content="Name">` or a visible byline with `rel="author"`. Combine with Person JSON-LD for E-E-A-T.
Evidence
```
{
  "for": "content.author"
}
```
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

14. Priority To-Do List

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 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 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 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." /> ```
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
[ ] Populate your sitemap with canonical URLs
The sitemap must list `<loc>` entries — empty sitemaps are worse than none.
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
[ ] 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
[ ] 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" /> ```
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 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 junwatu.com

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://junwatu.com/

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

Track this site week over week

Your charts, not these.