Scanned sites / propertylaw.ca

SEO report for propertylaw.ca DR 12

The latest Site Spider scan of propertylaw.ca, with 1 scan on record. Each scan is at its own address, for example /domain/propertylaw-ca/2026-09-15-1802.

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

Latest scan

Scanned 2026-09-15 18:02:54 UTC, finished 2026-09-15 18:14:09 UTC. Found with openstreetmap overpass

Site: https://propertylaw.ca/

Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.

83/ 100Good

On September 15, 2026 the Site Spider crawled 114 pages and 248 assets of propertylaw.ca, starting from https://propertylaw.ca/. It scored 83 out of 100, a good result. 10 of 27 checks found something to fix, led by links to other sites (73), title tags (43), meta descriptions (33); 10 checks passed. Most of the points went to title tags (−4), links to other sites (−4), meta descriptions (−2.5). 7 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: Medium4 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
114
Assets fetched
248
Status
Completed
Checks with issues
10 of 27
CoverageComplete crawl

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

  • Title tags43 issues
    43 of 95 pages have title issues. 12 noindex or canonicalized pages excluded.
    −4 points
  • Meta descriptions33 issues
    33 of 95 pages have meta description issues. 12 noindex or canonicalized pages excluded.
    −2.5 points
  • Headings11 issues
    11 of 95 pages have heading issues. 12 noindex or canonicalized pages excluded.
    −0.6 points
  • Broken links1 issue
    1 internal link point at 1 broken URL.
    −0.2 points
  • Links to other sites73 issues
    73 destinations answered with an error, 155 could not be determined (timeouts, rate limits or refusals), of 232 destinations checked.
    −4 points
  • Redirects5 issues
    6 redirecting URLs, 0 of them chained.
    −0.2 points
  • Non-200 responses2 issues
    23 URLs did not return a 2xx response. 7 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 107 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 0 image references have no alt attribute.
  • Heavy assets4 issues
    4 assets larger than 500 KB among 248 fetched assets.
    −2.4 points
  • Orphan pages32 issues
    32 pages have no internal links pointing at them.
    −1.2 points
  • Sitemap coverage34 issues
    5 sitemaps listing 97 URLs: 0 crawled pages missing, 1 listed URL broken or redirecting, 33 reachable only via the sitemap.
    −1.9 points
  • Internal link counts29 noted
    Internal link counts for 107 pages; 29 worth a look.
  • Thin contentOK
    0 of 95 pages have fewer than 200 words. 12 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format16 noted
    16 of 114 page URLs are harder to read, share or cache than they need to be.
  • Canonicals12 noted
    12 of 107 pages have a canonical worth checking.
  • Robots directives107 noted
    107 pages carry a robots directive; 0 carry none.
  • Anchor text29 noted
    29 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure74 noted
    74 of 95 pages could use the title, heading and snippet space better. 12 noindex or canonicalized pages excluded.
  • 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 107 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
    1 cookie set by the site; 13 response headers recorded across 362 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 107 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 Insights5 noted
    Mobile performance 69 on average across 5 pages; 5 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 site sits among all scanned sites

2873 sites, median 80%, average 79%

propertylaw.ca scores 83%, higher than 61% of the 2873 scanned sites. See the full ranking.

0751500%: 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%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 43 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 106 sites86%: 95 sites87%: 96 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites83% 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. 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.

The site has a good health score, but there are key improvements needed, including fixing broken links, addressing redirects, resolving non-200 responses, optimizing title tags, and improving meta descriptions. Prioritize these fixes for enhanced SEO performance.

  1. 1

    Fix Broken Link

    Why: A broken link harms user experience and SEO.

    How: Update the internal link to point to a valid URL instead.

    Checks: broken-links

  2. 2

    Address Redirects

    Why: Redirects can dilute page authority and affect load times.

    How: Consider consolidating similar pages to avoid unnecessary redirects.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: Non-200 responses can lead to poor user experiences and crawl issues.

    How: Identify the pages returning non-200 statuses and fix or remove them as needed.

    Checks: status-codes

  4. 4

    Optimize Title Tags

    Why: Improper title tags can affect search visibility and click-through rates.

    How: Shorten long titles and remove duplicates to improve relevance.

    Checks: titles

  5. 5

    Improve Meta Descriptions

    Why: Missing or long meta descriptions can impact click-through rates.

    How: Create concise, informative meta descriptions for pages that need them.

    Checks: meta-descriptions

  6. 6

    Link Orphan Pages Internally

    Why: Orphan pages are not indexed efficiently and lack visibility.

    How: Add internal links pointing to orphan pages from relevant sections of your site.

    Checks: orphan-pages

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

Your website has multiple security vulnerabilities that could expose it to attacks. Implementing headers for strict transport security, content security policy, clickjacking protection, and updating vulnerable libraries are critical improvements. Additionally, consider refining privacy settings and managing third-party scripts for enhanced security.

  • 0 high
  • 4 medium
  • 2 low
  • 1 info
  1. 1

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may access your site over HTTP, risking interception.

    Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.

    Evidence: HTTP Strict Transport Security

  2. 2

    No Content Security Policy (CSP)Medium

    Why it matters: Lack of CSP allows any script or style to load, increasing risk of XSS attacks.

    Fix: Include a CSP header: Content-Security-Policy: default-src 'self'; script-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options (Clickjacking Protection)Medium

    Why it matters: Absence of this header allows embedding of your pages in frames by malicious sites.

    Fix: Add the header: X-Frame-Options: DENY.

    Evidence: Clickjacking protection

  4. 4

    Outdated jQuery Libraries with VulnerabilitiesMedium

    Why it matters: Two jQuery libraries have known vulnerabilities that could be exploited depending on usage.

    Fix: Update to jQuery 3.5.0 and jQuery UI 1.13.2.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    No X-Content-Type-Options (MIME Sniffing Protection)Low

    Why it matters: Without this, browsers might erroneously interpret files, leading to potential exploits.

    Fix: Add the header: X-Content-Type-Options: nosniff.

    Evidence: MIME sniffing protection

  6. 6

    Missing Referrer PolicyLow

    Why it matters: Not having this policy could expose sensitive URL paths when users navigate to other sites.

    Fix: Add the header: Referrer-Policy: no-referrer.

    Evidence: Referrer policy

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: Not using this policy could allow risky browser features for scripts that may be injected.

    Fix: Add the header: Permissions-Policy: geolocation=(self), microphone=(self), camera=(self).

    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://propertylaw.ca/ → no strict-transport-security
    • https://propertylaw.ca/contact-us/ → no strict-transport-security
    • https://propertylaw.ca/residential-purchases-sales/ → no strict-transport-security
    • https://propertylaw.ca/mortgages-refinancing/ → no strict-transport-security
    • https://propertylaw.ca/ownership-transfers/ → no strict-transport-security
    • https://propertylaw.ca/lending-services/ → no strict-transport-security
    • https://propertylaw.ca/refi-law/ → no strict-transport-security
    • https://propertylaw.ca/solutions/ → no strict-transport-security
    • https://propertylaw.ca/solutions/for-homeowners/ → no strict-transport-security
    • https://propertylaw.ca/solutions/for-realty-agents/ → no strict-transport-security
    • https://propertylaw.ca/solutions/for-mortgage-professionals/ → no strict-transport-security
    • https://propertylaw.ca/why-property-law/about-us/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 107 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://propertylaw.ca/ → no content-security-policy
    • https://propertylaw.ca/contact-us/ → no content-security-policy
    • https://propertylaw.ca/residential-purchases-sales/ → no content-security-policy
    • https://propertylaw.ca/mortgages-refinancing/ → no content-security-policy
    • https://propertylaw.ca/ownership-transfers/ → no content-security-policy
    • https://propertylaw.ca/lending-services/ → no content-security-policy
    • https://propertylaw.ca/refi-law/ → no content-security-policy
    • https://propertylaw.ca/solutions/ → no content-security-policy
    • https://propertylaw.ca/solutions/for-homeowners/ → no content-security-policy
    • https://propertylaw.ca/solutions/for-realty-agents/ → no content-security-policy
    • https://propertylaw.ca/solutions/for-mortgage-professionals/ → no content-security-policy
    • https://propertylaw.ca/why-property-law/about-us/ → 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://propertylaw.ca/ → no x-frame-options
    • https://propertylaw.ca/contact-us/ → no x-frame-options
    • https://propertylaw.ca/residential-purchases-sales/ → no x-frame-options
    • https://propertylaw.ca/mortgages-refinancing/ → no x-frame-options
    • https://propertylaw.ca/ownership-transfers/ → no x-frame-options
    • https://propertylaw.ca/lending-services/ → no x-frame-options
    • https://propertylaw.ca/refi-law/ → no x-frame-options
    • https://propertylaw.ca/solutions/ → no x-frame-options
    • https://propertylaw.ca/solutions/for-homeowners/ → no x-frame-options
    • https://propertylaw.ca/solutions/for-realty-agents/ → no x-frame-options
    • https://propertylaw.ca/solutions/for-mortgage-professionals/ → no x-frame-options
    • https://propertylaw.ca/why-property-law/about-us/ → 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://propertylaw.ca/ → no x-content-type-options
    • https://propertylaw.ca/contact-us/ → no x-content-type-options
    • https://propertylaw.ca/residential-purchases-sales/ → no x-content-type-options
    • https://propertylaw.ca/mortgages-refinancing/ → no x-content-type-options
    • https://propertylaw.ca/ownership-transfers/ → no x-content-type-options
    • https://propertylaw.ca/lending-services/ → no x-content-type-options
    • https://propertylaw.ca/refi-law/ → no x-content-type-options
    • https://propertylaw.ca/solutions/ → no x-content-type-options
    • https://propertylaw.ca/solutions/for-homeowners/ → no x-content-type-options
    • https://propertylaw.ca/solutions/for-realty-agents/ → no x-content-type-options
    • https://propertylaw.ca/solutions/for-mortgage-professionals/ → no x-content-type-options
    • https://propertylaw.ca/why-property-law/about-us/ → 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://propertylaw.ca/ → no referrer-policy
    • https://propertylaw.ca/contact-us/ → no referrer-policy
    • https://propertylaw.ca/residential-purchases-sales/ → no referrer-policy
    • https://propertylaw.ca/mortgages-refinancing/ → no referrer-policy
    • https://propertylaw.ca/ownership-transfers/ → no referrer-policy
    • https://propertylaw.ca/lending-services/ → no referrer-policy
    • https://propertylaw.ca/refi-law/ → no referrer-policy
    • https://propertylaw.ca/solutions/ → no referrer-policy
    • https://propertylaw.ca/solutions/for-homeowners/ → no referrer-policy
    • https://propertylaw.ca/solutions/for-realty-agents/ → no referrer-policy
    • https://propertylaw.ca/solutions/for-mortgage-professionals/ → no referrer-policy
    • https://propertylaw.ca/why-property-law/about-us/ → 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://propertylaw.ca/ → no permissions-policy
    • https://propertylaw.ca/contact-us/ → no permissions-policy
    • https://propertylaw.ca/residential-purchases-sales/ → no permissions-policy
    • https://propertylaw.ca/mortgages-refinancing/ → no permissions-policy
    • https://propertylaw.ca/ownership-transfers/ → no permissions-policy
    • https://propertylaw.ca/lending-services/ → no permissions-policy
    • https://propertylaw.ca/refi-law/ → no permissions-policy
    • https://propertylaw.ca/solutions/ → no permissions-policy
    • https://propertylaw.ca/solutions/for-homeowners/ → no permissions-policy
    • https://propertylaw.ca/solutions/for-realty-agents/ → no permissions-policy
    • https://propertylaw.ca/solutions/for-mortgage-professionals/ → no permissions-policy
    • https://propertylaw.ca/why-property-law/about-us/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

    2 librarys with published vulnerabilities: jQuery 1.12.4, jQuery UI 1.10.4. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.12.4 in https://propertylaw.ca/wp-content/themes/es-theme-v2/dist/js/vendors.min.js?ver…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery UI 1.10.4 in https://propertylaw.ca/wp-content/themes/es-theme-v2/dist/js/vendors.min.js?ver…: CVE-2016-7103, CVE-2021-41182, CVE-2021-41183, CVE-2021-41184, CVE-2022-31160 (XSS through widget options); fixed in 1.13.2
  • NoteSoftware version disclosure

    Responses name the framework in an X-Powered-By header but hide the version.

    • server: cloudflare (362 responses)
    • x-powered-by: WP Engine (122 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 (40 script tags)
    • www.pierview.ai (40 script tags)
    • challenges.cloudflare.com (40 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /wp-admin/
6 checks passed
  • OKHTTPS

    All 107 crawled pages were served over HTTPS.

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

No other scans of this site yet.

Sites scoring near propertylaw.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 propertylaw.ca from its pages as published, the way a search engine does. It shows summary figures only.

Own propertylaw.ca?