Scanned sites / www.legalaid.mb.ca / 2026-11-09-0528

www.legalaid.mb.ca scan from 2026-11-09 05:28:20 UTC DR 51

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

Scan 2026-11-09-0528

Scanned 2026-11-09 05:28:20 UTC, finished 2026-11-09 05:35:17 UTC. Found with openstreetmap overpass

Site: https://www.legalaid.mb.ca/

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

74/ 100Needs work

On November 9, 2026 the Site Spider crawled 203 pages and 471 assets of www.legalaid.mb.ca, starting from https://www.legalaid.mb.ca/. It scored 74 out of 100, a result that needs work. 13 of 33 checks found something to fix, led by meta descriptions (165), title tags (124), heavy assets (19); 11 checks passed. Most of the points went to meta descriptions (−7), title tags (−6.6), heavy assets (−6). 9 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, 3 low and 2 info findings. See the security findings ↓

Pages crawled
203
Assets fetched
471
Status
Completed
Checks with issues
13 of 33
CoverageComplete crawl

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

  • Title tags124 issues
    124 of 165 pages have title issues. 24 noindex or canonicalized pages excluded.
    −6.6 points
  • Meta descriptions165 issues
    165 of 165 pages have meta description issues. 24 noindex or canonicalized pages excluded.
    −7 points
  • Headings1 issue
    1 of 165 pages have heading issues. 24 noindex or canonicalized pages excluded.
  • Broken links2 issues
    4 internal links point at 2 broken URLs.
    −0.2 points
  • Links to other sites18 issues
    18 destinations answered with an error, 73 could not be determined (timeouts, rate limits or refusals), of 149 destinations checked.
    −3.8 points
  • Redirects12 issues
    13 redirecting URLs, 0 of them chained.
    −0.3 points
  • Non-200 responses2 issues
    20 URLs did not return a 2xx response. 14 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.1 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability2 issues
    2 of 165 indexable pages have indexability warnings. 24 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
    −0.1 points
  • Image alt text569 issues
    569 of 1693 image references have no alt attribute. 107 use an empty alt (decorative), which is fine.
    −2 points
  • Heavy assets19 issues
    19 assets larger than 500 KB among 471 fetched assets. 45 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
  • Sitemap coverage7 issues
    7 sitemaps listing 171 URLs: 0 crawled pages missing, 5 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −0.2 points
  • Internal link counts56 noted
    Internal link counts for 189 pages; 56 worth a look.
  • Thin content1 issue
    1 of 165 pages have fewer than 200 words. 24 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format15 noted
    15 of 203 page URLs are harder to read, share or cache than they need to be.
  • Canonicals25 noted
    25 of 189 pages have a canonical worth checking.
  • Robots directives189 noted
    189 pages carry a robots directive; 0 carry none.
  • Anchor text8 noted
    8 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure165 noted
    165 of 165 pages could use the title, heading and snippet space better. 24 noindex or canonicalized pages excluded.
  • Image weight and alt length35 noted
    35 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 validationOK
    All 189 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    1 of 165 indexable pages carry structured data: Question (1), Answer (1). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 165 pages with enough text to compare.
  • Soft 404sOK
    None of 189 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 positionsOK
    0 of 164 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    89 pages in pagination sequences; 0 with problems.
  • Headers and cookiesOK
    0 cookies set by the site; 11 response headers recorded across 674 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 189 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.
  • Spelling145 noted
    145 words an English dictionary does not know, on 32 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2877 sites, median 80%, average 79%

www.legalaid.mb.ca scores 74%, higher than 26% of the 2877 scanned sites. See the full ranking.

0761510%: 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%: 10 sites55%: 10 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 30 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 53 sites70%: 47 sites71%: 80 sites72%: 76 sites73%: 82 sites74%: 83 sites75%: 86 sites76%: 94 sites77%: 109 sites78%: 131 sites79%: 113 sites80%: 127 sites81%: 124 sites82%: 133 sites83%: 119 sites84%: 131 sites85%: 105 sites86%: 95 sites87%: 95 sites88%: 81 sites89%: 74 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 28 sites94%: 25 sites95%: 15 sites96%: 19 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 151 sites74% 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 critical issues that need fixing, especially broken links, missing meta descriptions, and heavy assets. Prioritize addressing these for improved SEO and usability.

  1. 1

    Fix Broken Links

    Why: Resolving broken links enhances user experience and keeps visitors engaged.

    How: Update or remove links pointing to broken URLs on your website.

    Checks: broken-links

  2. 2

    Add Meta Descriptions

    Why: Meta descriptions improve click-through rates by providing better search results visibility.

    How: Create and implement meta descriptions on all pages with missing descriptions.

    Evidence: 165 pages have no meta description at all.

    165 pages affected

    Checks: meta-descriptions

  3. 3

    Address Non-200 Responses

    Why: Fixing URLs with non-200 responses improves overall site health and access.

    How: Identify and resolve the issues causing URLs to fail, ensuring all important pages return 200.

    Checks: status-codes

  4. 4

    Reduce Heavy Assets

    Why: Shrinking large assets speeds up loading times and enhances user experience.

    How: Compress or optimize large images and documents to reduce their size.

    Evidence: 5.2 MB of image, loaded by 14 pages, so every visitor to any of them downloads it.

    14 pages affected

    Depends on: If it is a download rather than part of the page, weight matters less; move it out of the page instead.

    Checks: heavy-assets

  5. 5

    Fix Indexability Issues

    Why: Ensuring correct indexing improves visibility in search engine results.

    How: Remove noindex directives from critical pages listed in the sitemap.

    Checks: indexability

  6. 6

    Improve Title Tags

    Why: Optimizing title tags can boost SEO and user engagement.

    How: Revise short and long title tags to meet SEO best practices.

    Checks: titles

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, which could expose visitors to various attacks. Implementing these headers will enhance protection against issues like content injection, clickjacking, and data leaks. Here are prioritized steps to strengthen your site’s security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, non-HTTPS requests can be intercepted.

    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: Absence of CSP allows unrestricted loading of potentially malicious scripts.

    Fix: Implement a CSP such as 'Content-Security-Policy: default-src 'self'' to restrict sources.

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking Protection (X-Frame-Options)Medium

    Why it matters: Lack of frame options means your site can be framed and potentially clicked through an overlay.

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

    Evidence: Clickjacking protection

  4. 4

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

    Why it matters: Without this header, browsers may interpret files incorrectly, leading to vulnerabilities.

    Fix: Set 'X-Content-Type-Options: nosniff' in your HTTP headers.

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: No referrer policy exposes sensitive URL details to third-party sites.

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

    Evidence: Referrer policy

  6. 6

    Third-party Scripts without Subresource IntegrityLow

    Why it matters: Scripts from another domain without integrity checks can change the behavior of your site.

    Fix: Consider adding Subresource Integrity attributes to scripts, or implement a CSP that restricts the sources.

    Evidence: Third-party scripts

  7. 7

    No Permissions PolicyInfo

    Why it matters: Lack of permissions policy could allow unnecessary access to browser features.

    Fix: Include 'Permissions-Policy: geolocation=(self)' in your HTTP headers to restrict access.

    Evidence: Permissions policy

  8. 8

    Sensitive Path in robots.txtInfo

    Why it matters: Robots.txt discloses paths that should be restricted from public access.

    Fix: Restrict access to /wp-admin/ using proper server rules rather than relying on robots.txt.

    Evidence: Sensitive paths in robots.txt

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.legalaid.mb.ca/ → no strict-transport-security
    • https://www.legalaid.mb.ca/lam/legal-aid-manitoba/ → no strict-transport-security
    • https://www.legalaid.mb.ca/pilc/public-interest-law-centre/ → no strict-transport-security
    • https://www.legalaid.mb.ca/services/who-we-serve/ → no strict-transport-security
    • https://www.legalaid.mb.ca/financial-rules/do-i-qualify-financially/ → no strict-transport-security
    • https://www.legalaid.mb.ca/how-to-apply/application-centres/ → no strict-transport-security
    • https://www.legalaid.mb.ca/you-your-lawyer/choosing-a-lawyer/ → no strict-transport-security
    • https://www.legalaid.mb.ca/q-a/ → no strict-transport-security
    • https://www.legalaid.mb.ca/news/ → no strict-transport-security
    • https://www.legalaid.mb.ca/for-lawyers-2/pbonline/ → no strict-transport-security
    • https://www.legalaid.mb.ca/contact/admin-office/ → no strict-transport-security
    • https://www.legalaid.mb.ca/lam/facts-stats/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 189 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.legalaid.mb.ca/ → no content-security-policy
    • https://www.legalaid.mb.ca/lam/legal-aid-manitoba/ → no content-security-policy
    • https://www.legalaid.mb.ca/pilc/public-interest-law-centre/ → no content-security-policy
    • https://www.legalaid.mb.ca/services/who-we-serve/ → no content-security-policy
    • https://www.legalaid.mb.ca/financial-rules/do-i-qualify-financially/ → no content-security-policy
    • https://www.legalaid.mb.ca/how-to-apply/application-centres/ → no content-security-policy
    • https://www.legalaid.mb.ca/you-your-lawyer/choosing-a-lawyer/ → no content-security-policy
    • https://www.legalaid.mb.ca/q-a/ → no content-security-policy
    • https://www.legalaid.mb.ca/news/ → no content-security-policy
    • https://www.legalaid.mb.ca/for-lawyers-2/pbonline/ → no content-security-policy
    • https://www.legalaid.mb.ca/contact/admin-office/ → no content-security-policy
    • https://www.legalaid.mb.ca/lam/facts-stats/ → 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.legalaid.mb.ca/ → no x-frame-options
    • https://www.legalaid.mb.ca/lam/legal-aid-manitoba/ → no x-frame-options
    • https://www.legalaid.mb.ca/pilc/public-interest-law-centre/ → no x-frame-options
    • https://www.legalaid.mb.ca/services/who-we-serve/ → no x-frame-options
    • https://www.legalaid.mb.ca/financial-rules/do-i-qualify-financially/ → no x-frame-options
    • https://www.legalaid.mb.ca/how-to-apply/application-centres/ → no x-frame-options
    • https://www.legalaid.mb.ca/you-your-lawyer/choosing-a-lawyer/ → no x-frame-options
    • https://www.legalaid.mb.ca/q-a/ → no x-frame-options
    • https://www.legalaid.mb.ca/news/ → no x-frame-options
    • https://www.legalaid.mb.ca/for-lawyers-2/pbonline/ → no x-frame-options
    • https://www.legalaid.mb.ca/contact/admin-office/ → no x-frame-options
    • https://www.legalaid.mb.ca/lam/facts-stats/ → 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.legalaid.mb.ca/ → no x-content-type-options
    • https://www.legalaid.mb.ca/lam/legal-aid-manitoba/ → no x-content-type-options
    • https://www.legalaid.mb.ca/pilc/public-interest-law-centre/ → no x-content-type-options
    • https://www.legalaid.mb.ca/services/who-we-serve/ → no x-content-type-options
    • https://www.legalaid.mb.ca/financial-rules/do-i-qualify-financially/ → no x-content-type-options
    • https://www.legalaid.mb.ca/how-to-apply/application-centres/ → no x-content-type-options
    • https://www.legalaid.mb.ca/you-your-lawyer/choosing-a-lawyer/ → no x-content-type-options
    • https://www.legalaid.mb.ca/q-a/ → no x-content-type-options
    • https://www.legalaid.mb.ca/news/ → no x-content-type-options
    • https://www.legalaid.mb.ca/for-lawyers-2/pbonline/ → no x-content-type-options
    • https://www.legalaid.mb.ca/contact/admin-office/ → no x-content-type-options
    • https://www.legalaid.mb.ca/lam/facts-stats/ → 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.legalaid.mb.ca/ → no referrer-policy
    • https://www.legalaid.mb.ca/lam/legal-aid-manitoba/ → no referrer-policy
    • https://www.legalaid.mb.ca/pilc/public-interest-law-centre/ → no referrer-policy
    • https://www.legalaid.mb.ca/services/who-we-serve/ → no referrer-policy
    • https://www.legalaid.mb.ca/financial-rules/do-i-qualify-financially/ → no referrer-policy
    • https://www.legalaid.mb.ca/how-to-apply/application-centres/ → no referrer-policy
    • https://www.legalaid.mb.ca/you-your-lawyer/choosing-a-lawyer/ → no referrer-policy
    • https://www.legalaid.mb.ca/q-a/ → no referrer-policy
    • https://www.legalaid.mb.ca/news/ → no referrer-policy
    • https://www.legalaid.mb.ca/for-lawyers-2/pbonline/ → no referrer-policy
    • https://www.legalaid.mb.ca/contact/admin-office/ → no referrer-policy
    • https://www.legalaid.mb.ca/lam/facts-stats/ → 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.legalaid.mb.ca/ → no permissions-policy
    • https://www.legalaid.mb.ca/lam/legal-aid-manitoba/ → no permissions-policy
    • https://www.legalaid.mb.ca/pilc/public-interest-law-centre/ → no permissions-policy
    • https://www.legalaid.mb.ca/services/who-we-serve/ → no permissions-policy
    • https://www.legalaid.mb.ca/financial-rules/do-i-qualify-financially/ → no permissions-policy
    • https://www.legalaid.mb.ca/how-to-apply/application-centres/ → no permissions-policy
    • https://www.legalaid.mb.ca/you-your-lawyer/choosing-a-lawyer/ → no permissions-policy
    • https://www.legalaid.mb.ca/q-a/ → no permissions-policy
    • https://www.legalaid.mb.ca/news/ → no permissions-policy
    • https://www.legalaid.mb.ca/for-lawyers-2/pbonline/ → no permissions-policy
    • https://www.legalaid.mb.ca/contact/admin-office/ → no permissions-policy
    • https://www.legalaid.mb.ca/lam/facts-stats/ → no permissions-policy
  • 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.)

    • use.typekit.net (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/
7 checks passed, 1 not applicable
  • OKHTTPS

    All 189 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

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

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

Own www.legalaid.mb.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.legalaid.mb.ca. Removal needs no account and no proof of purchase.