repubblica.it

Ranked #96 of 300 on the Leaderboard. Analyzed .

Index Quotient

76.35

See it on the LeaderboardAnalyze again
95.38
Technical
74.98
Content
53.60
Answers
72.60
AI
85.18
Authority

Technical Health

95.38

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.

  • URL and canonical hygieneStrong

    URLs are clean and consistent, each page has one address, and missing pages say so.

Opportunities

Nothing stands out to work on here.

Content Quality

74.98

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.

  • HeadingsStrong

    Each page has one main heading, with subheadings in a sensible order beneath it.

  • FreshnessStrong

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

Opportunities

  • 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

53.60

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

Strengths

  • Navigation aidsStrong

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

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.

  • Scannable formattingWeak

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

  • Structured dataPartial

    Structured data is partly there: not on every page, not always complete, and not always the types that earn rich results.

AI Visibility

72.60

Whether AI systems can reach, read, and confidently identify the site.

Opportunities

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

  • AI accessPartial

    AI systems are partly allowed in: some crawlers are blocked, or pages limit how much of them may be quoted.

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

Authority

85.18

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. #95theatlantic.com76.68
  2. #96repubblica.it76.35
  3. #97webmd.com76.27

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