1. Crawl Summary

• fail

  Fetched 0 of 1 pages successfully

  Target: https://app.ironfairh.llc

  Evidence

  {
    "pages": [
      {
        "url": "https://app.ironfairh.llc",
        "bytes": 0,
        "status": 0,
        "fetchMs": 148
      }
    ],
    "origin": "https://app.ironfairh.llc",
    "target": "https://app.ironfairh.llc"
  }

  P1

2. Data Found

3. Homepage Audit

• fail

  Homepage could not be fetched

  fetch failed

  P1

4. Schema / Structured Data Audit

No findings.

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

No findings.

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

9. Recommended Fixes

• warn

  Publish a sitemap.xml

  Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.

  Evidence

  {
    "for": "sitemap.exists"
  }

  P1
• warn

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

  Create a robots.txt

  Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.

  Evidence

  {
    "for": "robots.exists"
  }

  P2
• warn

  Add /skill.md

  Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.

  Evidence

  {
    "for": "skill_md"
  }

  P3
• warn

  Publish /.well-known/security.txt

  A security contact builds trust with crawlers and researchers. Minimal example: ``` Contact: mailto:security@yourdomain.com Expires: 2027-01-01T00:00:00.000Z Preferred-Languages: en ```

  Evidence

  {
    "for": "security_txt"
  }

  P3

10. Priority To-Do List

• warn

  [ ] Publish a sitemap.xml

  Generate /sitemap.xml automatically (Next.js: app/sitemap.ts). Include every canonical URL.

  Evidence

  {
    "priority": 1
  }

  P1
• warn

  [ ] Add /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

  [ ] Create a robots.txt

  Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.

  Evidence

  {
    "priority": 2
  }

  P2
• warn

  [ ] Add /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