usa.gov

Ranked #17 of 300 on the Leaderboard. Analyzed .

Index Quotient

84.10

See it on the LeaderboardAnalyze again
91.36
Technical
78.86
Content
88.44
Answers
78.89
AI
82.96
Authority

Technical Health

91.36

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

  • Secure connectionPartial

    The connection is encrypted but not fully hardened: steering every visit onto it and sending the standard security headers would finish the job.

Content Quality

78.86

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

88.44

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.

  • Question-and-answer shapeStrong

    Pages pose the questions people ask and answer them in a paragraph right under the heading.

  • Scannable formattingStrong

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

Opportunities

Nothing stands out to work on here. The most room left is in Question-and-answer shape.

AI Visibility

78.89

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

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

  • FeedsMissing

    There is no feed and the sitemap carries no dates, so nothing tells a machine when something new appears; a feed is a small addition.

Authority

82.96

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

  • Social presencePartial

    The site points to some of its social profiles; linking the rest of its major ones rounds this out.

Nearby on the Leaderboard

  1. #16wired.com84.11
  2. #17usa.gov84.10
  3. #18aalto.fi83.91

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