Scanned sites / plausible.io / 2026-10-04-0714

plausible.io scan from 10/4/2026, 7:14:03 AM

Scan 2026-10-04-0714

Scanned 10/4/2026, 7:14:03 AM, finished 10/4/2026, 7:34:31 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.

75/ 100Good

On October 4, 2026 the Site Spider crawled 452 pages and 574 assets of plausible.io, starting from https://plausible.io/. It scored 75 out of 100, a good result. 13 of 16 checks found something to fix, led by heavy assets (45), broken links (85), title tags (146); 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
452
Assets fetched
574
Status
Completed
Checks with issues
13 of 16
CoverageComplete crawl

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

  • Title tags146 issues
    146 of 288 pages have title issues. 65 noindex or canonicalized pages excluded.
    −4.1 points
  • Meta descriptions154 issues
    154 of 288 pages have meta description issues. 65 noindex or canonicalized pages excluded.
    −3.5 points
  • Headings2 issues
    2 of 288 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, 64 could not be determined (timeouts, rate limits or refusals), 401 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 289 indexable pages have indexability warnings. 64 pages noindex by design.
    −0.1 points
  • Image alt text164 issues
    164 of 1636 image references have no alt attribute. 164 use an empty alt (decorative), which is fine.
    −0.6 points
  • Heavy assets45 issues
    45 assets larger than 500 KB among 574 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 164 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 353 pages.
  • Thin content6 issues
    6 of 288 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

2057 sites, median 80%, average 78%

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

0511020%: 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%: 2 sites36%: 2 sites37%: 2 sites38%: 3 sites39%: 1 site40%: 1 site41%: 2 sites42%: 0 sites43%: 1 site44%: 1 site45%: 4 sites46%: 4 sites47%: 5 sites48%: 2 sites49%: 4 sites50%: 4 sites51%: 3 sites52%: 9 sites53%: 6 sites54%: 8 sites55%: 6 sites56%: 6 sites57%: 7 sites58%: 14 sites59%: 6 sites60%: 11 sites61%: 13 sites62%: 16 sites63%: 20 sites64%: 18 sites65%: 30 sites66%: 24 sites67%: 41 sites68%: 35 sites69%: 25 sites70%: 43 sites71%: 48 sites72%: 65 sites73%: 54 sites74%: 58 sites75%: 75 sites76%: 82 sites77%: 77 sites78%: 97 sites79%: 82 sites80%: 102 sites81%: 102 sites82%: 102 sites83%: 90 sites84%: 86 sites85%: 73 sites86%: 73 sites87%: 70 sites88%: 66 sites89%: 51 sites90%: 37 sites91%: 42 sites92%: 29 sites93%: 18 sites94%: 16 sites95%: 7 sites96%: 7 sites97%: 8 sites98%: 1 site99%: 2 sites100%: 56 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

Several issues need fixing to improve your site's SEO performance including broken links, confusing redirects, and ineffective metadata. Addressing these will enhance user experience and site visibility.

  1. 1

    Fix Broken Links

    Why: Improves user experience and reduces 404 errors.

    How: Update internal links that point to broken URLs or remove links if pages have been permanently deleted.

    Checks: broken-links

  2. 2

    Optimize Meta Descriptions

    Why: Enhances search visibility and click-through rates.

    How: Create unique and concise meta descriptions for pages lacking them or those with duplicates.

    Checks: meta-descriptions

  3. 3

    Revise Title Tags

    Why: Improves SEO and user engagement by aligning titles with content.

    How: Revise title tags that are too long, too short, or duplicated across multiple pages.

    Checks: titles

  4. 4

    Improve Sitemap Coverage

    Why: Ensures search engines can discover all relevant pages.

    How: Add missing URLs to the sitemap and correct any URLs that are broken or redirecting.

    Checks: sitemap-coverage

  5. 5

    Shrink Heavy Assets

    Why: Improves page load speeds, enhancing user experience.

    How: Compress or optimize large images and scripts to reduce their file sizes.

    Checks: heavy-assets

  6. 6

    Add H1 Tags

    Why: Improves page structure and SEO.

    How: Insert relevant H1 tags on pages missing them to ensure proper heading hierarchy.

    Checks: headings

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 website lacks essential security headers that can protect users from various attacks. Implementing these headers will enhance protection against potential vulnerabilities, ensuring a safer browsing experience.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, first-time visitors typing the address without HTTPS can be intercepted.

    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: Without this header, the site is vulnerable to clickjacking attacks.

    Fix: Add the header 'X-Frame-Options: DENY' or use a Content Security Policy with 'frame-ancestors'.

    Evidence: Clickjacking protection

  3. 3

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly interpret file types, leading to vulnerabilities.

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

    Evidence: MIME sniffing protection

  4. 4

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a referrer policy, sensitive information about page addresses is shared with other 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 353 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 353 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 353 crawled pages were served over HTTPS.

  • OKContent Security Policy

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

  • OKPermissions policy

    permissions-policy is set on all 353 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-04-0714 | DIY SEO Hub