Scanned sites / plausible.io

SEO report for plausible.io DR 90

The latest Site Spider scan of plausible.io, with 16 scans on record. Each scan is at its own address, for example /domain/plausible-io/2026-10-28-0919.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Latest scan

Scanned 2026-10-28 09:19:23 UTC, finished 2026-10-28 09:26:16 UTC. Found with 42backlinks.com tool directory

Site: https://plausible.io/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

75/ 100Good

On October 28, 2026 the Site Spider crawled 457 pages and 566 assets of plausible.io, starting from https://plausible.io/. It scored 75 out of 100, a good result. 13 of 33 checks found something to fix, led by heavy assets (34), broken links (85), title tags (149); 6 checks passed. Most of the points went to heavy assets (−6), broken links (−4.7), title tags (−4.2). 14 checks found something the score does not count, listed as noted. 4 checks were not run because the crawl fetched nothing for them. The list below shows each check's result, the fix plan, when present, explains what to do first, and the security review at the end of the page covers headers, transport, libraries and exposed files.

Security review: Medium2 medium and 2 low findings. See the security findings ↓

Pages crawled
457
Assets fetched
566
Status
Completed
Checks with issues
13 of 33
CoverageComplete crawl

1,023 of 1,024 discovered URLs were fetched, 1 failed. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 431 left unchecked.

  • Title tags149 issues
    149 of 292 pages have title issues. 66 noindex or canonicalized pages excluded.
    −4.2 points
  • Meta descriptions158 issues
    158 of 292 pages have meta description issues. 66 noindex or canonicalized pages excluded.
    −3.5 points
  • Headings2 issues
    2 of 292 pages have heading issues. 66 noindex or canonicalized pages excluded.
  • Broken links85 issues
    85 internal links point at 85 broken URLs.
    −4.7 points
  • Links to other sites13 issues
    13 destinations answered with an error, 65 could not be determined (timeouts, rate limits or refusals), 431 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.4 points
  • Redirects13 issues
    14 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses85 issues
    102 URLs did not return a 2xx response. 99 of them are pages, 85 with an error status; the rest are assets or redirects.
    −2.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability4 issues
    4 of 293 indexable pages have indexability warnings. 65 pages noindex by design.
    −0.1 points
  • Image alt text167 issues
    167 of 1636 image references have no alt attribute. 167 use an empty alt (decorative), which is fine.
    −0.6 points
  • Heavy assets34 issues
    34 assets larger than 500 KB among 566 fetched assets.
    −6 points
  • Orphan pages9 issues
    9 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage131 issues
    1 sitemap listing 167 URLs: 125 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.
    −2.2 points
  • Internal link counts35 noted
    Internal link counts for 358 pages; 35 worth a look.
  • Thin content6 issues
    6 of 292 pages have fewer than 200 words. 66 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format61 noted
    61 of 457 page URLs are harder to read, share or cache than they need to be.
  • Canonicals69 noted
    69 of 358 pages have a canonical worth checking.
  • Robots directives65 noted
    65 pages carry a robots directive; 293 carry none.
  • Anchor text35 noted
    35 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure65 noted
    65 of 292 pages could use the title, heading and snippet space better. 66 noindex or canonicalized pages excluded.
  • Image weight and alt length278 noted
    267 images over 100 KB; 11 with alt text over 100 characters.
  • Response anomalies4 noted
    4 URLs answered in a way worth looking at.
  • HTML and head validation2 noted
    2 of 358 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
  • hreflangOK
    123 pages declare hreflang, with 246 annotations, and every one checks out.
  • Structured data22 noted
    289 of 292 indexable pages carry structured data: BlogPosting (151), BreadcrumbList (122), ListItem (100), WebPage (15), FAQPage (8). 22 pages with errors a rich result would fail on.
  • Near duplicates2 noted
    2 pages in 1 group read almost the same as another page (95% alike or more).
  • Soft 404s2 noted
    2 pages answer 200 but say they are not there.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positions2 noted
    2 of 286 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    2 cookies set by the site; 14 response headers recorded across 1023 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 358 pages; 250 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not checked: this scan did not render pages. Tick "Include JavaScript rendering checks" when you request a scan to compare the served HTML with what a browser builds.
  • PageSpeed InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling249 noted
    249 words an English dictionary does not know, on 221 pages. Product names and jargon will appear here too.

What changed since the last scan

Score unchanged

plausible.io scored 75 out of 100 in both of its last two scans. That is a steady score, not an unchanged site: 87 findings changed between the two scans. 12 URLs the earlier crawl reached were not reached this time. The crawl reached 1 more page than last time, 457 in total, so some of the change is a change in what was crawled. Across 16 scans on record the score has ended up where it started, at 75.

  • Pages: 1 new
  • Titles: 7 changed
  • Meta descriptions: 7 changed
  • H1 headings: 3 changed
  • Internal links to the page: 69 changed
  • 12 URLs from the earlier crawl were not reached this time
  1. 2026-10-01 06:00:31 UTC75/100451 pages
  2. 2026-10-04 07:14:03 UTC75/100452 pages
  3. 2026-10-07 07:36:30 UTC75/100452 pages
  4. 2026-10-10 07:57:25 UTC75/100454 pages
  5. 2026-10-13 08:18:35 UTC75/100454 pages
  6. 2026-10-16 08:43:13 UTC75/100455 pages
  7. 2026-10-19 09:00:58 UTC75/100455 pages
  8. 2026-10-22 09:07:01 UTC74/100455 pages
  9. 2026-10-25 09:12:53 UTC75/100456 pages
  10. 2026-10-28 09:19:23 UTC75/100457 pages

Where this site sits among all scanned sites

2336 sites, median 79%, average 78%

plausible.io scores 75%, higher than 32% of the 2336 scanned sites. See the full ranking.

0581150%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 1 site34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 1 site40%: 3 sites41%: 1 site42%: 1 site43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 3 sites49%: 6 sites50%: 5 sites51%: 5 sites52%: 10 sites53%: 6 sites54%: 8 sites55%: 9 sites56%: 8 sites57%: 12 sites58%: 17 sites59%: 9 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 22 sites65%: 32 sites66%: 35 sites67%: 35 sites68%: 34 sites69%: 47 sites70%: 44 sites71%: 70 sites72%: 71 sites73%: 69 sites74%: 68 sites75%: 72 sites76%: 87 sites77%: 92 sites78%: 107 sites79%: 84 sites80%: 109 sites81%: 104 sites82%: 115 sites83%: 99 sites84%: 106 sites85%: 86 sites86%: 71 sites87%: 74 sites88%: 58 sites89%: 64 sites90%: 36 sites91%: 47 sites92%: 38 sites93%: 24 sites94%: 16 sites95%: 12 sites96%: 12 sites97%: 12 sites98%: 4 sites99%: 2 sites100%: 69 sites75% here100%90%80%70%60%50%40%30%20%10%0%

Green 90% and up (Excellent), lime 75 to 89 (Good), amber 50 to 74 (Needs work), red below 50 (Poor).

Internal link map

Loading the link map...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Your website has several areas needing improvement, particularly broken links, non-200 responses, and issues with titles and meta descriptions. Addressing these will enhance both user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: 85 internal links lead to broken URLs, harming user experience and SEO.

    How: Identify and update or remove broken links on affected pages.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: 102 URLs are not returning proper responses, affecting site accessibility.

    How: Check each URL for issues and ensure they return a 200 status.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: 149 pages have title issues, which can hurt discoverability and rankings.

    How: Revise title tags to ensure they are unique, descriptive, and under 60 characters.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: 158 pages have meta description issues, impacting click-through rates.

    How: Write unique meta descriptions for affected pages, keeping them under 160 characters.

    Evidence: 3 pages have no meta description at all.

    3 pages affected

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: 2 pages are missing H1 tags, which can affect SEO and page structure.

    How: Add relevant H1 tags to improve content hierarchy.

    Evidence: 2 pages: missing h1.

    2 pages affected

    Checks: headings

  6. 6

    Optimize Heavy Assets

    Why: 34 assets exceed 500 KB, affecting loading times and user experience.

    How: Compress heavy assets or host them externally.

    Evidence: 830 KB of script, loaded by 118 pages, so every visitor to any of them downloads it.

    118 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

Generated automatically; verify each change against your own site before relying on it.

Security review

Written by gpt-4o-mini from 16 checks over the crawl

Your website has several critical security headers missing, which increases the risk of certain attacks, such as clickjacking and man-in-the-middle interception. Implementing the recommended headers will enhance your site's security significantly.

  • 0 high
  • 2 medium
  • 2 low
  • 0 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Lack of HSTS allows interception of first requests if users enter addresses without HTTPS.

    Fix: Add the following header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, your pages can be embedded in frames, exposing users to clickjacking attacks.

    Fix: Set the following header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Absence of this header can lead to browsers executing files based on content rather than declared type.

    Fix: Add the following header: X-Content-Type-Options: nosniff.

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a referrer policy, full addresses including query strings may leak to other sites.

    Fix: Set the following header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    No HTML page sends strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://plausible.io/ → no strict-transport-security
    • https://plausible.io/simple-web-analytics → no strict-transport-security
    • https://plausible.io/lightweight-web-analytics → no strict-transport-security
    • https://plausible.io/privacy-focused-web-analytics → no strict-transport-security
    • https://plausible.io/open-source-website-analytics → no strict-transport-security
    • https://plausible.io/eu-hosted-web-analytics → no strict-transport-security
    • https://plausible.io/for-ecommerce → no strict-transport-security
    • https://plausible.io/for-saas → no strict-transport-security
    • https://plausible.io/for-freelancers-agencies → no strict-transport-security
    • https://plausible.io/for-bloggers-creators → no strict-transport-security
    • https://plausible.io/for-public-sector → no strict-transport-security
    • https://plausible.io/white-label-web-analytics → no strict-transport-security
  • FoundClickjacking protectionMedium

    No HTML page sends x-frame-options. Without X-Frame-Options (or a CSP frame-ancestors directive) the pages can be embedded in a frame on another site and overlaid with invisible controls.

    • https://plausible.io/ → no x-frame-options
    • https://plausible.io/simple-web-analytics → no x-frame-options
    • https://plausible.io/lightweight-web-analytics → no x-frame-options
    • https://plausible.io/privacy-focused-web-analytics → no x-frame-options
    • https://plausible.io/open-source-website-analytics → no x-frame-options
    • https://plausible.io/eu-hosted-web-analytics → no x-frame-options
    • https://plausible.io/for-ecommerce → no x-frame-options
    • https://plausible.io/for-saas → no x-frame-options
    • https://plausible.io/for-freelancers-agencies → no x-frame-options
    • https://plausible.io/for-bloggers-creators → no x-frame-options
    • https://plausible.io/for-public-sector → no x-frame-options
    • https://plausible.io/white-label-web-analytics → no x-frame-options
  • FoundMIME sniffing protectionLow

    65 of 358 HTML pages send x-content-type-options. Without X-Content-Type-Options: nosniff a browser may run a file as a script because of its contents rather than its declared type.

    • https://plausible.io/ → no x-content-type-options
    • https://plausible.io/simple-web-analytics → no x-content-type-options
    • https://plausible.io/lightweight-web-analytics → no x-content-type-options
    • https://plausible.io/privacy-focused-web-analytics → no x-content-type-options
    • https://plausible.io/open-source-website-analytics → no x-content-type-options
    • https://plausible.io/eu-hosted-web-analytics → no x-content-type-options
    • https://plausible.io/for-ecommerce → no x-content-type-options
    • https://plausible.io/for-saas → no x-content-type-options
    • https://plausible.io/for-freelancers-agencies → no x-content-type-options
    • https://plausible.io/for-bloggers-creators → no x-content-type-options
    • https://plausible.io/for-public-sector → no x-content-type-options
    • https://plausible.io/white-label-web-analytics → no x-content-type-options
  • FoundReferrer policyLow

    65 of 358 HTML pages send referrer-policy. Without a Referrer-Policy the full page address, including any query string, is sent to every site a visitor clicks through to.

    • https://plausible.io/ → no referrer-policy
    • https://plausible.io/simple-web-analytics → no referrer-policy
    • https://plausible.io/lightweight-web-analytics → no referrer-policy
    • https://plausible.io/privacy-focused-web-analytics → no referrer-policy
    • https://plausible.io/open-source-website-analytics → no referrer-policy
    • https://plausible.io/eu-hosted-web-analytics → no referrer-policy
    • https://plausible.io/for-ecommerce → no referrer-policy
    • https://plausible.io/for-saas → no referrer-policy
    • https://plausible.io/for-freelancers-agencies → no referrer-policy
    • https://plausible.io/for-bloggers-creators → no referrer-policy
    • https://plausible.io/for-public-sector → no referrer-policy
    • https://plausible.io/white-label-web-analytics → no referrer-policy
11 checks passed, 1 not applicable
  • OKHTTPS

    All 358 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 65 of 358 pages.

  • OKPermissions policy

    permissions-policy is set on all 358 HTML pages.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKCookie flags

    All 2 cookies carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    3 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKKeys and secrets in page code

    No API keys, tokens or private keys were found in the sampled HTML and scripts.

  • OKExposed files and listings

    None of the crawled URLs is a configuration file, backup, dump, repository folder or directory listing.

  • OKThird-party scripts

    The sampled pages load no scripts from other domains.

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

A passive review of what the crawl recorded: response headers, page and script contents and the URLs it found. It does not probe the site, test TLS settings or look for files that were not linked. Generated automatically; verify each finding against your own site before acting on it.

Earlier scans of plausible.io

Sites scoring near plausible.io

Their neighbours in the SEO rank table, which orders every scanned site by health score.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

This report was produced by the DIY SEO Hub Site Spider crawling plausible.io from its pages as published, the way a search engine does. It shows summary figures only.

Own plausible.io?