How the score is built

Six pillars, each 0 to 100, each tied to a distinct evidence source, compared against a competitor the tool finds by itself. Every number in a report traces back to a rule on this page.

How we pick the competitors

What counts as a direct competitor. A direct competitor sells a comparable product or service to the same buyers, at a similar or larger scale — not just any company that happens to share an industry.

Every report researches eight candidates with a cited web search, then validates them one at a time in rank order against the rules below — a public site, a different company, not a marketplace, directory, or social network, not the same company under another name — keeping every candidate that passes, up to five.

A candidate is rejected when it is:

  • The company itself, or a former name, alternate name, or redirect of it.
  • A parent company or a subsidiary of it.
  • A marketplace, directory, or review site (for example G2, Capterra, Crunchbase).
  • A social network, video platform, or news outlet.
  • A bare conglomerate homepage (for example microsoft.com) — a specific product site under it (for example dynamics.microsoft.com) is a valid competitor.

Each kept candidate must resolve to a live, public site that is not the company’s own — checked by re-fetching its homepage and rejecting it if it redirects back to the company or its name appears in the resulting page title.

How to read the charts

Radar

Six axes, one per pillar. Your polygon (aqua) and every rival in your set (indigo through magenta, ranked closest first) are overlaid on the same six axes, so the shape itself shows where you lead or trail at a glance.

Leaderboard

Every company in your set, ranked by score, one bar per row — you and every rival found. Each row shows its rank, score, band, and the points gap to you. A pillar section repeats this for that one pillar’s scores instead of the overall total.

Profile line

The same six pillars laid out left to right instead of around a circle, every company in your set as its own line. The gap between your line and your closest rival’s is shaded in the lead or trail colour for that stretch — a wider shaded band is a wider gap; every other rival draws as an unshaded reference line. The same chart can switch to a single pillar’s individual checks.

Trend lines

One line per company in your set, overlaid: how often each homepage changed, one point per year for the last eight years, and Publishing days per month, one point per calendar month for the last twenty-four months — the count of days in that month with at least one dated sitemap or feed entry, not a count of posts. A year whose true count could be higher than shown (the public archive’s own row cap was hit) carries a ≥ marker instead of a plain number. A month before the observation horizon, or with no dated entries at all, is shown as unknown, not zero.

Sector bars

Inside each pillar, one bar per check per company in your set, sized by the points earned as a percentage of that check’s own maximum (not the raw point gap, so a small check and a large one are compared fairly). Each bar is coloured by that company’s own series colour — the same colour that names it in the leaderboard and every other chart — never by a lead/trail/even verdict.

The six pillars

Every check below is deterministic (read straight from the page, PageSpeed, or the Wayback Machine) or researched (Perplexity, cited). Points sum to 100 per pillar.

Web Experience

Deterministic checks on the live site plus Google PageSpeed Insights (mobile).

CheckPointsSource
PageSpeed mobile performance × 0.3535PageSpeed
PageSpeed accessibility × 0.1515PageSpeed
PageSpeed best-practices × 0.1010PageSpeed
HTTPS served and http:// redirects to https://10Site fetch
<meta name="viewport"> present5Site fetch
Conversion paths — contact page/link 5, demo/trial/quote CTA 10, form on homepage 520 capSite fetch
Freshness — newest sitemap lastmod ≤ 90 days scores 5, ≤ 365 days scores 25Site fetch

When PageSpeed is unavailable, the 40 non-PageSpeed points are renormalised to 100 and confidence drops to 0.4.

Findability

Deterministic checks on the live site plus the PageSpeed SEO category.

CheckPointsSource
Lighthouse SEO category × 0.2525PageSpeed
<title> 10–70 characters 5, meta description 50–160 characters 5, exactly one <h1> 515Site fetch
<link rel="canonical"> present5Site fetch
robots.txt present and not Disallow: / for * 5, sitemap discoverable 1015Site fetch
JSON-LD schema.org present 10, OpenGraph tags 515Site fetch
Indexable footprint by sitemap URL count — under 20, 20–99, 100–999, 1000 or more15Site fetch
Domain age from first Wayback capture — under 1, 1–3, 3–10, over 10 years10Wayback CDX

When PageSpeed is unavailable, the remaining 75 points are renormalised and confidence drops to 0.7.

Content & Thought Leadership

Deterministic checks on the live site — sitemap, feed, and page structure.

CheckPointsSource
Blog, insights, resources, news, or articles section discovered20Site fetch
Publishing cadence in the last 90 days — 0 posts scores 0, rising to 30 at 12 or more30Site fetch
Formats detected — case studies, guides, webinars, video, podcast — 5 each25 capSite fetch
Newsletter or subscribe capture detected10Site fetch
RSS or Atom feed present5Site fetch
Newest post age — 10 points within 30 days, 6 within 90, 3 within 36510Site fetch

Confidence is 0.9 when a sitemap or feed was parsed, 0.6 when cadence is read from HTML dates only.

Social Presence

Profile links on the site plus researched audience and posting cadence.

CheckPointsSource
Profiles linked from the site — LinkedIn 10, YouTube 6, X 5, Instagram 5, TikTok 5, Facebook 430 capSite fetch
LinkedIn audience and posting cadence, each scored on a five-tier scale30Research
The two next-strongest platforms by cited followers, audience and cadence tiers40Research

Assessed only when the social research step succeeds. A successful search that finds no accounts is a legitimately low score, not a missing pillar — every researched number carries its citation URL, and a number without one is dropped.

Paid & Press

A newsroom check on the site plus researched press coverage and paid-ad evidence.

CheckPointsSource
Newsroom or press page on the site10Site fetch
Third-party press coverage in the last 12 months, cited40Research
Active paid ads per source — Google Ads Transparency Center, Meta Ad Library, LinkedIn Ad Library — 12 each36 capResearch
Ad-pixel corroboration — Google Ads tag, Meta Pixel, LinkedIn Insight — 4 each14 capMarTech fingerprint

Assessed only when the paid & press research step succeeds.

MarTech & Data

A curated, MIT-clean signature list of roughly 60 marketing tools, matched against script sources, inline globals, cookies, headers, and meta tags found in the page.

CheckPointsSource
Web analytics — GA4, Adobe Analytics, Matomo, Plausible, and similar15Fingerprint
Tag management / CDP — GTM, Tealium, Adobe Launch, Segment10Fingerprint
Marketing automation / email — HubSpot, Marketo, Pardot, ActiveCampaign, Mailchimp, and similar20Fingerprint
CRM & scheduling — Salesforce, HubSpot CRM, Zoho, Calendly, and similar10Fingerprint
Advertising pixels — Google Ads, Meta, LinkedIn Insight, Bing UET, and similar10Fingerprint
Conversational — Intercom, Drift, HubSpot Chat, Zendesk, and similar10Fingerprint
Experimentation & behaviour — Hotjar, Clarity, FullStory, Optimizely, and similar10Fingerprint
Consent management — OneTrust, Cookiebot, TrustArc, and similar10Fingerprint
ABM / personalisation / intent — 6sense, Demandbase, Clearbit, ZoomInfo5Fingerprint

Confidence 0.85. Known limit: only tags present in the static page source — script URLs, inline globals, cookies, headers — are visible. Tags injected at runtime by a tag manager can be missed; the report states "detected in page source."

Bands and verdict

BandScore range
Emerging024
Developing2544
Established4564
Advanced6584
Leading85100

Verdict per pillar and overall: Δ = your score minus your competitor's. Below 5 points either way reads as Neck and neck; 5 or more ahead reads as You lead; 5 or more behind reads as You trail.

Every number has a source

Deterministic checks come straight from the page source, PageSpeed Insights, or the Wayback Machine. Researched checks come from Perplexity search results with citations; a structurer discards any figure whose source URL is not among those citations.

The narrative that accompanies a report is written only from the finished comparison — the scores, bands, deltas, and evidence text already in the report. It is never given tools or web access, and a post-check verifies every number and every proper noun in it traces back to that input. A narrative that fails the check is regenerated once, then falls back to a deterministic template built from the deltas — the report is never blocked on it.

When a single check's source is unavailable — a PageSpeed quota limit, the Wayback CDX being down — that check is dropped and the pillar's score is renormalised over the checks that remain, with its confidence lowered and the report stating which check was skipped. A pillar whose required source is unavailable entirely (the site could not be read, or research failed) is never scored as zero — it is shown as insufficient public signal and left out of the overall.

What this cannot see

  • MarTech tags injected at runtime by a tag manager, rather than present in the static page source, script URLs, cookies, or headers, are not visible to this check.
  • Research depends on public coverage — a company with real social or press activity that Perplexity's search does not surface will read lower than reality on those pillars.
  • Competitor discovery depends on the same public coverage — a company with no clear public comparison to draw on may not find a rival at all.