Free audit
Menu

SEO, GEO and AEO audit · home page score ·

SEO audit for amazon.com

amazon.com scored 45 out of 100 (grade F) in the ratemysite.ai audit of 49 checks across technical SEO, content, answer engines, AI readiness and speed, with 31 issues to fix.

Share this score

amazon.com

45/100

  • Technical SEO: 46
  • Content and E-E-A-T: 29
  • Answer engines (AEO): 13
  • AI readiness (GEO): 55
  • Speed: 82

Email me about this score

What to email

One email to confirm. Stop any time.

Compare with another site

Show your score on your site

amazon.com SEO, GEO and AEO score on ratemysite.ai

Audit complete. This site has serious issues

Summary

Site health score

Grade F

45 out of 100

Desktop screenshot of the audited page
Phone screenshot of the audited page

This site has serious issues. 31 things to improve.

First audit of this domain

Fix first

31 of 44 checks
Show all 31 issues

Core Web Vitals

Phone, field data
  • Largest Contentful Paint: Passed1432 ms

  • Cumulative Layout Shift: Passed0.01

  • Interaction to Next Paint: Passed176 ms

  • Time to First Byte: Passed730 ms

Site health

The other pages were not scanned in this audit.

AI crawler access

2 of 16 allowed
  • GPTBotBlocked
  • OAI-SearchBotBlocked
  • ChatGPT-UserBlocked
  • ClaudeBotBlocked
  • Claude-SearchBotBlocked
  • Claude-UserBlocked
See all 16 crawlers

Google preview

Desktop

amazon.com

amazon.com

Google will show text from the page here.

See phone and desktop
See this week's leaderboard

Every check, by category

Technical SEO: grade F, 46 out of 100

Technical SEO

Technical SEO has serious issues

Whether search engines can crawl, index and understand the page: title, meta description, headings, canonical, HTTPS, robots.txt and sitemap.

Failed: Title tag lengthHigh impact

What we found

no <title> element found

Why it matters

A title tag is the page name shown as the link in search results. This check fails without a title and warns when it is under 30 or over 60 characters.

Read the step by step fix guide: Title tag length
Failed: Canonical URLMedium impact

What we found

no canonical link found

Why it matters

A canonical tag is a link in the page head that names the main URL of a page. A missing tag fails, and one that points to another URL gets a warning.

Read the step by step fix guide: Canonical URL
Failed: Meta descriptionMedium impact

What we found

no meta description found

Why it matters

A meta description is a short summary in the page head that search results often show under your link. This check fails without one and warns below 70 or above 160 characters.

Read the step by step fix guide: Meta description
Failed: Single H1Medium impact

What we found

no H1 found

Why it matters

An H1 is the top-level heading that says what a page is about. This check passes with exactly 1 H1, fails with none, and warns when a page has 2 or more.

Read the step by step fix guide: Single H1
Failed: XML sitemapMedium impact

What we found

no sitemap found at /sitemap.xml or via robots.txt

Why it matters

An XML sitemap is a file that lists the URLs you want indexed. This check passes when the sitemap named in robots.txt, or /sitemap.xml when none is named, loads without an error. Otherwise it fails.

Read the step by step fix guide: XML sitemap
Failed: Open Graph and Twitter cardsMedium impact

What we found

no Open Graph or Twitter card tags

Why it matters

Open Graph tags are meta tags that control how a link looks when shared. This check needs 4 tags: og:title, og:description, og:image and twitter:card. With none it fails, and with some missing it warns.

Read the step by step fix guide: Open Graph and Twitter cards
  • Passed: Mobile viewport

    viewport: width=device-width, initial-scale=1

  • Passed: HTML lang attribute

    lang="en"

  • Passed: HTTPS and redirect

    https with http redirecting to https

  • Passed: robots.txt

    robots.txt present and allows crawling

  • Passed: Indexable (no noindex)

    page is indexable

  • Not applicable: Heading hierarchy

    no headings on the page

  • Not applicable: Image alt text

    no images on the page

Site insights

What we found on the page beyond the checks. None of it changes the score.

2 of 16 allowed

AI crawler access

Which AI crawlers your robots.txt lets in, and the rule that decides.

2 of 16 allowed, 14 blocked, 0 partly blocked

  • GPTBot OpenAIBlocked

    Collects content to train OpenAI models

    Disallow: /
  • OAI-SearchBot OpenAIBlocked

    Indexes pages for ChatGPT search answers

    Disallow: /
  • ChatGPT-User OpenAIBlocked

    Fetches a page when a ChatGPT user asks for it

    Disallow: /
  • ClaudeBot AnthropicBlocked

    Collects content to train Claude models

    Disallow: /
  • Claude-SearchBot AnthropicBlocked

    Indexes pages for Claude search answers

    Disallow: /
  • Claude-User AnthropicBlocked

    Fetches a page when a Claude user asks for it

    Disallow: /
  • PerplexityBot PerplexityBlocked

    Indexes pages for Perplexity answers

    Disallow: /
  • Perplexity-User PerplexityBlocked

    Fetches a page when a Perplexity user asks for it

    Disallow: /
  • Google-Extended GoogleBlocked

    A control token, not a crawler: tells Google whether Gemini may use your content

    Disallow: /
  • Applebot-Extended AppleAllowed

    A control token, not a crawler: tells Apple whether its AI models may use your content

    Disallow: /exec/obidos/account-access-login(applies to all crawlers)
  • Amazonbot AmazonAllowed

    Indexes pages for Alexa and Amazon answers

    Disallow: /exec/obidos/account-access-login(applies to all crawlers)
  • meta-externalagent MetaBlocked

    Collects content for Meta AI

    Disallow: /
  • CCBot Common CrawlBlocked

    Builds the open web dataset many AI models train on

    Disallow: /
  • Bytespider ByteDanceBlocked

    Collects content for ByteDance AI models

    Disallow: /
  • DuckAssistBot DuckDuckGoBlocked

    Fetches pages for DuckDuckGo AI answers

    Disallow: /
  • MistralAI-User MistralBlocked

    Fetches a page when a Le Chat user asks for it

    Disallow: /

ChatGPT-User, Claude-User, Perplexity-User and MistralAI-User fetch pages when a person asks, and may not follow robots.txt rules.

Let AI assistants reach you

These crawlers are blocked. Blocking training crawlers can be a deliberate choice; to let AI assistants find and cite your pages, add these lines to your robots.txt:

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ChatGPT-User
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: Claude-User
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Perplexity-User
Allow: /

User-agent: Google-Extended
Allow: /

How to fix AI crawler access

Phone and desktop

Google search preview

An approximate preview of how this page can look in Google results.

Phone

amazon.com

amazon.com

Google will show text from the page here.

Desktop

amazon.com

amazon.com

Google will show text from the page here.

  • No title found. Google will write one itself.
  • No meta description found. Google will pick text from the page.
Lab data

Google PageSpeed

Google's lab test of this page on a phone and on a desktop.

MetricPhoneDesktop
Google score6958
First Contentful Paint3.6 s770 ms
Speed Index5.8 s1.8 s
Largest Contentful Paint5.3 s1.2 s
Time to Interactive12.4 s2.8 s
Total Blocking Time13 ms601 ms
Cumulative Layout Shift0.000.26

Phone opportunities

  • Render-blocking requestsEst savings of 1,480 ms
  • Improve image deliveryEst savings of 306 KiB, saves about 600 ms
  • Font displayEst savings of 50 ms
  • Use efficient cache lifetimesEst savings of 70 KiB
  • Minimize main-thread work2.2 s
  • Avoid enormous network payloadsTotal size was 6,520 KiB
  • Image elements do not have explicit width and height
  • Reduce unused CSSEst savings of 213 KiB

Desktop opportunities

  • Reduce JavaScript execution time1.9 s, saves about 600 ms
  • Minimize main-thread work3.7 s, saves about 600 ms
  • Render-blocking requestsEst savings of 370 ms
  • Font displayEst savings of 120 ms
  • Improve image deliveryEst savings of 497 KiB, saves about 100 ms
  • Avoid large layout shifts3 layout shifts found, saves about 0 ms
  • Use efficient cache lifetimesEst savings of 3 KiB
  • Legacy JavaScriptEst savings of 6 KiB

Page weight (phone)

TypeRequestsSize
Total2036.4 MB
Media43.9 MB
Script34797 KB
Image72704 KB
Font17493 KB
Document3352 KB
Other60126 KB
Stylesheet1392 KB

JavaScript errors (desktop)

15 errors in the browser console, first 10 shown.

  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • console.error: Error logged with the Track&Report JS errors API(http://tiny/1covqr6l8/wamazindeClieUserJava): {"m":"Found no value in attribute data-clientData under card root. Please assign in server.","csm":"v5 ue
  • network: Failed to load resource: net::ERR_CONNECTION_FAILED
  • network: Failed to load resource: net::ERR_TIMED_OUT
  • network: Failed to load resource: the server responded with a status of 400 (Bad Request)
SPF and DMARC

Email security

SPF and DMARC records stop others from sending email that pretends to come from this domain.

  • SPFFound: only the listed servers may send email (strict)
    v=spf1 include:spf1.amazon.com include:spf2.amazon.com include:amazonses.com -all
  • DMARCFound: fake emails go to spam
    v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com

    at _dmarc.amazon.com

1 audit

Score history

The overall score of each audit of this site, oldest first.

First audit of this domain

5 questions

Questions about this report

What is the SEO score of amazon.com?

amazon.com scored 45 out of 100, grade F, with technical SEO 46, content 29, answer engines 13, AI readiness 55 and speed 82.

What should amazon.com fix first?

Start with AI crawler access: robots.txt blocks tier 1 AI crawlers: GPTBot, ClaudeBot, PerplexityBot, Google-Extended. This report has 31 issues to fix in total.

How is the site health score calculated?

Site health is a score from 0 to 100 that combines five category scores. Technical SEO counts for 25%, content counts for 15%, answer engines counts for 20%, AI readiness counts for 25% and speed counts for 15%.

How often can this report be updated?

A new audit can run 24 hours after the last one. To run it, use the Re-analyze button at the top of this page.

Is this audit free?

Yes. Audits are free and need no account.

This report is older than 24 hours