Scanned sites / plausible.io / 2026-09-13-0311

plausible.io scan from 2026-09-13 03:11:41 UTC DR 90

A newer scan exists. See the latest report for plausible.io.

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

Scan 2026-09-13-0311

Scanned 2026-09-13 03:11:41 UTC, finished 2026-09-13 04:00:35 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 September 13, 2026 the Site Spider crawled 445 pages and 573 assets of plausible.io, starting from https://plausible.io/. It scored 75 out of 100, a good result. 13 of 27 checks found something to fix, led by heavy assets (45), broken links (84), title tags (144); 4 checks passed. Most of the points went to heavy assets (−6), broken links (−4.8), title tags (−4.1). 10 checks found something the score does not count, listed as noted. 10 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 1 low findings. See the security findings ↓

Pages crawled
445
Assets fetched
573
Status
Completed
Checks with issues
13 of 27
CoverageComplete crawl

1,018 of 1,019 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 302 link destinations on other sites were checked, 381 left unchecked.

  • Title tags144 issues
    144 of 286 pages have title issues. 62 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions153 issues
    153 of 286 pages have meta description issues. 62 noindex or canonicalized pages excluded.
    −3.5 points
  • Headings2 issues
    2 of 286 pages have heading issues. 62 noindex or canonicalized pages excluded.
  • Broken links84 issues
    84 internal links point at 84 broken URLs.
    −4.8 points
  • Links to other sites10 issues
    10 destinations answered with an error, 66 could not be determined (timeouts, rate limits or refusals), 381 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.1 points
  • Redirects12 issues
    13 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses84 issues
    97 URLs did not return a 2xx response. 97 of them are pages, 84 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 287 indexable pages have indexability warnings. 61 pages noindex by design.
    −0.1 points
  • Image alt text162 issues
    162 of 1622 image references have no alt attribute. 162 use an empty alt (decorative), which is fine.
    −0.6 points
  • Heavy assets45 issues
    45 assets larger than 500 KB among 573 fetched assets.
    −6 points
  • Orphan pages8 issues
    8 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage130 issues
    1 sitemap listing 162 URLs: 124 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.
    −2.2 points
  • Internal link counts33 noted
    Internal link counts for 348 pages; 33 worth a look.
  • Thin content6 issues
    6 of 286 pages have fewer than 200 words. 62 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format57 noted
    57 of 445 page URLs are harder to read, share or cache than they need to be.
  • Canonicals65 noted
    65 of 348 pages have a canonical worth checking.
  • Robots directives61 noted
    61 pages carry a robots directive; 287 carry none.
  • Anchor text35 noted
    35 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure65 noted
    65 of 286 pages could use the title, heading and snippet space better. 62 noindex or canonicalized pages excluded.
  • Image weight and alt length304 noted
    302 images over 100 KB; 2 with alt text over 100 characters.
  • Response anomalies4 noted
    4 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 12 response headers recorded across 1018 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 348 pages; 241 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 Insights1 noted
    Mobile performance 99 on average across 5 pages; 1 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2337 sites, median 79%, average 78%

plausible.io scores 75%, higher than 31% of the 2337 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%: 108 sites81%: 105 sites82%: 115 sites83%: 99 sites84%: 106 sites85%: 87 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your website has notable areas for improvement, particularly in broken links, meta descriptions, and title tags. Addressing these will enhance user experience and SEO. The health score is good, but addressing the issues listed below will help boost it further.

  1. 1

    Fix Broken Links

    Why: 84 internal links are broken, harming user experience and SEO.

    How: Identify each broken link and replace or remove them from the relevant pages.

    Checks: broken-links

  2. 2

    Correct Meta Descriptions

    Why: 96 pages have meta issues, which may affect click-through rates.

    How: Revise the meta descriptions, ensuring each is unique and under 160 characters.

    Checks: meta-descriptions

  3. 3

    Improve Title Tags

    Why: 144 pages have title issues, impacting search visibility.

    How: Review and optimize title tags to be unique and between 30-60 characters.

    Checks: titles

  4. 4

    Resolve Non-200 Responses

    Why: 97 URLs have issues, affecting site accessibility and SEO.

    How: Check each URL's response, correcting any 404 or misconfigured links.

    Checks: status-codes

  5. 5

    Add Headings to Missing H1s

    Why: Pages without H1 tags can confuse search engines and users.

    How: Add relevant H1 tags to the affected pages.

    Checks: headings

  6. 6

    Enhance Sitemap Coverage

    Why: Sitemap issues can prevent search engines from crawling all pages.

    How: Update the sitemap to include all relevant URLs and ensure it doesn't list redirected or broken URLs.

    Checks: sitemap-coverage

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 site has important security vulnerabilities affecting user data and clickjacking protection. Implementing proper security headers is crucial to protect users from potential attacks. Immediate attention is recommended for the missing HTTP Strict Transport Security (HSTS) and X-Frame-Options headers.

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

    Missing HTTP Strict Transport Security (HSTS) HeaderMedium

    Why it matters: Without HSTS, users typing the address without HTTPS may be vulnerable to interception on their first request.

    Fix: Add the HSTS header: "Strict-Transport-Security: max-age=31536000; includeSubDomains" to all server responses.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without this header, the site's pages can be embedded in frames, increasing the risk of clickjacking attacks.

    Fix: Set the X-Frame-Options header: "X-Frame-Options: DENY" or use a CSP with "frame-ancestors" to protect against this vulnerability.

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Absence of this header increases risk of browsers incorrectly handling file types, potentially executing unsafe files as scripts.

    Fix: Add the X-Content-Type-Options header: "X-Content-Type-Options: nosniff" to all server responses, especially HTML.

    Evidence: MIME sniffing protection

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

    61 of 348 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
9 checks passed, 4 not applicable
  • OKHTTPS

    All 348 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 61 of 348 pages.

  • OKSoftware version disclosure

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

  • 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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