Scanned sites / pnwfamilylaw.com / 2026-09-14-1109

pnwfamilylaw.com scan from 2026-09-14 11:09:41 UTC DR 29

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

Scan 2026-09-14-1109

Scanned 2026-09-14 11:09:41 UTC, finished 2026-09-14 12:19:16 UTC. Found with openstreetmap overpass

Site: https://pnwfamilylaw.com/

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

71/ 100Needs work

On September 14, 2026 the Site Spider crawled 1870 pages and 751 assets of pnwfamilylaw.com, starting from https://pnwfamilylaw.com/. It scored 71 out of 100, a result that needs work. 10 of 27 checks found something to fix, led by meta descriptions (1,772), indexability (1,220), heavy assets (18); 7 checks passed. Most of the points went to meta descriptions (−7.8), indexability (−6.7), heavy assets (−6). 10 checks found something the score does not count, listed as noted. 10 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
1870
Assets fetched
751
Status
Completed
Checks with issues
10 of 27
CoverageComplete crawl

2,621 of 2,622 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 328 link destinations on other sites were checked, 47 left unchecked.

  • Title tags662 issues
    662 of 1773 pages have title issues. 39 noindex or canonicalized pages excluded.
    −3.7 points
  • Meta descriptions1,772 issues
    1772 of 1773 pages have meta description issues. 39 noindex or canonicalized pages excluded.
    −7.8 points
  • Headings57 issues
    57 of 1773 pages have heading issues. 39 noindex or canonicalized pages excluded.
    −0.2 points
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • Links to other sites12 issues
    12 destinations answered with an error, 32 could not be determined (timeouts, rate limits or refusals), 47 were left unchecked by the per-scan cap, of 300 destinations checked.
    −0.3 points
  • Redirects58 issues
    93 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses311 noted
    311 URLs did not return a 2xx response. 58 of them are pages, 0 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability1,220 issues
    1220 of 1773 indexable pages have indexability warnings. 39 pages noindex by design. 1 noindex page is listed in the sitemap, which asks search engines both to visit and to ignore it.
    −6.7 points
  • Image alt text2 issues
    2 of 5764 image references have no alt attribute. 216 use an empty alt (decorative), which is fine.
  • Heavy assets18 issues
    18 assets larger than 500 KB among 751 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages414 issues
    414 pages have no internal links pointing at them.
    −0.9 points
  • Sitemap coverage1,111 issues
    13 sitemaps listing 1081 URLs: 695 crawled pages missing, 2 listed URLs broken or redirecting, 413 reachable only via the sitemap.
    −3.7 points
  • Internal link counts133 noted
    Internal link counts for 500 pages; 133 worth a look.
  • Thin contentOK
    0 of 1773 pages have fewer than 200 words. 39 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format104 noted
    104 of 1870 page URLs are harder to read, share or cache than they need to be.
  • Canonicals1,257 noted
    1257 of 1812 pages have a canonical worth checking.
  • Robots directives1,812 noted
    1812 pages carry a robots directive; 0 carry none.
  • Anchor text389 noted
    389 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure501 noted
    501 of 1773 pages could use the title, heading and snippet space better. 39 noindex or canonicalized pages excluded.
  • Image weight and alt length7 noted
    0 images over 100 KB; 7 with alt text over 100 characters.
  • Response anomalies2 noted
    2 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 1812 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    0 cookies set by the site; 14 response headers recorded across 2621 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 1812 pages; 1741 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 Insights4 noted
    Mobile performance 87 on average across 5 pages; 4 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this scan sits among all scanned sites

2872 sites, median 80%, average 79%

pnwfamilylaw.com scores 71%, higher than 18% of the 2872 scanned sites. See the full ranking.

0751500%: 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%: 43 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%: 125 sites82%: 132 sites83%: 119 sites84%: 131 sites85%: 105 sites86%: 94 sites87%: 97 sites88%: 80 sites89%: 75 sites90%: 55 sites91%: 59 sites92%: 43 sites93%: 29 sites94%: 24 sites95%: 15 sites96%: 18 sites97%: 16 sites98%: 8 sites99%: 3 sites100%: 150 sites71% 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

Address some critical issues affecting search visibility and user experience, including non-200 responses and missing titles or meta descriptions. Prioritize high-impact fixes first.

  1. 1

    Fix Non-200 Responses

    Why: 311 URLs not returning 2xx responses can derail traffic.

    How: Redirect the broken URLs to their correct pages or update links accordingly.

    Checks: status-codes

  2. 2

    Revise Title Tags

    Why: 662 pages with title issues can hinder search engine visibility.

    How: Update title tags to be unique and under 60 characters for affected pages.

    Checks: titles

  3. 3

    Add Meta Descriptions

    Why: 1771 pages missing meta descriptions negatively affect click-through rates.

    How: Craft and add unique meta descriptions under 160 characters for affected pages.

    Checks: meta-descriptions

  4. 4

    Resolve Indexability Warnings

    Why: 1219 indexable pages with warnings can confuse search engines about content prioritization.

    How: Ensure all pages have proper canonical tags or are indexable as needed.

    Checks: indexability

  5. 5

    Address Redirects

    Why: 93 URLs redirecting might cause confusion and dilute page authority.

    How: Consolidate or correct unnecessary redirects within the site structure.

    Checks: redirects

  6. 6

    Fix Orphan Pages

    Why: 414 orphan pages lack internal linking, leading to poor visibility.

    How: Create internal links pointing to those orphan pages to improve navigation.

    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 crawl

Your site is missing critical security headers that can leave it vulnerable to attacks. Implementing these headers will improve your site's protection against data interception and malicious embedding. Prioritize adding security policies to shield your content and enhance your site's overall safety.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors accessing without HTTPS could be intercepted.

    Fix: Add the header: Strict-Transport-Security: max-age=63072000; includeSubDomains

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows unrestricted sources for scripts and resources, risking XSS attacks.

    Fix: Add the header: Content-Security-Policy: default-src 'self'; script-src 'self';

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: Lack of protection allows your pages to be embedded in other sites, risking clickjacking.

    Fix: Add the header: X-Frame-Options: DENY

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Absence of this header increases the risk of MIME sniffing vulnerabilities.

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

    Evidence: MIME sniffing protection

  5. 5

    Third-Party Scripts without Subresource IntegrityLow

    Why it matters: Using scripts from external domains without integrity checks can introduce vulnerabilities.

    Fix: Consider implementing Subresource Integrity (SRI) or a Content-Security-Policy to specify trusted sources.

    Evidence: Third-party scripts

  6. 6

    Sensitive Paths in robots.txtInfo

    Why it matters: Public robots.txt reveals private paths, which could aid attackers in probing the site.

    Fix: Restrict access to sensitive areas via proper authentication rather than relying solely 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://pnwfamilylaw.com/ → no strict-transport-security
    • https://pnwfamilylaw.com/our-approach-to-family-law/ → no strict-transport-security
    • https://pnwfamilylaw.com/divorce/ → no strict-transport-security
    • https://pnwfamilylaw.com/child-custody/ → no strict-transport-security
    • https://pnwfamilylaw.com/committed-intimate-relationships/ → no strict-transport-security
    • https://pnwfamilylaw.com/child-support/ → no strict-transport-security
    • https://pnwfamilylaw.com/adoption/ → no strict-transport-security
    • https://pnwfamilylaw.com/protection-orders/ → no strict-transport-security
    • https://pnwfamilylaw.com/estate-planning/ → no strict-transport-security
    • https://pnwfamilylaw.com/probate/ → no strict-transport-security
    • https://pnwfamilylaw.com/locations/ → no strict-transport-security
    • https://pnwfamilylaw.com/bellevue-wa/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 1812 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://pnwfamilylaw.com/ → no content-security-policy
    • https://pnwfamilylaw.com/our-approach-to-family-law/ → no content-security-policy
    • https://pnwfamilylaw.com/divorce/ → no content-security-policy
    • https://pnwfamilylaw.com/child-custody/ → no content-security-policy
    • https://pnwfamilylaw.com/committed-intimate-relationships/ → no content-security-policy
    • https://pnwfamilylaw.com/child-support/ → no content-security-policy
    • https://pnwfamilylaw.com/adoption/ → no content-security-policy
    • https://pnwfamilylaw.com/protection-orders/ → no content-security-policy
    • https://pnwfamilylaw.com/estate-planning/ → no content-security-policy
    • https://pnwfamilylaw.com/probate/ → no content-security-policy
    • https://pnwfamilylaw.com/locations/ → no content-security-policy
    • https://pnwfamilylaw.com/bellevue-wa/ → 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://pnwfamilylaw.com/ → no x-frame-options
    • https://pnwfamilylaw.com/our-approach-to-family-law/ → no x-frame-options
    • https://pnwfamilylaw.com/divorce/ → no x-frame-options
    • https://pnwfamilylaw.com/child-custody/ → no x-frame-options
    • https://pnwfamilylaw.com/committed-intimate-relationships/ → no x-frame-options
    • https://pnwfamilylaw.com/child-support/ → no x-frame-options
    • https://pnwfamilylaw.com/adoption/ → no x-frame-options
    • https://pnwfamilylaw.com/protection-orders/ → no x-frame-options
    • https://pnwfamilylaw.com/estate-planning/ → no x-frame-options
    • https://pnwfamilylaw.com/probate/ → no x-frame-options
    • https://pnwfamilylaw.com/locations/ → no x-frame-options
    • https://pnwfamilylaw.com/bellevue-wa/ → 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://pnwfamilylaw.com/ → no x-content-type-options
    • https://pnwfamilylaw.com/our-approach-to-family-law/ → no x-content-type-options
    • https://pnwfamilylaw.com/divorce/ → no x-content-type-options
    • https://pnwfamilylaw.com/child-custody/ → no x-content-type-options
    • https://pnwfamilylaw.com/committed-intimate-relationships/ → no x-content-type-options
    • https://pnwfamilylaw.com/child-support/ → no x-content-type-options
    • https://pnwfamilylaw.com/adoption/ → no x-content-type-options
    • https://pnwfamilylaw.com/protection-orders/ → no x-content-type-options
    • https://pnwfamilylaw.com/estate-planning/ → no x-content-type-options
    • https://pnwfamilylaw.com/probate/ → no x-content-type-options
    • https://pnwfamilylaw.com/locations/ → no x-content-type-options
    • https://pnwfamilylaw.com/bellevue-wa/ → no x-content-type-options
  • NoteThird-party scripts

    Scripts run from 5 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.)

    • c0.wp.com (133 script tags)
    • www.googletagmanager.com (40 script tags)
    • stats.wp.com (40 script tags)
    • www.google.com (18 script tags)
    • maps.googleapis.com (1 script tag)
  • 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/
6 checks passed, 4 not applicable
  • OKHTTPS

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

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

  • Not applicableReferrer policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicablePermissions policy

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableCookie flags

    This scan predates the crawler recording the headers this check needs. Rescan the site to check it.

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

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

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