Scanned sites / stanleylawoffice.ca / 2026-11-01-1116
stanleylawoffice.ca scan from 2026-11-01 11:16:29 UTC DR 1
DR is Ahrefs Domain Rating (0-100, backlink strength), used under its Domain Rating License.
Scan 2026-11-01-1116
Scanned 2026-11-01 11:16:29 UTC, finished 2026-11-01 11:48:24 UTC. Found on page 4 of brave web search results
Site: https://stanleylawoffice.ca/
Download SQLite databaseEvery page and asset from this scan, with the crawl events, in one file.
On November 1, 2026 the Site Spider crawled 26 pages and 151 assets of stanleylawoffice.ca, starting from https://stanleylawoffice.ca/. It scored 72 out of 100, a result that needs work. 8 of 33 checks found something to fix, led by meta descriptions (24), title tags (12), headings (19); 12 checks passed. Most of the points went to meta descriptions (−7.4), title tags (−4.6), headings (−4.4). 13 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, 2 low and 1 info findings. See the security findings ↓
- Pages crawled
- 26
- Assets fetched
- 151
- Status
- Completed
- Checks with issues
- 8 of 33
177 of 183 discovered URLs were fetched, 6 blocked by robots.txt. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 2 link destinations on other sites were checked.
- Title tags12 issues12 of 24 pages have title issues. 2 noindex or canonicalized pages excluded.−4.6 points
- Meta descriptions24 issues24 of 24 pages have meta description issues. 2 noindex or canonicalized pages excluded.−7.4 points
- Headings19 issues19 of 24 pages have heading issues. 2 noindex or canonicalized pages excluded.−4.4 points
- Broken linksOK0 internal links point at 0 broken URLs.
- Links to other sites4 noted0 destinations answered with an error, 1 could not be determined (timeouts, rate limits or refusals), of 2 destinations checked.
- Redirects1 noted1 redirecting URL, 0 of them chained.
- Non-200 responses1 noted1 URL did not return a 2xx response. 0 of them are pages, 0 with an error status; the rest are assets or redirects.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability3 issues3 of 24 indexable pages have indexability warnings. 2 pages noindex by design.−1.2 points
- Image alt textOK0 of 76 image references have no alt attribute. 52 use an empty alt (decorative), which is fine.
- Heavy assets5 issues5 assets larger than 500 KB among 151 fetched assets.−3 points
- Orphan pages11 issues11 pages have no internal links pointing at them.−1.7 points
- Sitemap coverage12 issues6 sitemaps listing 23 URLs: 1 crawled page missing, 0 listed URLs broken or redirecting, 11 reachable only via the sitemap.−2.8 points
- Internal link counts3 notedInternal link counts for 26 pages; 3 worth a look.
- Thin content10 issues10 of 24 pages have fewer than 200 words. 2 noindex or canonicalized pages excluded.−3.1 points
- Duplicate contentOK0 groups of pages with identical HTML.
- URL format10 noted10 of 26 page URLs are harder to read, share or cache than they need to be.
- Canonicals5 noted5 of 26 pages have a canonical worth checking.
- Robots directives26 noted26 pages carry a robots directive; 0 carry none.
- Anchor text3 noted3 destinations are linked without useful anchor text, or with nofollow.
- Title and heading structure9 noted9 of 24 pages could use the title, heading and snippet space better. 2 noindex or canonicalized pages excluded.
- Image weight and alt length11 noted11 images over 100 KB; 0 with alt text over 100 characters.
- Response anomaliesOKNo redirect loops, header redirects or pages served as something other than HTML.
- HTML and head validationOKAll 26 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
- hreflangOKNo page declares hreflang.
- Structured dataOKNo page carries structured data (24 indexable pages checked).
- Near duplicatesOKNo near duplicates among 19 pages with enough text to compare.
- Soft 404sOKNone of 26 pages answering 200 reads like an error page.
- AccessibilityNot checkedNot checked: the accessibility audit runs in the browser. Tick "Include JavaScript rendering checks" when you request a scan to run it.
- Link positions2 noted2 of 13 linked pages are linked only from the template, never from another page's content.
- PaginationOKNo page declares rel=next or rel=prev pagination.
- Headers and cookies1 noted1 cookie set by the site, 1 missing a protective flag; 15 response headers recorded across 177 URLs.
- Orphans in searchNot checkedNot checked: import a Search Console Pages export on the scan page to find pages Google shows that the site does not link to.
- Link ScoreOKLink Score (internal PageRank, 0-100) for 26 pages; 0 hold almost none (10 or less).
- JavaScript renderingNot checkedNot 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 checkedNot checked yet: PageSpeed Insights runs on the top pages once the crawl has finished.
- Spelling3 noted3 words an English dictionary does not know, on 2 pages. Product names and jargon will appear here too.
Where this scan sits among all scanned sites
2499 sites, median 80%, average 78%
stanleylawoffice.ca scores 72%, higher than 22% of the 2499 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe site has several SEO issues needing attention, including title, meta description, and heading problems on multiple pages, as well as orphaned content. Prioritize resolving these issues for better visibility and indexing.
- 1
Fix Redirects on Sitemap
Why: Redirected URLs can hinder site navigation and indexing.
How: Update sitemap to ensure direct links are used, removing unnecessary redirects.
Checks: redirects
- 2
Add Meta Descriptions
Why: All pages lack meta descriptions, affecting CTR in search results.
How: Create unique, compelling meta descriptions for all pages.
Evidence: 24 pages have no meta description at all.
24 pages affected
Checks: meta-descriptions
- 3
Improve Title Tags
Why: Short titles can lead to lower rankings and CTR.
How: Revise titles to be descriptive and meet best practices, ensuring they are longer than 30 characters.
Checks: titles
- 4
Address Heading Issues
Why: Multiple H1s or missing H1s can confuse search engines about page content.
How: Ensure each page has one H1 and fix any multiple H1 issues.
Evidence: 16 pages: multiple h1s.
16 pages affected
Checks: headings
- 5
Reduce Heavy Assets
Why: Large assets slow down page load times, impacting user experience.
How: Optimize or shrink large images and scripts identified in the report.
Evidence: 85.5 KB of script, loaded by 25 pages, so every visitor to any of them downloads it.
25 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
- 6
Fix Orphan Pages
Why: Orphan pages can’t be indexed properly and limit content discoverability.
How: Create internal links to orphan pages to enhance their visibility.
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 crawlThe site has several security weaknesses that need addressing, particularly around response headers and cookie security. Missing HTTP Strict Transport Security (HSTS) can expose visitors to interception. Additionally, lack of X-Frame-Options, X-Content-Type-Options, and proper cookie flags increase vulnerability to various attacks. Immediate action is recommended to enhance security.
- 0 high
- 3 medium
- 2 low
- 1 info
- 1
Missing HTTP Strict Transport Security (HSTS)Medium
Why it matters: Without HSTS, visitors can be intercepted if they access the site without HTTPS.
Fix: Add the header: Strict-Transport-Security: max-age=31536000; includeSubDomains.
Evidence: HTTP Strict Transport Security
- 2
Missing X-Frame-OptionsMedium
Why it matters: Without this header, pages can be embedded in frames, leading to clickjacking attacks.
Fix: Add the header: X-Frame-Options: DENY.
Evidence: Clickjacking protection
- 3
Insecure Cookie FlagsMedium
Why it matters: Cookies lacking HttpOnly, Secure, and SameSite flags are vulnerable to attacks.
Fix: Set the cookie flags for 'wordpress_test_cookie': HttpOnly; Secure; SameSite=Strict.
Evidence: Cookie flags
- 4
Missing X-Content-Type-OptionsLow
Why it matters: This absence can allow browsers to execute files as scripts based on their contents.
Fix: Add the header: X-Content-Type-Options: nosniff.
Evidence: MIME sniffing protection
- 5
Server Version DisclosureLow
Why it matters: Revealing server versions can assist attackers in targeting known vulnerabilities.
Fix: Remove or modify headers: Server: (change to server name filter) and X-Powered-By: (remove if possible).
Evidence: Software version disclosure
- 6
Missing Permissions-Policy HeaderInfo
Why it matters: This header limits browser features that can be exploited by injected scripts.
Fix: Add the header: Permissions-Policy: interest-coalition=(), geolocation=(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://stanleylawoffice.ca/ → no strict-transport-security
- https://stanleylawoffice.ca/aboutus_new/ → no strict-transport-security
- https://stanleylawoffice.ca/meet-the-team/ → no strict-transport-security
- https://stanleylawoffice.ca/events/ → no strict-transport-security
- https://stanleylawoffice.ca/our-services/ → no strict-transport-security
- https://stanleylawoffice.ca/contact/ → no strict-transport-security
- https://stanleylawoffice.ca/hello-world/ → no strict-transport-security
- https://stanleylawoffice.ca/divi_overlay/immigration/ → no strict-transport-security
- https://stanleylawoffice.ca/divi_overlay/criminal/ → no strict-transport-security
- https://stanleylawoffice.ca/divi_overlay/real-estate/ → no strict-transport-security
- https://stanleylawoffice.ca/divi_overlay/family/ → no strict-transport-security
- https://stanleylawoffice.ca/divi_overlay/wills/ → no strict-transport-security
- FoundClickjacking protectionMedium
2 of 26 HTML pages send 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://stanleylawoffice.ca/ → no x-frame-options
- https://stanleylawoffice.ca/aboutus_new/ → no x-frame-options
- https://stanleylawoffice.ca/meet-the-team/ → no x-frame-options
- https://stanleylawoffice.ca/events/ → no x-frame-options
- https://stanleylawoffice.ca/our-services/ → no x-frame-options
- https://stanleylawoffice.ca/contact/ → no x-frame-options
- https://stanleylawoffice.ca/hello-world/ → no x-frame-options
- https://stanleylawoffice.ca/divi_overlay/immigration/ → no x-frame-options
- https://stanleylawoffice.ca/divi_overlay/criminal/ → no x-frame-options
- https://stanleylawoffice.ca/divi_overlay/real-estate/ → no x-frame-options
- https://stanleylawoffice.ca/divi_overlay/family/ → no x-frame-options
- https://stanleylawoffice.ca/divi_overlay/wills/ → 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://stanleylawoffice.ca/ → no x-content-type-options
- https://stanleylawoffice.ca/aboutus_new/ → no x-content-type-options
- https://stanleylawoffice.ca/meet-the-team/ → no x-content-type-options
- https://stanleylawoffice.ca/events/ → no x-content-type-options
- https://stanleylawoffice.ca/our-services/ → no x-content-type-options
- https://stanleylawoffice.ca/contact/ → no x-content-type-options
- https://stanleylawoffice.ca/hello-world/ → no x-content-type-options
- https://stanleylawoffice.ca/divi_overlay/immigration/ → no x-content-type-options
- https://stanleylawoffice.ca/divi_overlay/criminal/ → no x-content-type-options
- https://stanleylawoffice.ca/divi_overlay/real-estate/ → no x-content-type-options
- https://stanleylawoffice.ca/divi_overlay/family/ → no x-content-type-options
- https://stanleylawoffice.ca/divi_overlay/wills/ → no x-content-type-options
- 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://stanleylawoffice.ca/ → no permissions-policy
- https://stanleylawoffice.ca/aboutus_new/ → no permissions-policy
- https://stanleylawoffice.ca/meet-the-team/ → no permissions-policy
- https://stanleylawoffice.ca/events/ → no permissions-policy
- https://stanleylawoffice.ca/our-services/ → no permissions-policy
- https://stanleylawoffice.ca/contact/ → no permissions-policy
- https://stanleylawoffice.ca/hello-world/ → no permissions-policy
- https://stanleylawoffice.ca/divi_overlay/immigration/ → no permissions-policy
- https://stanleylawoffice.ca/divi_overlay/criminal/ → no permissions-policy
- https://stanleylawoffice.ca/divi_overlay/real-estate/ → no permissions-policy
- https://stanleylawoffice.ca/divi_overlay/family/ → no permissions-policy
- https://stanleylawoffice.ca/divi_overlay/wills/ → no permissions-policy
- FoundSoftware version disclosureLow
Responses reveal the exact server or framework version, which lets an attacker look up known vulnerabilities for it without guessing.
- server: nginx (177 responses)
- x-powered-by: PHP/8.3.36 (36 responses)
- FoundCookie flagsMedium
1 of 1 cookie are missing protective flags. Without HttpOnly a script can read the cookie; without Secure it travels over plain HTTP; without SameSite it is sent on cross-site requests.
- wordpress_test_cookie (set by https://stanleylawoffice.ca/wp-login.php) lacks SameSite
- 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/
9 checks passed
- OKHTTPS
All 26 crawled pages were served over HTTPS.
- OKContent Security Policy
A Content-Security-Policy is set on 2 of 26 pages.
- OKReferrer policy
A referrer policy is set through a <meta name="referrer"> tag.
- OKMixed content
No HTTPS page loads a script, stylesheet, font or image over plain HTTP.
- OKForms over HTTPS
19 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.
- OKThird-party scripts
The sampled pages load no scripts from other domains.
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 stanleylawoffice.ca
Their neighbours in the SEO rank table, which orders every scanned site by health score.
- www.veert.comDR 472/100 · rank 1883 · 170 pages
- yellowstoneballet.infoDR 1672/100 · rank 1883 · 53 pages
- ccstcalgary.comDR 472/100 · rank 1883 · 110 pages
- fromboise.comDR 3272/100 · rank 1883 · 445 pages
- naylorelectricmt.comDR 172/100 · rank 1883 · 6 pages
- www.jslawmt.comDR 872/100 · rank 1883 · 217 pages
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 stanleylawoffice.ca from its pages as published, the way a search engine does. It shows summary figures only.
Own stanleylawoffice.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 stanleylawoffice.ca. Removal needs no account and no proof of purchase.