Scanned sites / plausible.io / 2026-11-06-1112
plausible.io scan from 2026-11-06 11:12:33 UTC DR 90
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-11-06-1112
Scanned 2026-11-06 11:12:33 UTC, finished 2026-11-06 11:17:25 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 6, 2026 the Site Spider crawled 465 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
- 465
- Assets fetched
- 556
- Status
- Completed
- Checks with issues
- 13 of 33
1,021 of 1,022 discovered URLs were fetched. 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 295 pages have title issues. 69 noindex or canonicalized pages excluded.−4.1 points
- Meta descriptions160 issues160 of 295 pages have meta description issues. 69 noindex or canonicalized pages excluded.−3.5 points
- Headings2 issues2 of 295 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, 65 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 issues101 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 296 indexable pages have indexability warnings. 68 pages noindex by design.−0.1 points
- Image alt text167 issues167 of 1648 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 coverage134 issues1 sitemap listing 167 URLs: 128 crawled pages missing, 1 listed URL broken or redirecting, 5 reachable only via the sitemap.−2.2 points
- Internal link counts39 notedInternal link counts for 364 pages; 39 worth a look.
- Thin content6 issues6 of 295 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 465 page URLs are harder to read, share or cache than they need to be.
- Canonicals72 noted72 of 364 pages have a canonical worth checking.
- Robots directives68 noted68 pages carry a robots directive; 296 carry none.
- Anchor text35 noted35 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure65 noted65 of 295 pages could use the title, heading and snippet space better. 69 noindex or canonicalized pages excluded.
- Image weight and alt length277 noted266 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 364 pages have HTML problems: 0 with head tags outside <head>, 0 over 2 MB.
- hreflangOK126 pages declare hreflang, with 252 annotations, and every one checks out.
- Structured data19 noted292 of 295 indexable pages carry structured data: BlogPosting (151), BreadcrumbList (125), ListItem (106), 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 289 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 1021 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 364 pages; 258 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.
- Spelling254 noted254 words an English dictionary does not know, on 227 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2867 sites, median 80%, average 79%
plausible.io scores 75%, higher than 29% of the 2867 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 website has several technical issues needing attention, particularly broken links and meta description problems. Addressing these will enhance user experience and SEO performance.
- 1
Fix Broken Links
Why: 86 internal links point to non-existing URLs, affecting user experience and SEO.
How: Identify broken links and update or remove them.
Checks: broken-links
- 2
Update Meta Descriptions
Why: 160 pages have meta description issues, impacting click-through rates.
How: Create unique meta descriptions for pages exceeding length limits and those missing descriptions.
Evidence: 3 pages have no meta description at all.
3 pages affected
Checks: meta-descriptions
- 3
Improve Title Tags
Why: 150 pages have title issues, leading to poor SEO and user clarity.
How: Revise title tags to ensure they are concise and relevant, avoiding duplicates.
Checks: titles
- 4
Address Indexability Warnings
Why: 4 pages have indexability warnings, risking search visibility.
How: Correct canonical tags and ensure appropriate visibility settings.
Checks: indexability
- 5
Fix Orphan Pages
Why: 10 pages have no internal links, making them hard for users to find.
How: Add internal links pointing to these pages from relevant content.
Checks: orphan-pages
- 6
Optimize Heavy Assets
Why: Several large files could slow down website performance.
How: Compress or resize images and scripts to enhance load times.
Evidence: 830 KB of script, loaded by 126 pages, so every visitor to any of them downloads it.
126 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
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 crawlThis security review identifies areas for improving the protection of your website. Addressing these findings will help mitigate risks such as data interception, clickjacking, and unauthorized exposure of information.
- 0 high
- 2 medium
- 2 low
- 0 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Lack of HSTS allows potential interception of first requests if users type the URL without HTTPS.
Fix: Add the header Strict-Transport-Security: max-age=31536000; includeSubDomains to all HTTP responses.
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-Options for Clickjacking ProtectionMedium
Why it matters: Without this header, pages can be framed by malicious sites, risking user data and interactions.
Fix: Add the header X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN to all pages.
Evidence: Clickjacking protection
- 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, risking security.
Fix: Add the header X-Content-Type-Options: nosniff to pages not sending it.
Evidence: MIME sniffing protection
- 4
Missing Referrer-PolicyLow
Why it matters: This absence exposes full page addresses to sites users navigate to, potentially disclosing sensitive data.
Fix: Add the header Referrer-Policy: no-referrer-when-downgrade to all pages.
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 364 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 364 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 364 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 68 of 364 pages.
- OKPermissions policy
permissions-policy is set on all 364 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.
- carrerlift.inDR 2076/100 · rank 1856 · 200 pages
- pdf.fusenv.comDR 4276/100 · rank 1856 · 1 page
- www.dentalchoice.caDR 3575/100 · rank 1951 · 841 pages
- www.mardaloopphysio.comDR 675/100 · rank 1951 · 94 pages
- www.signaturedentistry.caDR 275/100 · rank 1951 · 88 pages
- www.vikinglandscaping.caDR 2775/100 · rank 1951 · 171 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.