racket-lang.org

Ranked #287 of 300 on the Leaderboard. Analyzed .

Index Quotient

53.86

See it on the LeaderboardAnalyze again
74.80
Technical
47.29
Content
24.54
Answers
53.43
AI
69.22
Authority

Technical Health

74.80

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

Strengths

  • SpeedStrong

    Pages load quickly, and the server answers fast.

  • Safe to visitStrong

    Nothing marks this site as unsafe to visit.

Opportunities

  • URL and canonical hygieneMissing

    Nothing here settles which address a page lives at, and missing pages answer as if they exist; one address per page is the place to start.

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

  • Secure connectionPartial

    The connection is encrypted but not fully hardened: steering every visit onto it and sending the standard security headers would finish the job.

Content Quality

47.29

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

Strengths

  • Images and linksStrong

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

Opportunities

  • Titles and descriptionsWeak

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

  • Depth and readabilityPartial

    Pages have substance, but many stop short, drift from their titles, or read harder than they need to.

  • FreshnessMissing

    Nothing here is recently dated, or dated at all; a date on each article, and something new to date, would change that.

Answer Readiness

24.54

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

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

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

  • Navigation aidsMissing

    Pages give no sign of where they sit in the site; a breadcrumb trail on interior pages, in text and in markup, is the fix.

AI Visibility

53.43

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

  • IdentityWeak

    Little here says who is behind the site, in the markup or on the pages themselves.

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

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

Authority

69.22

Whether the wider web vouches for the site.

Strengths

  • Domain historyStrong

    The domain has a long history, and history counts.

  • Social presenceStrong

    The site links to its profiles on the major platforms.

Opportunities

  • BacklinksPartial

    A fair number of sites link here; more links from well-regarded ones would lift this further.

  • TrafficPartial

    The site has a real audience, though not yet a large one.

Nearby on the Leaderboard

  1. #286c-span.org53.92
  2. #287racket-lang.org53.86
  3. #288walgreens.com52.87

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