ibm.com

Ranked #64 of 300 on the Leaderboard. Analyzed .

Index Quotient

78.83

See it on the LeaderboardAnalyze again
81.73
Technical
84.18
Content
52.55
Answers
83.96
AI
91.71
Authority

Technical Health

81.73

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.

  • URL and canonical hygieneStrong

    URLs are clean and consistent, each page has one address, and missing pages say so.

  • Secure connectionStrong

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

Opportunities

  • SpeedWeak

    Pages load slowly, which costs visitors before it costs rankings.

Content Quality

84.18

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

Strengths

  • Titles and descriptionsStrong

    Every page has a clear title and a description of its own, and shares well when linked.

  • Depth and readabilityStrong

    Pages say enough to be useful, in plain language, and stay on the topic their titles promise.

  • HeadingsStrong

    Each page has one main heading, with subheadings in a sensible order beneath it.

Opportunities

  • Images and linksPartial

    Pages link to one another, though some images lack a description and some link text says "read more" rather than where it leads.

Answer Readiness

52.55

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

Opportunities

  • Question-and-answer shapeWeak

    Few pages are shaped as questions and answers, so there is little for an answer engine to lift as a direct answer.

  • Structured dataPartial

    Structured data is partly there: not on every page, not always complete, and not always the types that earn rich results.

  • Scannable formattingPartial

    Pages are partly scannable; opening with a short summary, and putting facts in lists and tables, makes them easier to lift from.

AI Visibility

83.96

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.

  • IdentityStrong

    It is clear who is behind this site, on its pages, in its markup, and in the public record.

Opportunities

  • Readable without JavaScriptPartial

    Most content is readable without running scripts, but some pages arrive thin, or the content is not clearly marked out from the furniture around it.

  • 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.

  • Authorship and sourcingPartial

    Some articles say who wrote them and when, and some pages cite sources; the rest should say so too.

Authority

91.71

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. #63underarmour.com78.93
  2. #64ibm.com78.83
  3. #65pcmag.com78.71

Scores reflect what IndexBot could read from ibm.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.