Scanned sites / www.pringlelaw.ca / 2026-11-02-0316

www.pringlelaw.ca scan from 2026-11-02 03:16:42 UTC DR 21

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

Scan 2026-11-02-0316

Scanned 2026-11-02 03:16:42 UTC, finished 2026-11-02 03:37:17 UTC. Found on page 5 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.

76/ 100Good

On November 2, 2026 the Site Spider crawled 95 pages and 29 assets of www.pringlelaw.ca, starting from https://www.pringlelaw.ca/. It scored 76 out of 100, a good result. 9 of 33 checks found something to fix, led by sitemap coverage (72), title tags (41), meta descriptions (37); 17 checks passed. Most of the points went to sitemap coverage (−6), title tags (−5.7), meta descriptions (−4.1). 7 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: Medium3 medium, 4 low and 1 info findings. See the security findings ↓

Pages crawled
95
Assets fetched
29
Status
Completed
Checks with issues
9 of 33
CoverageComplete crawl

124 of 124 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 57 link destinations on other sites were checked.

  • Title tags41 issues
    41 of 72 pages have title issues.
    −5.7 points
  • Meta descriptions37 issues
    37 of 72 pages have meta description issues.
    −4.1 points
  • Headings15 issues
    15 of 72 pages have heading issues.
    −1.3 points
  • Broken links9 issues
    12 internal links point at 9 broken URLs.
    −2.5 points
  • Links to other sites3 issues
    3 destinations answered with an error, 24 could not be determined (timeouts, rate limits or refusals), of 57 destinations checked.
    −1.2 points
  • Redirects13 issues
    14 redirecting URLs, 0 of them chained.
    −0.7 points
  • Non-200 responses10 issues
    30 URLs did not return a 2xx response. 23 of them are pages, 10 with an error status; the rest are assets or redirects.
    −1.4 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 72 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 185 image references have no alt attribute. 137 use an empty alt (decorative), which is fine.
  • Heavy assets2 issues
    2 assets larger than 500 KB among 29 fetched assets.
    −1.2 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage72 issues
    1 sitemap listing 0 URLs: 72 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −6 points
  • Internal link countsOK
    Internal link counts for 72 pages; none is a dead end or buried.
  • Thin contentOK
    0 of 72 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 95 page URLs are plain lowercase addresses without parameters.
  • CanonicalsOK
    0 of 72 pages have a canonical worth checking.
  • Robots directives72 noted
    72 pages carry a robots directive; 0 carry none.
  • Anchor text2 noted
    2 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure5 noted
    5 of 72 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 anomalies4 noted
    4 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 72 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data43 noted
    72 of 72 indexable pages carry structured data: Blog (57), LegalService (45), Service (30), WebPage (15), Person (12). 43 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 72 pages with enough text to compare.
  • Soft 404sOK
    None of 72 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 positions1 noted
    1 of 72 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 13 response headers recorded across 124 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 72 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 InsightsNot checked
    Not checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
  • Spelling48 noted
    48 words an English dictionary does not know, on 18 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2537 sites, median 80%, average 78%

www.pringlelaw.ca scores 76%, higher than 34% of the 2537 scanned sites. See the full ranking.

0601190%: 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%: 1 site37%: 1 site38%: 3 sites39%: 2 sites40%: 3 sites41%: 1 site42%: 2 sites43%: 3 sites44%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 6 sites51%: 5 sites52%: 8 sites53%: 8 sites54%: 9 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 12 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 31 sites66%: 37 sites67%: 39 sites68%: 38 sites69%: 48 sites70%: 48 sites71%: 74 sites72%: 72 sites73%: 74 sites74%: 75 sites75%: 76 sites76%: 91 sites77%: 101 sites78%: 115 sites79%: 102 sites80%: 119 sites81%: 112 sites82%: 115 sites83%: 116 sites84%: 118 sites85%: 95 sites86%: 77 sites87%: 85 sites88%: 65 sites89%: 70 sites90%: 46 sites91%: 55 sites92%: 40 sites93%: 28 sites94%: 20 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites76% 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

Your website has several issues affecting SEO performance that need addressing. Prioritize fixing broken links, adding a sitemap, and resolving title and meta description issues to enhance visibility and user experience.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO.

    How: Replace or remove the internal links leading to broken URLs.

    Checks: broken-links

  2. 2

    Update Sitemap Coverage

    Why: Missing URLs in the sitemap can prevent indexing.

    How: Include all crawled pages in your sitemap and resubmit it to search engines.

    Checks: sitemap-coverage

  3. 3

    Improve Title Tags

    Why: Most pages have title issues impacting search results and click-through rates.

    How: Revise titles to adhere to best practices and avoid duplication.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Missing or duplicated meta descriptions affect visibility.

    How: Create unique meta descriptions for all pages without them.

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: Missing or multiple H1 tags can confuse search engines and visitors.

    How: Ensure each page has one H1 tag and revise others accordingly.

    Checks: headings

  6. 6

    Optimize Heavy Assets

    Why: Large assets slow down the site, impacting user experience.

    How: Compress images larger than 500 KB to improve loading times.

    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 crawl

This review highlights security vulnerabilities on your website, including missing security headers, which can expose you to various risks. Implementing the recommended fixes will enhance your site's protection 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, visitors using HTTP can be intercepted on their first request, compromising security.

    Fix: Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` to your HTTP response headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without CSP, your site is vulnerable to cross-site scripting (XSS) and data injection attacks.

    Fix: Add `Content-Security-Policy: default-src 'self';` to your HTTP response headers.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Without X-Frame-Options, your site can be embedded in a frame, increasing the risk of clickjacking attacks.

    Fix: Add `X-Frame-Options: DENY` to your HTTP response headers.

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly interpret files, which can lead to security issues.

    Fix: Add `X-Content-Type-Options: nosniff` to your HTTP response headers.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Without a Referrer-Policy, sensitive URL information may be shared when users navigate away from your site.

    Fix: Add `Referrer-Policy: no-referrer` to your HTTP response headers.

    Evidence: Referrer policy

  6. 6

    Server Identity ExposureLow

    Why it matters: Revealing the framework in use (even without the version) can help attackers target known vulnerabilities.

    Fix: Consider removing or obscuring the `X-Powered-By` header in your server configuration.

    Evidence: Software version disclosure

  7. 7

    Lack of Subresource Integrity on Third-party ScriptsLow

    Why it matters: Without SRI, compromised third-party scripts can manipulate your site in harmful ways.

    Fix: Implement Subresource Integrity for external scripts or use a CSP to restrict valid sources.

    Evidence: Third-party scripts

  8. 8

    Missing Permissions Policy HeaderInfo

    Why it matters: A Permissions-Policy helps mitigate the risk from potentially harmful browser features that your site does not use.

    Fix: Add `Permissions-Policy: interest-cohort=()`, or adapt it to your feature set, to your HTTP response headers.

    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/our-lawyers/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → no strict-transport-security
    • https://www.pringlelaw.ca/lawyers/tania-shapka/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 72 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/our-lawyers/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no content-security-policy
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → 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/our-lawyers/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no x-frame-options
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → 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/our-lawyers/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no x-content-type-options
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → 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/our-lawyers/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no referrer-policy
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → 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/our-lawyers/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/alexander-pringle-qc-1947-2015/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/dan-chivers/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/michael-d-sparks/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/daniel-j-song-q-c/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/nicole-j-stewart/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/evan-mcintyre/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/curtis-steeves/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/laura-matalas/ → no permissions-policy
    • https://www.pringlelaw.ca/lawyers/stephen-brophy/ → 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 (124 responses)
    • x-powered-by: WP Engine (103 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 (38 script tags)
    • pcst.wpenginepowered.com (661 script tags)
    • www.google.com (38 script tags)
7 checks passed, 1 not applicable
  • OKHTTPS

    All 72 crawled pages were served over HTTPS.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

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