Scanned sites / www.advocateslaw.com / 2026-11-04-0714

www.advocateslaw.com scan from 2026-11-04 07:14:32 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-04-0714

Scanned 2026-11-04 07:14:32 UTC, finished 2026-11-04 22:11:41 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 4, 2026 the Site Spider crawled 571 pages and 338 assets of www.advocateslaw.com, starting from https://www.advocateslaw.com/. It scored 82 out of 100, a good result. 11 of 33 checks found something to fix, led by heavy assets (11), meta descriptions (303), title tags (200); 9 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
571
Assets fetched
338
Status
Completed
Checks with issues
11 of 33
CoverageComplete crawl

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

  • Title tags200 issues
    200 of 430 pages have title issues. 72 noindex or canonicalized pages excluded.
    −4 points
  • Meta descriptions303 issues
    303 of 430 pages have meta description issues. 72 noindex or canonicalized pages excluded.
    −4.8 points
  • Headings3 issues
    3 of 430 pages have heading issues. 72 noindex or canonicalized pages excluded.
  • Broken links11 issues
    46 internal links point at 11 broken URLs.
    −0.4 points
  • Links to other sites3 issues
    3 destinations answered with an error, 58 could not be determined (timeouts, rate limits or refusals), 312 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.2 points
  • Redirects59 issues
    62 redirecting URLs, 18 of them chained.
    −0.5 points
  • Non-200 responses12 issues
    75 URLs did not return a 2xx response. 69 of them are pages, 12 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. 52 pages noindex by design.
    −0.9 points
  • Image alt textOK
    0 of 2391 image references have no alt attribute. 640 use an empty alt (decorative), which is fine.
  • Heavy assets11 issues
    11 assets larger than 500 KB among 338 fetched assets.
    −6 points
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverage109 issues
    9 sitemaps listing 337 URLs: 101 crawled pages missing, 7 listed URLs broken or redirecting, 1 reachable only via the sitemap.
    −1.3 points
  • Internal link counts104 noted
    Internal link counts for 500 pages; 104 worth a look.
  • Thin contentOK
    0 of 430 pages have fewer than 200 words. 72 noindex or canonicalized pages excluded.
  • Duplicate content12 issues
    1 group of pages with identical HTML.
    −0.2 points
  • URL format18 noted
    18 of 571 page URLs are harder to read, share or cache than they need to be.
  • Canonicals72 noted
    72 of 502 pages have a canonical worth checking.
  • Robots directives496 noted
    496 pages carry a robots directive; 6 carry none.
  • Anchor text92 noted
    92 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. 72 noindex or canonicalized pages excluded.
  • Image weight and alt length119 noted
    92 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 502 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured data20 noted
    500 of 430 indexable pages carry structured data: WebSite (499), BreadcrumbList (498), ListItem (498), https://www.schema.org/SiteNavigationElement (497), LegalService (308). 20 pages with errors a rich result would fail on.
  • Near duplicates42 noted
    42 pages in 21 groups read almost the same as another page (95% alike or more).
  • Soft 404sOK
    None of 502 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
    231 pages in pagination sequences; 20 with problems.
  • Headers and cookiesOK
    2 cookies set by the site; 13 response headers recorded across 909 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 502 pages; 300 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

2857 sites, median 80%, average 79%

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

0741480%: 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%: 6 sites52%: 8 sites53%: 9 sites54%: 10 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 21 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 79 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 108 sites78%: 131 sites79%: 111 sites80%: 127 sites81%: 124 sites82%: 132 sites83%: 120 sites84%: 129 sites85%: 107 sites86%: 96 sites87%: 94 sites88%: 79 sites89%: 74 sites90%: 55 sites91%: 58 sites92%: 43 sites93%: 28 sites94%: 25 sites95%: 14 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 148 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

The site identified several critical issues affecting SEO performance. Key actions include fixing broken links, addressing redirects, and improving title and meta descriptions. Implementing these changes will enhance user experience and search visibility.

  1. 1

    Fix Broken Links

    Why: 46 internal links are broken, harming user experience and SEO.

    How: Identify and update or remove 46 broken links pointing to the 11 URLs.

    Checks: broken-links

  2. 2

    Address Redirects

    Why: 62 URLs are redirecting, with 18 being chained, which can hurt loading times.

    How: Minimize chain redirects by updating internal links to point directly to final URLs.

    Checks: redirects

  3. 3

    Optimize Title Tags

    Why: 200 pages have title issues affecting search rankings.

    How: Revise titles on the identified pages to ensure they are concise and unique.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: 303 pages lack effective meta descriptions, impacting click-through rates.

    How: Create concise and relevant meta descriptions for all affected pages.

    Evidence: 173 pages have no meta description at all.

    173 pages affected

    Checks: meta-descriptions

  5. 5

    Fix Heading Issues

    Why: 3 pages have multiple H1s, which could confuse search engines.

    How: Ensure each page has one H1 and adjust the H2s accordingly.

    Checks: headings

  6. 6

    Shrink Heavy Assets

    Why: 11 assets exceed 500 KB, affecting loading speed.

    How: Compress or optimize large assets to improve loading performance, beginning with the largest.

    Evidence: 478 KB of stylesheet, loaded by 275 pages, so every visitor to any of them downloads it.

    275 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

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 essential security headers and has cookies missing protective flags. Additionally, there is a vulnerable JavaScript library present. These findings expose the site to potential threats. Implementing the suggested fixes will enhance overall security.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on their first request if they use HTTP.

    Fix: Add the header: "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload".

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: No CSP means arbitrary content can be loaded, increasing XSS risks.

    Fix: Add the header: "Content-Security-Policy: default-src 'self'".

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of this header allows clickjacking attacks by embedding the site in a frame.

    Fix: Add the header: "X-Frame-Options: DENY" or configure CSP with frame-ancestors.

    Evidence: Clickjacking protection

  4. 4

    Missing HttpOnly, Secure, and SameSite Cookie FlagsMedium

    Why it matters: Cookies can be accessed by scripts and sent on insecure connections.

    Fix: Set cookies with flags: Secure, HttpOnly, SameSite=Lax.

    Evidence: Cookie flags

  5. 5

    Vulnerable jQuery Library DetectedMedium

    Why it matters: Version 3.2.1 has known vulnerabilities that could be exploited.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  6. 6

    Missing X-Content-Type-Options HeaderLow

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

    Fix: Add the header: "X-Content-Type-Options: nosniff".

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer Policy HeaderLow

    Why it matters: Lack of this header may expose sensitive URL information to other sites.

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

    Evidence: Referrer policy

  8. 8

    Missing Permissions Policy HeaderInfo

    Why it matters: This header could restrict access to unused browser features.

    Fix: Add the header: "Permissions-Policy: geolocation=(), microphone=(), camera=()".

    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 502 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

    13 of 15 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.

    • 04 Nov 2026 09:02:28 GMT (set by https://www.advocateslaw.com/?page_id=8674) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 09:17:51 GMT (set by https://www.advocateslaw.com/?page_id=8695) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 09:36:14 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8763) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 09:36:28 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8764) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 09:46:28 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8767) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 09:47:31 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8765) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 09:47:36 GMT (set by https://www.advocateslaw.com/es/?post_type=practices&p=8766) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 15:28:01 GMT (set by https://www.advocateslaw.com/faq/how-long-does-a-truck-accident-settlement-take/) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 17:04:25 GMT (set by https://www.advocateslaw.com/old-car-vs-new-car-saftey/) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 17:06:31 GMT (set by https://www.advocateslaw.com/washington-motorcycle-laws-what-you-need-to-know/) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 18:13:22 GMT (set by https://www.advocateslaw.com/back-injury-explainer/) lacks Secure, HttpOnly, SameSite
    • 04 Nov 2026 18:38:18 GMT (set by https://www.advocateslaw.com/cases-we-handle/seattle-car-accident-lawyer/) lacks Secure, HttpOnly, SameSite
  • FoundVulnerable JavaScript librariesMedium

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

    • 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 (909 responses)
    • x-powered-by: WP Engine (565 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 (2 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 502 crawled pages were served over HTTPS.

  • OKMixed content

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

  • OKForms over HTTPS

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