Scanned sites / plausible.io / 2026-09-16-0401
plausible.io scan from 9/16/2026, 4:01:44 AM
Scan 2026-09-16-0401
Scanned 9/16/2026, 4:01:44 AM, finished 9/16/2026, 4:10:02 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 16, 2026 the Site Spider crawled 445 pages and 573 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 (162), title tags (144), 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
- 445
- Assets fetched
- 573
- Status
- Completed
- Checks with issues
- 12 of 14
- Title tags144 issues144 of 286 pages have title issues. 62 noindex or canonicalized pages excluded.
- Meta descriptions96 issues96 of 286 pages have meta description issues. 62 noindex or canonicalized pages excluded.
- Headings2 issues2 of 286 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 issues97 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability4 issues4 of 287 indexable pages have indexability warnings. 61 pages noindex by design.
- Image alt text162 issues162 of 1622 image references have no alt attribute. 162 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 162 URLs: 124 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.
- Thin content6 issues6 of 286 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
1059 sites, median 82%, average 80%
plausible.io scores 77%, higher than 30% of the 1059 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 findingsYour site has several issues that require attention, especially broken links and redirects. Improving title tags and meta descriptions will also enhance SEO performance. Focus on resolving the most critical findings first.
- 1
Fix Broken Links
Why: 84 internal links are broken, negatively impacting user experience and SEO.
How: Identify broken URLs and either update them to existing pages or remove the links.
Checks: broken-links
- 2
Address Non-200 Responses
Why: 97 URLs returned non-200 responses, which can hurt rankings.
How: Review and redirect or fix the URLs returning errors.
Checks: status-codes
- 3
Optimize Title Tags
Why: 144 pages have title issues, which can affect search visibility.
How: Update titles to be unique, accurately reflect page content, and stay within optimal length (60 characters).
Checks: titles
- 4
Improve Meta Descriptions
Why: 96 pages have meta description issues, impacting click-through rates.
How: Rewrite them to be compelling, unique, and under 160 characters.
Checks: meta-descriptions
- 5
Resolve Redirects
Why: 13 URLs are redirecting, which may dilute page authority.
How: Ensure redirects serve relevant and updated content and remove unnecessary ones.
Checks: redirects
- 6
Fix Orphan Pages
Why: 8 orphan pages have no internal links and are hard to discover.
How: Add internal links pointing to these pages from relevant content.
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 crawlYour website has several important security headers missing that protect against various types of attacks, including interception, clickjacking, and data leaks. It is crucial to add these headers to improve the security posture of your site.
- 0 high
- 2 medium
- 2 low
- 0 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted when typing the address without HTTPS.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-Options headerMedium
Why it matters: The lack of this header makes your pages vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 3
Missing X-Content-Type-Options headerLow
Why it matters: This could lead to serious vulnerabilities if files are interpreted incorrectly by browsers.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 4
Missing Referrer-Policy headerLow
Why it matters: Without it, full URLs of pages are shared with third-party sites.
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
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
- FoundReferrer policyLow
61 of 348 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 348 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 61 of 348 pages.
- OKPermissions policy
permissions-policy is set on all 348 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.