Foglift
amazon.es — Website Report
Scored 55/100 · Scanned with Foglift
D
amazon.es scored 55. One fix would take it to 75.
6 critical14 warnings24 total issues
Quick wins
~192 min total fix time1Missing viewport meta tag~1m
2AI search engines can't read your site~2m
3Missing X-Content-Type-Options header~2m
https://amazon.es/ · 5/15/2026, 1:45:18 PM
Scanned with Foglift · SEO + AI Visibility analysis
AI Action Plan
Website Analysis for https://Amazon.es Your site scores 55/100 overall, but AI engines may be missing you. Your AI Visibility is 55/100 — there's significant room to improve how ChatGPT, Perplexity, and Gemini surface your brand. We found 6 critical issues and 14 warnings. Here's your prioritized action plan:
FIX FIRST (Critical): 1. AI search engines can't read your site — Your site blocks 7 AI crawlers (GPTBot, ChatGPT-User, Claude-Web...). 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. AI engines can't understand your business — Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you. 3. Missing Content Security Policy header — Add a Content-Security-Policy header to prevent XSS and injection attacks. 4. Missing viewport meta tag — No viewport meta tag found. This is essential for mobile responsiveness. 5. Mis
19 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.
AI Visibility
How likely AI assistants like ChatGPT, Perplexity, and Gemini are to cite your brand
55D
100
Brand Mentions
Found 20+ web mentions of "amazon"
54
Domain Authority
PageRank: 4.5/10, 8+ external references
0
Content Freshness
Unable to analyze content freshness: Sitemap not found (404)
31
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 7 AI crawlers (GPTBot, ChatGPT-User, Claude-Web...). 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.
AI engines can't understand your businesscritical~10 min fix
Your site has no structured data — the machine-readable labels that tell AI what your business does, what you offer, and why you're an authority. Without this, AI assistants are much less likely to mention or recommend you.
Quick Fix
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company Name",
"url": "https://yoursite.com",
"description": "Brief description of your business",
"sameAs": [
"https://twitter.com/yourhandle",
"https://linkedin.com/company/yourcompany"
]
}
</script>Add JSON-LD structured data so AI models understand your business entity and can cite you accurately.
No FAQ section foundwarning~15 min fix
AI assistants love Q&A content — it's the easiest format for them to extract and quote. Add a Frequently Asked Questions section to your page, and you'll significantly increase your chances of being cited in AI-generated answers.
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>AI models frequently cite FAQ content. Add FAQPage schema to boost your chances of appearing in AI-generated answers.
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 Amazon?
When users ask AI about your industry, are you recommended?
G
C
P
Ge
A
See how ChatGPT, Claude, Perplexity, and Gemini talk about Amazon
SEO & Technical Issues (20)
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.
Missing viewport meta tagcriticalSEO~1 min fix
No viewport meta tag found. This is essential for mobile responsiveness.
Quick Fix
<meta name="viewport" content="width=device-width, initial-scale=1">Without a viewport meta tag, mobile devices render your page at desktop width. This is critical for mobile SEO.
Missing H1 headingcriticalSEO~3 min fix
Every page should have exactly one H1 heading that describes the main topic. This is important for SEO and accessibility.
Quick Fix
<h1>Your Main Page Heading</h1>
<!-- Only use one H1 per page. Make it descriptive and include your target keyword. -->Every page needs exactly one H1 that describes the main topic. It's a key SEO signal.
6 images missing alt textcriticalSEO
Found 6 of 161 images without alt attributes. Alt text is critical for accessibility (screen readers) and SEO (image search).
Missing X-Content-Type-Options headerwarningSecurity~2 min fix
Set X-Content-Type-Options: nosniff to prevent MIME-type sniffing.
Quick Fix
# Nginx:
add_header X-Content-Type-Options "nosniff" always;
# Next.js (next.config.js headers):
{ key: 'X-Content-Type-Options', value: 'nosniff' }Prevents browsers from MIME-type sniffing, which can lead to security vulnerabilities.
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 82 characters. Keep it under 60 for best display in search results.
Missing Open Graph tagswarningSEO~10 min fix
Missing og:title, 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.
No sitemap.xml foundwarningSEO~15 min fix
Your site is missing a sitemap.xml file. Sitemaps help search engines discover and index all your pages. Submit one to Google Search Console.
Quick Fix
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://yoursite.com/</loc>
<lastmod>2026-03-15</lastmod>
<priority>1.0</priority>
</url>
<url>
<loc>https://yoursite.com/about</loc>
<lastmod>2026-03-15</lastmod>
<priority>0.8</priority>
</url>
</urlset>A sitemap.xml helps search engines discover and index all your pages. Place it at your site root.
4% of images lack alt textwarningAccessibility
6 of 161 images have no alt attribute. Screen readers cannot describe these images to visually impaired users.
Skipped heading levelwarningAccessibility
Heading hierarchy jumps from H2 to H5. Don't skip heading levels — this confuses screen readers and assistive technology.
Server response could be fasterwarningPerformance
Server responded in 1.2s. Aim for under 200ms TTFB. Consider caching, CDN, or server-side optimizations.
Large HTML documentwarningPerformance
Your HTML is 961KB. Large HTML documents take longer to parse. Consider lazy loading content or splitting into multiple pages.
1 render-blocking scriptwarningPerformance
1 script without async or defer attributes. These block page rendering. Add defer or async to non-critical scripts.
7 external stylesheetswarningPerformance
Loading 7 CSS files. Each blocks rendering. Consider combining stylesheets or inlining critical CSS.
161 images without lazy loadingwarningPerformance
161 images don't use loading="lazy". Add lazy loading to below-the-fold images to improve initial page load.
No structured data foundinfoSEO
Add JSON-LD structured data (Schema.org) to help search engines understand your content and earn rich snippets in search results.
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.
HTML contains many commentsinfoPerformance
Found 70 HTML comments. Remove unnecessary comments in production to reduce file size.
Your Potential Score
55
Now
69
Potential
+14 points possible by fixing 24 issues
That moves you from D to D — above average
Track your AI visibility over time
AI Visibility Monitoring
We check AI prompts weekly across ChatGPT, Perplexity, and Google AI. See how often your brand appears.
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.
Start monitoring — from $49/mo
Free tier available · No credit card required
Industry Benchmark
SEO
Avg: 62-7Behind
AI Readiness
Avg: 35+19Ahead
Performance
Avg: 55+1On par
Security
Avg: 40-5Behind
Accessibility
Avg: 68+6On par
Based on 120+ websites scanned across industries. See full benchmark report →
What This Score Means for You
SEO issues — Your site may be losing 20-40% of potential Google traffic due to missing meta tags, broken structure, or indexing problems.
Not AI-ready — ChatGPT, Perplexity, and Google AI Overviews likely cannot cite your site. You're invisible to the fastest-growing search channel.
Security gaps — Missing security headers may flag your site as unsafe in browsers, hurting trust and conversions.
Slow loading — Sites loading in 3+ seconds lose 53% of mobile visitors (Google data).
Most of these issues have simple, copy-paste fixes. Check the code snippets above for quick solutions.
Security score: 35/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.