mskcc.org

Ranked #91 of 300 on the Leaderboard. Analyzed .

Index Quotient

76.94

See it on the LeaderboardAnalyze again
81.91
Technical
75.29
Content
81.84
Answers
67.52
AI
78.15
Authority

Technical Health

81.91

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

Strengths

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

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

  • 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

75.29

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

81.84

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

Strengths

  • Structured dataStrong

    Pages carry structured data of the kinds engines use, filled in properly, and the site says its own name in it.

  • Scannable formattingStrong

    Pages open with a short summary and use lists and tables, so an engine can lift the facts without reading everything.

  • Navigation aidsStrong

    Interior pages show where they sit in the site, and say so in a way engines can read.

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.

AI Visibility

67.52

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.

  • Readable without JavaScriptStrong

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

Opportunities

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

  • Authorship and sourcingMissing

    No article names an author or a date, and nothing links out to a source; a byline and a date on every article is the place to start.

  • FeedsPartial

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

Authority

78.15

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. #90bbc.com77.00
  2. #91mskcc.org76.94
  3. #92berkeley.edu76.91

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