Scanned sites / www.sandlawnd.com / 2026-10-02-1857

www.sandlawnd.com scan from 10/2/2026, 6:57:32 PM

Scan 2026-10-02-1857

Scanned 10/2/2026, 6:57:32 PM, finished 10/2/2026, 11:26:53 PM. Found on page 5 of brave web search results

Site: https://www.sandlawnd.com/

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

87/ 100Good

On October 2, 2026 the Site Spider crawled 464 pages and 1000 assets of www.sandlawnd.com, starting from https://www.sandlawnd.com/. It scored 87 out of 100, a good result. 10 of 16 checks found something to fix, led by heavy assets (45), title tags (224), links to other sites (38); 5 checks passed. Most of the points went to heavy assets (−6), title tags (−4.9), links to other sites (−3.3). 1 check found something the score does not count, listed as noted. 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 1 info findings. See the security findings ↓

Pages crawled
464
Assets fetched
1000
Status
Completed
Checks with issues
10 of 16
CoverageJob finished, partial coverage

1,464 of 1,464 discovered URLs were fetched, 221 left out by the 5,000-page and 1,000-asset budget. The job finished, but the crawl did not reach everything it found. HTML only: nothing here ran JavaScript. 300 link destinations on other sites were checked, 529 left unchecked.

  • Title tags224 issues
    224 of 376 pages have title issues. 81 noindex or canonicalized pages excluded.
    −4.9 points
  • Meta descriptions54 issues
    54 of 376 pages have meta description issues. 81 noindex or canonicalized pages excluded.
    −0.9 points
  • Headings2 issues
    2 of 376 pages have heading issues. 81 noindex or canonicalized pages excluded.
  • Broken links1 issue
    9 internal links point at 1 broken URL.
  • Links to other sites38 issues
    38 destinations answered with an error, 105 could not be determined (timeouts, rate limits or refusals), 529 were left unchecked by the per-scan cap, of 300 destinations checked.
    −3.3 points
  • Redirects6 issues
    7 redirecting URLs, 0 of them chained.
    −0.1 points
  • Non-200 responses1 issue
    9 URLs did not return a 2xx response. 7 of them are pages, 1 with an error status; the rest are assets or redirects.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 443 indexable pages have indexability warnings. 14 pages noindex by design.
  • Image alt textOK
    0 of 459 image references have no alt attribute. 15 use an empty alt (decorative), which is fine.
  • Heavy assets45 issues
    45 assets larger than 500 KB among 1000 fetched assets.
    −6 points
  • Orphan pages22 issues
    22 pages have no internal links pointing at them.
    −0.2 points
  • Sitemap coverage40 issues
    5 sitemaps listing 358 URLs: 18 crawled pages missing, 0 listed URLs broken or redirecting, 22 reachable only via the sitemap.
    −0.5 points
  • Internal link countsOK
    Internal link counts for 457 pages.
  • Thin contentOK
    0 of 376 pages have fewer than 200 words. 81 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1883 sites, median 80%, average 79%

www.sandlawnd.com scores 87%, higher than 79% of the 1883 scanned sites. See the full ranking.

0541080%: 0 sites1%: 0 sites2%: 0 sites3%: 0 sites4%: 0 sites5%: 0 sites6%: 0 sites7%: 0 sites8%: 0 sites9%: 0 sites10%: 0 sites11%: 0 sites12%: 0 sites13%: 0 sites14%: 0 sites15%: 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%: 2 sites38%: 2 sites39%: 1 site40%: 2 sites41%: 2 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 4 sites46%: 2 sites47%: 3 sites48%: 2 sites49%: 7 sites50%: 4 sites51%: 5 sites52%: 8 sites53%: 6 sites54%: 7 sites55%: 4 sites56%: 6 sites57%: 6 sites58%: 14 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 16 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 21 sites67%: 36 sites68%: 30 sites69%: 26 sites70%: 39 sites71%: 40 sites72%: 56 sites73%: 52 sites74%: 49 sites75%: 61 sites76%: 73 sites77%: 72 sites78%: 88 sites79%: 68 sites80%: 91 sites81%: 108 sites82%: 85 sites83%: 86 sites84%: 86 sites85%: 63 sites86%: 73 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 35 sites91%: 36 sites92%: 28 sites93%: 15 sites94%: 13 sites95%: 12 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites87% 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

Your website has several SEO issues to address, including broken links, redirect chains, and metadata improvements. Focus on fixing internal link errors first, as they affect user experience and SEO significantly.

  1. 1

    Fix Broken Links

    Why: Fixing broken links improves user experience and eliminates 404 errors.

    How: Update or remove links pointing to the broken URL: https://www.sandlawnd.com/products-that-can-raise-blood-alcohol-content.

    Checks: broken-links

  2. 2

    Address Non-200 Responses

    Why: Ensuring URLs return 200 responses improves site credibility and usability.

    How: Investigate and update the 9 URLs not returning 2xx responses, particularly focusing on resolving redirect issues.

    Checks: status-codes

  3. 3

    Improve Title Tags

    Why: Optimizing titles enhances click-through rates from search results.

    How: Revise the 224 pages with title issues to ensure uniqueness and appropriate length.

    Checks: titles

  4. 4

    Enhance Meta Descriptions

    Why: Unique meta descriptions can improve search visibility and CTR.

    How: Customize meta descriptions for the 54 pages with issues, specifically addressing duplicates.

    Checks: meta-descriptions

  5. 5

    Clean Up Redirects

    Why: Reducing unnecessary redirects improves page load times and user satisfaction.

    How: Review and streamline the 7 redirecting URLs to ensure they lead to relevant pages.

    Checks: redirects

  6. 6

    Fix Orphan Pages

    Why: Connecting orphan pages improves navigability and indexing opportunities.

    How: Add internal links to the 22 orphan pages so users and search engines can access them.

    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

The website lacks important security headers which can expose users to various risks, including interception of communications and clickjacking. Implementing HTTPS Strict Transport Security, Content Security Policy, and other security measures is essential for protecting user data and ensuring site integrity.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users may be intercepted on the initial request by not using HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Absence of CSP allows scripts and styles to load from any source, increasing the risk of Cross-Site Scripting (XSS).

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

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without this header, the site can be framed by malicious sites, risking clickjacking attacks.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-OptionsLow

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

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-PolicyLow

    Why it matters: Lack of referrer policy may expose sensitive URL information when users navigate away from the site.

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

    Evidence: Referrer policy

  6. 6

    Third-Party Scripts Without Subresource Integrity (SRI)Low

    Why it matters: Using external scripts without SRI poses a risk of compromising the site's functionality.

    Fix: Implement a Content Security Policy that includes trusted sources for scripts.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions-PolicyInfo

    Why it matters: Not using this policy can allow scripts to access restricted features that may not be necessary.

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

    Evidence: Permissions policy

What the checks found

  • FoundHTTP Strict Transport SecurityMedium

    100 of 457 HTML pages send strict-transport-security. Without it a visitor who types the address without https:// can be intercepted on the first request.

    • https://www.sandlawnd.com/ → no strict-transport-security
    • https://www.sandlawnd.com/firm-overview/ → no strict-transport-security
    • https://www.sandlawnd.com/firm-overview/proven-process/ → no strict-transport-security
    • https://www.sandlawnd.com/your-team/ → no strict-transport-security
    • https://www.sandlawnd.com/results/ → no strict-transport-security
    • https://www.sandlawnd.com/testimonials/ → no strict-transport-security
    • https://www.sandlawnd.com/firm-overview/career-opportunities/ → no strict-transport-security
    • https://www.sandlawnd.com/newsroom/ → no strict-transport-security
    • https://www.sandlawnd.com/payments/ → no strict-transport-security
    • https://www.sandlawnd.com/blog/ → no strict-transport-security
    • https://www.sandlawnd.com/practice-areas/criminal-defense/ → no strict-transport-security
    • https://www.sandlawnd.com/arrested-north-dakota-need-know/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 457 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.sandlawnd.com/ → no content-security-policy
    • https://www.sandlawnd.com/firm-overview/ → no content-security-policy
    • https://www.sandlawnd.com/firm-overview/proven-process/ → no content-security-policy
    • https://www.sandlawnd.com/your-team/ → no content-security-policy
    • https://www.sandlawnd.com/results/ → no content-security-policy
    • https://www.sandlawnd.com/testimonials/ → no content-security-policy
    • https://www.sandlawnd.com/firm-overview/career-opportunities/ → no content-security-policy
    • https://www.sandlawnd.com/newsroom/ → no content-security-policy
    • https://www.sandlawnd.com/payments/ → no content-security-policy
    • https://www.sandlawnd.com/blog/ → no content-security-policy
    • https://www.sandlawnd.com/practice-areas/criminal-defense/ → no content-security-policy
    • https://www.sandlawnd.com/arrested-north-dakota-need-know/ → no content-security-policy
  • FoundClickjacking protectionMedium

    100 of 457 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://www.sandlawnd.com/ → no x-frame-options
    • https://www.sandlawnd.com/firm-overview/ → no x-frame-options
    • https://www.sandlawnd.com/firm-overview/proven-process/ → no x-frame-options
    • https://www.sandlawnd.com/your-team/ → no x-frame-options
    • https://www.sandlawnd.com/results/ → no x-frame-options
    • https://www.sandlawnd.com/testimonials/ → no x-frame-options
    • https://www.sandlawnd.com/firm-overview/career-opportunities/ → no x-frame-options
    • https://www.sandlawnd.com/newsroom/ → no x-frame-options
    • https://www.sandlawnd.com/payments/ → no x-frame-options
    • https://www.sandlawnd.com/blog/ → no x-frame-options
    • https://www.sandlawnd.com/practice-areas/criminal-defense/ → no x-frame-options
    • https://www.sandlawnd.com/arrested-north-dakota-need-know/ → no x-frame-options
  • FoundMIME sniffing protectionLow

    100 of 457 HTML pages send 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.sandlawnd.com/ → no x-content-type-options
    • https://www.sandlawnd.com/firm-overview/ → no x-content-type-options
    • https://www.sandlawnd.com/firm-overview/proven-process/ → no x-content-type-options
    • https://www.sandlawnd.com/your-team/ → no x-content-type-options
    • https://www.sandlawnd.com/results/ → no x-content-type-options
    • https://www.sandlawnd.com/testimonials/ → no x-content-type-options
    • https://www.sandlawnd.com/firm-overview/career-opportunities/ → no x-content-type-options
    • https://www.sandlawnd.com/newsroom/ → no x-content-type-options
    • https://www.sandlawnd.com/payments/ → no x-content-type-options
    • https://www.sandlawnd.com/blog/ → no x-content-type-options
    • https://www.sandlawnd.com/practice-areas/criminal-defense/ → no x-content-type-options
    • https://www.sandlawnd.com/arrested-north-dakota-need-know/ → no x-content-type-options
  • FoundReferrer policyLow

    100 of 457 HTML pages send 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.sandlawnd.com/ → no referrer-policy
    • https://www.sandlawnd.com/firm-overview/ → no referrer-policy
    • https://www.sandlawnd.com/firm-overview/proven-process/ → no referrer-policy
    • https://www.sandlawnd.com/your-team/ → no referrer-policy
    • https://www.sandlawnd.com/results/ → no referrer-policy
    • https://www.sandlawnd.com/testimonials/ → no referrer-policy
    • https://www.sandlawnd.com/firm-overview/career-opportunities/ → no referrer-policy
    • https://www.sandlawnd.com/newsroom/ → no referrer-policy
    • https://www.sandlawnd.com/payments/ → no referrer-policy
    • https://www.sandlawnd.com/blog/ → no referrer-policy
    • https://www.sandlawnd.com/practice-areas/criminal-defense/ → no referrer-policy
    • https://www.sandlawnd.com/arrested-north-dakota-need-know/ → no referrer-policy
  • FoundPermissions policyInfo

    100 of 457 HTML pages send 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.sandlawnd.com/ → no permissions-policy
    • https://www.sandlawnd.com/firm-overview/ → no permissions-policy
    • https://www.sandlawnd.com/firm-overview/proven-process/ → no permissions-policy
    • https://www.sandlawnd.com/your-team/ → no permissions-policy
    • https://www.sandlawnd.com/results/ → no permissions-policy
    • https://www.sandlawnd.com/testimonials/ → no permissions-policy
    • https://www.sandlawnd.com/firm-overview/career-opportunities/ → no permissions-policy
    • https://www.sandlawnd.com/newsroom/ → no permissions-policy
    • https://www.sandlawnd.com/payments/ → no permissions-policy
    • https://www.sandlawnd.com/blog/ → no permissions-policy
    • https://www.sandlawnd.com/practice-areas/criminal-defense/ → no permissions-policy
    • https://www.sandlawnd.com/arrested-north-dakota-need-know/ → no permissions-policy
  • 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.)

    • www.googletagmanager.com (40 script tags)
    • px.premion.com (40 script tags)
    • cdn.jotfor.ms (62 script tags)
    • cdn.callrail.com (39 script tags)
    • cpats.s3.amazonaws.com (1 script tag)
7 checks passed, 2 not applicable
  • OKHTTPS

    All 457 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.

  • OKVulnerable JavaScript libraries

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

  • OKSensitive paths in robots.txt

    robots.txt does not point at admin, backup or private paths.

  • Not applicableCookie flags

    The crawl set no cookies, so there are no cookie flags to check.

  • Not applicableForms over HTTPS

    No forms were found on the sampled pages.

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.sandlawnd.com

Their neighbours in the SEO rank table, which orders every scanned site by health score.

This report was produced by the DIY SEO Hub Site Spider crawling www.sandlawnd.com from its pages as published, the way a search engine does. It shows summary figures only.

Own www.sandlawnd.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.sandlawnd.com. Removal needs no account and no proof of purchase.
www.sandlawnd.com scan 2026-10-02-1857 | DIY SEO Hub