Scanned sites / www.advocateslaw.com / 2026-11-06-0831

www.advocateslaw.com scan from 2026-11-06 08:31:39 UTC DR 32

A newer scan exists. See the latest report for www.advocateslaw.com.

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

Scan 2026-11-06-0831

Scanned 2026-11-06 08:31:39 UTC, finished 2026-11-06 13:20:40 UTC. Found with openstreetmap overpass

Site: https://www.advocateslaw.com/

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

82/ 100Good

On November 6, 2026 the Site Spider crawled 561 pages and 339 assets of www.advocateslaw.com, starting from https://www.advocateslaw.com/. It scored 82 out of 100, a good result. 12 of 33 checks found something to fix, led by heavy assets (10), meta descriptions (304), title tags (201); 8 checks passed. Most of the points went to heavy assets (−6), meta descriptions (−4.8), title tags (−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: Medium5 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
561
Assets fetched
339
Status
Completed
Checks with issues
12 of 33
CoverageComplete crawl

900 of 900 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 310 left unchecked.

  • Title tags201 issues
    201 of 430 pages have title issues. 73 noindex or canonicalized pages excluded.
    −4 points
  • Meta descriptions304 issues
    304 of 430 pages have meta description issues. 73 noindex or canonicalized pages excluded.
    −4.8 points
  • Headings3 issues
    3 of 430 pages have heading issues. 73 noindex or canonicalized pages excluded.
  • Broken links10 issues
    34 internal links point at 10 broken URLs.
    −0.4 points
  • Links to other sites2 issues
    2 destinations answered with an error, 58 could not be determined (timeouts, rate limits or refusals), 310 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.2 points
  • Redirects49 issues
    52 redirecting URLs, 18 of them chained.
    −0.4 points
  • Non-200 responses11 issues
    64 URLs did not return a 2xx response. 58 of them are pages, 11 with an error status; the rest are assets or redirects.
    −0.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability44 issues
    44 of 450 indexable pages have indexability warnings. 53 pages noindex by design.
    −0.9 points
  • Image alt textOK
    0 of 2435 image references have no alt attribute. 677 use an empty alt (decorative), which is fine.
  • Heavy assets10 issues
    10 assets larger than 500 KB among 339 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage108 issues
    9 sitemaps listing 336 URLs: 101 crawled pages missing, 6 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −1.3 points
  • Internal link counts105 noted
    Internal link counts for 500 pages; 105 worth a look.
  • Thin content2 issues
    2 of 430 pages have fewer than 200 words. 73 noindex or canonicalized pages excluded.
  • Duplicate content11 issues
    1 group of pages with identical HTML.
    −0.2 points
  • URL format18 noted
    18 of 561 page URLs are harder to read, share or cache than they need to be.
  • Canonicals73 noted
    73 of 503 pages have a canonical worth checking.
  • Robots directives497 noted
    497 pages carry a robots directive; 6 carry none.
  • Anchor text91 noted
    91 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure159 noted
    159 of 430 pages could use the title, heading and snippet space better. 73 noindex or canonicalized pages excluded.
  • Image weight and alt length118 noted
    91 images over 100 KB; 27 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validationOK
    All 503 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data20 noted
    501 of 430 indexable pages carry structured data: WebSite (500), BreadcrumbList (499), ListItem (499), https://www.schema.org/SiteNavigationElement (498), LegalService (307). 20 pages with errors a rich result would fail on.
  • Near duplicates44 noted
    44 pages in 22 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 503 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 positions69 noted
    69 of 430 linked pages are linked only from the template, never from another page's content.
  • Pagination20 noted
    230 pages in pagination sequences; 20 with problems.
  • Headers and cookiesOK
    2 cookies set by the site; 13 response headers recorded across 900 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 503 pages; 293 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.
  • Spelling91 noted
    91 words an English dictionary does not know, on 223 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2868 sites, median 80%, average 79%

www.advocateslaw.com scores 82%, higher than 56% of the 2868 scanned sites. See the full ranking.

0751490%: 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%: 42 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%: 126 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 104 sites86%: 96 sites87%: 95 sites88%: 81 sites89%: 75 sites90%: 55 sites91%: 58 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 149 sites82% 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

Several issues need addressing to enhance site performance and SEO. Key areas include fixing broken links, optimizing redirects, resolving non-200 status codes, improving title tags, and addressing meta description issues.

  1. 1

    Fix Broken Links

    Why: Improves user experience and SEO health.

    How: Identify the broken URLs and either update or remove the links pointing to them.

    Checks: broken-links

  2. 2

    Optimize Redirects

    Why: Reduces crawl inefficiencies and improves loading speeds.

    How: Minimize chained redirects by updating linked references directly to the final destination URL.

    Checks: redirects

  3. 3

    Resolve Non-200 Responses

    Why: Ensures all pages return the correct status for better indexing.

    How: Investigate the URLs with non-200 responses and fix or remove faulty pages.

    Checks: status-codes

  4. 4

    Improve Title Tags

    Why: Better titles enhance click-through rates and search visibility.

    How: Revise short, duplicate, or overly long title tags to meet best practices.

    Checks: titles

  5. 5

    Address Meta Description Issues

    Why: Optimized meta descriptions can improve search result visibility.

    How: Create unique, informative meta descriptions for all affected pages.

    Evidence: 174 pages have no meta description at all.

    174 pages affected

    Checks: meta-descriptions

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 significant security gaps, including missing HTTP headers essential for protecting user data. Key issues involve vulnerabilities in JavaScript libraries and inadequate cookie protection. Immediate remediation is advised for a more secure web presence.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors typing the URL without HTTPS are at risk of interception.

    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: Without CSP, the site is vulnerable to script-injection attacks.

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

    Evidence: Content Security Policy

  3. 3

    No Clickjacking ProtectionMedium

    Why it matters: Pages can be embedded in frames on other sites, increasing risks of clickjacking.

    Fix: Set `X-Frame-Options: DENY` or use a CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  4. 4

    Insecure Cookie FlagsMedium

    Why it matters: Cookies are vulnerable to access via scripts and insecure connections.

    Fix: Set cookies with `Secure; HttpOnly; SameSite=Strict` attributes.

    Evidence: Cookie flags

  5. 5

    Vulnerable JavaScript LibrariesMedium

    Why it matters: Outdated libraries expose the site to known vulnerabilities.

    Fix: Update jQuery to version 3.5.0 or higher to eliminate vulnerabilities.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Lack of MIME Sniffing ProtectionLow

    Why it matters: Browsers might misinterpret content types, increasing vulnerability.

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

    Evidence: MIME sniffing protection

  7. 7

    Absence of Referrer PolicyLow

    Why it matters: Full URLs, including sensitive data, may be shared with external sites.

    Fix: Set `Referrer-Policy: no-referrer` to limit referrer information.

    Evidence: Referrer policy

  8. 8

    No Permissions PolicyInfo

    Why it matters: Default browser features are enabled, increasing potential attack vectors.

    Fix: Add `Permissions-Policy: features=('none')` to restrict unused features.

    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://www.advocateslaw.com/ → no strict-transport-security
    • https://www.advocateslaw.com/seattle/ → no strict-transport-security
    • https://www.advocateslaw.com/spokane/ → no strict-transport-security
    • https://www.advocateslaw.com/portland/ → no strict-transport-security
    • https://www.advocateslaw.com/es/ → no strict-transport-security
    • https://www.advocateslaw.com/what-is-an-advocate/ → no strict-transport-security
    • https://www.advocateslaw.com/about-ken-and-doni/ → no strict-transport-security
    • https://www.advocateslaw.com/testimonials/ → no strict-transport-security
    • https://www.advocateslaw.com/community-involvement/ → no strict-transport-security
    • https://www.advocateslaw.com/our-results/ → no strict-transport-security
    • https://www.advocateslaw.com/our-lawyers/ → no strict-transport-security
    • https://www.advocateslaw.com/cases-we-handle/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 503 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.advocateslaw.com/ → no content-security-policy
    • https://www.advocateslaw.com/seattle/ → no content-security-policy
    • https://www.advocateslaw.com/spokane/ → no content-security-policy
    • https://www.advocateslaw.com/portland/ → no content-security-policy
    • https://www.advocateslaw.com/es/ → no content-security-policy
    • https://www.advocateslaw.com/what-is-an-advocate/ → no content-security-policy
    • https://www.advocateslaw.com/about-ken-and-doni/ → no content-security-policy
    • https://www.advocateslaw.com/testimonials/ → no content-security-policy
    • https://www.advocateslaw.com/community-involvement/ → no content-security-policy
    • https://www.advocateslaw.com/our-results/ → no content-security-policy
    • https://www.advocateslaw.com/our-lawyers/ → no content-security-policy
    • https://www.advocateslaw.com/cases-we-handle/ → 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.advocateslaw.com/ → no x-frame-options
    • https://www.advocateslaw.com/seattle/ → no x-frame-options
    • https://www.advocateslaw.com/spokane/ → no x-frame-options
    • https://www.advocateslaw.com/portland/ → no x-frame-options
    • https://www.advocateslaw.com/es/ → no x-frame-options
    • https://www.advocateslaw.com/what-is-an-advocate/ → no x-frame-options
    • https://www.advocateslaw.com/about-ken-and-doni/ → no x-frame-options
    • https://www.advocateslaw.com/testimonials/ → no x-frame-options
    • https://www.advocateslaw.com/community-involvement/ → no x-frame-options
    • https://www.advocateslaw.com/our-results/ → no x-frame-options
    • https://www.advocateslaw.com/our-lawyers/ → no x-frame-options
    • https://www.advocateslaw.com/cases-we-handle/ → 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.advocateslaw.com/ → no x-content-type-options
    • https://www.advocateslaw.com/seattle/ → no x-content-type-options
    • https://www.advocateslaw.com/spokane/ → no x-content-type-options
    • https://www.advocateslaw.com/portland/ → no x-content-type-options
    • https://www.advocateslaw.com/es/ → no x-content-type-options
    • https://www.advocateslaw.com/what-is-an-advocate/ → no x-content-type-options
    • https://www.advocateslaw.com/about-ken-and-doni/ → no x-content-type-options
    • https://www.advocateslaw.com/testimonials/ → no x-content-type-options
    • https://www.advocateslaw.com/community-involvement/ → no x-content-type-options
    • https://www.advocateslaw.com/our-results/ → no x-content-type-options
    • https://www.advocateslaw.com/our-lawyers/ → no x-content-type-options
    • https://www.advocateslaw.com/cases-we-handle/ → 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.advocateslaw.com/ → no referrer-policy
    • https://www.advocateslaw.com/seattle/ → no referrer-policy
    • https://www.advocateslaw.com/spokane/ → no referrer-policy
    • https://www.advocateslaw.com/portland/ → no referrer-policy
    • https://www.advocateslaw.com/es/ → no referrer-policy
    • https://www.advocateslaw.com/what-is-an-advocate/ → no referrer-policy
    • https://www.advocateslaw.com/about-ken-and-doni/ → no referrer-policy
    • https://www.advocateslaw.com/testimonials/ → no referrer-policy
    • https://www.advocateslaw.com/community-involvement/ → no referrer-policy
    • https://www.advocateslaw.com/our-results/ → no referrer-policy
    • https://www.advocateslaw.com/our-lawyers/ → no referrer-policy
    • https://www.advocateslaw.com/cases-we-handle/ → 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.advocateslaw.com/ → no permissions-policy
    • https://www.advocateslaw.com/seattle/ → no permissions-policy
    • https://www.advocateslaw.com/spokane/ → no permissions-policy
    • https://www.advocateslaw.com/portland/ → no permissions-policy
    • https://www.advocateslaw.com/es/ → no permissions-policy
    • https://www.advocateslaw.com/what-is-an-advocate/ → no permissions-policy
    • https://www.advocateslaw.com/about-ken-and-doni/ → no permissions-policy
    • https://www.advocateslaw.com/testimonials/ → no permissions-policy
    • https://www.advocateslaw.com/community-involvement/ → no permissions-policy
    • https://www.advocateslaw.com/our-results/ → no permissions-policy
    • https://www.advocateslaw.com/our-lawyers/ → no permissions-policy
    • https://www.advocateslaw.com/cases-we-handle/ → no permissions-policy
  • FoundCookie flagsMedium

    12 of 14 cookies 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.

    • 06 Nov 2026 09:26:27 GMT (set by https://www.advocateslaw.com/?page_id=8674) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 09:33:02 GMT (set by https://www.advocateslaw.com/?page_id=8695) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 09:35:10 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8763) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 09:35:15 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8764) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 09:35:32 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8767) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 09:36:28 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8765) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 11:02:04 GMT (set by https://www.advocateslaw.com/old-car-vs-new-car-saftey/) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 11:03:15 GMT (set by https://www.advocateslaw.com/back-injury-explainer/) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 11:04:31 GMT (set by https://www.advocateslaw.com/washington-motorcycle-laws-what-you-need-to-know/) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 11:05:16 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8766) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 11:42:47 GMT (set by https://www.advocateslaw.com/cases-we-handle/seattle-car-accident-lawyer/) lacks Secure, HttpOnly, SameSite
    • 06 Nov 2026 13:50:20 GMT (set by https://www.advocateslaw.com/wp-content/uploads/2016/08/AdobeStock_118584325-mi…) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 3.2.2 in https://www.advocateslaw.com/wp-content/plugins/gravityforms/js/placeholders.jq…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
    • jQuery 3.2.1 in https://www.advocateslaw.com/wp-content/plugins/gravityforms/js/placeholders.jq…: CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • NoteSoftware version disclosure

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

    • server: cloudflare (900 responses)
    • x-powered-by: WP Engine (555 responses)
  • 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 (40 script tags)
    • widget.reviewability.com (5 script tags)
  • NoteSensitive paths in robots.txt

    robots.txt lists 8 paths 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/
    • Disallow: /wp-admin/
    • Disallow: /wp-admin/
    • Disallow: /wp-admin/
    • Disallow: /wp-admin/
    • Disallow: /wp-admin/
    • Disallow: /wp-admin/
    • Disallow: /wp-admin/
5 checks passed
  • OKHTTPS

    All 503 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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

Sites scoring near www.advocateslaw.com

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

Own www.advocateslaw.com?

  • 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.advocateslaw.com. Removal needs no account and no proof of purchase.