CrawlProof
View raw .md

AEO Audit for pdfsleuth.com

Target: https://pdfsleuth.com/
Score: 52 / 100
Generated: 2026-05-13T14:49:26.122Z
Pages crawled: 9
Findings: 33 pass · 39 warn · 1 fail · 0 unknown


1. Crawl Summary

2. Data Found

Data PointFound?SourceNotes
PricingYesPricing pagehttps://pdfsleuth.com/pricing
Customer logosNo
Social proofNo
Recent launchesYesPress/news pageshttps://pdfsleuth.com/changelog
Blog post activityYesBloghttps://pdfsleuth.com/changelog
New hiresNoOften only on a /blog/team or LinkedIn page
Headline copyYesHomepageSearch Across Multiple PDFs Instantly with PDFSleuth
PositioningNo
Executive teamNo
Product/service descriptionsYesHomepageFrom meta description
Case studies or testimonialsNo
Contact/demo/signup pathsYesNavigation links

3. Homepage Audit

  • ⚠️ Page load time: 1.36s Acceptable — consider optimizing for faster crawl times.
  • ⚠️ Content volume: 197 words Thin content. Aim for 300+ words on the homepage so AI models can extract a useful description.
  • Homepage fetched successfully HTTP 200 · 52601 bytes · 1360ms
  • declared
  • Single H1 Search Across Multiple PDFs Instantly with PDFSleuth
  • <title> present (70 chars)
  • Meta description present (156 chars)
  • Canonical present https://pdfsleuth.com/
  • Open Graph tags complete
  • Twitter Card tags complete
  • Critical content is server-rendered Raw and rendered text are within 3% of each other.
  • Alt text coverage: 100% 2/2 images have alt text.
  • Heading structure: 9 (h1:1, h2:1, h3:7) Multiple headings help AI chunk and outline your page.
  • Internal links: 20 20 internal + 0 external links help crawlers navigate.

4. Schema / Structured Data Audit

  • ⚠️ SoftwareApplication missing Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
  • 5 JSON-LD block(s) found Types: Organization, WebApplication, FAQPage, WebSite, WebPage
  • Organization present
  • WebSite present
  • FAQPage JSON-LD present

5. robots.txt and sitemap.xml Audit

  • robots.txt present 2406 chars
  • robots.txt references sitemap(s)
  • sitemap.xml present (19 URLs)

6. LLM / AI Crawler Accessibility

  • ⚠️ llms.txt missing Add /llms.txt — a concise, link-rich summary that helps LLMs orient on your site.
  • ⚠️ 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.
  • ⚠️ 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.
  • ⚠️ 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.
  • GPTBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • PerplexityBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • Google-Extended has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
  • CCBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.

7. Positioning Clarity

  • ⚠️ No clear About/Team link Add an About or Team link in the nav or footer so LLMs can identify the company.
  • ⚠️ Value-prop language not detected Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
  • H1 communicates value Search Across Multiple PDFs Instantly with PDFSleuth
  • Pricing path discoverable
  • Contact / signup path discoverable

8. Missing or Hard-to-Find Information

  • 6 data point(s) could not be found from public pages · Customer logos · Social proof · New hires · Positioning · Executive team · Case studies or testimonials
  • ⚠️ 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.

  • ⚠️ Speed up homepage rendering AI crawlers commonly time out around 3s. Cache the HTML, ship less JS for the first paint, and pre-render the hero section server-side.

  • ⚠️ 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.

  • ⚠️ Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot 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.

  • ⚠️ 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.

  • ⚠️ Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.

10. Priority To-Do List

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

  • P3 — Speed up homepage rendering AI crawlers commonly time out around 3s. Cache the HTML, ship less JS for the first paint, and pre-render the hero section server-side.

  • P3 — 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.

  • P3 — Allow ClaudeBot in robots.txt Add an explicit User-agent: ClaudeBot Allow: / block so this AI crawler can read your site.

  • P3 — Allow OAI-SearchBot in robots.txt Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.

  • P3 — Allow Applebot-Extended in robots.txt Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your 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.

  • P3 — Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.


Report by CrawlProof. Reusable after every major website change.