Scanned sites / plausible.io / 2026-10-19-0900

plausible.io scan from 2026-10-19 09:00:58 UTC DR 90

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

Scan 2026-10-19-0900

Scanned 2026-10-19 09:00:58 UTC, finished 2026-10-19 09:06:26 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 19, 2026 the Site Spider crawled 455 pages and 576 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 (44), broken links (85), title tags (147); 6 checks passed. Most of the points went to heavy assets (−6), broken links (−4.8), title tags (−4.1). 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
455
Assets fetched
576
Status
Completed
Checks with issues
13 of 33
CoverageComplete crawl

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

  • Title tags147 issues
    147 of 290 pages have title issues. 66 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions155 issues
    155 of 290 pages have meta description issues. 66 noindex or canonicalized pages excluded.
    −3.5 points
  • Headings2 issues
    2 of 290 pages have heading issues. 66 noindex or canonicalized pages excluded.
  • Broken links85 issues
    85 internal links point at 85 broken URLs.
    −4.8 points
  • Links to other sites11 issues
    11 destinations answered with an error, 66 could not be determined (timeouts, rate limits or refusals), 404 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.2 points
  • Redirects13 issues
    14 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses85 issues
    99 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 291 indexable pages have indexability warnings. 65 pages noindex by design.
    −0.1 points
  • Image alt text165 issues
    165 of 1648 image references have no alt attribute. 165 use an empty alt (decorative), which is fine.
    −0.6 points
  • Heavy assets44 issues
    44 assets larger than 500 KB among 576 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 165 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 356 pages; 35 worth a look.
  • Thin content6 issues
    6 of 290 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 455 page URLs are harder to read, share or cache than they need to be.
  • Canonicals69 noted
    69 of 356 pages have a canonical worth checking.
  • Robots directives65 noted
    65 pages carry a robots directive; 291 carry none.
  • Anchor text35 noted
    35 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure68 noted
    68 of 290 pages could use the title, heading and snippet space better. 66 noindex or canonicalized pages excluded.
  • Image weight and alt length304 noted
    299 images over 100 KB; 5 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 356 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
    287 of 290 indexable pages carry structured data: BlogPosting (149), 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 284 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 1031 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 356 pages; 248 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.
  • Spelling247 noted
    247 words an English dictionary does not know, on 218 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2285 sites, median 79%, average 78%

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

0571140%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 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%: 16 sites59%: 7 sites60%: 16 sites61%: 12 sites62%: 19 sites63%: 27 sites64%: 21 sites65%: 32 sites66%: 36 sites67%: 34 sites68%: 35 sites69%: 45 sites70%: 41 sites71%: 68 sites72%: 70 sites73%: 66 sites74%: 70 sites75%: 71 sites76%: 88 sites77%: 91 sites78%: 104 sites79%: 87 sites80%: 106 sites81%: 107 sites82%: 114 sites83%: 95 sites84%: 107 sites85%: 84 sites86%: 67 sites87%: 71 sites88%: 62 sites89%: 61 sites90%: 33 sites91%: 44 sites92%: 34 sites93%: 20 sites94%: 13 sites95%: 10 sites96%: 10 sites97%: 9 sites98%: 4 sites99%: 0 sites100%: 70 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

The site has several technical issues to address, including broken links and missing meta descriptions. Prioritizing these fixes will improve user experience and SEO performance.

  1. 1

    Fix Broken Links

    Why: 85 internal links point to broken URLs, impacting user experience.

    How: Update these links to point to the correct pages or remove them if the destination is no longer valid.

    Checks: broken-links

  2. 2

    Address Non-200 Status Codes

    Why: 99 URLs did not return a 2xx response, affecting crawlers and users.

    How: Identify and resolve the 85 URLs returning errors and ensure they return valid pages.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: 147 pages have title issues which can affect rankings.

    How: Revise titles to be unique, descriptive, and under 60 characters where possible.

    Checks: titles

  4. 4

    Add Meta Descriptions

    Why: 155 pages have meta description issues, limiting click-through rates.

    How: Create unique, engaging meta descriptions for affected pages to improve visibility.

    Checks: meta-descriptions

  5. 5

    Fix Orphan Pages

    Why: 9 pages have no internal links, making them harder to discover.

    How: Add relevant internal links to these pages to improve their accessibility.

    Checks: orphan-pages

  6. 6

    Reduce Heavy Assets

    Why: 44 assets are larger than 500 KB, which can slow page load times.

    How: Optimize these assets by compressing images and scripts to improve loading speeds.

    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

The security review of plausible.io identified several issues that could expose the site to vulnerabilities. Key areas requiring attention include the absence of important HTTP security headers, which increases the risk of attacks like clickjacking and data exposure. Implementing recommended security headers will enhance overall safety.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors accessing the site via HTTP may be intercepted during their initial request.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Absence of this header allows the site to be embedded in a frame, which could lead to clickjacking attacks.

    Fix: Add the header: X-Frame-Options: DENY or FRAME-ANCORS.

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly interpret files based on content rather than declared type, increasing security risks.

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

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer-Policy HeaderLow

    Why it matters: Absence of a referrer policy exposes the full page address, including sensitive query strings, when users navigate away.

    Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade.

    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 356 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 356 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 356 crawled pages were served over HTTPS.

  • OKContent Security Policy

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

  • OKPermissions policy

    permissions-policy is set on all 356 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.

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?