turso.tech

Ranked #160 of 300 on the Leaderboard. Analyzed .

Index Quotient

72.38

See it on the LeaderboardAnalyze again
97.14
Technical
76.59
Content
55.12
Answers
70.45
AI
62.59
Authority

Technical Health

97.14

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

76.59

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.

  • Images and linksStrong

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

  • HeadingsStrong

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

Opportunities

  • Depth and readabilityPartial

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

Answer Readiness

55.12

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

Strengths

  • Structured dataStrong

    Pages carry structured data of the kinds engines use, filled in properly, and the site says its own name in it.

Opportunities

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

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

  • 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

70.45

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.

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

  • 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

62.59

Whether the wider web vouches for the site.

Strengths

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

  • Domain historyWeak

    The domain is fairly new; age is earned only by time.

Nearby on the Leaderboard

  1. #159mozilla.org72.43
  2. #160turso.tech72.38
  3. #161prettier.io72.36

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