Public share link

AEO Audit for summitandstoneproperties.com

Target: https://summitandstoneproperties.com/
Score: 59 / 100
Generated: 2026-09-03T00:38:43.498Z
Pages crawled: 9
Findings: 66 pass · 92 warn · 0 fail · 0 unknown

1. Crawl Summary

✅ Fetched 9 of 9 pages successfully Target: https://summitandstoneproperties.com

2. Data Found

Data Point	Found?	Source	Notes
Pricing	No	—	—
Customer logos	No	—	—
Social proof	No	—	—
Recent launches	Yes	Press/news pages	https://summitandstoneproperties.com/blog
Blog post activity	Yes	Blog	https://summitandstoneproperties.com/blog
New hires	No	—	Often only on a /blog/team or LinkedIn page
Headline copy	Yes	Homepage	Find Your Dream Home in Zambia
Positioning	No	—	—
Executive team	Yes	About/team page	https://summitandstoneproperties.com/about
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	Yes	Navigation links	testimonial
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

✅ Homepage fetched successfully HTTP 200 · 154514 bytes · 145ms
✅ Page load time: 0.14s Fast — well within AI crawler budgets.
✅ declared
✅ Single H1 Find Your Dream Home in Zambia
✅ <title> present (68 chars)
✅ Meta description present (146 chars)
✅ Canonical present https://summitandstoneproperties.com/
✅ Open Graph tags complete
✅ Twitter Card tags complete
✅ Critical content is server-rendered Raw and rendered text are within 25% of each other.
✅ Alt text coverage: 100% 12/12 images have alt text.
✅ Content volume: 2057 words Substantive content — AI models have enough to summarize and recommend.
✅ Heading structure: 19 (h1:1, h2:6, h3:12) Multiple headings help AI chunk and outline your page.
✅ Internal links: 196 196 internal + 15 external links help crawlers navigate.
✅ Robots meta: "index, follow"
✅ Favicon declared

4. Content Quality

⚠️ 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.
⚠️ Text-to-HTML ratio: 9.2% Low text density — most of the response is markup/script.
⚠️ No author byline found Add <meta name="author" content="Name"> or a visible byline with rel="author". Strengthens E-E-A-T signals.
✅ Heading levels are well-ordered 23 headings nested in order.
✅ Snippet-ready blocks: 3 (ul:3, ol:0, table:0) Lists and tables are extracted verbatim by AI answer engines.
✅ Date signal present time[datetime]: 3

5. Schema / Structured Data Audit

⚠️ SoftwareApplication missing Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
⚠️ 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.
⚠️ Product / Offer JSON-LD not found Add Product / Offer 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.
⚠️ VideoObject JSON-LD not found Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
✅ 5 JSON-LD block(s) found Types: WebSite, Organization+RealEstateAgent, FAQPage, RealEstateAgent+LocalBusiness, Organization
✅ Organization present
✅ WebSite present
✅ FAQPage JSON-LD present
✅ LocalBusiness JSON-LD present

6. Links & Images

⚠️ Modern image formats: 0% (0/12 webp/avif) 7 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
⚠️ Explicit dimensions: 42% (5/12) Add width and height attributes on tags to prevent CLS.
⚠️ Responsive srcset: 0/12 Use srcset/sizes to serve appropriately-sized images on mobile. Reduces wasted bytes.
⚠️ External nofollow: 73% (11/15) Most external links are nofollow. Verify this matches your link policy.
✅ Lazy loading: 67% (8/12) Most below-the-fold images defer load — good for perf and crawl budgets.
✅ No broken links in first 20 HEAD-probed the first 20 unique homepage links — all 2xx/3xx.

7. Performance

⚠️ 1 render-blocking script(s) in Move non-critical scripts to end of or add defer/async.
⚠️ No Cache-Control header Add a Cache-Control header so CDNs and AI crawlers can revalidate efficiently.
✅ Page size: 151 KB Compact HTML payload — well within AI crawler limits.
✅ Resource requests: 15 (scripts:1, css:2, img:12) Reasonable request count.
✅ Inline JS+CSS bulk: 15 KB Inline payload is modest.
✅ Response time: 145ms Fast first response.
✅ Compression enabled (Brotli) Content-Encoding: br
✅ Lazy loading: 8/12 images

8. Security

⚠️ HSTS missing Add Strict-Transport-Security: max-age=31536000; includeSubDomains once you're confident in https.
✅ Served over HTTPS
✅ No mixed content detected
✅ Content-Security-Policy set default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://analytics.ahrefs.com http…
✅ 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=(), usb=()

9. robots.txt and sitemap.xml Audit

✅ robots.txt present 1121 chars
✅ robots.txt references sitemap(s)
✅ sitemap.xml present (184 URLs)

10. LLM / AI Crawler Accessibility

⚠️ Google-Extended not explicitly addressed No User-agent: Google-Extended 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.
⚠️ CCBot not explicitly addressed No User-agent: CCBot 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.
⚠️ /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.
✅ llms.txt present 5557 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 Find Your Dream Home in Zambia
✅ Contact / signup path discoverable

12. Missing or Hard-to-Find Information

⚠️ 5 data point(s) could not be found from public pages · Pricing · Customer logos · Social proof · New hires · Positioning

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.
⚠️ 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.
⚠️ Raise your text-to-HTML ratio Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
⚠️ 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.
⚠️ Allow Google-Extended in robots.txt Add an explicit User-agent: Google-Extended 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.
⚠️ Allow CCBot in robots.txt Add an explicit User-agent: CCBot 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
```
⚠️ Eliminate render-blocking head scripts Add defer or async to any <script src="…"> in <head>, or move it to the end of <body>.
⚠️ Set a Cache-Control header Add Cache-Control: public, max-age=300, s-maxage=3600 (or similar) so CDNs and AI crawlers can revalidate cheaply.
⚠️ 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 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.
⚠️ Add Product / SoftwareApplication JSON-LD On /pricing and feature pages — include offers, name, applicationCategory.
⚠️ Enable HSTS Add Strict-Transport-Security: max-age=31536000; includeSubDomains once you're confident every subdomain is https-ready.
⚠️ 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.
⚠️ Use srcset/sizes for responsive images Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
⚠️ Review nofollow usage on outbound links Nearly-all-nofollow can read as a link-spam pattern. Use nofollow only for paid/UGC links per Google's guidance.
⚠️ 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.
⚠️ Add VideoObject JSON-LD For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.

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 — 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.
P3 — Raise your text-to-HTML ratio Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.

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 — Allow Google-Extended in robots.txt Add an explicit User-agent: Google-Extended 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 — Allow CCBot in robots.txt Add an explicit User-agent: CCBot 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 — Eliminate render-blocking head scripts Add defer or async to any <script src="…"> in <head>, or move it to the end of <body>.
P3 — Set a Cache-Control header Add Cache-Control: public, max-age=300, s-maxage=3600 (or similar) so CDNs and AI crawlers can revalidate cheaply.
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 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.

Report by CrawlProof. Reusable after every major website change.

AEO audit

https://summitandstoneproperties.com/

Completed 9/3/2026, 12:38:43 AM

/100

1. Crawl Summary

pass

Fetched 9 of 9 pages successfully

Target: https://summitandstoneproperties.com

Evidence

{
  "pages": [
    {
      "url": "https://summitandstoneproperties.com",
      "bytes": 154514,
      "status": 200,
      "fetchMs": 145
    },
    {
      "url": "https://summitandstoneproperties.com/about",
      "bytes": 112273,
      "status": 200,
      "fetchMs": 59
    },
    {
      "url": "https://summitandstoneproperties.com/blog",
      "bytes": 64680,
      "status": 200,
      "fetchMs": 73
    },
    {
      "url": "https://summitandstoneproperties.com/blog/how-to-evict-a-tenant-zambia",
      "bytes": 12401,
      "status": 200,
      "fetchMs": 40
    },
    {
      "url": "https://summitandstoneproperties.com/blog/security-deposit-zambia",
      "bytes": 12404,
      "status": 200,
      "fetchMs": 39
    },
    {
      "url": "https://summitandstoneproperties.com/blog/lusaka-top-5-neighbourhoods-2025",
      "bytes": 12494,
      "status": 200,
      "fetchMs": 91
    },
    {
      "url": "https://summitandstoneproperties.com/blog/understanding-lease-agreements-in-zambia",
      "bytes": 12441,
      "status": 200,
      "fetchMs": 40
    },
    {
      "url": "https://summitandstoneproperties.com/contact",
      "bytes": 70374,
      "status": 200,
      "fetchMs": 65
    },
    {
      "url": "https://summitandstoneproperties.com/",
      "bytes": 154514,
      "status": 200,
      "fetchMs": 73
    }
  ],
  "origin": "https://summitandstoneproperties.com",
  "target": "https://summitandstoneproperties.com"
}

2. Data Found

Data Point	Found?	Source	Notes
Pricing	No	—	—
Customer logos	No	—	—
Social proof	No	—	—
Recent launches	Yes	Press/news pages	https://summitandstoneproperties.com/blog
Blog post activity	Yes	Blog	https://summitandstoneproperties.com/blog
New hires	No	—	Often only on a /blog/team or LinkedIn page
Headline copy	Yes	Homepage	Find Your Dream Home in Zambia
Positioning	No	—	—
Executive team	Yes	About/team page	https://summitandstoneproperties.com/about
Product/service descriptions	Yes	Homepage	From meta description
Case studies or testimonials	Yes	Navigation links	testimonial
Contact/demo/signup paths	Yes	Navigation links	—

3. Homepage Audit

pass
Internal links: 196
196 internal + 15 external links help crawlers navigate.
Evidence
```
{
  "external": 15,
  "internal": 196
}
```
P5
pass
Robots meta: "index, follow"
Evidence
```
{
  "content": "index, follow"
}
```
P5
pass
Favicon declared
Evidence
```
{
  "href": "/favicon.svg"
}
```
P5
pass
Homepage fetched successfully
HTTP 200 · 154514 bytes · 145ms
Evidence
```
{
  "bytes": 154514,
  "status": 200,
  "fetchMs": 145
}
```
P5
pass
Single H1
Find Your Dream Home in Zambia
Evidence
```
{
  "h1": "Find Your Dream Home in Zambia"
}
```
P5
pass
<html lang="en"> declared
Evidence
```
{
  "lang": "en"
}
```
P5
pass
Page load time: 0.14s
Fast — well within AI crawler budgets.
Evidence
```
{
  "fetchMs": 145
}
```
P5

pass

Open Graph tags complete

Evidence

{
  "image": "https://summitandstoneproperties.com/assets/ss-brand-logo.jpeg",
  "title": "Houses for Sale & Rent in Lusaka, Zambia | Summit & Stone Properties",
  "description": "Find houses for sale and rent in Lusaka, Zambia. Browse verified residential, commercial and investment properties with Summit & Stone Properties."
}

pass
Canonical present
https://summitandstoneproperties.com/
Evidence
```
{
  "canonical": "https://summitandstoneproperties.com/"
}
```
P5

pass

Meta description present (146 chars)

Evidence

{
  "description": "Find houses for sale and rent in Lusaka, Zambia. Browse verified residential, commercial and investment properties with Summit & Stone Properties."
}

pass

`<title>` present (68 chars)

Evidence

{
  "title": "Houses for Sale & Rent in Lusaka, Zambia | Summit & Stone Properties"
}

pass

Twitter Card tags complete

Evidence

{
  "card": "summary_large_image",
  "image": "https://summitandstoneproperties.com/assets/ss-brand-logo.jpeg",
  "title": "Houses for Sale & Rent in Lusaka, Zambia | Summit & Stone Properties",
  "description": "Find houses for sale and rent in Lusaka, Zambia. Browse verified residential, commercial and investment properties with Summit & Stone Properties."
}

pass
Critical content is server-rendered
Raw and rendered text are within 25% of each other.
Evidence
```
{
  "ratio": 0.24977344022307424,
  "rawTextLen": 28690,
  "renderedTextLen": 7166
}
```
P5
pass
Alt text coverage: 100%
12/12 images have alt text.
P5
pass
Content volume: 2057 words
Substantive content — AI models have enough to summarize and recommend.
Evidence
```
{
  "wordCount": 2057
}
```
P5
pass
Heading structure: 19 (h1:1, h2:6, h3:12)
Multiple headings help AI chunk and outline your page.
Evidence
```
{
  "h1": 1,
  "h2": 6,
  "h3": 12
}
```
P5

4. Content Quality

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
Text-to-HTML ratio: 9.2%
Low text density — most of the response is markup/script.
Evidence
```
{
  "ratio": 0.09151627943169512,
  "htmlBytes": 154213,
  "textChars": 14113
}
```
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

Heading levels are well-ordered

23 headings nested in order.

Evidence

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

pass
Snippet-ready blocks: 3 (ul:3, ol:0, table:0)
Lists and tables are extracted verbatim by AI answer engines.
Evidence
```
{
  "ol": 0,
  "ul": 3,
  "tables": 0
}
```
P5
pass
Date signal present
time[datetime]: 3
P5

5. Schema / Structured Data Audit

warn
SoftwareApplication missing
Adding SoftwareApplication JSON-LD helps LLMs identify your entity.
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
Product / Offer JSON-LD not found
Add Product / Offer where applicable so AI answer engines can resolve the entity precisely.
P3
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
warn
VideoObject JSON-LD not found
Add VideoObject where applicable so AI answer engines can resolve the entity precisely.
P4

pass

5 JSON-LD block(s) found

Types: WebSite, Organization+RealEstateAgent, FAQPage, RealEstateAgent+LocalBusiness, Organization

Evidence

{
  "types": [
    "WebSite",
    "Organization+RealEstateAgent",
    "FAQPage",
    "RealEstateAgent+LocalBusiness",
    "Organization"
  ],
  "blocks": 5
}

pass
Organization present
P5
pass
LocalBusiness JSON-LD present
P5
pass
FAQPage JSON-LD present
P5
pass
WebSite present
P5

6. Links & Images

warn
Modern image formats: 0% (0/12 webp/avif)
7 legacy (png/jpg/gif) image(s). Convert hero/above-the-fold images to WebP or AVIF.
Evidence
```
{
  "total": 12,
  "legacy": 7,
  "modern": 0
}
```
P3
warn
Explicit dimensions: 42% (5/12)
Add width and height attributes on <img> tags to prevent CLS.
Evidence
```
{
  "total": 12,
  "withDims": 5
}
```
P3
warn
Responsive srcset: 0/12
Use srcset/sizes to serve appropriately-sized images on mobile. Reduces wasted bytes.
P4
warn
External nofollow: 73% (11/15)
Most external links are nofollow. Verify this matches your link policy.
P4
pass
Lazy loading: 67% (8/12)
Most below-the-fold images defer load — good for perf and crawl budgets.
Evidence
```
{
  "lazy": 8,
  "total": 12
}
```
P5
pass
No broken links in first 20
HEAD-probed the first 20 unique homepage links — all 2xx/3xx.
Evidence
```
{
  "broken": 0,
  "sampled": 20,
  "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
warn
No Cache-Control header
Add a Cache-Control header so CDNs and AI crawlers can revalidate efficiently.
Evidence
```
{
  "cdn": [
    "Cloudflare"
  ]
}
```
P3
pass
Page size: 151 KB
Compact HTML payload — well within AI crawler limits.
Evidence
```
{
  "bytes": 154514
}
```
P5

pass

Resource requests: 15 (scripts:1, css:2, img:12)

Reasonable request count.

Evidence

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

pass
Inline JS+CSS bulk: 15 KB
Inline payload is modest.
Evidence
```
{
  "inlineJsBytes": 8539,
  "inlineCssBytes": 6696
}
```
P5
pass
Response time: 145ms
Fast first response.
Evidence
```
{
  "bytes": 154514,
  "fetchMs": 145
}
```
P5
pass
Compression enabled (Brotli)
Content-Encoding: br
Evidence
```
{
  "encoding": "br"
}
```
P5
pass
Lazy loading: 8/12 images
P5

8. Security

warn
HSTS missing
Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you're confident in https.
P3

pass

Served over HTTPS

Evidence

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

pass
No mixed content detected
P5

pass

Content-Security-Policy set

default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://analytics.ahrefs.com http…

Evidence

{
  "value": "default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://analytics.ahrefs.com https://www.google.com https://www.gstatic.com https://unpkg.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: https://res.cloudinary.com https://img.youtube.com https://upload.wikimedia.org https://static.wixstatic.com https://*.basemaps.cartocdn.com https://www.google.com https://www.googletagmanager.com; font-src 'self' https://fonts.gstatic.com data:; media-src 'self' https://res.cloudinary.com; connect-src 'self' https://api.cloudinary.com https://analytics.ahrefs.com https://www.google-analytics.com https://*.google-analytics.com https://www.googletagmanager.com; frame-src 'self' https://maps.google.com https://www.google.com https://www.googletagmanager.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self';"
}

pass
X-Frame-Options set
SAMEORIGIN
Evidence
```
{
  "value": "SAMEORIGIN"
}
```
P5
pass
X-Content-Type-Options set
nosniff
Evidence
```
{
  "value": "nosniff"
}
```
P5
pass
Referrer-Policy set
strict-origin-when-cross-origin
Evidence
```
{
  "value": "strict-origin-when-cross-origin"
}
```
P5
pass
Permissions-Policy set
camera=(), microphone=(), geolocation=(), payment=(), usb=()
Evidence
```
{
  "value": "camera=(), microphone=(), geolocation=(), payment=(), usb=()"
}
```
P5

9. robots.txt and sitemap.xml Audit

pass

robots.txt present

1121 chars

Evidence

{
  "snippet": "User-agent: *\nDisallow: /admin\nDisallow: /api/\nAllow: /\n\n# Crawlers\n# Each named bot below gets its own Disallow rules explicitly — per the\n# robots.txt spec, a crawler that matches a specific named group ignores the\n# wildcard \"*\" group entirely (groups are matched by specificity, not\n# merged). Without repeating Disallow: /admin and /api/ here, every bot named\n# below — including Googlebot — would have no restriction on those paths at\n# all, silently undoing the wildcard group's protection for exactly the\n# crawlers that matter most.\nUser-agent: AhrefsBot\nDisallow: /admin\nDisallow: /api/\nAllow: /\n\nUser-agent: SemrushBot\nDisallow: /admin\nDisallow: /api/\nAllow: /\n\nUser-agent: Googlebot\nDisallow: /admin\nDisallow: /api/\nAllow: /\n\nUser-agent: Bingbot\nDisallow: /admin\nDisallow: /api/\nAllow: /\n"
}

pass

robots.txt references sitemap(s)

Evidence

{
  "sitemaps": [
    "https://summitandstoneproperties.com/sitemap.xml"
  ]
}

pass

sitemap.xml present (184 URLs)

Evidence

{
  "snippet": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<urlset xmlns=\"http://www.sitemaps.org/schemas/sitemap/0.9\">\n  <url>\n    <loc>https://summitandstoneproperties.com/</loc>\n    <changefreq>daily</changefreq>\n    <priority>1.0</priority>\n  </url>\n  <url>\n    <loc>https://summitandstoneproperties.com/residential-sale</loc>\n    <changefreq>daily</changefreq>\n    <priority>0.9</priority>\n  </url>\n  <url>\n    <loc>https://summitandstoneproperties.com/residential-rent</loc>\n    <changefreq>daily</changefreq>\n    <priority>0.9</priority>\n  </url>\n  <url>\n    <loc>https://summitandstoneproperties.com/commercial-sale</loc>\n    <changefreq>weekly</changefreq>\n    <priority>0.8</priority>\n  </url>\n  <url>\n    <loc>https://summitandstoneproperties.com/commercial-rent</loc>\n    <changefreq>weekly</changefreq>\n    ",
  "urlCount": 184
}

10. LLM / AI Crawler Accessibility

warn
Google-Extended not explicitly addressed
No User-agent: Google-Extended block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
warn
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.
P3
warn
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.
P3
warn
CCBot not explicitly addressed
No User-agent: CCBot block in robots.txt. We recommend explicit Allow rules so crawlers don't fall back to defaults.
P3
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
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
pass
GPTBot 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
pass
PerplexityBot has explicit rules
An explicit User-agent block exists. Make sure it allows the paths you want indexed.
P5

pass

llms.txt present

5557 chars

Evidence

{
  "snippet": "# Summit & Stone Properties — Zambia Real Estate Platform\n\n## About\nSummit & Stone Properties is a licensed Zambian real estate agency and property listing platform. We connect buyers, renters, and investors with verified residential and commercial properties across Zambia, primarily in Lusaka. We list properties in both USD and Zambian Kwacha (ZMW).\n\n## Services\n- Residential property sales — ho"
}

11. Generative Engine Optimization (GEO)

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
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": []
}
```
P2
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
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

pass

llms.txt present with meaningful content

9 section(s), 33 linked resource(s), 635 words.

Evidence

{
  "words": 635,
  "snippet": "# Summit & Stone Properties — Zambia Real Estate Platform\n\n## About\nSummit & Stone Properties is a licensed Zambian real estate agency and property listing platform. We connect buyers, renters, and investors with verified residential and commercial properties across Zambia, primarily in Lusaka. We list properties in both USD and Zambian Kwacha (ZMW).\n\n## Services\n- Residential property sales — ho",
  "headings": 9,
  "urlLines": 33
}

pass
Brand entity declared: "Summit & Stone Properties"
AI systems can resolve "Summit & Stone Properties" as a distinct entity. Ensure this name is used consistently in titles, H1s, and social profiles.
Evidence
```
{
  "schemaName": "Summit & Stone Properties"
}
```
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
H1 communicates value
Find Your Dream Home in Zambia
P5
pass
About/Team path discoverable
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
<!doctype html> declared
P5
pass
Meta viewport present
content="width=device-width,initial-scale=1"
Evidence
```
{
  "content": "width=device-width,initial-scale=1"
}
```
P5

14. Accessibility

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
All semantic landmarks present (header/nav/main/footer)
Evidence
```
{
  "nav": 3,
  "main": 1,
  "footer": 1,
  "header": 1
}
```
P5
pass
Form label coverage: 100% (1/1)
P5

15. Well-Known URIs

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
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
pass
/.well-known/change-password present
HTTP 200
P5
pass
/.well-known/api-catalog present
HTTP 200
P5

16. Privacy

warn
No privacy policy link found
Add a visible link to your privacy policy. Required by GDPR, CCPA, and expected by AI agents assessing trustworthiness.
P2
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

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

20. Recommended Fixes

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
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
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
Raise your text-to-HTML ratio
Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
Evidence
```
{
  "for": "content.text_ratio"
}
```
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
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
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
Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "for": "images.dimensions"
}
```
P3
warn
Allow Google-Extended in robots.txt
Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Google-Extended"
}
```
P3
warn
Allow OAI-SearchBot in robots.txt
Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.OAI-SearchBot"
}
```
P3
warn
Allow Applebot-Extended in robots.txt
Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.Applebot-Extended"
}
```
P3
warn
Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "for": "aibot.CCBot"
}
```
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
Set a Cache-Control header
Add `Cache-Control: public, max-age=300, s-maxage=3600` (or similar) so CDNs and AI crawlers can revalidate cheaply.
Evidence
```
{
  "for": "perf.caching"
}
```
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
Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "for": "schema.product"
}
```
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 BreadcrumbList JSON-LD
Helps AI engines understand site hierarchy and improves citation context.
Evidence
```
{
  "for": "schema.breadcrumb"
}
```
P3
warn
Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "for": "schema.product"
}
```
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
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
Use srcset/sizes for responsive images
Serve appropriately-sized images per viewport — saves bytes on mobile crawls.
Evidence
```
{
  "for": "images.srcset"
}
```
P4
warn
Review nofollow usage on outbound links
Nearly-all-nofollow can read as a link-spam pattern. Use nofollow only for paid/UGC links per Google's guidance.
Evidence
```
{
  "for": "links.nofollow_ratio"
}
```
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
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
Add VideoObject JSON-LD
For embedded videos, include VideoObject with thumbnailUrl, uploadDate, duration. AI engines cite these in multimedia answers.
Evidence
```
{
  "for": "schema.video"
}
```
P4

21. Priority To-Do List

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
[ ] 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 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
[ ] 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
[ ] Raise your text-to-HTML ratio
Strip unused inline scripts/styles and move large bundles to external files. AI crawlers struggle when most of the response is markup.
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
[ ] 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
[ ] 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
[ ] Set width/height on images
Explicit dimensions prevent Cumulative Layout Shift and help AI extractors reserve space correctly.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow Google-Extended in robots.txt
Add an explicit User-agent: Google-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow OAI-SearchBot in robots.txt
Add an explicit User-agent: OAI-SearchBot Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow Applebot-Extended in robots.txt
Add an explicit User-agent: Applebot-Extended Allow: / block so this AI crawler can read your site.
Evidence
```
{
  "priority": 3
}
```
P3
warn
[ ] Allow CCBot in robots.txt
Add an explicit User-agent: CCBot Allow: / block so this AI crawler can read your site.
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
[ ] Set a Cache-Control header
Add `Cache-Control: public, max-age=300, s-maxage=3600` (or similar) so CDNs and AI crawlers can revalidate cheaply.
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
[ ] Add Product / SoftwareApplication JSON-LD
On /pricing and feature pages — include offers, name, applicationCategory.
Evidence
```
{
  "priority": 3
}
```
P3

AEO Audit for summitandstoneproperties.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

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