forbes.com

Ranked #37 of 300 on the Leaderboard. Analyzed .

Index Quotient

81.14

See it on the LeaderboardAnalyze again
86.92
Technical
79.98
Content
67.78
Answers
77.73
AI
93.28
Authority

Technical Health

86.92

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

Strengths

  • SpeedStrong

    Pages load quickly, and the server answers fast.

  • 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

  • CrawlabilityPartial

    Crawlers can get in, but not everything helps them along: a complete sitemap, working links and pages that are allowed into the index are what to check.

Content Quality

79.98

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

Strengths

  • Depth and readabilityStrong

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

  • Images and linksStrong

    Images are described in text, and pages link to each other with links that say where they go.

  • HeadingsStrong

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

Opportunities

  • Titles and descriptionsPartial

    Titles are mostly in place; descriptions and link previews are patchier, and each page wants ones of its own.

Answer Readiness

67.78

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

Opportunities

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

  • Structured dataPartial

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

  • Navigation aidsWeak

    Few pages show their place in the site, so engines see pages rather than a structure.

AI Visibility

77.73

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

Strengths

  • IdentityStrong

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

  • Readable without JavaScriptStrong

    The content is in the page itself, marked out from the navigation, and written in prose a machine can lift.

Opportunities

  • Authorship and sourcingWeak

    Articles rarely say who wrote them or when, and pages rarely link out to sources, which gives an AI little reason to trust them.

  • AI accessPartial

    AI systems are partly allowed in: some crawlers are blocked, or pages limit how much of them may be quoted.

  • FeedsPartial

    Either a feed or sitemap dates are in place, not both; machines that watch for new content want both.

Authority

93.28

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. #36illinois.edu81.17
  2. #37forbes.com81.14
  3. #38sydney.edu.au80.84

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