AEO Audit for profullstack.com
Target: https://profullstack.com/
Score: 39 / 100
Generated: 2026-05-13T00:41:20.577Z
Pages crawled: 9
Findings: 15 pass · 33 warn · 3 fail · 0 unknown
1. Crawl Summary
- ✅ Fetched 9 of 9 pages successfully Target: https://profullstack.com
2. Data Found
| Data Point | Found? | Source | Notes |
|---|---|---|---|
| Pricing | Yes | Pricing page | https://profullstack.com/plans |
| Customer logos | No | — | — |
| Social proof | No | — | — |
| Recent launches | Yes | Press/news pages | https://profullstack.com/blog |
| Blog post activity | Yes | Blog | https://profullstack.com/blog |
| New hires | No | — | Often only on a /blog/team or LinkedIn page |
| Headline copy | Yes | Homepage | We build web products with the same rigor I learned inside Yahoo!, IBM, and PayPal. |
| Positioning | No | — | — |
| Executive team | No | — | — |
| Product/service descriptions | Yes | Homepage | From meta description |
| Case studies or testimonials | Yes | Navigation links | — |
| Contact/demo/signup paths | Yes | Navigation links | — |
3. Homepage Audit
- ⚠️ Multiple H1s found 7
<h1>tags. Prefer one focused H1 per page. - ⚠️ Missing canonical link Add
<link rel="canonical" href="https://your-domain">to prevent dup-content confusion. - ❌ Open Graph: missing title, description, image
- ✅ Homepage fetched successfully HTTP 200 · 50436 bytes · 78ms
- ✅
<title>present - ✅ Meta description present
- ✅ Alt text coverage: 100% 12/12 images have alt text.
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.
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 We build web products with the same rigor I learned inside Yahoo!, IBM, and PayPal.
- ✅ Pricing path discoverable
- ✅ Contact / signup path discoverable
8. Missing or Hard-to-Find Information
- ⚠️ 5 data point(s) could not be found from public pages · Customer logos · Social proof · New hires · Positioning · Executive team
9. Recommended Fixes
- ⚠️ 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.
- ⚠️ Create a robots.txt Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
- ⚠️ 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. - ⚠️ Add a canonical link
<link rel="canonical" href="https://yoursite.com/">on every page to prevent dup-content drift. - ⚠️ Complete Open Graph tags Set og:title, og:description, og:image. AI bots also use OG for fast disambiguation.
- ⚠️ Add /skill.md Describe what an agent can do with your site (e.g., 'Search docs', 'Look up pricing'). Useful for agentic flows.
- ⚠️ State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
10. Priority To-Do Checklist
- 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 — Create a robots.txt Even a minimal robots.txt is better than none. Always reference your Sitemap and explicitly address AI bots.
- P3 — 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. - P3 — Add a canonical link
<link rel="canonical" href="https://yoursite.com/">on every page to prevent dup-content drift. - P3 — Complete Open Graph tags Set og:title, og:description, og:image. AI bots also use OG for fast disambiguation.
- 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 — State your audience explicitly Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Report by CrawlProof. Reusable after every major website change.