Scanned sites / plausible.io / 2026-10-01-0600

plausible.io scan from 10/1/2026, 6:00:31 AM

Scan 2026-10-01-0600

Scanned 10/1/2026, 6:00:31 AM, finished 10/1/2026, 7:13:03 AM. 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.

76/ 100Good

On October 1, 2026 the Site Spider crawled 451 pages and 579 assets of plausible.io, starting from https://plausible.io/. It scored 76 out of 100, a good result. 13 of 16 checks found something to fix, led by heavy assets (45), broken links (85), title tags (145); 2 checks passed. Most of the points went to heavy assets (−6), broken links (−4.8), title tags (−4.1). 1 check found something the score does not count, listed as noted. 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
451
Assets fetched
579
Status
Completed
Checks with issues
13 of 16
CoverageComplete crawl

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

  • Title tags145 issues
    145 of 287 pages have title issues. 65 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions153 issues
    153 of 287 pages have meta description issues. 65 noindex or canonicalized pages excluded.
    −3.5 points
  • Headings2 issues
    2 of 287 pages have heading issues. 65 noindex or canonicalized pages excluded.
  • Broken links85 issues
    85 internal links point at 85 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), 385 were left unchecked by the per-scan cap, of 300 destinations checked.
    −1.1 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 288 indexable pages have indexability warnings. 64 pages noindex by design.
    −0.1 points
  • Image alt text163 issues
    163 of 1632 image references have no alt attribute. 163 use an empty alt (decorative), which is fine.
    −0.6 points
  • Heavy assets45 issues
    45 assets larger than 500 KB among 579 fetched assets.
    −6 points
  • Orphan pages9 issues
    9 pages have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage130 issues
    1 sitemap listing 163 URLs: 124 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.
    −2.2 points
  • Internal link countsOK
    Internal link counts for 352 pages.
  • Thin content6 issues
    6 of 287 pages have fewer than 200 words. 65 noindex or canonicalized pages excluded.
    −0.1 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1478 sites, median 80%, average 79%

plausible.io scores 76%, higher than 31% of the 1478 scanned sites. See the full ranking.

046920%: 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%: 0 sites15%: 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%: 0 sites34%: 0 sites35%: 1 site36%: 1 site37%: 2 sites38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 3 sites50%: 3 sites51%: 5 sites52%: 6 sites53%: 5 sites54%: 5 sites55%: 3 sites56%: 5 sites57%: 5 sites58%: 10 sites59%: 5 sites60%: 8 sites61%: 11 sites62%: 15 sites63%: 14 sites64%: 8 sites65%: 15 sites66%: 15 sites67%: 26 sites68%: 24 sites69%: 18 sites70%: 34 sites71%: 34 sites72%: 44 sites73%: 34 sites74%: 42 sites75%: 47 sites76%: 54 sites77%: 50 sites78%: 69 sites79%: 54 sites80%: 74 sites81%: 92 sites82%: 74 sites83%: 69 sites84%: 64 sites85%: 49 sites86%: 53 sites87%: 49 sites88%: 52 sites89%: 38 sites90%: 30 sites91%: 33 sites92%: 19 sites93%: 9 sites94%: 11 sites95%: 7 sites96%: 6 sites97%: 5 sites98%: 1 site99%: 2 sites100%: 52 sites76% 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 issues that need addressing, including broken links and meta description problems. The following prioritized fixes will have the most significant impact with manageable effort.

  1. 1

    Fix Broken Links

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

    How: Identify and update the links to point to active pages or remove them if unnecessary.

    Checks: broken-links

  2. 2

    Address Non-200 Responses

    Why: 99 URLs returned non-200 responses, affecting site accessibility and SEO.

    How: Review and fix or remove these URLs to ensure they return a 200 status.

    Checks: status-codes

  3. 3

    Improve Meta Descriptions

    Why: 153 pages have meta description issues which can impact click-through rates.

    How: Craft unique and engaging meta descriptions for affected pages that are under 160 characters.

    Checks: meta-descriptions

  4. 4

    Add Missing Headings

    Why: Missing H1 tags on 2 pages can affect SEO and accessibility.

    How: Insert an H1 tag to those pages with descriptive content relevant to the page.

    Checks: headings

  5. 5

    Update Sitemap Coverage

    Why: 124 URLs aren’t listed in the sitemap, reducing discoverability.

    How: Ensure all crawled and indexable pages are included in the sitemap or update accordingly.

    Checks: sitemap-coverage

  6. 6

    Optimize Heavy Assets

    Why: Large assets can slow down page load times, affecting user experience.

    How: Compress or resize images and scripts that exceed 500 KB.

    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 weaknesses in security configurations that could expose users to risks, such as interception on initial visits or clickjacking attacks. Addressing these issues will enhance your site's security posture.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users can be intercepted if they access your site using HTTP instead of HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing X-Frame-Options for Clickjacking ProtectionMedium

    Why it matters: Lack of this header allows embedding of your pages in frames, making them vulnerable to clickjacking.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options (MIME Sniffing Protection)Low

    Why it matters: Without this header, browsers may execute files as scripts based on content rather than type.

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

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive URL information may be leaked to external sites.

    Fix: Add the 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

    64 of 352 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

    64 of 352 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 352 crawled pages were served over HTTPS.

  • OKContent Security Policy

    A Content-Security-Policy is set on 64 of 352 pages.

  • OKPermissions policy

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

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?

plausible.io scan 2026-10-01-0600 | DIY SEO Hub