Scanned sites / www.pringlelaw.ca / 2026-10-02-0026

www.pringlelaw.ca scan from 2026-10-02 00:26:35 UTC DR 18

A newer scan exists. See the latest report for www.pringlelaw.ca.

DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.

Scan 2026-10-02-0026

Scanned 2026-10-02 00:26:35 UTC, finished 2026-10-02 00:45:26 UTC. 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.

63/ 100Needs work

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. 4 of 27 checks found something to fix, led by broken links (67), non-200 responses (67), meta descriptions (1); 19 checks passed. Most of the points went to broken links (−20), non-200 responses (−10), meta descriptions (−4). 4 checks found something the score does not count, listed as noted. 10 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
69
Assets fetched
6
Status
Completed
Checks with issues
4 of 27
CoverageComplete crawl

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 tagsOK
    0 of 2 pages have title issues.
  • Meta descriptions1 issue
    1 of 2 pages have meta description issues.
    −4 points
  • HeadingsOK
    0 of 2 pages have heading issues.
  • Broken links67 issues
    122 internal links point at 67 broken URLs.
    −20 points
  • Links to other sites1 noted
    0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 5 destinations checked.
  • RedirectsOK
    0 redirecting URLs, 0 of them chained.
  • Non-200 responses67 issues
    70 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 limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 2 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 25 image references have no alt attribute. 13 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 6 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage1 issue
    No 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 countsOK
    Internal link counts for 2 pages; none is a dead end or buried.
  • Thin contentOK
    0 of 2 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 69 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 2 pages have a canonical worth checking.
  • Robots directives2 noted
    2 pages carry a robots directive; 0 carry none.
  • Anchor text1 noted
    1 destination are linked without useful anchor text, or with nofollow.
  • Title and heading structureOK
    0 of 2 pages could use the title, heading and snippet space better.
  • Image weight and alt lengthOK
    No image is over 100 KB or carries alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 2 pages answering 200 reads like an error page.
  • AccessibilityNot checked
    Not checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
  • Link positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 75 URLs.
  • Orphans in searchNot checked
    Not checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
  • Link ScoreOK
    Link Score (internal PageRank, 0-100) for 2 pages; 0 hold almost none (10 or less).
  • JavaScript renderingNot checked
    Not 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 Insights2 noted
    Mobile performance 43 on average across 2 pages; 2 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2909 sites, median 80%, average 79%

www.pringlelaw.ca scores 63%, higher than 7% of the 2909 scanned sites. See the full ranking.

0761520%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 1 site10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 1 site15%: 0 sites16%: 0 sites17%: 0 sites18%: 0 sites19%: 0 sites20%: 0 sites21%: 1 site22%: 0 sites23%: 0 sites24%: 0 sites25%: 0 sites26%: 0 sites27%: 0 sites28%: 1 site29%: 0 sites30%: 0 sites31%: 0 sites32%: 0 sites33%: 0 sites34%: 0 sites35%: 2 sites36%: 2 sites37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 16 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 55 sites70%: 48 sites71%: 79 sites72%: 77 sites73%: 82 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 134 sites79%: 112 sites80%: 129 sites81%: 123 sites82%: 136 sites83%: 121 sites84%: 131 sites85%: 106 sites86%: 97 sites87%: 95 sites88%: 82 sites89%: 77 sites90%: 57 sites91%: 61 sites92%: 44 sites93%: 32 sites94%: 25 sites95%: 17 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 152 sites63% here100%90%80%70%60%50%40%30%20%10%0%

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...

Start page (centre)OKRedirectErrorOrphanLinked from most pagesOne inbound link or noneRings = clicks from the start page. Size = inbound links. Drag to pan, scroll to zoom, click a page to see only its links.

Fix plan

Written by gpt-4o-mini from the scan findings

Written from an earlier version of the analysis (rules v4). The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Your 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. 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. 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. 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. 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 crawl

The 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. 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. 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. 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. 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. 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. 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. 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. 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.

Sites scoring near www.pringlelaw.ca

Their neighbours in the SEO rank table, which orders every scanned site by health score.

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 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.