Skip to content

Score methodology

How we score a site out of 100.

seoscore is an in-house metric. We fetch your home page, run 44 checks in eight areas and add up the points. Every check and weight is on this page.

Points by area

How a score is made

From home page to League rank.

  1. Step 1

    Fetch

    We load your home page as seoscorebot, the way a search engine does.

  2. Step 2

    Check

    We run 44 checks on its HTML, headers, speed and site files.

  3. Step 3

    Score each area

    Each of the eight areas earns points, up to its weight.

  4. Step 4

    Add them up

    The areas add up to one score out of 100.

  5. Step 5

    Rank

    Your score places you on the public League Table.

What we check

The eight areas, and every check.

Each area is weighted by how much it matters to search engines and AI assistants. Open one to see its checks, why each matters and how to fix it.

Every check follows published guidance: Google Search Central, Core Web Vitals on web.dev, WCAG 2.2, OWASP Secure Headers, schema.org, Google AI features and llms.txt.

Performance

How fast the page loads and answers.
  • Page reachable

    Whether the page answers with a successful HTTP status.

    Why it matters

    If crawlers cannot load the page, nothing else on it can rank, and visitors bounce before they see it.

    How to fix

    Make sure the URL returns 200 without redirects to error pages, and that your server or firewall is not blocking crawlers.

  • Server response time

    How long the server takes to send the first byte of the page.

    Why it matters

    A slow first response delays everything after it. It drags down Core Web Vitals and makes the site feel sluggish.

    How to fix

    Aim for under 600 ms: add page or full-page caching, use a CDN, and fix slow database queries or plugins.

  • Page asset weight

    How many scripts, stylesheets and images the page loads.

    Why it matters

    Every extra request adds download time, especially on mobile connections, and slows the moment the page becomes usable.

    How to fix

    Remove unused scripts and styles, bundle and minify what is left, and lazy-load anything below the fold.

  • Image delivery

    Whether images set their dimensions, lazy-load below the fold and offer responsive sizes (srcset).

    Why it matters

    Images are usually the heaviest part of a page. Oversized images are the most common cause of a slow Largest Contentful Paint.

    How to fix

    Set width and height on every image, add loading="lazy" below the fold, and provide srcset/sizes (ideally AVIF or WebP via a CDN).

  • Third-party scripts & resource hints

    How many external scripts the page loads, and whether it uses preconnect or dns-prefetch hints.

    Why it matters

    Third-party tags (chat widgets, trackers, ads) block the main thread and are outside your control. Resource hints cut connection time for the ones you keep.

    How to fix

    Audit and remove unneeded tags, load the rest with async or defer, and add <link rel="preconnect"> for critical third-party origins.

  • Core Web Vitals (PageSpeed Insights)

    Real-world speed and stability metrics: LCP, CLS, TBT, FCP and Speed Index.

    Why it matters

    Core Web Vitals are a Google ranking signal and track how fast and stable the page feels to real visitors.

    How to fix

    Keep LCP under 2.5 s, CLS under 0.1 and TBT under 200 ms: speed up the hero image and server, reserve space for media, and defer non-critical JavaScript.

Content Quality

Titles, descriptions, headings and the words on the page.
  • Title tag

    Whether the page has one title tag of a sensible length.

    Why it matters

    The title is the clickable headline in search results and one of the strongest on-page relevance signals.

    How to fix

    Write a unique title of 20–65 characters with the main keyword near the start.

  • Meta description

    Whether the page has a meta description of a sensible length.

    Why it matters

    It is the snippet under your title in search results. A clear one earns more clicks, and if it is missing Google picks text for you.

    How to fix

    Write a 70–160 character summary that includes the main keyword and a reason to click.

  • Content length

    How much visible body text the page has.

    Why it matters

    Thin pages rarely answer a searcher’s question fully, so they struggle to rank against more thorough pages.

    How to fix

    Expand the page with genuinely useful detail (examples, steps, FAQs) rather than padding. Several hundred words is a sensible floor for key pages.

  • Heading structure

    Whether the page has a single H1 and an orderly H2/H3 outline.

    Why it matters

    Headings tell search engines and screen-reader users what each section is about, and help readers scan.

    How to fix

    Use exactly one H1, then split the page into sections with descriptive H2 and H3 headings.

  • Topical relevance

    Whether the page’s main topic appears consistently in the title, headings and opening text.

    Why it matters

    Search engines rank pages that clearly match the query. Mixed or vague signals make it hard to know what the page is for.

    How to fix

    Work the main keyword and close variants naturally into the title, H1, subheadings and first paragraph.

Technical

Whether search engines can crawl, read and index it.
  • Canonical tag

    Whether the page declares its preferred URL with rel="canonical".

    Why it matters

    Without it, URL variants (tracking parameters, http/https, trailing slashes) can split ranking signals across duplicates.

    How to fix

    Add <link rel="canonical"> pointing at the preferred, absolute URL of the page.

  • Indexability

    Whether robots meta tags or headers stop the page being indexed.

    Why it matters

    A stray noindex removes the page from search results entirely, however good it is.

    How to fix

    Remove noindex from pages you want ranked. Keep it only on utility pages such as login or internal search.

  • Character encoding

    Whether the page declares its character set (UTF-8).

    Why it matters

    Without a declared charset, browsers and crawlers can misread accents and symbols, garbling your text in results.

    How to fix

    Add <meta charset="utf-8"> as the first element in the document head.

  • Structured data (JSON-LD)

    Whether the page includes schema.org structured data in JSON-LD.

    Why it matters

    Structured data helps search engines and AI assistants understand the page and can unlock rich results such as stars, FAQs and breadcrumbs.

    How to fix

    Add JSON-LD for your organisation and the page type (Article, Product, LocalBusiness, FAQPage) and validate it with Google’s Rich Results Test.

  • robots.txt

    Whether a valid robots.txt exists at the site root.

    Why it matters

    It tells crawlers what they may fetch. A missing or broken file can waste crawl budget or accidentally block important pages.

    How to fix

    Publish robots.txt that allows public pages, disallows private or admin paths, and lists your sitemap.

  • XML sitemap

    Whether an XML sitemap exists and is discoverable.

    Why it matters

    A sitemap helps search engines find new and deep pages quickly, especially on larger or newer sites.

    How to fix

    Generate sitemap.xml, keep it up to date automatically, and declare it in robots.txt with a Sitemap: line.

Mobile

How well it fits a phone screen.
  • Viewport meta tag

    Whether the page sets a responsive viewport.

    Why it matters

    Without it, phones render a shrunken desktop page. Google indexes the mobile version first, so this affects rankings everywhere.

    How to fix

    Add <meta name="viewport" content="width=device-width, initial-scale=1"> to the head.

  • Responsive stylesheets

    Whether the CSS adapts the layout to different screen sizes.

    Why it matters

    Most searches happen on phones. A layout that does not adapt is hard to read and use, which hurts engagement and conversions.

    How to fix

    Use media queries or a responsive framework so content reflows cleanly from 320 px upwards.

  • Responsive images

    Whether images use srcset/sizes or flexible widths.

    Why it matters

    Phones should not download desktop-sized images: it wastes data and slows the page.

    How to fix

    Provide srcset and sizes (or a <picture> element) so each screen gets an appropriately sized image.

  • No fixed desktop widths

    Hard-coded wide pixel widths that cause sideways scrolling on phones.

    Why it matters

    Content wider than the screen forces sideways scrolling, a common mobile usability failure.

    How to fix

    Replace fixed pixel widths with max-width: 100%, flex or grid layouts and relative units.

Security

HTTPS and the headers that protect visitors.
  • HTTPS encryption

    Whether the page is served over HTTPS.

    Why it matters

    HTTPS is a ranking signal, and browsers label plain HTTP pages “Not secure”, which scares visitors away.

    How to fix

    Install a TLS certificate (free from Let’s Encrypt), redirect all HTTP traffic to HTTPS and update internal links.

  • Security headers

    Protective HTTP headers such as HSTS, Content-Security-Policy, X-Content-Type-Options and X-Frame-Options.

    Why it matters

    They defend visitors against clickjacking, content sniffing and script injection, and signal a well-maintained site.

    How to fix

    Add the missing headers at your server or CDN, starting with HSTS and X-Content-Type-Options: nosniff.

  • Secure form submissions

    Whether forms on the page submit over HTTPS.

    Why it matters

    Forms posting to plain HTTP expose what people type, and browsers warn users before they submit.

    How to fix

    Point every form action at an https:// URL (or a relative URL on an HTTPS page).

Accessibility

Whether everyone can use it, whatever their device or ability.
  • Image alt text

    Whether images have alt text.

    Why it matters

    Alt text lets screen-reader users understand images, and gives search engines context for image search.

    How to fix

    Describe each meaningful image in a short phrase. Use alt="" for purely decorative images.

  • Form labels

    Whether form fields have associated labels.

    Why it matters

    Unlabelled fields are unusable with a screen reader and harder for everyone to fill in correctly.

    How to fix

    Give every input a visible <label for="…"> (or aria-label when a visible label is impossible).

  • Landmarks & semantic regions

    Whether the page uses landmarks such as <header>, <nav>, <main> and <footer>.

    Why it matters

    Landmarks let assistive-technology users jump straight to the content, and help machines understand page structure.

    How to fix

    Wrap the page regions in semantic elements, with exactly one <main>.

Social

How it looks when someone shares it.
  • Open Graph tags

    Open Graph title, description, URL and type tags.

    Why it matters

    They control how the page looks when shared on LinkedIn, Facebook, Slack and messaging apps. Good previews earn more clicks.

    How to fix

    Add og:title, og:description, og:url and og:type to the head.

  • Social share image

    Whether an og:image is set for link previews.

    Why it matters

    Shares without an image are easy to scroll past. An image makes the preview far more noticeable.

    How to fix

    Add og:image pointing at a 1200×630 image, with the absolute URL.

  • Twitter/X card

    Twitter/X card meta tags.

    Why it matters

    They control the preview on X. Without them, shared links can show as bare URLs.

    How to fix

    Add twitter:card (summary_large_image) plus twitter:title and twitter:description.

AEO

Answer engine optimization: whether ChatGPT, Claude and AI Overviews can read, trust and quote it.
  • AI crawler access

    Whether robots.txt lets the 7 answer-engine crawlers read the page: ChatGPT's, Claude's, Perplexity's, Googlebot and Bingbot. Training-only crawlers like GPTBot cost no points.

    Why it matters

    An answer engine can only cite pages its crawler is allowed to read. One Disallow line can keep you out of ChatGPT or Perplexity answers entirely.

    How to fix

    Remove Disallow rules for the answer crawlers in robots.txt, and check that your CDN or firewall (for example Cloudflare's AI bot blocking) lets them through. You can still block training-only crawlers.

  • Content without JavaScript

    How much of the page's text is in the HTML before any JavaScript runs.

    Why it matters

    GPTBot, ClaudeBot and PerplexityBot read the HTML as sent and do not run JavaScript. A page drawn in the browser looks empty to them.

    How to fix

    Render the main content on the server (server-side rendering, static generation or plain HTML) so the words are in the page source.

  • Snippets allowed

    Robots rules that stop engines quoting the page: nosnippet, a tiny max-snippet, noai, or data-nosnippet around the main content.

    Why it matters

    Google AI Overviews and other answer engines only quote what your snippet rules allow. nosnippet removes you from them.

    How to fix

    Remove nosnippet, max-snippet:0 and noai from the robots meta tag and the X-Robots-Tag header, and keep data-nosnippet off your main content.

  • llms.txt for LLM crawlers

    Whether /llms.txt exists at the site root.

    Why it matters

    llms.txt gives AI assistants a short, curated map of your key pages, making it easier for them to understand and cite your site.

    How to fix

    Publish a Markdown llms.txt at the site root that lists your key pages with one-line summaries.

  • Entity & author signals

    Structured data that says who is behind the page: Organization or Person schema, sameAs links to your official profiles, and an author or publisher.

    Why it matters

    Answer engines prefer sources they can identify. Clear entity markup connects your site to your brand, your profiles and your authors.

    How to fix

    Add Organization (or Person) JSON-LD with name, url, logo and sameAs links, and name an author or publisher on articles.

  • Content freshness

    Whether the page states when it was published or last updated (schema dates, article meta tags, a <time> element or the Last-Modified header), and that it is within the last year.

    Why it matters

    Answer engines favour recent sources, especially for questions where facts change. A page with no date reads as possibly out of date.

    How to fix

    Add dateModified to your JSON-LD, show a visible "Updated" date, and refresh key pages at least once a year.

  • Outbound citations

    Links out to studies, documentation or other sources.

    Why it matters

    Pages that cite their sources read as more trustworthy, to people and to AI systems deciding what to quote.

    How to fix

    Link to the studies, standards and docs you reference, using descriptive anchor text.

  • Direct answer structure

    Whether the paragraph after the main heading gives a short, direct answer.

    Why it matters

    Assistants lift concise definitions. A long preamble makes your page less likely to be quoted.

    How to fix

    Follow the H1 with a one- or two-sentence answer (“X is a Y that…”), then go into detail.

  • FAQ & question formatting

    FAQ schema and question-shaped headings.

    Why it matters

    AI assistants and featured snippets favour content phrased as questions and answers they can quote directly.

    How to fix

    Add an FAQ section with question headings (H2/H3) and short answers, and mark it up with FAQPage JSON-LD.

  • Answer blocks under questions

    Whether each question heading or FAQ toggle is followed straight away by a short answer (8 to 90 words).

    Why it matters

    Answer engines take the first paragraph under a question as its answer. A short, complete answer there is what gets quoted.

    How to fix

    Put a 40–60 word answer right under each question, then the detail, examples and links.

  • Factual density

    How many concrete facts (numbers, dates, prices, measurements) the visible copy contains.

    Why it matters

    Assistants prefer sources with specific, verifiable facts over vague marketing prose.

    How to fix

    Add concrete figures, dates and named examples where they support your claims.

These are the page checks behind AEO and GEO (generative engine optimization). Run them on any page with the free AEO and GEO checker, or read the GEO guide.

The eight areas add up to the score, capped at 100. The audit report adds what we found on your page.

Verified tiers & badges

Cross a line, earn a tier.

A verified tier shows on your badge, your public profile and your League row.

  1. Unrated

    Below 60

  2. Bronze

    Score 60+

  3. Silver

    Score 75+

  4. Gold

    Score 90+

  5. Platinum

    Score 95+

Below 60 a site is Unrated: no verified tier is awarded.

League ranks

How the table is ordered.

Highest score first

Every finished audit re-ranks the whole table within minutes. A tie goes to the newest audit.

  • 3 Audited 2 days ago
  • 4 Audited 9 days ago
Example · a tie on 88

Form and movement

We save every site's rank after each audit. That drives the arrows, the form guide, Climbers and rank alerts.

4 up 3
Example · up 3 places, last five audits

By area, category or country

Rank any table by one area, open the table of one of 16 categories, or narrow it to a country.

Performance Category Country

Owner means the site's owner runs it on a paid seoscore plan; it never changes a rank or a score.

Joining and leaving

How sites get into the League, and how to leave.

Ways in

  • A customer audits it

    Any site one of our customers audits joins the table.

  • It joins the waitlist

    A site added on the waitlist joins the table too.

  • We audit it ourselves

    From a list of well-known company websites around the world, re-audited every week. Owners can add them to their own account.

Ways out

  • Block seoscorebot

    Our crawler respects robots.txt: our own scans skip any site that blocks it, or every bot, from its home page.

  • Unlist your copy

    A customer can unlist their own copy of a site in its settings.

  • Remove it for good

    A site's owner can remove it from the League, whoever audits it.

Each score is a dated measurement of the public home page on our checks, not a verdict on the business.

See how your site scores.

The same 44 checks, a fix for each one, and your place on the League Table.

Get my free score