Scanned sites / www.pringlelaw.ca
SEO report for www.pringlelaw.ca
The latest Site Spider scan of www.pringlelaw.ca, with 2 scans on record. Each scan is at its own address, for example /domain/www-pringlelaw-ca/2026-10-02-0026.
Latest scan
Scanned 10/2/2026, 12:26:35 AM, finished 10/2/2026, 12:45:26 AM. Found on page 4 of brave web search results
Site: https://www.pringlelaw.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On October 2, 2026 the Site Spider crawled 69 pages and 6 assets of www.pringlelaw.ca, starting from https://www.pringlelaw.ca/. It scored 63 out of 100, a result that needs work. 5 of 16 checks found something to fix, led by broken links (67), non-200 responses (67), meta descriptions (1); 10 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), meta descriptions (−4). 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓
- Pages crawled
- 69
- Assets fetched
- 6
- Status
- Completed
- Checks with issues
- 5 of 16
75 of 75 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 5 link destinations on other sites were checked.
- Title tagsOK0 of 2 pages have title issues.
- Meta descriptions1 issue1 of 2 pages have meta description issues.−4 points
- HeadingsOK0 of 2 pages have heading issues.
- Broken links67 issues122 internal links point at 67 broken URLs.−20 points
- Links to other sites1 issue1 destination answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 5 destinations checked.−0.4 points
- RedirectsOK0 redirecting URLs, 0 of them chained.
- Non-200 responses67 issues70 URLs did not return a 2xx response. 67 of them are pages, 67 with an error status; the rest are assets or redirects.−10 points
- Rate limitedOKThe site did not rate limit the crawler.
- IndexabilityOK0 of 2 indexable pages have indexability warnings.
- Image alt textOK0 of 25 image references have no alt attribute. 13 use an empty alt (decorative), which is fine.
- Heavy assetsOK0 assets larger than 500 KB among 6 fetched assets.
- Orphan pagesOK0 pages have no internal links pointing at them.
- Sitemap coverage1 issueNo sitemap found. Tried: https://www.pringlelaw.ca/sitemap.xml (403), https://www.pringlelaw.ca/sitemap_index.xml (403). Add one at /sitemap.xml or list it in robots.txt.−3 points
- Internal link countsOKInternal link counts for 2 pages.
- Thin contentOK0 of 2 pages have fewer than 200 words.
- Duplicate contentOK0 groups of pages with identical HTML.
What changed since the last scan
-20 pointswww.pringlelaw.ca lost 20 points since the previous scan, moving from 83 to 63 out of 100. 238 findings changed. 67 URLs the earlier crawl reached were not reached this time. The crawl reached 44 fewer pages than last time, 69 in total, so some of the change is a change in what was crawled.
- Pages: 66 gone, 12 not re-checked
- Broken links: 67 new, 1 not re-checked
- Page status codes: 32 gone, 67 changed
- Redirects: 2 gone, 13 not re-checked
- Internal links to the page: 2 changed
- Sitemap inclusion: 2 changed
- 67 URLs from the earlier crawl were not reached this time
- 10/1/2026, 5:11:33 PM83/100113 pages
- 10/2/2026, 12:26:35 AM63/10069 pages
Where this site sits among all scanned sites
1645 sites, median 80%, average 79%
www.pringlelaw.ca scores 63%, higher than 7% of the 1645 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 broken internal links and URLs returning errors. Fixing these will improve user experience and SEO performance. Additionally, you'll need to create a sitemap and address a missing meta description.
- 1
Fix Broken Links
Why: Correcting broken links enhances user experience and site credibility.
How: Identify the broken links and either restore the pages or remove the links from the site.
Checks: broken-links
- 2
Fix Non-200 Response URLs
Why: Resolving these ensures all your pages are accessible and improves indexing.
How: Investigate URLs returning error responses and either fix or remove them according to your strategy.
Checks: status-codes
- 3
Add a Sitemap
Why: A sitemap helps search engines index your pages effectively.
How: Create a sitemap and make it accessible at /sitemap.xml. List it in your robots.txt.
Checks: sitemap-coverage
- 4
Address Missing Meta Description
Why: A meta description helps improve click-through rates from search results.
How: Add a clear and concise meta description for the page missing it.
Checks: meta-descriptions
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 that protect against interception, clickjacking, and data leaks. Implementing these headers can significantly enhance the site's security and user privacy.
- 0 high
- 3 medium
- 4 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, users can be intercepted on initial requests typing the address without HTTPS.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains
Evidence: HTTP Strict Transport Security
- 2
Missing Content Security Policy (CSP)Medium
Why it matters: Lack of CSP allows scripts and styles to load from any source, increasing risk of XSS attacks.
Fix: Add the header: Content-Security-Policy: default-src 'self';
Evidence: Content Security Policy
- 3
Missing X-Frame-OptionsMedium
Why it matters: Without X-Frame-Options, the site is vulnerable to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY
Evidence: Clickjacking protection
- 4
Missing X-Content-Type-OptionsLow
Why it matters: Without this header, browsers may execute files as scripts based on content rather than type.
Fix: Add the header: X-Content-Type-Options: nosniff
Evidence: MIME sniffing protection
- 5
Missing Referrer PolicyLow
Why it matters: No Referrer-Policy can expose sensitive URL information when navigating to other sites.
Fix: Add the header: Referrer-Policy: no-referrer
Evidence: Referrer policy
- 6
X-Powered-By Header Exposing FrameworkLow
Why it matters: Revealing the framework may help attackers in tailored attacks.
Fix: Consider removing or modifying the header: X-Powered-By.
Evidence: Software version disclosure
- 7
Third-Party Scripts Without Subresource IntegrityLow
Why it matters: Third-party script vulnerabilities can compromise site integrity without SRI.
Fix: Implement a Content Security Policy that allows only trusted sources and consider adding SRI.
Evidence: Third-party scripts
- 8
Missing Permissions PolicyInfo
Why it matters: This header can limit what browser features are accessible, reducing risks from injected scripts.
Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(), camera=()
Evidence: Permissions 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://www.pringlelaw.ca/ → no strict-transport-security
- https://www.pringlelaw.ca/lawyers/tania-shapka/ → no strict-transport-security
- FoundContent Security PolicyMedium
None of the 2 HTML pages send a Content-Security-Policy header or meta tag, so the browser has no restriction on where scripts, styles and frames may load from.
- https://www.pringlelaw.ca/ → no content-security-policy
- https://www.pringlelaw.ca/lawyers/tania-shapka/ → no content-security-policy
- 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://www.pringlelaw.ca/ → no x-frame-options
- https://www.pringlelaw.ca/lawyers/tania-shapka/ → no x-frame-options
- FoundMIME sniffing protectionLow
No HTML page sends 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://www.pringlelaw.ca/ → no x-content-type-options
- https://www.pringlelaw.ca/lawyers/tania-shapka/ → no x-content-type-options
- FoundReferrer policyLow
No HTML page sends 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://www.pringlelaw.ca/ → no referrer-policy
- https://www.pringlelaw.ca/lawyers/tania-shapka/ → no referrer-policy
- FoundPermissions policyInfo
No HTML page sends permissions-policy. A Permissions-Policy header turns off browser features the site does not use (camera, microphone, geolocation), limiting what an injected script could do.
- https://www.pringlelaw.ca/ → no permissions-policy
- https://www.pringlelaw.ca/lawyers/tania-shapka/ → no permissions-policy
- NoteSoftware version disclosure
Responses name the framework in an X-Powered-By header but hide the version.
- server: nginx (75 responses)
- x-powered-by: WP Engine (72 responses)
- NoteThird-party scripts
Scripts run from 3 other domains without Subresource Integrity, so a compromise of any of them changes what runs on this site. (Tag managers and analytics rarely support SRI; a Content-Security-Policy that names these hosts is the usual control.)
- www.googletagmanager.com (2 script tags)
- pcst.wpenginepowered.com (38 script tags)
- www.google.com (2 script tags)
7 checks passed, 1 not applicable
- OKHTTPS
All 2 crawled pages were served over HTTPS.
- 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.
- OKVulnerable JavaScript libraries
1 library version recognised, none with known vulnerabilities.
- 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.
- OKSensitive paths in robots.txt
robots.txt does not point at admin, backup or private paths.
- Not applicableCookie flags
The crawl set no cookies, so there are no cookie flags to check.
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.
Earlier scans of www.pringlelaw.ca
- 10/1/2026, 5:11:33 PM (2026-10-01-1711)Score 83 · 113 pages
Sites scoring near www.pringlelaw.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- karmagroup.com64/100 · rank 1500 · 3,837 pages
- www.borealpeonies.com64/100 · rank 1500 · 12 pages
- slaaay.lol64/100 · rank 1500 · 40 pages
- www.delgadoaccounting.com63/100 · rank 1510 · 2 pages
- www.naturalenvironmentslandscaping.com63/100 · rank 1510 · 299 pages
- fossumelectric.com63/100 · rank 1510 · 59 pages
This report was produced by the DIY SEO Hub Site Spider crawling www.pringlelaw.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own www.pringlelaw.ca?
- 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 www.pringlelaw.ca. Removal needs no account and no proof of purchase.