apple.com

Ranked #93 of 300 on the Leaderboard. Analyzed .

Index Quotient

76.89

See it on the LeaderboardAnalyze again
94.43
Technical
51.47
Content
67.79
Answers
73.76
AI
97.02
Authority

Technical Health

94.43

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.

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

Opportunities

  • SpeedPartial

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

Content Quality

51.47

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.

  • LanguageStrong

    The page language is declared and matches what is on the page.

Opportunities

  • Depth and readabilityWeak

    Pages are thin: there is little text for a search engine to judge them on, and what is there does not always match the title.

  • Images and linksWeak

    Pages barely link to one another or leave images undescribed, so crawlers have little to follow and little to see.

  • HeadingsWeak

    Pages lack a main heading, or the headings they have are out of order; a page's structure should be readable from its headings alone.

Answer Readiness

67.79

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.

  • Navigation aidsStrong

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

Opportunities

  • Question-and-answer shapeMissing

    No page poses a question and answers it directly beneath, which is the shape answer engines look for; adding those pages is where this starts.

  • Scannable formattingWeak

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

AI Visibility

73.76

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.

  • IdentityStrong

    It is clear who is behind this site, on its pages, in its markup, and in the public record.

Opportunities

  • Readable without JavaScriptWeak

    Much of the content only appears once scripts run, so a crawler that reads the raw page finds little.

  • 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

97.02

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 stands out to work on here.

Nearby on the Leaderboard

  1. #92berkeley.edu76.91
  2. #93apple.com76.89
  3. #94billboard.com76.71

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