1. Crawl Summary

pass

Fetched 9 of 9 pages successfully

Target: https://profullstack.com

Evidence

{
  "pages": [
    {
      "url": "https://profullstack.com",
      "bytes": 50436,
      "status": 200,
      "fetchMs": 109
    },
    {
      "url": "https://profullstack.com/blog",
      "bytes": 16081,
      "status": 200,
      "fetchMs": 18
    },
    {
      "url": "https://profullstack.com/blog/building-modern-web-apps",
      "bytes": 10962,
      "status": 200,
      "fetchMs": 17
    },
    {
      "url": "https://profullstack.com/blog/blockchain-for-business",
      "bytes": 10886,
      "status": 200,
      "fetchMs": 17
    },
    {
      "url": "https://profullstack.com/blog/importance-of-mvp",
      "bytes": 10800,
      "status": 200,
      "fetchMs": 17
    },
    {
      "url": "https://profullstack.com/",
      "bytes": 50436,
      "status": 200,
      "fetchMs": 18
    },
    {
      "url": "https://profullstack.com/case-studies",
      "bytes": 37246,
      "status": 200,
      "fetchMs": 18
    },
    {
      "url": "https://profullstack.com/portfolio",
      "bytes": 32117,
      "status": 200,
      "fetchMs": 19
    },
    {
      "url": "https://profullstack.com/plans",
      "bytes": 38726,
      "status": 200,
      "fetchMs": 39
    }
  ],
  "origin": "https://profullstack.com",
  "target": "https://profullstack.com"
}

P5

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	Yes	Homepage	platform for
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

warn

Multiple H1s found

7 `<h1>` tags. Prefer one focused H1 per page.

Evidence

{
  "h1s": [
    "We build web products with the same rigor I learned inside Yahoo!, IBM, and PayPal.",
    "Who we work with",
    "What we build",
    "Results",
    "Selected work",
    "Latest from our blog",
    "Ready to build something that works?"
  ]
}

P3

warn
Missing canonical link
Add `<link rel="canonical" href="https://your-domain">` to prevent dup-content confusion.
P3
fail
Open Graph: missing title, description, image
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
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5
pass
Homepage fetched successfully
HTTP 200 · 50436 bytes · 109ms
Evidence
```
{
  "bytes": 50436,
  "status": 200,
  "fetchMs": 109
}
```
P5
pass
Page load time: 0.11s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 109
}
```
P5

pass

`<title>` present (43 chars)

Evidence

{
  "title": "Profullstack, Inc. — Web Development Agency"
}

P5

pass

Meta description present (53 chars)

Evidence

{
  "description": "Bringing your ideas to life with code and creativity."
}

P5

pass
Critical content is server-rendered
Raw and rendered text are within 19% of each other.
Evidence
```
{
  "ratio": 0.19166927654243657,
  "rawTextLen": 38316,
  "renderedTextLen": 7344
}
```
P5
pass
Alt text coverage: 100%
12/12 images have alt text.
P5
pass
Content volume: 936 words
Substantive content — AI models have enough to summarize and recommend.
Evidence
```
{
  "wordCount": 936
}
```
P5
pass
Heading structure: 26 (h1:7, h2:1, h3:18)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 7,
  "h2": 1,
  "h3": 18
}
```
P5
pass
Internal links: 18
18 internal + 6 external links help crawlers navigate.
Evidence
```
{
  "external": 6,
  "internal": 18
}
```
P5

pass

Favicon declared

Evidence

{
  "href": "/favicon.ico?favicon.0316mbgg5gqnv.ico"
}

P5

4. Content Quality

fail

5 heading-level skip(s)

Heading levels jump (e.g. h2 → h4). AI outline parsers expect monotonic nesting.

Evidence

{
  "levels": [
    1,
    1,
    3,
    3,
    3,
    2,
    1,
    3,
    3,
    3,
    3,
    3,
    3,
    3,
    3,
    3,
    3,
    3,
    3,
    1,
    3,
    3,
    3,
    1,
    4,
    4,
    4,
    4,
    4,
    4,
    1,
    4,
    4,
    4,
    1
  ]
}

P2

fail
Snippet-ready blocks: 0 (ul:0, ol:0, table:0)
Add bullet lists, numbered steps, or a comparison table. Answer engines prefer structured blocks over prose.
Evidence
```
{
  "ol": 0,
  "ul": 0,
  "tables": 0
}
```
P2
warn
No question-style headings found
Phrase at least one heading as a user question (e.g. 'How does pricing work?') to match conversational AI queries.
P3
warn
No date signal found
Add <time datetime="…"> or article:published_time meta. AI ranking weights freshness.
P3
warn
No author byline found
Add `<meta name="author" content="Name">` or a visible byline with `rel="author"`. Strengthens E-E-A-T signals.
P4
pass
Text-to-HTML ratio: 14.3%
Visible text density is healthy for AI extraction.
Evidence
```
{
  "ratio": 0.14329389343285953,
  "htmlBytes": 50372,
  "textChars": 7218
}
```
P5

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

6. Links & Images

warn
Modern image formats: 0% (0/12 webp/avif)
11 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
Evidence
```
{
  "total": 12,
  "legacy": 11,
  "modern": 0
}
```
P3
fail
Lazy loading: 0% (0/12)
Add `loading="lazy"` to below-the-fold images to reduce initial payload.
Evidence
```
{
  "lazy": 0,
  "total": 12
}
```
P3
fail
Explicit dimensions: 0% (0/12)
Add width and height attributes on <img> tags to prevent CLS.
Evidence
```
{
  "total": 12,
  "withDims": 0
}
```
P3
warn
Responsive srcset: 0/12
Use srcset/sizes to serve appropriately-sized images on mobile. Reduces wasted bytes.
P4
pass
External nofollow: 0% (0/6)
Healthy mix of follow and nofollow outbound links.
P5
pass
No broken links in first 17
HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
Evidence
```
{
  "broken": 0,
  "sampled": 17,
  "examples": []
}
```
P5

7. Performance

warn
1 render-blocking script(s) in <head>
Move non-critical scripts to end of <body> or add `defer`/`async`.
P3
pass
Cache-Control set
Cache-Control: s-maxage=31536000
Evidence
```
{
  "cdn": [],
  "cacheControl": "s-maxage=31536000"
}
```
P5
pass
Page size: 49 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 50436
}
```
P5

pass

Resource requests: 22 (scripts:8, css:2, img:12)

Reasonable request count.

Evidence

{
  "imgs": 12,
  "styles": 2,
  "scripts": 8,
  "inlineStyles": 0,
  "inlineScripts": 13
}

P5

pass
Inline JS+CSS bulk: 30 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 31055,
  "inlineCssBytes": 0
}
```
P5
pass
Response time: 109ms
Fast first response.
Evidence
```
{
  "bytes": 50436,
  "fetchMs": 109
}
```
P5

8. Security

warn
HSTS missing
Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you're confident in https.
P3
warn
Content-Security-Policy missing
Define a CSP to limit script sources — large reduction in XSS surface.
P3
warn
X-Frame-Options missing
Add `X-Frame-Options: SAMEORIGIN` (or use CSP frame-ancestors) to prevent clickjacking.
P4
warn
X-Content-Type-Options missing
Add `X-Content-Type-Options: nosniff` to block MIME-type sniffing.
P4
warn
Referrer-Policy missing
Add `Referrer-Policy: strict-origin-when-cross-origin` for safer referrers.
P4
warn
Permissions-Policy missing
Restrict browser features (camera, mic, geolocation) you don't use.
P4

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://profullstack.com/"
}

P5

pass
No mixed content detected
P5

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

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

11. Positioning Clarity

warn
No clear About/Team link
Add an About or Team link in the nav or footer so LLMs can identify the company.
P2
pass
H1 communicates value
We build web products with the same rigor I learned inside Yahoo!, IBM, and PayPal.
P5
pass
Value-prop language detected
P5
pass
Pricing path discoverable
P5
pass
Contact / signup path discoverable
P5

12. Missing or Hard-to-Find Information

warn
4 data point(s) could not be found from public pages
· Customer logos · Social proof · New hires · Executive team
Evidence
```
{
  "missing": [
    "Customer logos",
    "Social proof",
    "New hires",
    "Executive team"
  ]
}
```
P3

13. 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 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
Fix heading-level skips
Don't jump from h2 to h4. AI outline parsers expect monotonic nesting — keep heading depth contiguous.
Evidence
```
{
  "for": "content.heading_order"
}
```
P2
warn
Add lists or comparison tables
Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
Evidence
```
{
  "for": "content.snippet_blocks"
}
```
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
```
{
  "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
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
Phrase a heading as a user question
Use headings like 'How does pricing work?' or 'Who is this for?' — they map directly to conversational AI queries.
Evidence
```
{
  "for": "content.qa_headings"
}
```
P3
warn
Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "for": "content.date_signal"
}
```
P3
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"
}
```
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
Use modern image formats
Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as <picture> fallbacks.
Evidence
```
{
  "for": "images.format"
}
```
P3
warn
Lazy-load below-the-fold images
Add `loading="lazy"` on `<img>` tags that aren't in the initial viewport. Reduces first-paint payload.
Evidence
```
{
  "for": "images.lazy_loading"
}
```
P3
warn
Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "for": "images.dimensions"
}
```
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
Eliminate render-blocking head scripts
Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`.
Evidence
```
{
  "for": "perf.render_blocking"
}
```
P3
warn
Enable HSTS
Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you're confident every subdomain is https-ready.
Evidence
```
{
  "for": "security.hsts"
}
```
P3
warn
Define a Content-Security-Policy
Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius.
Evidence
```
{
  "for": "security.csp"
}
```
P3
warn
Declare an author byline
Add `<meta name="author" content="Name">` or a visible byline with `rel="author"`. Combine with Person JSON-LD for E-E-A-T.
Evidence
```
{
  "for": "content.author"
}
```
P4
warn
Use srcset/sizes for responsive images
Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
Evidence
```
{
  "for": "images.srcset"
}
```
P4
warn
Add X-Frame-Options
`X-Frame-Options: SAMEORIGIN` (or CSP `frame-ancestors`) blocks clickjacking via iframe embeds.
Evidence
```
{
  "for": "security.xfo"
}
```
P4
warn
Add X-Content-Type-Options
`X-Content-Type-Options: nosniff` prevents browsers from MIME-sniffing responses.
Evidence
```
{
  "for": "security.xcto"
}
```
P4
warn
Set a Referrer-Policy
`Referrer-Policy: strict-origin-when-cross-origin` is a safe default.
Evidence
```
{
  "for": "security.referrer"
}
```
P4
warn
Set a Permissions-Policy
Restrict browser features you don't use, e.g. `Permissions-Policy: camera=(), microphone=(), geolocation=()`.
Evidence
```
{
  "for": "security.permissions"
}
```
P4

14. 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 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
[ ] Fix heading-level skips
Don't jump from h2 to h4. AI outline parsers expect monotonic nesting — keep heading depth contiguous.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add lists or comparison tables
Answer engines lift bulleted lists, numbered steps, and tables verbatim. Add at least 2 snippet-ready blocks to the homepage.
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
[ ] 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
[ ] 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
[ ] Phrase a heading as a user question
Use headings like 'How does pricing work?' or 'Who is this for?' — they map directly to conversational AI queries.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Publish a date signal
Add `<time datetime="2026-05-17">` or `<meta property="article:published_time">`. AI ranking heavily weights freshness.
Evidence
```
{
  "priority": 3
}
```
P3
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": 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
[ ] Use modern image formats
Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as <picture> fallbacks.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Lazy-load below-the-fold images
Add `loading="lazy"` on `<img>` tags that aren't in the initial viewport. Reduces first-paint payload.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
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
[ ] Eliminate render-blocking head scripts
Add `defer` or `async` to any `<script src="…">` in `<head>`, or move it to the end of `<body>`.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Enable HSTS
Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you're confident every subdomain is https-ready.
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for profullstack.com

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Positioning Clarity

12. Missing or Hard-to-Find Information

13. Recommended Fixes

14. Priority To-Do List

https://profullstack.com/

1. Crawl Summary

2. Data Found

3. Homepage Audit

4. Content Quality

5. Schema / Structured Data Audit

6. Links & Images

7. Performance

8. Security

9. robots.txt and sitemap.xml Audit

10. LLM / AI Crawler Accessibility

11. Positioning Clarity

12. Missing or Hard-to-Find Information

13. Recommended Fixes

14. Priority To-Do List

Track this site week over week

Your charts, not these.