keras.io

Ranked #295 of 300 on the Leaderboard. Analyzed .

Index Quotient

46.11

See it on the LeaderboardAnalyze again
89.97
Technical
14.75
Content
6.15
Answers
50.46
AI
69.22
Authority

Technical Health

89.97

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.

  • SpeedStrong

    Pages load quickly, and the server answers fast.

  • Safe to visitStrong

    Nothing marks this site as unsafe to visit.

Opportunities

  • URL and canonical hygienePartial

    URLs are mostly in order; what remains is giving every page one settled address and making missing pages answer as missing.

  • 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

14.75

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

Opportunities

  • Titles and descriptionsMissing

    Pages have no usable titles or descriptions, so search results have nothing to show for them; one of each, per page, is the place to start.

  • Depth and readabilityMissing

    Pages carry almost no readable text, so there is nothing for search engines or answer engines to work with; writing real content is the whole job here.

  • 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

6.15

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

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 shapeMissing

    No page poses a question and answers it directly beneath, which is the shape answer engines look for; adding those pages is where this starts.

  • Scannable formattingWeak

    Pages read as unbroken prose: few lists or tables, and openings that take a while to get to the point.

AI Visibility

50.46

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

  • Readable without JavaScriptWeak

    Much of the content only appears once scripts run, so a crawler that reads the raw page finds little.

  • IdentityWeak

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

  • FeedsPartial

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

Authority

69.22

Whether the wider web vouches for the site.

Strengths

  • BacklinksStrong

    Plenty of other sites link here, including ones that matter.

  • Domain historyStrong

    The domain has a long history, and history counts.

Opportunities

  • TrafficPartial

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

  • Social presenceWeak

    The site barely points to its presence on other platforms; linking its profiles from the site connects the two.

Nearby on the Leaderboard

  1. #294hyundaiusa.com46.21
  2. #295keras.io46.11
  3. #296supremecourt.gov45.45

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