uu.se

Ranked #151 of 300 on the Leaderboard. Analyzed .

Index Quotient

72.93

See it on the LeaderboardAnalyze again
94.71
Technical
72.04
Content
48.24
Answers
68.65
AI
81.00
Authority

Technical Health

94.71

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. The most room left is in Crawlability.

Content Quality

72.04

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

Strengths

  • Depth and readabilityStrong

    Pages say enough to be useful, in plain language, and stay on the topic their titles promise.

  • 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

  • Titles and descriptionsPartial

    Titles are mostly in place; descriptions and link previews are patchier, and each page wants ones of its own.

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

  • LanguagePartial

    A language is declared, but either it is not the language the pages are written in, or the alternate-language versions do not point at each other.

Answer Readiness

48.24

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

Opportunities

  • Structured dataWeak

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

  • Question-and-answer shapePartial

    Some headings are questions with an answer beneath them; more of them, each followed by a short direct answer, is what an answer engine lifts.

  • Scannable formattingPartial

    Pages are partly scannable; opening with a short summary, and putting facts in lists and tables, makes them easier to lift from.

AI Visibility

68.65

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.

  • Readable without JavaScriptStrong

    The content is in the page itself, marked out from the navigation, and written in prose a machine can lift.

Opportunities

  • IdentityWeak

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

  • Authorship and sourcingPartial

    Some articles say who wrote them and when, and some pages cite sources; the rest should say so too.

  • FeedsPartial

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

Authority

81.00

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. #150airbnb.com72.94
  2. #151uu.se72.93
  3. #152cvs.com72.79

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