Skip to main content

www.sandrews.es — Website Report

Scored 66/100 · Scanned with Foglift

D
OverallOverall Score — weighted average of all category scores

sandrews.es scored 66. Addressing the 16 listed issues could raise its estimated score to 91.

4 critical10 warnings16 total issues

Quick wins

~123 min total fix time
1AI search engines can't read your site~2m
2Missing HSTS header~2m
3Missing Referrer Policy header~2m

https://www.sandrews.es/ · 2026-08-14

Scanned with Foglift · Technical Audit + AI Readiness analysis

AI Action Plan

Website Analysis for https://www.sandrews.es Your site scores 66/100 overall. AI Readiness is 55/100 — there's significant room to improve the technical, content, and authority signals that help AI systems access, understand, and reuse the page. We found 4 critical issues and 10 warnings. Here's your prioritized action plan:

FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.

2. Missing HSTS header — Enable HTTP Strict Transport Security to force HTTPS connections. 3. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 4. 5 render-blocking scripts — 5 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts. QUICK WINS (Warnings): 1. Structured data needs more detail — You have basic structured data, but it's missing the rich types that AI engines

13 more critical fixes + quick wins in your full report

Enter your email and we'll send the complete action plan to your inbox.

No spam. Just your report.

Share This Report

Send this scan to a teammate or contact. The shareable link includes all scores and issues.

Email to Contact

AI Readiness

Technical and authority signals that support AI systems in accessing, understanding, and reusing your content

55D
Technical45
Authority63
Set up all 6 tiers free →
100
Brand Mentions
Found 20+ web mentions of "sandrews"
24
Domain Authority
PageRank: 1.6/10, 3+ external references
77
Content Freshness
119 of 496 pages updated in the last 30 days
45
Technical Readiness
Low technical readiness — missing key AI-friendly markup

Technical Issues

AI search engines can't read your sitecritical~2 min fix

Your site blocks 4 AI crawlers (GPTBot, ClaudeBot, Google-Extended...). This means ChatGPT, Perplexity, and other AI assistants won't recommend your site in their answers. Ask your developer to update the robots.txt file to allow these crawlers.

Quick Fix
# Add to your robots.txt to allow AI crawlers:
User-agent: GPTBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /
Allow AI crawlers to index your content so you appear in ChatGPT, Perplexity, and Google AI Overviews.
Structured data needs more detailwarning

You have basic structured data, but it's missing the rich types that AI engines look for — like FAQ sections, how-to guides, or product info. Adding these helps AI assistants extract and cite your content more accurately.

No FAQ section foundwarning~15 min fix

A clear Frequently Asked Questions section presents important questions and answers in a directly extractable format. Add one when it reflects real customer questions, and keep each answer factual and self-contained.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "What does your company do?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "We provide [your service]. Our solution helps..."
    }
  }]
}
</script>
FAQPage schema labels questions and answers in a machine-readable format, making the page easier for search and AI systems to extract accurately.
AI doesn't know who you areinfo~10 min fix

Your site is missing identity markup that tells AI engines "we are [Company X], and here's what we do." Adding this helps AI assistants recognize your brand as an authority and recommend you by name.

Quick Fix
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://yoursite.com",
  "logo": "https://yoursite.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourhandle",
    "https://linkedin.com/company/yourcompany",
    "https://github.com/yourorg"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@yoursite.com",
    "contactType": "customer service"
  }
}
</script>
Entity markup tells AI models who you are, making them more likely to cite your brand accurately.

How does AI see Sandrews?

When users ask AI about your industry, are you recommended?

G
C
P
Ge
A

Start with weekly Google AI Overview checks for Sandrews. Paid plans add ChatGPT, Perplexity, Gemini, and Claude.

SEO & Technical Issues (12)

Missing HSTS headercriticalSecurity~2 min fix

Enable HTTP Strict Transport Security to force HTTPS connections.

Quick Fix
# Nginx:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

# Apache (.htaccess):
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"

# Next.js (next.config.js headers):
{ key: 'Strict-Transport-Security', value: 'max-age=31536000; includeSubDomains' }
HSTS forces browsers to use HTTPS, preventing downgrade attacks and cookie hijacking.
Missing Content Security Policy headercriticalSecurity~5 min fix

Add a Content-Security-Policy header to prevent XSS and injection attacks.

Quick Fix
# Nginx:
add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';" always;

# Apache (.htaccess):
Header set Content-Security-Policy "default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline';"

# Next.js (next.config.js headers):
{ key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'" }
Content-Security-Policy prevents XSS attacks by controlling which resources the browser can load.
5 render-blocking scriptscriticalPerformance

5 scripts without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.

Missing Referrer Policy headerwarningSecurity~2 min fix

Add a Referrer-Policy header to control information leakage.

Quick Fix
# Nginx:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Next.js (next.config.js headers):
{ key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' }
Controls how much referrer information is sent with requests, protecting user privacy.
Missing Permissions Policy headerwarningSecurity~2 min fix

Add a Permissions-Policy header to control browser feature access.

Quick Fix
# Nginx:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

# Next.js (next.config.js headers):
{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=()' }
Permissions-Policy restricts which browser features your site can use, reducing attack surface.
Title tag too longwarningSEO

Your title is 70 characters. Keep it under 60 for best display in search results.

Missing Open Graph tagswarningSEO~10 min fix

Missing og:image. Add these for better social media sharing previews on Facebook, LinkedIn, and Twitter.

Quick Fix
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://yoursite.com/og-image.jpg">
<meta property="og:url" content="https://yoursite.com/page">
<meta property="og:type" content="website">
Open Graph tags control how your page looks when shared on Facebook, LinkedIn, and other social platforms.
Multiple H1 headings foundwarningSEO

Found 2 H1 headings. Best practice is to have exactly one H1 per page for clear content hierarchy.

1 form input may lack labelswarningAccessibility

Form inputs should have associated labels or aria-label attributes so screen readers can identify them.

Skipped heading levelwarningAccessibility

Heading hierarchy jumps from H1 to H4. Don't skip heading levels — this confuses screen readers and assistive technology.

Large HTML documentwarningPerformance

Your HTML is 228KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.

No skip navigation linkinfoAccessibility~5 min fix

Add a 'Skip to main content' link at the top of the page so keyboard users can bypass repetitive navigation.

Quick Fix
<!-- Add as the first element inside <body> -->
<a href="#main-content" class="sr-only focus:not-sr-only focus:absolute focus:top-2 focus:left-2 focus:z-50 focus:px-4 focus:py-2 focus:bg-blue-600 focus:text-white focus:rounded">
  Skip to main content
</a>

<!-- Add id to your main content area -->
<main id="main-content">
  ...
</main>
Skip links let keyboard users bypass repetitive navigation and jump straight to content.

Your Potential Score

66

Now

91

Estimated potential

+25 points estimated improvement from addressing 16 listed issues

Estimate based on the measured category scores and the issues listed in this audit.

Track your AI visibility over time

AI Visibility Monitoring

Free checks Google AI Overview weekly while you're active. Paid plans add ChatGPT, Perplexity, Gemini, and Claude with daily, twice-daily, or hourly monitoring.

Competitor Tracking

Compare your AI visibility against competitors. Know when they overtake you.

Weekly Digest

Get AI-generated insights emailed every Monday with action items.

Set up Free monitoring

Weekly Google AI Overview while active · No credit card required

Compare paid plans — from $49/mo

Industry Benchmark

SEO
Avg: 62+23Ahead
AI Readiness
Avg: 35+20Ahead
Performance
Avg: 55+15Ahead
Security
Avg: 40-10Behind
Accessibility
Avg: 68+21Ahead

Based on 120+ websites scanned across industries. See full benchmark report →

What This Score Means for You

Readiness gaps — This Technical Audit found barriers that can make your page harder for AI systems to access, understand, or reuse. It does not measure citations, recommendations, or answer-level visibility.

Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.

Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.

Security score: 30/100

Most security issues are 5-minute fixes — adding HTTP headers to your server config. Check the code fixes above for the exact headers to add — we include copy-paste code for Nginx, Apache, Vercel, and Netlify.

AI visibility preview

See which brands Google AI Overview surfaces for your category.

Recent scans on Foglift

Scan your own site free →