Scanned sites / www.fmlegal.ca / 2026-11-02-2042

www.fmlegal.ca scan from 2026-11-02 20:42:34 UTC DR 1

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

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

Scan 2026-11-02-2042

Scanned 2026-11-02 20:42:34 UTC, finished 2026-11-03 00:22:20 UTC. Found on page 3 of brave web search results

Site: https://www.fmlegal.ca/

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

66/ 100Needs work

On November 2, 2026 the Site Spider crawled 19 pages and 51 assets of www.fmlegal.ca, starting from https://www.fmlegal.ca/. It scored 66 out of 100, a result that needs work. 8 of 33 checks found something to fix, led by broken links (6), meta descriptions (13), title tags (10); 15 checks passed. Most of the points went to broken links (−9.2), meta descriptions (−8), title tags (−7.7). 10 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: Medium2 medium and 3 low findings. See the security findings ↓

Pages crawled
19
Assets fetched
51
Status
Completed
Checks with issues
8 of 33
CoverageComplete crawl

70 of 70 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 1 link destination on other sites was checked.

  • Title tags10 issues
    10 of 13 pages have title issues.
    −7.7 points
  • Meta descriptions13 issues
    13 of 13 pages have meta description issues.
    −8 points
  • Headings1 issue
    1 of 13 pages have heading issues.
    −0.5 points
  • Broken links6 issues
    11 internal links point at 6 broken URLs.
    −9.2 points
  • Links to other sitesOK
    0 destinations answered with an error, of 1 destination checked.
  • Redirects1 noted
    1 redirecting URL, 0 of them chained.
  • Non-200 responses6 issues
    15 URLs did not return a 2xx response. 6 of them are pages, 6 with an error status; the rest are assets or redirects.
    −4.6 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 13 indexable pages have indexability warnings.
    −1.5 points
  • Image alt textOK
    0 of 39 image references have no alt attribute. 25 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among 51 fetched assets.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage2 issues
    2 sitemaps listing 11 URLs: 2 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −0.9 points
  • Internal link countsOK
    Internal link counts for 13 pages; none is a dead end or buried.
  • Thin content2 issues
    2 of 13 pages have fewer than 200 words.
    −1.2 points
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format1 noted
    1 of 19 page URLs are harder to read, share or cache than they need to be.
  • Canonicals2 noted
    2 of 13 pages have a canonical worth checking.
  • Robots directives13 noted
    13 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 structure12 noted
    12 of 13 pages could use the title, heading and snippet space better.
  • Image weight and alt length2 noted
    2 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 13 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    10 of 13 indexable pages carry structured data: BreadcrumbList (10), ListItem (10). 0 pages with errors a rich result would fail on.
  • Near duplicates2 noted
    2 pages in 1 group read almost the same as another page (95% alike or more).
  • Soft 404s2 noted
    2 pages answer 200 but say they are not there.
  • 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 positionsOK
    0 of 13 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; 15 response headers recorded across 70 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 13 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.
  • Spelling5 noted
    5 words an English dictionary does not know, on 3 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2664 sites, median 80%, average 78%

www.fmlegal.ca scores 66%, higher than 11% of the 2664 scanned sites. See the full ranking.

0621230%: 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%: 5 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 10 sites55%: 9 sites56%: 7 sites57%: 16 sites58%: 18 sites59%: 9 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 32 sites66%: 41 sites67%: 40 sites68%: 37 sites69%: 49 sites70%: 47 sites71%: 75 sites72%: 73 sites73%: 81 sites74%: 76 sites75%: 85 sites76%: 96 sites77%: 105 sites78%: 121 sites79%: 109 sites80%: 122 sites81%: 118 sites82%: 120 sites83%: 119 sites84%: 123 sites85%: 101 sites86%: 89 sites87%: 91 sites88%: 74 sites89%: 73 sites90%: 50 sites91%: 56 sites92%: 39 sites93%: 28 sites94%: 22 sites95%: 14 sites96%: 17 sites97%: 15 sites98%: 7 sites99%: 2 sites100%: 69 sites66% 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

The site has several issues, including broken links and title/meta description deficiencies. Addressing these key areas will improve SEO performance significantly.

  1. 1

    Fix Broken Links

    Why: 11 internal links lead to broken URLs, harming user experience and SEO.

    How: Remove or update links to the following broken URLs: /2021/09/05/, /2021/09/09/, /2021/12/20/, /2022/02/16/, /2022/04/27/, and /2022/07/24/.

    Checks: broken-links

  2. 2

    Update Title Tags

    Why: 10 pages have title issues, which are crucial for search rankings.

    How: Create unique and descriptive title tags for the 10 affected pages, ensuring they are between 30-60 characters.

    Checks: titles

  3. 3

    Add Meta Descriptions

    Why: All pages lack meta descriptions, which affects click-through rates.

    How: Write compelling meta descriptions for all 13 pages to summarize content effectively.

    Checks: meta-descriptions

  4. 4

    Address Heading Issues

    Why: One page has multiple H1s, confusing search engines.

    How: Ensure there is only one H1 tag per page, standardizing the heading structure.

    Checks: headings

  5. 5

    Fix Indexability Warnings

    Why: 2 pages have no canonical, which can lead to duplicate content issues.

    How: Add canonical tags for the two flagged pages to indicate their preferred version.

    Checks: indexability

  6. 6

    Update Sitemap Coverage

    Why: 2 relevant URLs are not listed in the sitemap, limiting visibility.

    How: Add the missing URLs for the author pages to the sitemap.

    Checks: sitemap-coverage

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 has several security issues that need addressing, including the absence of a Content Security Policy, outdated JavaScript libraries with vulnerabilities, and exposure of server version information. Implementing the recommended changes can help enhance the site's security significantly.

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

    Missing Content Security PolicyMedium

    Why it matters: Without a Content Security Policy (CSP), scripts, styles, and frames can be loaded from any source, increasing risk of attacks.

    Fix: Add a CSP header: `Content-Security-Policy: default-src 'self';`.

    Evidence: Content Security Policy

  2. 2

    Outdated JavaScript LibrariesMedium

    Why it matters: Two libraries used are vulnerable, which could allow for various types of attacks depending on their usage.

    Fix: Update jQuery to at least version 3.5.0 and Bootstrap to at least version 4.3.1.

    Evidence: Vulnerable JavaScript libraries

  3. 3

    Server Version DisclosureLow

    Why it matters: The server reveals exact version information, allowing attackers to find known vulnerabilities.

    Fix: Remove `X-Powered-By` header or set it to a value like `X-Powered-By: private`.

    Evidence: Software version disclosure

  4. 4

    Missing Referrer PolicyLow

    Why it matters: Not having a Referrer Policy exposes full URLs, risking sensitive information being shared with third parties.

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

    Evidence: Referrer policy

  5. 5

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Scripts from external domains can be modified, potentially introducing malware.

    Fix: Implement a CSP to specifically address these domains or ensure third-party scripts utilize Subresource Integrity (SRI).

    Evidence: Third-party scripts

What the checks found

  • FoundContent Security PolicyMedium

    None of the 13 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.fmlegal.ca/ → no content-security-policy
    • https://www.fmlegal.ca/people/ → no content-security-policy
    • https://www.fmlegal.ca/services/ → no content-security-policy
    • https://www.fmlegal.ca/services/prenuptial-and-cohabitation-agreements/ → no content-security-policy
    • https://www.fmlegal.ca/services/divorce/ → no content-security-policy
    • https://www.fmlegal.ca/services/separation-divorce/ → no content-security-policy
    • https://www.fmlegal.ca/services/guardianship/ → no content-security-policy
    • https://www.fmlegal.ca/services/committeeship/ → no content-security-policy
    • https://www.fmlegal.ca/services/commissioner-notary-and-flat-fee-services/ → no content-security-policy
    • https://www.fmlegal.ca/contact/ → no content-security-policy
    • https://www.fmlegal.ca/author/mclosen/ → no content-security-policy
    • https://www.fmlegal.ca/privacy-policy/ → no content-security-policy
  • 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.fmlegal.ca/ → no referrer-policy
    • https://www.fmlegal.ca/people/ → no referrer-policy
    • https://www.fmlegal.ca/services/ → no referrer-policy
    • https://www.fmlegal.ca/services/prenuptial-and-cohabitation-agreements/ → no referrer-policy
    • https://www.fmlegal.ca/services/divorce/ → no referrer-policy
    • https://www.fmlegal.ca/services/separation-divorce/ → no referrer-policy
    • https://www.fmlegal.ca/services/guardianship/ → no referrer-policy
    • https://www.fmlegal.ca/services/committeeship/ → no referrer-policy
    • https://www.fmlegal.ca/services/commissioner-notary-and-flat-fee-services/ → no referrer-policy
    • https://www.fmlegal.ca/contact/ → no referrer-policy
    • https://www.fmlegal.ca/author/mclosen/ → no referrer-policy
    • https://www.fmlegal.ca/privacy-policy/ → no referrer-policy
  • FoundSoftware version disclosureLow

    Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.

    • x-powered-by: PHP/7.4.33 (30 responses)
  • FoundVulnerable JavaScript librariesMedium

    2 libraries with published vulnerabilities: jQuery 1.9.1, Bootstrap 4.1.3. Whether they are exploitable depends on how the site uses them, but each has a fixed release.

    • jQuery 1.9.1 in https://www.fmlegal.ca/wp-content/themes/business-gravity/assets/vendors/bootst…: 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
    • Bootstrap 4.1.3 in https://www.fmlegal.ca/wp-content/themes/business-gravity/assets/vendors/bootst…: CVE-2018-14040, CVE-2018-14041, CVE-2018-14042, CVE-2019-8331 (XSS through data attributes in tooltip, popover, collapse and scrollspy); fixed in 4.3.1
  • NoteThird-party scripts

    Scripts run from 2 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 (26 script tags)
    • challenges.cloudflare.com (1 script tag)
10 checks passed, 1 not applicable
  • OKHTTPS

    All 13 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 13 HTML pages.

  • OKClickjacking protection

    x-frame-options is set on all 13 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 13 HTML pages.

  • OKPermissions policy

    permissions-policy is set on all 13 HTML pages.

  • OKMixed content

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

  • OKForms over HTTPS

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

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

Own www.fmlegal.ca?