americanexpress.com

Ranked #277 of 300 on the Leaderboard. Analyzed .

Index Quotient

58.34

See it on the LeaderboardAnalyze again
86.08
Technical
37.63
Content
23.35
Answers
60.31
AI
84.31
Authority

Technical Health

86.08

Whether search engines can fetch, trust, and quickly load the site.

Strengths

  • CrawlabilityStrong

    Crawlers are welcome here: a sitemap points the way, links work, and pages are allowed into the index.

  • Secure connectionStrong

    Every visit is encrypted, and the headers that keep it that way are in place.

  • Safe to visitStrong

    Nothing marks this site as unsafe to visit.

Opportunities

  • SpeedPartial

    Pages load reasonably but not quickly, so visitors wait longer than they need to.

  • URL and canonical hygienePartial

    URLs are mostly in order; what remains is giving every page one settled address and making missing pages answer as missing.

Content Quality

37.63

Whether pages say clearly what they are about, in a form machines can read.

Strengths

  • LanguageStrong

    The page language is declared and matches what is on the page.

Opportunities

  • Depth and readabilityWeak

    Pages are thin: there is little text for a search engine to judge them on, and what is there does not always match the title.

  • Titles and descriptionsWeak

    Titles and descriptions are thin, repeated across pages, or missing, so search results have little to show for each page.

  • Images and linksWeak

    Pages barely link to one another or leave images undescribed, so crawlers have little to follow and little to see.

Answer Readiness

23.35

Whether content is shaped and marked up so an engine can lift a direct answer.

Opportunities

  • Structured dataMissing

    Pages carry no structured data, so nothing tells an engine what each one is; marking up the page type, and the site's name, is the first step here.

  • Question-and-answer shapePartial

    Some headings are questions with an answer beneath them; more of them, each followed by a short direct answer, is what an answer engine lifts.

  • Scannable formattingWeak

    Pages read as unbroken prose: few lists or tables, and openings that take a while to get to the point.

AI Visibility

60.31

Whether AI systems can reach, read, and confidently identify the site.

Strengths

  • AI accessStrong

    AI crawlers are allowed in, and pages may be quoted in AI answers.

Opportunities

  • Readable without JavaScriptWeak

    Much of the content only appears once scripts run, so a crawler that reads the raw page finds little.

  • IdentityPartial

    Who is behind the site is partly clear; an About page, a Contact page, and markup naming the organization would let machines say so with confidence.

  • FeedsMissing

    There is no feed and the sitemap carries no dates, so nothing tells a machine when something new appears; a feed is a small addition.

Authority

84.31

Whether the wider web vouches for the site.

Strengths

  • BacklinksStrong

    Plenty of other sites link here, including ones that matter.

  • TrafficStrong

    The site has a large audience.

  • Domain historyStrong

    The domain has a long history, and history counts.

Opportunities

Nothing here to work on. The points left are the ones only the web's largest sites earn.

Nearby on the Leaderboard

  1. #276wiktionary.org59.62
  2. #277americanexpress.com58.34
  3. #278weather.gov57.41

Scores reflect what IndexBot could read from americanexpress.com's available pages on .

IndexBot

IndexBot is the crawler behind SEO Leaderboard. It visits a website only when someone submits that domain, reads it the way a search engine would, and leaves.

What it does

  • Fetches the homepage, robots.txt, the sitemap, and up to 24 more pages, at most four at a time.
  • Reads raw HTML only. It runs no JavaScript and loads no images, fonts, or scripts.
  • Visits a domain at most once every 24 hours, however many people submit it.
  • Stores what it measured, never full copies of pages.

How it identifies itself

Mozilla/5.0 (compatible; IndexBot/1.0; +https://seoleaderboard.com/bot)

How to let it in

Bot protection often turns IndexBot away before it reads anything, and the domain then cannot be scored. If you run the site, allow the User-Agent IndexBot. In Cloudflare that is a WAF skip rule; most other tools have the same idea under a different name.

(http.user_agent contains "IndexBot")

IndexBot has no fixed IP range to allow instead, so the User-Agent is the only thing to match on. It never tries to disguise itself as a browser, and the limits above are the whole of what it asks for.

How to keep it out

IndexBot obeys robots.txt. Add this and it will not read your site, and your domain cannot be scored.

User-agent: IndexBot
Disallow: /

Questions

Write to bot@seoleaderboard.com.