ftc.gov

Ranked #198 of 300 on the Leaderboard. Analyzed .

Index Quotient

70.09

See it on the LeaderboardAnalyze again
79.22
Technical
76.98
Content
36.32
Answers
68.85
AI
89.08
Authority

Technical Health

79.22

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

Strengths

  • URL and canonical hygieneStrong

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

  • 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

  • SpeedPartial

    Pages load reasonably but not quickly, so visitors wait longer than they need to.

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

Content Quality

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

  • 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

36.32

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

Strengths

  • Scannable formattingStrong

    Pages open with a short summary and use lists and tables, so an engine can lift the facts without reading everything.

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 aidsPartial

    Some interior pages show where they sit in the site; the rest would benefit from the same trail.

AI Visibility

68.85

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 sourcingPartial

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

Authority

89.08

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. #197jquery.com70.11
  2. #198ftc.gov70.09
  3. #199colorado.edu70.07

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