SEO report for www.amazon.co.uk
https://www.amazon.co.uk/ · checked Sun, 01 Nov 2026 13:16 GMT
Fix these first
- Title tagcritical
“Amazon.co.uk: Low Prices in Electronics, Books, Sports Equipment & more”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- Mobile viewportcritical
No viewport meta tag – the page won't fit phones.
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
- XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- Topic focushigh
3 of 7 title keywords appear in the main content (missing: prices, electronics, sports, equipment).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Render-blocking resourceshigh
2 blocking script(s) and 6 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to amazon.co.uk…
Indexing & crawling 88%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✗
XML sitemaphigh
No XML sitemap found at /sitemap.xml or in robots.txt.
Fix: Create an XML sitemap listing every page and submit it in Google Search Console.
- ✓
Canonical URLhigh
Canonical: https://www.amazon.co.uk/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://amazon.co.uk/ → https://www.amazon.co.uk/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
amazon.co.uk redirects to www.amazon.co.uk.
Search snippet & sharing 29%
How the page looks in Google results and when shared.
- ✗
Title tagcritical
“Amazon.co.uk: Low Prices in Electronics, Books, Sports Equipment & more”
About 667px of Google's ~580px desktop width – it will probably be cut off.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- !
Meta descriptionhigh
168 characters, ~1094px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-gb"
Content quality 27%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
407 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- !
Readabilitymedium
Flesch reading ease 45 (fairly difficult), about 8 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✗
Topic focushigh
3 of 7 title keywords appear in the main content (missing: prices, electronics, sports, equipment).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- ✗
H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
22 headings for 407 words – a lot for the amount of text.
1 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
0% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 34%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- !
AI crawler accesshigh
robots.txt blocks search crawlers: OAI-SearchBot (ChatGPT search), ChatGPT-User (ChatGPT browsing), Claude-SearchBot (Claude search), Claude-User (Claude browsing), PerplexityBot (Perplexity).
Training-only crawlers blocked: GPTBot, ClaudeBot, Google-Extended, CCBot, meta-externalagent. That's a licensing choice – these companies document them as separate from their search crawlers.
Fix: Allow Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot and PerplexityBot so search and AI tools can cite you (you can still block training-only bots such as GPTBot or Google-Extended).
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- !
Question-led contentmedium
1 heading(s) phrased as questions, e.g. “Time for a new one?”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✗
Trust pages (E-E-A-T)medium
Links found to privacy; missing about and contact.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 69%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
84 internal and 28 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “customer service”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- !
Broken links (sample)high
Checked 12 internal link(s).
Broken: /gp/site-directory?ref_=nav_em_js_disabled (404).
6 link(s) point to a redirect – link to the final address instead.
Fix: Fix or remove links that return errors, and update links that redirect.
Performance 41%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
402 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
964 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 6 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
100 script tag(s); files loaded from 1 other domain(s): m.media-amazon.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
14 image(s).
13 without width/height – can cause layout shift (CLS).
11 image(s) after the first three aren't lazy-loaded.
9 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- !
Cachinglow
Cache-Control: no-cache
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 100%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=47474747; includeSubDomains; preload
- ✓
Security headerslow
Present: CSP, nosniff, Permissions-Policy, clickjacking protection.
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 33%
Usable on phones and by everyone – Google indexes the mobile version.
- ✗
Mobile viewportcritical
No viewport meta tag – the page won't fit phones.
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
- !
Image alt textmedium
1 of 14 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✓
Form labelsmedium
All 2 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.