stjude.org

Ranked #60 of 300 on the Leaderboard. Analyzed .

Index Quotient

79.15

See it on the LeaderboardAnalyze again
92.62
Technical
87.68
Content
51.25
Answers
85.21
AI
78.99
Authority

Technical Health

92.62

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

  • SpeedPartial

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

Content Quality

87.68

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.

  • Images and linksStrong

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

Opportunities

Nothing stands out to work on here. The most room left is in Depth and readability.

Answer Readiness

51.25

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

Strengths

  • Scannable formattingStrong

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

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 dataWeak

    Little structured data is present, so engines have to infer what each page is rather than being told.

  • Navigation aidsPartial

    Some interior pages show where they sit in the site; the rest would benefit from the same trail.

AI Visibility

85.21

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.

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

  • FeedsPartial

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

Authority

78.99

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. #59uam.es79.31
  2. #60stjude.org79.15
  3. #61denverpost.com79.10

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