1. Crawl Summary

pass

Fetched 1 of 1 pages successfully

Target: https://app.ironfaith.llc

Evidence

{
  "pages": [
    {
      "url": "https://app.ironfaith.llc",
      "bytes": 942,
      "status": 200,
      "fetchMs": 250
    }
  ],
  "origin": "https://app.ironfaith.llc",
  "target": "https://app.ironfaith.llc"
}

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	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 7 chars of text; rendered DOM contains 2704 (386.3× more). LLM crawlers like GPTBot generally do not run JavaScript — they will miss most of your content.
Evidence
```
{
  "ratio": 386.2857142857143,
  "rawTextLen": 7,
  "renderedTextLen": 2704
}
```
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
Open Graph: missing title, description, image
P3
warn
Short `<title>` (7 chars)
Aim for 30–60 chars. Lead with brand or product, then value prop.
Evidence
```
{
  "title": "HolyFit"
}
```
P3
warn
Missing canonical link
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
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 · 942 bytes · 250ms
Evidence
```
{
  "bytes": 942,
  "status": 200,
  "fetchMs": 250
}
```
P5
pass
Page load time: 0.25s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 250
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5

pass

Meta description present (84 chars)

Evidence

{
  "description": "HolyFit — train with intention. The fitness app for focus, discipline, and progress."
}

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

8. Missing or Hard-to-Find Information

fail
11 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 · 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",
    "Case studies or testimonials",
    "Contact/demo/signup paths"
  ]
}
```
P1

9. 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
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
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</title> ```
Evidence
```
{
  "for": "homepage.title"
}
```
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
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
State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "for": "positioning.audience"
}
```
P3

10. 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
[ ] 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
[ ] 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 /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
[ ] 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
[ ] 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</title> ```
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
[ ] 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
warn
[ ] State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for app.ironfaith.llc

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://app.ironfaith.llc/

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.