Scanned sites / plausible.io / 2026-11-03-0934
plausible.io scan from 2026-11-03 09:34:02 UTC DR 90
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-11-03-0934
Scanned 2026-11-03 09:34:02 UTC, finished 2026-11-03 11:11:15 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.
On November 3, 2026 the Site Spider crawled 464 pages and 556 assets of plausible.io, starting from https://plausible.io/. It scored 75 out of 100, a good result. 13 of 33 checks found something to fix, led by heavy assets (32), broken links (86), title tags (150); 6 checks passed. Most of the points went to heavy assets (−6), broken links (−4.7), title tags (−4.1). 14 checks found something the score does not count, listed as noted. 4 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 2 low findings. See the security findings ↓
- Pages crawled
- 464
- Assets fetched
- 556
- Status
- Completed
- Checks with issues
- 13 of 33
1,020 of 1,021 discovered URLs were fetched, 1 failed. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 434 left unchecked.
- Title tags150 issues150 of 294 pages have title issues. 69 noindex or canonicalized pages excluded.−4.1 points
- Meta descriptions159 issues159 of 294 pages have meta description issues. 69 noindex or canonicalized pages excluded.−3.5 points
- Headings2 issues2 of 294 pages have heading issues. 69 noindex or canonicalized pages excluded.
- Broken links86 issues86 internal links point at 86 broken URLs.−4.7 points
- Links to other sites11 issues11 destinations answered with an error, 69 could not be determined (timeouts, rate limits or refusals), 434 were left unchecked by the per-scan cap, of 300 destinations checked.−1.2 points
- Redirects14 issues15 redirecting URLs, 0 of them chained.−0.2 points
- Non-200 responses86 issues102 URLs did not return a 2xx response. 101 of them are pages, 86 with an error status; the rest are assets or redirects.−2.4 points
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability4 issues4 of 295 indexable pages have indexability warnings. 68 pages noindex by design.−0.1 points
- Image alt text167 issues167 of 1645 image references have no alt attribute. 167 use an empty alt (decorative), which is fine.−0.6 points
- Heavy assets32 issues32 assets larger than 500 KB among 556 fetched assets.−6 points
- Orphan pages10 issues10 pages have no internal links pointing at them.−0.1 points
- Sitemap coverage133 issues1 sitemap listing 167 URLs: 127 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.−2.2 points
- Internal link counts38 notedInternal link counts for 363 pages; 38 worth a look.
- Thin content6 issues6 of 294 pages have fewer than 200 words. 69 noindex or canonicalized pages excluded.−0.1 points
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format64 noted64 of 464 page URLs are harder to read, share or cache than they need to be.
- Canonicals72 noted72 of 363 pages have a canonical worth checking.
- Robots directives68 noted68 pages carry a robots directive; 295 carry none.
- Anchor text35 noted35 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure65 noted65 of 294 pages could use the title, heading and snippet space better. 69 noindex or canonicalized pages excluded.
- Image weight and alt length276 noted265 images over 100 KB; 11 with alt text over 100 characters.
- Response anomalies4 noted4 URLs answered in a way worth looking at.
- HTML and head validation2 noted2 of 363 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
- hreflangOK125 pages declare hreflang, with 250 annotations, and every one checks out.
- Structured data19 noted291 of 294 indexable pages carry structured data: BlogPosting (151), BreadcrumbList (124), ListItem (105), WebPage (15), FAQPage (8). 19 pages with errors a rich result would fail on.
- Near duplicates2 noted2 pages in 1 group read almost the same as another page (95% alike or more).
- Soft 404s2 noted2 pages answer 200 but say they are not there.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions2 noted2 of 288 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookiesOK2 cookies set by the site; 14 response headers recorded across 1020 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 363 pages; 259 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 InsightsNot checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling253 noted253 words an English dictionary does not know, on 226 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2731 sites, median 80%, average 79%
plausible.io scores 75%, higher than 30% of the 2731 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 has several issues to address, including broken links, title and meta description problems, and heavy assets that need optimization. Prioritizing these will improve user experience and SEO performance.
- 1
Fix Broken Links
Why: 86 internal links lead to broken URLs, damaging user experience and SEO.
How: Update or remove internal links that point to broken URLs. Cross-check the links to ensure they direct to valid pages.
Checks: broken-links
- 2
Optimize Heavy Assets
Why: Large assets slow down loading time, affecting user experience.
How: Compress and optimize the specified heavy assets to reduce load time, especially scripts and images.
Evidence: 830 KB of script, loaded by 125 pages, so every visitor to any of them downloads it.
125 pages affected
Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.
Checks: heavy-assets
- 3
Revise Title Tags
Why: 150 pages have title issues, which can harm search visibility.
How: Modify titles to be within optimal length (50-60 characters) and ensure uniqueness.
Checks: titles
- 4
Update Meta Descriptions
Why: 159 pages have meta description issues, impacting click-through rates.
How: Create or adjust meta descriptions to be engaging and within the recommended length (150-160 characters).
Evidence: 3 pages have no meta description at all.
3 pages affected
Checks: meta-descriptions
- 5
Address Sitemap Coverage Issues
Why: 127 URLs are missing from the sitemap, hindering discoverability.
How: Ensure all relevant pages are listed in the sitemap and remove broken or redirecting URLs.
Checks: sitemap-coverage
- 6
Resolve Heading Issues
Why: Missing H1 tags can affect SEO and user navigation.
How: Add a relevant H1 tag to the pages missing headings to enhance structure.
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 crawlThe website lacks several important security headers, which can expose users to various attacks. Implementing these headers is crucial to enhance security and privacy for your visitors.
- 0 high
- 2 medium
- 2 low
- 0 info
- 1
HTTP Strict Transport Security (HSTS) MissingMedium
Why it matters: Without HSTS, users typing the address without HTTPS can be intercepted during their first request.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload.
Evidence: HTTP Strict Transport Security
- 2
Clickjacking Protection MissingMedium
Why it matters: Without 'X-Frame-Options', your pages can be framed and potentially manipulated by attackers.
Fix: Add the header: X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN.
Evidence: Clickjacking protection
- 3
MIME Sniffing Protection MissingLow
Why it matters: Lack of 'X-Content-Type-Options' may allow browsers to misinterpret contents and run unsafe files.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 4
Referrer Policy MissingLow
Why it matters: Not having a 'Referrer-Policy' sends full URLs to external sites, potentially leaking sensitive information.
Fix: Add the header: Referrer-Policy: no-referrer-when-downgrade or proper alternatives.
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
68 of 363 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
68 of 363 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 363 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 68 of 363 pages.
- OKPermissions policy
permissions-policy is set on all 363 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.
- pastryperfection.comDR 1376/100 · rank 1737 · 47 pages
- carrerlift.inDR 2076/100 · rank 1737 · 200 pages
- pdf.fusenv.comDR 4276/100 · rank 1737 · 1 page
- www.vikinglandscaping.caDR 2775/100 · rank 1833 · 171 pages
- www.silverwooddental.comDR 775/100 · rank 1833 · 332 pages
- www.lapetitemaisonrmt.comDR 075/100 · rank 1833 · 13 pages
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?
- Claim this site to manage the listing, hide it from the public lists, or keep it.
- Want it gone instead? Ask through the support form or e-mail support@diyseohub.com, naming plausible.io. Removal needs no account and no proof of purchase.