Scanned sites / www.forumlaw.ca / 2026-09-12-0301

www.forumlaw.ca scan from 2026-09-12 03:01:36 UTC DR 26

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

Scan 2026-09-12-0301

Scanned 2026-09-12 03:01:36 UTC, finished 2026-09-12 04:54:04 UTC

Site: https://www.forumlaw.ca/

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

88/ 100Good

On September 12, 2026 the Site Spider crawled 128 pages and 303 assets of www.forumlaw.ca, starting from https://www.forumlaw.ca/. It scored 88 out of 100, a good result. 8 of 27 checks found something to fix, led by meta descriptions (79), title tags (39), heavy assets (3); 9 checks passed. Most of the points went to meta descriptions (−5.1), title tags (−3.1), heavy assets (−1.8). 10 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 and 2 low findings. See the security findings ↓

Pages crawled
128
Assets fetched
303
Status
Completed
Checks with issues
8 of 27
CoverageComplete crawl

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

  • Title tags39 issues
    39 of 123 pages have title issues. 1 noindex or canonicalized page excluded.
    −3.1 points
  • Meta descriptions79 issues
    79 of 123 pages have meta description issues. 1 noindex or canonicalized page excluded.
    −5.1 points
  • Headings1 issue
    1 of 123 pages have heading issues. 1 noindex or canonicalized page excluded.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites129 noted
    0 destinations answered with an error, 6 could not be determined (timeouts, rate limits or refusals), of 22 destinations checked.
  • Redirects4 issues
    5 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses9 noted
    9 URLs did not return a 2xx response. 4 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 123 indexable pages have indexability warnings. 1 page noindex by design.
  • Image alt text620 issues
    620 of 7226 image references have no alt attribute. 6601 use an empty alt (decorative), which is fine.
    −0.5 points
  • Heavy assets3 issues
    3 assets larger than 500 KB among 303 fetched assets.
    −1.8 points
  • Orphan pages17 issues
    17 pages have no internal links pointing at them.
    −0.5 points
  • Sitemap coverage23 issues
    6 sitemaps listing 117 URLs: 6 crawled pages missing, 0 listed URLs broken or redirecting, 17 reachable only via the sitemap.
    −1.1 points
  • Internal link counts5 noted
    Internal link counts for 124 pages; 5 worth a look.
  • Thin contentOK
    0 of 123 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL formatOK
    All 128 page URLs are plain lowercase addresses without parameters.
  • Canonicals1 noted
    1 of 124 pages have a canonical worth checking.
  • Robots directives124 noted
    124 pages carry a robots directive; 0 carry none.
  • Anchor text36 noted
    36 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure27 noted
    27 of 123 pages could use the title, heading and snippet space better. 1 noindex or canonicalized page excluded.
  • Image weight and alt length30 noted
    30 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • 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 124 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; 12 response headers recorded across 431 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 124 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 scan sits among all scanned sites

2873 sites, median 80%, average 79%

www.forumlaw.ca scores 88%, higher than 80% 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 sites88% 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.

Your site has some SEO issues requiring fixes, particularly with redirects and title/meta description optimization. Prioritize correcting these to enhance search engine visibility.

  1. 1

    Fix Redirects

    Why: Redirects can confuse users and search engines, affecting rankings.

    How: Ensure all redirected URLs use the final destination without unnecessary redirects.

    Checks: redirects

  2. 2

    Correct Non-200 Responses

    Why: Non-200 responses can block user access and impact SEO.

    How: Identify and fix the 9 URLs returning non-200 responses to ensure they return a 200 status.

    Checks: status-codes

  3. 3

    Optimize Title Tags

    Why: Title tags are critical for SEO; missing or short titles harm visibility.

    How: Revise the 39 pages with title tag issues to include concise, relevant titles that are 50-60 characters long.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Meta descriptions influence click-through rates from search results.

    How: Add or revise meta descriptions for the 42 pages with issues, keeping them under 160 characters.

    Checks: meta-descriptions

  5. 5

    Resolve Orphan Pages

    Why: Orphan pages are not discoverable via internal links, hurting SEO.

    How: Create internal links to the 17 orphan pages to make them accessible from other content.

    Checks: orphan-pages

  6. 6

    Improve Image Alt Text

    Why: Missing alt text affects accessibility and image search rankings.

    How: Add descriptive alt text for the 620 images missing it to improve SEO and user experience.

    Checks: images-alt

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 lacks several important security headers, which could expose it to various attacks. Implementing these headers will improve your site's security posture significantly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing your address without 'https://' can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP means scripts and styles can load from untrusted sources, increasing XSS risks.

    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: Lack of X-Frame-Options allows your pages to be embedded maliciously in frames.

    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 run files as scripts based on their content.

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

    Evidence: MIME sniffing protection

  5. 5

    Third-party Scripts Without Subresource IntegrityLow

    Why it matters: Running scripts from another domain can expose your site to risks if those scripts are compromised.

    Fix: Consider adding Subresource Integrity (SRI) attributes to scripts, or implement a strict Content-Security-Policy.

    Evidence: Third-party scripts

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.forumlaw.ca/ → no strict-transport-security
    • https://www.forumlaw.ca/calgary/litigation-lawyer/ → no strict-transport-security
    • https://www.forumlaw.ca/about-us/ → no strict-transport-security
    • https://www.forumlaw.ca/civil-litigation-lawyer/ → no strict-transport-security
    • https://www.forumlaw.ca/commercial-litigation-lawyer/ → no strict-transport-security
    • https://www.forumlaw.ca/commercial-landlord-and-tenant-lawyer-edmonton/ → no strict-transport-security
    • https://www.forumlaw.ca/breach-of-contract-lawyer/ → no strict-transport-security
    • https://www.forumlaw.ca/insurance-litigation/ → no strict-transport-security
    • https://www.forumlaw.ca/debt-collection-lawyer/ → no strict-transport-security
    • https://www.forumlaw.ca/shareholder-disputes/ → no strict-transport-security
    • https://www.forumlaw.ca/arbitration-mediation-lawyer/ → no strict-transport-security
    • https://www.forumlaw.ca/builders-liens-lawyer/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 124 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.forumlaw.ca/ → no content-security-policy
    • https://www.forumlaw.ca/calgary/litigation-lawyer/ → no content-security-policy
    • https://www.forumlaw.ca/about-us/ → no content-security-policy
    • https://www.forumlaw.ca/civil-litigation-lawyer/ → no content-security-policy
    • https://www.forumlaw.ca/commercial-litigation-lawyer/ → no content-security-policy
    • https://www.forumlaw.ca/commercial-landlord-and-tenant-lawyer-edmonton/ → no content-security-policy
    • https://www.forumlaw.ca/breach-of-contract-lawyer/ → no content-security-policy
    • https://www.forumlaw.ca/insurance-litigation/ → no content-security-policy
    • https://www.forumlaw.ca/debt-collection-lawyer/ → no content-security-policy
    • https://www.forumlaw.ca/shareholder-disputes/ → no content-security-policy
    • https://www.forumlaw.ca/arbitration-mediation-lawyer/ → no content-security-policy
    • https://www.forumlaw.ca/builders-liens-lawyer/ → 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.forumlaw.ca/ → no x-frame-options
    • https://www.forumlaw.ca/calgary/litigation-lawyer/ → no x-frame-options
    • https://www.forumlaw.ca/about-us/ → no x-frame-options
    • https://www.forumlaw.ca/civil-litigation-lawyer/ → no x-frame-options
    • https://www.forumlaw.ca/commercial-litigation-lawyer/ → no x-frame-options
    • https://www.forumlaw.ca/commercial-landlord-and-tenant-lawyer-edmonton/ → no x-frame-options
    • https://www.forumlaw.ca/breach-of-contract-lawyer/ → no x-frame-options
    • https://www.forumlaw.ca/insurance-litigation/ → no x-frame-options
    • https://www.forumlaw.ca/debt-collection-lawyer/ → no x-frame-options
    • https://www.forumlaw.ca/shareholder-disputes/ → no x-frame-options
    • https://www.forumlaw.ca/arbitration-mediation-lawyer/ → no x-frame-options
    • https://www.forumlaw.ca/builders-liens-lawyer/ → 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.forumlaw.ca/ → no x-content-type-options
    • https://www.forumlaw.ca/calgary/litigation-lawyer/ → no x-content-type-options
    • https://www.forumlaw.ca/about-us/ → no x-content-type-options
    • https://www.forumlaw.ca/civil-litigation-lawyer/ → no x-content-type-options
    • https://www.forumlaw.ca/commercial-litigation-lawyer/ → no x-content-type-options
    • https://www.forumlaw.ca/commercial-landlord-and-tenant-lawyer-edmonton/ → no x-content-type-options
    • https://www.forumlaw.ca/breach-of-contract-lawyer/ → no x-content-type-options
    • https://www.forumlaw.ca/insurance-litigation/ → no x-content-type-options
    • https://www.forumlaw.ca/debt-collection-lawyer/ → no x-content-type-options
    • https://www.forumlaw.ca/shareholder-disputes/ → no x-content-type-options
    • https://www.forumlaw.ca/arbitration-mediation-lawyer/ → no x-content-type-options
    • https://www.forumlaw.ca/builders-liens-lawyer/ → no x-content-type-options
  • NoteThird-party scripts

    Scripts run from 1 other domain 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.)

    • blazeo.com (40 script tags)
8 checks passed, 3 not applicable
  • OKHTTPS

    All 124 crawled pages were served over HTTPS.

  • OKSoftware version disclosure

    The Server header names a product without a version, and there is no X-Powered-By header.

  • OKMixed content

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

  • OKForms over HTTPS

    84 forms found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    2 library versions 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 applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

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

Own www.forumlaw.ca?