Scanned sites / plausible.io / 2026-09-19-0411
plausible.io scan from 9/19/2026, 4:11:46 AM
Scan 2026-09-19-0411
Scanned 9/19/2026, 4:11:46 AM, finished 9/19/2026, 4:46: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.
On September 19, 2026 the Site Spider crawled 446 pages and 581 assets of plausible.io, starting from https://plausible.io/. It scored 77 out of 100, a good result. 12 of 14 checks found something to fix, led by image alt text (163), title tags (145), sitemap coverage (130); 2 checks passed. 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
- 446
- Assets fetched
- 581
- Status
- Completed
- Checks with issues
- 12 of 14
- Title tags145 issues145 of 287 pages have title issues. 62 noindex or canonicalized pages excluded.
- Meta descriptions96 issues96 of 287 pages have meta description issues. 62 noindex or canonicalized pages excluded.
- Headings2 issues2 of 287 pages have heading issues. 62 noindex or canonicalized pages excluded.
- Broken links84 issues84 internal links point at 84 broken URLs.
- Redirects12 issues13 redirecting URLs, 0 of them chained.
- Non-200 responses84 issues99 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability4 issues4 of 288 indexable pages have indexability warnings. 61 pages noindex by design.
- Image alt text163 issues163 of 1626 image references have no alt attribute. 163 use an empty alt (decorative), which is fine.
- Heavy assets45 issues45 assets larger than 500 KB among the 100 heaviest.
- Orphan pages8 issues8 pages have no internal links pointing at them.
- Sitemap coverage130 issues1 sitemap listing 163 URLs: 124 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.
- Thin content6 issues6 of 287 pages have fewer than 200 words. 62 noindex or canonicalized pages excluded.
- Duplicate contentOK0 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1099 sites, median 82%, average 80%
plausible.io scores 77%, higher than 30% of the 1099 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe site shows a good health score but has several issues affecting SEO performance. Prioritize resolving broken links and title issues for maximum impact.
- 1
Fix Broken Links
Why: 84 internal links point to broken URLs, harming user experience and SEO.
How: Identify broken links and update or remove them from menus and content.
Checks: broken-links
- 2
Address Non-200 Responses
Why: 99 URLs return non-200 responses affecting accessibility and user experience.
How: Check these URLs and correct status codes or update links leading to them.
Checks: status-codes
- 3
Optimize Title Tags
Why: 145 title tag issues can confuse search engines and users, impacting CTR.
How: Revise titles to meet best practices: ensure unique, relevant, and within 60 characters.
Checks: titles
- 4
Improve Meta Descriptions
Why: 96 meta description issues limit click-through rates from search results.
How: Rewrite to be unique, relevant, and under 160 characters for each page.
Checks: meta-descriptions
- 5
Fix Sitemap Coverage
Why: The sitemap does not include 124 pages, missing valuable indexable content.
How: Update the sitemap to reflect all important URLs and ensure it doesn’t list broken URLs.
Checks: sitemap-coverage
- 6
Resolve Orphan Pages
Why: 8 orphan pages lack internal links, making them hard to discover for users and search engines.
How: Add internal links to these pages from relevant content across the site.
Checks: orphan-pages
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 crawlPlausible.io needs to enhance its security headers to protect user data and prevent vulnerabilities. Key issues include the lack of HTTP Strict Transport Security, clickjacking protection, and MIME sniffing protection across multiple pages. Addressing these findings will improve overall site security.
- 0 high
- 2 medium
- 2 low
- 0 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be vulnerable to interception when typing the URL without 'https://'.
Fix: Add the header 'Strict-Transport-Security' with value 'max-age=31536000; includeSubDomains; preload'.
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-Options HeaderMedium
Why it matters: Lack of this header allows clickjacking attacks, where malicious pages can embed your site in a frame.
Fix: Add the header 'X-Frame-Options' with value 'DENY' or 'SAMEORIGIN'.
Evidence: Clickjacking protection
- 3
Missing X-Content-Type-Options HeaderLow
Why it matters: Without this header, browsers may execute files incorrectly based on their content rather than declared type.
Fix: Add the header 'X-Content-Type-Options' with value 'nosniff'.
Evidence: MIME sniffing protection
- 4
Missing Referrer-Policy HeaderLow
Why it matters: Not having a referrer-policy can expose sensitive information when users navigate away from your site.
Fix: Add the header 'Referrer-Policy' with value '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
61 of 349 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
61 of 349 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 349 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 61 of 349 pages.
- OKPermissions policy
permissions-policy is set on all 349 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.
This report was produced by the DIY SEO Hub Site Spider crawling plausible.io from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.