# AEO Audit for app.ironfaith.llc **Target:** https://app.ironfaith.llc/ **Score:** 27 / 100 **Generated:** 2026-05-14T01:27:46.450Z **Pages crawled:** 1 **Findings:** 6 pass · 62 warn · 10 fail · 0 unknown --- ## 1. Crawl Summary - ✅ **Fetched 1 of 1 pages successfully** Target: https://app.ironfaith.llc ## 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 - ❌ **Missing H1** No `

` 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 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. - ❌ Content volume: 0 words Very thin content. AI models need substantive text to understand and recommend your site. - ⚠️ Short `` (7 chars) Aim for 30–60 chars. Lead with brand or product, then value prop. - ⚠️ Missing canonical link Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion. - ❌ Open Graph: missing title, description, image - ⚠️ No Twitter Card tags Add twitter:card, twitter:title, twitter:description, twitter:image for richer previews in social and AI agent surfaces. - ❌ 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 · 942 bytes · 250ms - ✅ Page load time: 0.25s Fast — well within AI crawler budgets. - ✅ <html lang="en"> declared - ✅ Meta description present (84 chars) ## 4. Schema / Structured Data Audit - ❌ No JSON-LD structured data found Add JSON-LD blocks (Organization, SoftwareApplication, FAQPage, BreadcrumbList) so AI answer engines can ingest your data without guessing. ## 5. robots.txt and sitemap.xml Audit - ❌ sitemap.xml not found Add /sitemap.xml — required for reliable AI/SERP discovery. - ⚠️ robots.txt not found No /robots.txt was reachable. Add one explicitly — silence is read differently by different crawlers, and you lose the chance to control AI bots. ## 6. LLM / AI Crawler Accessibility - ⚠️ llms.txt missing Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site. - ⚠️ skill.md missing Add /skill.md describing what your site lets agents do — speeds up agent task routing. - ⚠️ /.well-known/security.txt missing Publish a /.well-known/security.txt with at least a Contact: line. Crawlers and security researchers expect it; AI systems use it as a trust signal. ## 7. Positioning Clarity - ⚠️ 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 not detected Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize. ## 8. Missing or Hard-to-Find Information - ❌ 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 ## 9. Recommended Fixes - ⚠️ 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. - ⚠️ Publish a sitemap.xml Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL. - ⚠️ Add JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section. - ⚠️ Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary. - ⚠️ Make your About/Team page reachable Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site. - ⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers. - ⚠️ Create a robots.txt Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots. - ⚠️ Set a meaningful `<title>` 30–60 chars. Lead with the brand or product, then the value prop. ```html <title>CrawlProof — AEO audits for AI crawlers ``` - ⚠️ Add a canonical link Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html ``` - ⚠️ Complete Open Graph tags AI bots use OG for fast disambiguation. Add all four: ```html ``` - ⚠️ Add Twitter Card meta tags Used by social platforms and AI agents for richer previews. ```html ``` - ⚠️ Add 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. - ⚠️ 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 ``` - ⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page. ## 10. Priority To-Do List - [ ] P1 — Add a single, focused H1 to the homepage One `

` 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. - [ ] P1 — Publish a sitemap.xml Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL. - [ ] P1 — Add JSON-LD structured data Start with Organization on the root layout and SoftwareApplication or Product on /pricing. Add FAQPage on any FAQ section. - [ ] P2 — Add /llms.txt A short Markdown-flavored summary at the root. Include your H1, value prop, top 5–10 links, and pricing summary. - [ ] P2 — Make your About/Team page reachable Add a top-nav or footer link to /about or /team so LLMs can identify the entity behind the site. - [ ] P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers. - [ ] P2 — Create a robots.txt Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots. - [ ] P3 — Set a meaningful `` 30–60 chars. Lead with the brand or product, then the value prop. ```html <title>CrawlProof — AEO audits for AI crawlers ``` - [ ] P3 — Add a canonical link Prevents dup-content drift and tells AI crawlers which URL is authoritative. ```html ``` - [ ] P3 — Complete Open Graph tags AI bots use OG for fast disambiguation. Add all four: ```html ``` - [ ] P3 — Add Twitter Card meta tags Used by social platforms and AI agents for richer previews. ```html ``` - [ ] P3 — Add 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 — Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows. - [ ] P3 — Publish /.well-known/security.txt A security contact builds trust with crawlers and researchers. Minimal example: ``` Contact: mailto:security@yourdomain.com Expires: 2027-01-01T00:00:00.000Z Preferred-Languages: en ``` - [ ] P3 — State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page. --- _Report by [CrawlProof](https://crawlproof.com). Reusable after every major website change._