unige.ch

Ranked #267 of 300 on the Leaderboard. Analyzed .

Index Quotient

61.86

See it on the LeaderboardAnalyze again
82.66
Technical
60.79
Content
20.28
Answers
64.30
AI
81.26
Authority

Technical Health

82.66

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

Strengths

  • SpeedStrong

    Pages load quickly, and the server answers fast.

  • 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

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

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

Content Quality

60.79

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

Strengths

  • FreshnessStrong

    Something here was published or updated recently, and the site says when.

  • LanguageStrong

    The page language is declared and matches what is on the page.

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.

  • Images and linksPartial

    Pages link to one another, though some images lack a description and some link text says "read more" rather than where it leads.

Answer Readiness

20.28

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

64.30

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

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

  • 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

81.26

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. #266ing.com62.10
  2. #267unige.ch61.86
  3. #268kernel.org61.73

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