Public share link

AEO Audit for surefix.netlify.app

Target: https://surefix.netlify.app/
Score: 55 / 100
Generated: 2026-08-17T16:28:14.929Z
Pages crawled: 9
Findings: 67 pass · 80 warn · 2 fail · 0 unknown

1. Crawl Summary

✅ Fetched 9 of 9 pages successfully Target: https://surefix.netlify.app

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	Yes	Homepage	SCREWTHE OLDWAY.
Positioning	No	—	—
Executive team	No	—	—
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	No	—	—
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

✅ Homepage fetched successfully HTTP 200 · 76075 bytes · 90ms
✅ Page load time: 0.09s Fast — well within AI crawler budgets.
✅ declared
✅ Single H1 SCREWTHE OLDWAY.
✅ <title> present (45 chars)
✅ Meta description present (141 chars)
✅ Canonical present https://surefix.netlify.app/
✅ Open Graph tags complete
✅ Twitter Card tags complete
✅ Alt text coverage: 100% 8/8 images have alt text.
✅ Content volume: 1371 words Substantive content — AI models have enough to summarize and recommend.
✅ Heading structure: 14 (h1:1, h2:8, h3:5) Multiple headings help AI chunk and outline your page.
✅ Internal links: 19 19 internal + 7 external links help crawlers navigate.
✅ Robots meta: "index, follow"
✅ Favicon declared

4. Content Quality

⚠️ No date signal found Add or article:published_time meta. AI ranking weights freshness.
✅ Heading levels are well-ordered 14 headings nested in order.
✅ Snippet-ready blocks: 4 (ul:3, ol:0, table:1) Lists and tables are extracted verbatim by AI answer engines.
✅ 1 question-style heading(s) Questions in headings map cleanly to user queries. Pair with FAQPage JSON-LD for max lift.
✅ Author byline declared
✅ Text-to-HTML ratio: 11.2% Visible text density is healthy for AI extraction.

5. Schema / Structured Data Audit

⚠️ SoftwareApplication missing Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
⚠️ FAQPage JSON-LD missing Add an FAQPage block on pages that answer common questions — high-value for AI summaries.
⚠️ Article / BlogPosting JSON-LD not found Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
⚠️ BreadcrumbList JSON-LD not found Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
⚠️ LocalBusiness JSON-LD not found Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
⚠️ Person (author / founder) JSON-LD not found Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
⚠️ HowTo JSON-LD not found Add HowTo where applicable so AI answer engines can resolve the entity precisely.
✅ 5 JSON-LD block(s) found Types: Organization, WebSite, WebPage, VideoObject, Product
✅ Organization present
✅ WebSite present
✅ Product / Offer JSON-LD present
✅ VideoObject JSON-LD present

6. Links & Images

⚠️ Modern image formats: 50% (4/8 webp/avif) 4 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
❌ Explicit dimensions: 0% (0/8) Add width and height attributes on tags to prevent CLS.
⚠️ 1 broken link(s) in first 13 · 403 — https://www.tiktok.com/@surefixltd
⚠️ Responsive srcset: 0/8 Use srcset/sizes to serve appropriately-sized images on mobile. Reduces wasted bytes.
✅ Lazy loading: 63% (5/8) Most below-the-fold images defer load — good for perf and crawl budgets.
✅ External nofollow: 0% (0/7) Healthy mix of follow and nofollow outbound links.

7. Performance

✅ Page size: 74 KB Compact HTML payload — well within AI crawler limits.
✅ Resource requests: 12 (scripts:2, css:2, img:8) Reasonable request count.
✅ No render-blocking head scripts All head scripts use async or defer.
✅ Inline JS+CSS bulk: 12 KB Inline payload is modest.
✅ Response time: 90ms Fast first response.
✅ Cache-Control set (CDN: Netlify) Cache-Control: public,max-age=0,must-revalidate CDN detected: Netlify
✅ Compression enabled (Brotli) Content-Encoding: br
✅ Lazy loading: 5/8 images

8. Security

⚠️ Content-Security-Policy missing Define a CSP to limit script sources — large reduction in XSS surface.
✅ Served over HTTPS
✅ No mixed content detected
✅ HSTS set max-age=31536000; includeSubDomains; preload
✅ X-Frame-Options set SAMEORIGIN
✅ X-Content-Type-Options set nosniff
✅ Referrer-Policy set strict-origin-when-cross-origin
✅ Permissions-Policy set camera=(), microphone=(), geolocation=(), payment=()

9. robots.txt and sitemap.xml Audit

✅ robots.txt present 2740 chars
✅ robots.txt references sitemap(s)
✅ sitemap.xml present (18 URLs)

10. LLM / AI Crawler Accessibility

⚠️ 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.
⚠️ /llms-full.txt missing Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.
✅ GPTBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
✅ ClaudeBot 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.
✅ OAI-SearchBot has explicit rules An explicit User-agent block exists. Make sure it allows the paths you want indexed.
✅ Applebot-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.
✅ llms.txt present 20526 chars

11. Positioning Clarity

⚠️ 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.
✅ About/Team path discoverable
✅ H1 communicates value SCREWTHE OLDWAY.
✅ Contact / signup path discoverable

12. Missing or Hard-to-Find Information

❌ 9 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials

13. Recommended Fixes

⚠️ Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

⚠️ Add an AI agent integration file At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API:
```
# Your Brand Skill

API endpoint: https://yoursite.com/api
Auth: Bearer token

## Tools

- search: Search the knowledge base
- get_article: Retrieve a full article by ID
```
Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
⚠️ Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
⚠️ Publish a date signal Add <time datetime="2026-05-17"> or <meta property="article:published_time">. AI ranking heavily weights freshness.
⚠️ Generate /llms-full.txt for RAG pipelines llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root:
```
# Your Brand — Full Content

## Getting Started
<full markdown content of /docs/start>

## API Reference
<full markdown content of /docs/api>
```
Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.
⚠️ Add outbound links to authoritative sources Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood.
Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
⚠️ Use modern image formats Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as fallbacks.
⚠️ Set width/height on images Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
⚠️ Fix broken homepage links We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
⚠️ 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.
⚠️ Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
⚠️ Add Article / BlogPosting JSON-LD On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
⚠️ Add BreadcrumbList JSON-LD Helps AI engines understand site hierarchy and improves citation context.
⚠️ Define a Content-Security-Policy Start with Content-Security-Policy-Report-Only to learn safe sources, then enforce. Cuts XSS blast radius.
⚠️ Use srcset/sizes for responsive images Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
⚠️ Add LocalBusiness JSON-LD (if you have a physical location) Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
⚠️ Add Person JSON-LD for authors / founders Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
⚠️ Add HowTo JSON-LD for step-by-step content For any 'how to' page, wrap the steps in HowTo JSON-LD. AI step-by-step answers cite these heavily.

14. Priority To-Do List

P2 — Add sameAs knowledge graph links to Organization schema Extend your Organization JSON-LD to include sameAs pointing to authoritative directories:

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Brand",
  "url": "https://yoursite.com",
  "sameAs": [
    "https://en.wikipedia.org/wiki/Your_Brand",
    "https://www.wikidata.org/wiki/Q12345678",
    "https://www.linkedin.com/company/your-brand",
    "https://www.crunchbase.com/organization/your-brand"
  ]
}
```

These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.

P2 — Add an AI agent integration file At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API:

```markdown
# Your Brand Skill

API endpoint: https://yoursite.com/api
Auth: Bearer token

## Tools

- search: Search the knowledge base
- get_article: Retrieve a full article by ID
```

Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.

P2 — Add a /pricing page Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
P3 — Publish a date signal Add <time datetime="2026-05-17"> or <meta property="article:published_time">. AI ranking heavily weights freshness.

P3 — Generate /llms-full.txt for RAG pipelines llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root:

```
# Your Brand — Full Content

## Getting Started
<full markdown content of /docs/start>

## API Reference
<full markdown content of /docs/api>
```

Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.

P3 — Add outbound links to authoritative sources Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood.
```
Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
```
P3 — Use modern image formats Serve WebP or AVIF for hero/above-the-fold images. Keep legacy PNG/JPG only as fallbacks.
P3 — Set width/height on images Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
P3 — Fix broken homepage links We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
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.
P3 — Add FAQPage JSON-LD Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
P3 — Add Article / BlogPosting JSON-LD On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
P3 — Add BreadcrumbList JSON-LD Helps AI engines understand site hierarchy and improves citation context.
P3 — Define a Content-Security-Policy Start with Content-Security-Policy-Report-Only to learn safe sources, then enforce. Cuts XSS blast radius.
P4 — Use srcset/sizes for responsive images Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
P4 — Add LocalBusiness JSON-LD (if you have a physical location) Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
P4 — Add Person JSON-LD for authors / founders Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.

Report by CrawlProof. Reusable after every major website change.

AEO audit

https://surefix.netlify.app/

Completed 8/17/2026, 4:28:15 PM

/100

1. Crawl Summary

pass

Fetched 9 of 9 pages successfully

Target: https://surefix.netlify.app

Evidence

{
  "pages": [
    {
      "url": "https://surefix.netlify.app",
      "bytes": 76075,
      "status": 200,
      "fetchMs": 90
    },
    {
      "url": "https://surefix.netlify.app/",
      "bytes": 76075,
      "status": 200,
      "fetchMs": 13
    },
    {
      "url": "https://surefix.netlify.app/shop",
      "bytes": 69756,
      "status": 200,
      "fetchMs": 250
    },
    {
      "url": "https://surefix.netlify.app/competition",
      "bytes": 49572,
      "status": 200,
      "fetchMs": 196
    },
    {
      "url": "https://surefix.netlify.app/safer-gutter-bracket-installation",
      "bytes": 25684,
      "status": 200,
      "fetchMs": 182
    },
    {
      "url": "https://surefix.netlify.app/testimonials",
      "bytes": 31634,
      "status": 200,
      "fetchMs": 244
    },
    {
      "url": "https://surefix.netlify.app/rise-and-fall-gutter-bracket",
      "bytes": 26146,
      "status": 200,
      "fetchMs": 194
    },
    {
      "url": "https://surefix.netlify.app/fastest-gutter-bracket",
      "bytes": 22806,
      "status": 200,
      "fetchMs": 183
    },
    {
      "url": "https://surefix.netlify.app/no-masonry-damage-gutter-bracket",
      "bytes": 24209,
      "status": 200,
      "fetchMs": 243
    }
  ],
  "origin": "https://surefix.netlify.app",
  "target": "https://surefix.netlify.app"
}

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	Yes	Homepage	SCREWTHE OLDWAY.
Positioning	No	—	—
Executive team	No	—	—
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	No	—	—
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

pass

Open Graph tags complete

Evidence

{
  "image": "https://surefix.netlify.app/assets/images/SurefixR-F-Product-01.webp",
  "title": "SureFix — Screw The Old Way",
  "description": "The patented screw-in rise and fall gutter bracket. Under 30 seconds per bracket. 78% faster. Zero damage. Trade prices available."
}

pass
Canonical present
https://surefix.netlify.app/
Evidence
```
{
  "canonical": "https://surefix.netlify.app/"
}
```
P5

pass

Meta description present (141 chars)

Evidence

{
  "description": "SureFix: patented screw-in rise & fall gutter bracket. Installs in under 30 seconds. 78% faster. Zero masonry damage. Trade prices available."
}

pass

`<title>` present (45 chars)

Evidence

{
  "title": "SureFix | Screw-In Rise & Fall Gutter Bracket"
}

pass
Single H1
SCREWTHE OLDWAY.
Evidence
```
{
  "h1": "SCREWTHE OLDWAY."
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5
pass
Page load time: 0.09s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 90
}
```
P5
pass
Homepage fetched successfully
HTTP 200 · 76075 bytes · 90ms
Evidence
```
{
  "bytes": 76075,
  "status": 200,
  "fetchMs": 90
}
```
P5

pass

Favicon declared

Evidence

{
  "href": "https://d2xsxph8kpxj0f.cloudfront.net/97557150/gBVQbQCeQPYMevmDAokqpL/SFFavicon_8d53d53f.webp"
}

pass
Robots meta: "index, follow"
Evidence
```
{
  "content": "index, follow"
}
```
P5
pass
Internal links: 19
19 internal + 7 external links help crawlers navigate.
Evidence
```
{
  "external": 7,
  "internal": 19
}
```
P5
pass
Heading structure: 14 (h1:1, h2:8, h3:5)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 1,
  "h2": 8,
  "h3": 5
}
```
P5
pass
Content volume: 1371 words
Substantive content — AI models have enough to summarize and recommend.
Evidence
```
{
  "wordCount": 1371
}
```
P5
pass
Alt text coverage: 100%
8/8 images have alt text.
P5

pass

Twitter Card tags complete

Evidence

{
  "card": "summary_large_image",
  "image": "https://surefix.netlify.app/assets/images/SurefixR-F-Product-01.webp",
  "title": "SureFix — Screw-In Rise and Fall Gutter Bracket",
  "description": "UK patent-protected screw-in rise and fall gutter bracket. Installs in under 30 seconds. Zero masonry damage. Buy direct from SureFix HQ."
}

4. Content Quality

warn
No date signal found
Add <time datetime="…"> or article:published_time meta. AI ranking weights freshness.
P3
pass
Text-to-HTML ratio: 11.2%
Visible text density is healthy for AI extraction.
Evidence
```
{
  "ratio": 0.11170338782279081,
  "htmlBytes": 75978,
  "textChars": 8487
}
```
P5
pass
Author byline declared
P5
pass
1 question-style heading(s)
Questions in headings map cleanly to user queries. Pair with FAQPage JSON-LD for max lift.
Evidence
```
{
  "samples": [
    "WHAT DOES IT COSTYOU NOT TO SWITCH?"
  ]
}
```
P5
pass
Snippet-ready blocks: 4 (ul:3, ol:0, table:1)
Lists and tables are extracted verbatim by AI answer engines.
Evidence
```
{
  "ol": 0,
  "ul": 3,
  "tables": 1
}
```
P5

pass

Heading levels are well-ordered

14 headings nested in order.

Evidence

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

5. Schema / Structured Data Audit

warn
SoftwareApplication missing
Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
P3
warn
FAQPage JSON-LD missing
Add an FAQPage block on pages that answer common questions — high-value for AI summaries.
P3
warn
Article / BlogPosting JSON-LD not found
Add Article / BlogPosting where applicable so AI answer engines can resolve the entity precisely.
P3
warn
BreadcrumbList JSON-LD not found
Add BreadcrumbList where applicable so AI answer engines can resolve the entity precisely.
P3
warn
LocalBusiness JSON-LD not found
Add LocalBusiness where applicable so AI answer engines can resolve the entity precisely.
P4
warn
Person (author / founder) JSON-LD not found
Add Person (author / founder) where applicable so AI answer engines can resolve the entity precisely.
P4
warn
HowTo JSON-LD not found
Add HowTo where applicable so AI answer engines can resolve the entity precisely.
P4
pass
VideoObject JSON-LD present
P5
pass
Product / Offer JSON-LD present
P5
pass
WebSite present
P5
pass
Organization present
P5

pass

5 JSON-LD block(s) found

Types: Organization, WebSite, WebPage, VideoObject, Product

Evidence

{
  "types": [
    "Organization",
    "WebSite",
    "WebPage",
    "VideoObject",
    "Product"
  ],
  "blocks": 5
}

6. Links & Images

warn
Modern image formats: 50% (4/8 webp/avif)
4 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
Evidence
```
{
  "total": 8,
  "legacy": 4,
  "modern": 4
}
```
P3
fail
Explicit dimensions: 0% (0/8)
Add width and height attributes on <img> tags to prevent CLS.
Evidence
```
{
  "total": 8,
  "withDims": 0
}
```
P3

warn

1 broken link(s) in first 13

· 403 — https://www.tiktok.com/@surefixltd

Evidence

{
  "broken": 1,
  "sampled": 13,
  "examples": [
    {
      "url": "https://www.tiktok.com/@surefixltd",
      "status": 403
    }
  ]
}

warn
Responsive srcset: 0/8
Use srcset/sizes to serve appropriately-sized images on mobile. Reduces wasted bytes.
P4
pass
Lazy loading: 63% (5/8)
Most below-the-fold images defer load — good for perf and crawl budgets.
Evidence
```
{
  "lazy": 5,
  "total": 8
}
```
P5
pass
External nofollow: 0% (0/7)
Healthy mix of follow and nofollow outbound links.
P5

7. Performance

pass
Compression enabled (Brotli)
Content-Encoding: br
Evidence
```
{
  "encoding": "br"
}
```
P5
pass
Lazy loading: 5/8 images
P5
pass
Cache-Control set (CDN: Netlify)
Cache-Control: public,max-age=0,must-revalidate CDN detected: Netlify
Evidence
```
{
  "cdn": [
    "Netlify"
  ],
  "cacheControl": "public,max-age=0,must-revalidate"
}
```
P5
pass
Response time: 90ms
Fast first response.
Evidence
```
{
  "bytes": 76075,
  "fetchMs": 90
}
```
P5
pass
Inline JS+CSS bulk: 12 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 12387,
  "inlineCssBytes": 0
}
```
P5
pass
No render-blocking head scripts
All head scripts use async or defer.
P5

pass

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

Reasonable request count.

Evidence

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

pass
Page size: 74 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 76075
}
```
P5

8. Security

warn
Content-Security-Policy missing
Define a CSP to limit script sources — large reduction in XSS surface.
P3
pass
Permissions-Policy set
camera=(), microphone=(), geolocation=(), payment=()
Evidence
```
{
  "value": "camera=(), microphone=(), geolocation=(), payment=()"
}
```
P5
pass
Referrer-Policy set
strict-origin-when-cross-origin
Evidence
```
{
  "value": "strict-origin-when-cross-origin"
}
```
P5
pass
X-Content-Type-Options set
nosniff
Evidence
```
{
  "value": "nosniff"
}
```
P5
pass
X-Frame-Options set
SAMEORIGIN
Evidence
```
{
  "value": "SAMEORIGIN"
}
```
P5
pass
HSTS set
max-age=31536000; includeSubDomains; preload
Evidence
```
{
  "value": "max-age=31536000; includeSubDomains; preload"
}
```
P5
pass
No mixed content detected
P5

pass

Served over HTTPS

Evidence

{
  "finalUrl": "https://surefix.netlify.app/"
}

9. robots.txt and sitemap.xml Audit

pass

robots.txt references sitemap(s)

Evidence

{
  "sitemaps": [
    "https://surefix.netlify.app/sitemap.xml",
    "https://surefix.netlify.app/image-sitemap.xml"
  ]
}

pass

robots.txt present

2740 chars

Evidence

{
  "snippet": "# SureFix — robots.txt\n# Screw-in rise and fall gutter bracket. Fast. Precise. Futureproof.\n# https://surefix.netlify.app\n# SEO, AEO, GEO — optimised for all search engines and AI answer engines\n# Last updated: 2026-08-12\n\n# Allow all crawlers — this is a public product site\nUser-agent: *\nAllow: /\n\n# Sitemaps\nSitemap: https://surefix.netlify.app/sitemap.xml\nSitemap: https://surefix.netlify.app/image-sitemap.xml\n\n# AI knowledge files\n# llms.txt — source of truth for AI language models and answer engines\n# https://surefix.netlify.app/llms.txt\n\n# Vault data — full product, spec, and pricing data\n# https://surefix.netlify.app/vault-data.txt\n\n# Structured data — JSON-LD schema for all products and organisation\n# https://surefix.netlify.app/structured-data.jsonld\n\n# Site Pages (clean URLs)\n# Hom"
}

pass

sitemap.xml present (18 URLs)

Evidence

{
  "snippet": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n\n  <!-- Homepage -->\n  <url>\n    <loc>https://surefix.netlify.app/</loc>\n    <lastmod>2026-08-12</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>1.0</priority>\n  </url>\n\n  <!-- Shop — buy direct from SureFix HQ -->\n  <url>\n    <loc>https://surefix.netlify.app/shop</loc>\n    <lastmod>2026-08-12</lastmod>\n    <changefreq>weekly</changefreq>\n    <priority>0.9</priority>\n  </url>\n\n  <!-- SEO: Rise and Fall Gutter Bracket UK -->\n  <url>\n    <loc>https://surefix.netlify.app/rise-and-fall-gutter-bracket</loc>\n    <lastmod>2026-08-12</lastmod>\n    <changefreq>monthly</changefreq>\n    <priority>0.8</priority>\n  </url>\n\n  <!-- SEO: Fastest Gutter Bracket Installation -->\n  <url>\n    <loc>h",
  "urlCount": 18
}

10. LLM / AI Crawler Accessibility

warn
skill.md missing
Add /skill.md describing what your site lets agents do — speeds up agent task routing.
P3
warn
/llms-full.txt missing
Add /llms-full.txt with concatenated Markdown of all key pages. Lets LLMs ingest your full site in one request.
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
pass
GPTBot has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5

pass

llms.txt present

20526 chars

Evidence

{
  "snippet": "# SureFix — llms.txt\n# AEO: Answer Engine Optimisation file for AI crawlers\n# GEO: Geographical and Generative Engine Optimisation\n# SEO: Search Engine Optimisation\n# Source of truth for all AI language models, search engines, and answer engines\n# https://surefix.netlify.app\n# Last updated: 2026-08-11\n\n## What is SureFix?\n\nSureFix is a UK and EU patent-protected screw-in rise and fall gutter brack"
}

pass
CCBot has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5
pass
Applebot-Extended has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5
pass
OAI-SearchBot has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5
pass
Google-Extended has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5
pass
PerplexityBot has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5
pass
ClaudeBot has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5

11. Generative Engine Optimization (GEO)

warn
Organization schema has no knowledge graph sameAs links
Add `sameAs` pointing to Wikipedia, Wikidata, LinkedIn, or Crunchbase. AI systems use these links to resolve your brand name as a known entity rather than an ambiguous string.
Evidence
```
{
  "existingSameAs": [
    "https://www.facebook.com/profile.php?id=61570688158148",
    "https://www.instagram.com/surefixltd/"
  ]
}
```
P2
warn
No AI agent integration files found
Add at least one: /.well-known/ai-plugin.json (ChatGPT plugin discovery), /.well-known/agent-card.json (A2A protocol), or /skill.md (Claude tool integration). These let AI agents interact with your site programmatically and signal that your site is AI-native.
P2
warn
No outbound links to authoritative sources on the homepage
Generative AI systems cite pages that themselves cite credible sources. Link to Wikipedia, .gov, .edu, peer-reviewed research, or major news outlets to signal epistemic trustworthiness.
P3
warn
No llms-full.txt found
llms-full.txt is an extended version of llms.txt that embeds the full text of every listed resource. Large-context models and RAG pipelines can ingest your entire site in one request — greatly improving citation coverage.
P3

pass

llms.txt present with meaningful content

30 section(s), 31 linked resource(s), 3060 words.

Evidence

{
  "words": 3060,
  "snippet": "# SureFix — llms.txt\n# AEO: Answer Engine Optimisation file for AI crawlers\n# GEO: Geographical and Generative Engine Optimisation\n# SEO: Search Engine Optimisation\n# Source of truth for all AI language models, search engines, and answer engines\n# https://surefix.netlify.app\n# Last updated: 2026-08-11\n\n## What is SureFix?\n\nSureFix is a UK and EU patent-protected screw-in rise and fall gutter brack",
  "headings": 30,
  "urlLines": 31
}

pass
Brand entity declared: "SureFix Ltd"
AI systems can resolve "SureFix Ltd" as a distinct entity. Ensure this name is used consistently in titles, H1s, and social profiles.
Evidence
```
{
  "schemaName": "SureFix Ltd"
}
```
P5

12. Positioning Clarity

warn
No pricing/plans link found
AI summaries commonly include pricing. Add a /pricing page even if pricing is custom.
P2
warn
Value-prop language not detected
Pages with phrases like 'we help X', 'platform for Y', 'built for Z' are easier for LLMs to summarize.
P3
pass
About/Team path discoverable
P5
pass
H1 communicates value
SCREWTHE OLDWAY.
P5
pass
Contact / signup path discoverable
P5

13. Foundations

warn
No theme-color meta tag
Add <meta name="theme-color" content="#yourcolor"> to tint the browser chrome on mobile.
P4
warn
No feed announced
Add <link rel="alternate" type="application/rss+xml" href="/feed.xml"> so agents and readers can subscribe.
P4
pass
Meta viewport present
content="width=device-width, initial-scale=1.0"
Evidence
```
{
  "content": "width=device-width, initial-scale=1.0"
}
```
P5
pass
<!doctype html> declared
P5

14. Accessibility

warn
Missing landmark(s): <header>
Semantic landmarks help screen readers and AI agents navigate page structure.
Evidence
```
{
  "nav": 1,
  "main": 1,
  "footer": 1,
  "header": 0
}
```
P3
warn
No skip navigation link found
Add a visible-on-focus skip link as the first focusable element: <a href="#main">Skip to main content</a>.
P3
pass
Form label coverage: 100% (3/3)
P5

15. Well-Known URIs

warn
No HTTP Link header
Add a Link response header to advertise sitemap, llms.txt, and api-catalog to crawlers without requiring HTML parsing.
P4
warn
/.well-known/change-password missing
Redirect /.well-known/change-password to your password-change page so password managers can deep-link directly.
P4
warn
/.well-known/api-catalog missing
Publish a /.well-known/api-catalog (RFC 9727 Linkset) so agents can discover your API endpoints automatically.
P4
warn
/.well-known/agent-card.json missing
Publish an agent card at /.well-known/agent-card.json to enable agent-to-agent (A2A) discovery.
P4

16. Privacy

pass
Privacy policy link found
#
Evidence
```
{
  "href": "#"
}
```
P5
pass
No third-party scripts detected
P5

17. Resilience

warn
No Web App Manifest found
Add <link rel="manifest" href="/manifest.json"> and a manifest.json with name, icons, start_url, and display.
P4

18. Website Specification

No findings.

19. Missing or Hard-to-Find Information

fail
9 data point(s) could not be found from public pages
· Pricing · Customer logos · Social proof · Recent launches · Blog post activity · New hires · Positioning · Executive team · Case studies or testimonials
Evidence
```
{
  "missing": [
    "Pricing",
    "Customer logos",
    "Social proof",
    "Recent launches",
    "Blog post activity",
    "New hires",
    "Positioning",
    "Executive team",
    "Case studies or testimonials"
  ]
}
```
P1

20. Recommended Fixes

warn
Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "for": "positioning.pricing"
}
```
P2
warn
Add an AI agent integration file
At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API: ```markdown # Your Brand Skill API endpoint: https://yoursite.com/api Auth: Bearer token ## Tools - search: Search the knowledge base - get_article: Retrieve a full article by ID ``` Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
Evidence
```
{
  "for": "geo.agent_integration"
}
```
P2
warn
Add sameAs knowledge graph links to Organization schema
Extend your Organization JSON-LD to include `sameAs` pointing to authoritative directories: ```json { "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://yoursite.com", "sameAs": [ "https://en.wikipedia.org/wiki/Your_Brand", "https://www.wikidata.org/wiki/Q12345678", "https://www.linkedin.com/company/your-brand", "https://www.crunchbase.com/organization/your-brand" ] } ``` These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.
Evidence
```
{
  "for": "geo.knowledge_graph"
}
```
P2
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
Add BreadcrumbList JSON-LD
Helps AI engines understand site hierarchy and improves citation context.
Evidence
```
{
  "for": "schema.breadcrumb"
}
```
P3
warn
Add Article / BlogPosting JSON-LD
On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
Evidence
```
{
  "for": "schema.article"
}
```
P3
warn
Add FAQPage JSON-LD
Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
Evidence
```
{
  "for": "schema.faq"
}
```
P3
warn
Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "for": "schema.product"
}
```
P3
warn
State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "for": "positioning.audience"
}
```
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
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
Fix broken homepage links
We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
Evidence
```
{
  "for": "links.broken_sample"
}
```
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
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
Add outbound links to authoritative sources
Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood. Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
Evidence
```
{
  "for": "geo.citation_signals"
}
```
P3
warn
Generate /llms-full.txt for RAG pipelines
llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root: ``` # Your Brand — Full Content ## Getting Started <full markdown content of /docs/start> ## API Reference <full markdown content of /docs/api> ``` Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.
Evidence
```
{
  "for": "geo.llms_full_txt"
}
```
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
Use srcset/sizes for responsive images
Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
Evidence
```
{
  "for": "images.srcset"
}
```
P4
warn
Add LocalBusiness JSON-LD (if you have a physical location)
Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
Evidence
```
{
  "for": "schema.local_business"
}
```
P4
warn
Add Person JSON-LD for authors / founders
Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
Evidence
```
{
  "for": "schema.person"
}
```
P4
warn
Add HowTo JSON-LD for step-by-step content
For any 'how to' page, wrap the steps in HowTo JSON-LD. AI step-by-step answers cite these heavily.
Evidence
```
{
  "for": "schema.howto"
}
```
P4

21. Priority To-Do List

warn
[ ] Add an AI agent integration file
At minimum, add a skill.md at /skill.md so Claude and similar agents can discover your API: ```markdown # Your Brand Skill API endpoint: https://yoursite.com/api Auth: Bearer token ## Tools - search: Search the knowledge base - get_article: Retrieve a full article by ID ``` Also consider /.well-known/ai-plugin.json (ChatGPT plugin discovery) and /.well-known/agent-card.json (Google A2A protocol) for broader agent compatibility.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add sameAs knowledge graph links to Organization schema
Extend your Organization JSON-LD to include `sameAs` pointing to authoritative directories: ```json { "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://yoursite.com", "sameAs": [ "https://en.wikipedia.org/wiki/Your_Brand", "https://www.wikidata.org/wiki/Q12345678", "https://www.linkedin.com/company/your-brand", "https://www.crunchbase.com/organization/your-brand" ] } ``` These links anchor your brand as a known entity in AI knowledge graphs, making it far more likely that generative models cite you by name rather than paraphrase.
Evidence
```
{
  "priority": 2
}
```
P2
warn
[ ] Add a /pricing page
Even contact-us pricing benefits from a /pricing page that LLMs can link to in answers.
Evidence
```
{
  "priority": 2
}
```
P2
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
[ ] 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
[ ] Fix broken homepage links
We HEAD-probed the first 20 unique homepage links and found 4xx/5xx responses. Repair or remove them — broken links erode crawler trust.
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
[ ] 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
[ ] Add outbound links to authoritative sources
Link to Wikipedia, .gov or .edu resources, peer-reviewed studies, or major news outlets when making factual claims. Generative AI systems treat pages that cite authoritative sources as more trustworthy, which raises citation likelihood. Examples: statistics from Statista or Census.gov, definitions from Wikipedia, research from nature.com or pubmed.ncbi.nlm.nih.gov.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Generate /llms-full.txt for RAG pipelines
llms-full.txt is a concatenation of the full markdown text of every resource listed in llms.txt. Generate it statically at build time and serve it from your root: ``` # Your Brand — Full Content ## Getting Started <full markdown content of /docs/start> ## API Reference <full markdown content of /docs/api> ``` Large-context models can ingest your entire knowledge base in a single request, dramatically improving recall and citation accuracy.
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
[ ] Define a Content-Security-Policy
Start with `Content-Security-Policy-Report-Only` to learn safe sources, then enforce. Cuts XSS blast radius.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add BreadcrumbList JSON-LD
Helps AI engines understand site hierarchy and improves citation context.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add Article / BlogPosting JSON-LD
On every blog/article page, include Article JSON-LD with headline, author, datePublished, dateModified. AI engines weight these heavily for freshness and authority.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add FAQPage JSON-LD
Wrap your homepage FAQ in FAQPage JSON-LD; it routinely lifts AI answer inclusion.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] State your audience explicitly
Use phrases like 'Built for B2B SaaS marketing teams' on the homepage and About page.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Use srcset/sizes for responsive images
Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
Evidence
```
{
  "priority": 4
}
```
P4
warn
[ ] Add LocalBusiness JSON-LD (if you have a physical location)
Include address, geo, openingHours, telephone. Required for AI engines to surface you in 'near me' queries.
Evidence
```
{
  "priority": 4
}
```
P4
warn
[ ] Add Person JSON-LD for authors / founders
Mark up bylines and founder bios with Person schema — name, jobTitle, sameAs (their profiles). Strengthens E-E-A-T.
Evidence
```
{
  "priority": 4
}
```
P4

AEO Audit for surefix.netlify.app

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

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. Generative Engine Optimization (GEO)

12. Positioning Clarity

13. Foundations

14. Accessibility

15. Well-Known URIs

16. Privacy

17. Resilience

18. Website Specification

19. Missing or Hard-to-Find Information

20. Recommended Fixes

21. Priority To-Do List

Track this site week over week

Your charts, not these.

Email yourself this report

Watch this URL