Scanned sites / www.lairdcowley.com / 2026-11-01-1741

www.lairdcowley.com scan from 2026-11-01 17:41:54 UTC DR 4

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

Scan 2026-11-01-1741

Scanned 2026-11-01 17:41:54 UTC, finished 2026-11-01 18:29:41 UTC. Found on page 5 of brave web search results

Site: https://www.lairdcowley.com/

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

81/ 100Good

On November 1, 2026 the Site Spider crawled 107 pages and 233 assets of www.lairdcowley.com, starting from https://www.lairdcowley.com/. It scored 81 out of 100, a good result. 10 of 33 checks found something to fix, led by meta descriptions (27), heavy assets (6), title tags (17); 13 checks passed. Most of the points went to meta descriptions (−3.6), heavy assets (−3.6), title tags (−2.8). 10 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
107
Assets fetched
233
Status
Completed
Checks with issues
10 of 33
CoverageComplete crawl

340 of 343 discovered URLs were fetched. The crawl reached everything it found. HTML only: nothing here ran JavaScript. 22 link destinations on other sites were checked.

  • Title tags17 issues
    17 of 44 pages have title issues. 16 noindex or canonicalized pages excluded.
    −2.8 points
  • Meta descriptions27 issues
    27 of 44 pages have meta description issues. 16 noindex or canonicalized pages excluded.
    −3.6 points
  • Headings1 issue
    1 of 44 pages have heading issues. 16 noindex or canonicalized pages excluded.
    −0.1 points
  • Broken links5 issues
    8 internal links point at 5 broken URLs.
    −1.7 points
  • Links to other sites109 noted
    0 destinations answered with an error, 13 could not be determined (timeouts, rate limits or refusals), of 22 destinations checked.
  • Redirects36 issues
    34 redirecting URLs, 7 of them chained.
    −2.4 points
  • Non-200 responses14 issues
    50 URLs did not return a 2xx response. 47 of them are pages, 14 with an error status; the rest are assets or redirects.
    −2.3 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability5 issues
    5 of 44 indexable pages have indexability warnings. 16 pages noindex by design. 5 noindex pages are listed in the sitemap, which asks search engines both to visit and to ignore them.
    −0.8 points
  • Image alt textOK
    0 of 119 image references have no alt attribute.
  • Heavy assets6 issues
    6 assets larger than 500 KB among 233 fetched assets. 1 document over that size is listed but not counted: downloads are not page weight.
    −3.6 points
  • Orphan pages13 issues
    13 pages have no internal links pointing at them.
    −0.9 points
  • Sitemap coverage12 issues
    3 sitemaps listing 49 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 7 reachable only via the sitemap.
    −1.2 points
  • Internal link counts13 noted
    Internal link counts for 60 pages; 13 worth a look.
  • Thin contentOK
    0 of 44 pages have fewer than 200 words. 16 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.
  • URL format23 noted
    23 of 107 page URLs are harder to read, share or cache than they need to be.
  • Canonicals11 noted
    11 of 60 pages have a canonical worth checking.
  • Robots directives60 noted
    60 pages carry a robots directive; 0 carry none.
  • Anchor text22 noted
    22 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure1 noted
    1 of 44 pages could use the title, heading and snippet space better. 16 noindex or canonicalized pages excluded.
  • Image weight and alt length6 noted
    6 images over 100 KB; 0 with alt text over 100 characters.
  • Response anomaliesOK
    No redirect loops, header redirects or pages served as something other than HTML.
  • HTML and head validationOK
    All 60 pages keep their head tags in <head>, once each, under Googlebot's 2 MB.
  • hreflangOK
    No page declares hreflang.
  • Structured dataOK
    50 of 44 indexable pages carry structured data: WebSite (50), BreadcrumbList (49), ListItem (49), WebPage (49). 0 pages with errors a rich result would fail on.
  • Near duplicatesOK
    No near duplicates among 41 pages with enough text to compare.
  • Soft 404sOK
    None of 60 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 positions4 noted
    4 of 37 linked pages are linked only from the template, never from another page's content.
  • PaginationOK
    No page declares rel=next or rel=prev pagination.
  • Headers and cookiesOK
    0 cookies set by the site; 12 response headers recorded across 340 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 60 pages; 0 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.
  • Spelling11 noted
    11 words an English dictionary does not know, on 14 pages. Product names and jargon will appear here too.

Where this scan sits among all scanned sites

2494 sites, median 80%, average 78%

www.lairdcowley.com scores 81%, higher than 54% of the 2494 scanned sites. See the full ranking.

0591180%: 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%: 1 site45%: 4 sites46%: 5 sites47%: 5 sites48%: 4 sites49%: 7 sites50%: 5 sites51%: 6 sites52%: 8 sites53%: 8 sites54%: 8 sites55%: 10 sites56%: 8 sites57%: 12 sites58%: 18 sites59%: 8 sites60%: 16 sites61%: 12 sites62%: 20 sites63%: 28 sites64%: 21 sites65%: 31 sites66%: 36 sites67%: 36 sites68%: 37 sites69%: 49 sites70%: 48 sites71%: 73 sites72%: 72 sites73%: 74 sites74%: 72 sites75%: 75 sites76%: 88 sites77%: 99 sites78%: 112 sites79%: 98 sites80%: 118 sites81%: 111 sites82%: 112 sites83%: 112 sites84%: 116 sites85%: 94 sites86%: 78 sites87%: 85 sites88%: 60 sites89%: 70 sites90%: 45 sites91%: 52 sites92%: 40 sites93%: 27 sites94%: 21 sites95%: 13 sites96%: 14 sites97%: 14 sites98%: 6 sites99%: 2 sites100%: 68 sites81% 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 site has a good health score, but there are issues with broken links, redirects, title tags, meta descriptions, and more. Prioritize fixes to enhance user experience and SEO.

  1. 1

    Fix Broken Links

    Why: These broken links can harm user experience and SEO.

    How: Update/remove links pointing to broken URLs (e.g., /tom-bell/).

    Checks: broken-links

  2. 2

    Address Redirects

    Why: Chained redirects can slow site performance and confuse search engines.

    How: Simplify URLs and minimize redirects, especially the 7 chained ones.

    Checks: redirects

  3. 3

    Optimize Title Tags

    Why: Missing/incorrect title tags can affect click-through rates.

    How: Revise titles exceeding 60 characters or too brief; ensure uniqueness.

    Checks: titles

  4. 4

    Improve Meta Descriptions

    Why: Missing descriptions can result in lower search visibility.

    How: Add concise, unique meta descriptions for all pages without them.

    Checks: meta-descriptions

  5. 5

    Resolve Indexability Warnings

    Why: Pages listed as noindex should not be in the sitemap, hindering SEO.

    How: Remove noindex pages from the sitemap or change their index status.

    Checks: indexability, sitemap-coverage

  6. 6

    Shrink Heavy Assets

    Why: Large assets slow down page loading times which can impact user experience.

    How: Reduce sizes of large scripts/stylesheets or move non-essential ones.

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

    50 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

Your website has several important security issues that need attention, including missing response headers like HTTP Strict Transport Security and Content Security Policy. Additionally, there are vulnerabilities in an outdated JavaScript library and exposed API keys. Addressing these concerns will help enhance your site's security and protect user data.

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

    Missing HTTP Strict Transport SecurityMedium

    Why it matters: Without HSTS, users can be intercepted on their first request if they type the address without HTTPS.

    Fix: Add `Strict-Transport-Security: max-age=31536000; includeSubDomains` to response headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: No CSP means scripts and styles can be loaded from anywhere, increasing XSS risk.

    Fix: Add `Content-Security-Policy: default-src 'self';` to response headers.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-OptionsMedium

    Why it matters: Without it, your pages can be embedded in frames, risking clickjacking attacks.

    Fix: Add `X-Frame-Options: DENY` to response headers.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: jQuery 2.8.18 has known vulnerabilities that could be exploited depending on usage.

    Fix: Upgrade jQuery to version 3.5.0 or higher.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: An exposed API key can lead to unauthorized access to your Google services.

    Fix: Restrict the API key in the Google Cloud console by HTTP referrer and review its usage.

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-OptionsLow

    Why it matters: The absence of this header may allow browsers to incorrectly interpret files.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, full addresses are sent when users navigate away.

    Fix: Add `Referrer-Policy: no-referrer` to response headers.

    Evidence: Referrer policy

  8. 8

    Missing Permissions PolicyInfo

    Why it matters: No policy means all browser features remain available, which could be exploited.

    Fix: Add `Permissions-Policy: none` to response headers to limit 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.lairdcowley.com/ → no strict-transport-security
    • https://www.lairdcowley.com/about-us/ → no strict-transport-security
    • https://www.lairdcowley.com/locations/ → no strict-transport-security
    • https://www.lairdcowley.com/missoula-location/ → no strict-transport-security
    • https://www.lairdcowley.com/helena-location/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas-overview/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas/commercial-litigation/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas/personal-injury/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas/insurance-litgation/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas/professional-negligence/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas/family-law/ → no strict-transport-security
    • https://www.lairdcowley.com/practice-areas/employment-law/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 60 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.lairdcowley.com/ → no content-security-policy
    • https://www.lairdcowley.com/about-us/ → no content-security-policy
    • https://www.lairdcowley.com/locations/ → no content-security-policy
    • https://www.lairdcowley.com/missoula-location/ → no content-security-policy
    • https://www.lairdcowley.com/helena-location/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas-overview/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas/commercial-litigation/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas/personal-injury/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas/insurance-litgation/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas/professional-negligence/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas/family-law/ → no content-security-policy
    • https://www.lairdcowley.com/practice-areas/employment-law/ → 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.lairdcowley.com/ → no x-frame-options
    • https://www.lairdcowley.com/about-us/ → no x-frame-options
    • https://www.lairdcowley.com/locations/ → no x-frame-options
    • https://www.lairdcowley.com/missoula-location/ → no x-frame-options
    • https://www.lairdcowley.com/helena-location/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas-overview/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas/commercial-litigation/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas/personal-injury/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas/insurance-litgation/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas/professional-negligence/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas/family-law/ → no x-frame-options
    • https://www.lairdcowley.com/practice-areas/employment-law/ → 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.lairdcowley.com/ → no x-content-type-options
    • https://www.lairdcowley.com/about-us/ → no x-content-type-options
    • https://www.lairdcowley.com/locations/ → no x-content-type-options
    • https://www.lairdcowley.com/missoula-location/ → no x-content-type-options
    • https://www.lairdcowley.com/helena-location/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas-overview/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas/commercial-litigation/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas/personal-injury/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas/insurance-litgation/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas/professional-negligence/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas/family-law/ → no x-content-type-options
    • https://www.lairdcowley.com/practice-areas/employment-law/ → 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.lairdcowley.com/ → no referrer-policy
    • https://www.lairdcowley.com/about-us/ → no referrer-policy
    • https://www.lairdcowley.com/locations/ → no referrer-policy
    • https://www.lairdcowley.com/missoula-location/ → no referrer-policy
    • https://www.lairdcowley.com/helena-location/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas-overview/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas/commercial-litigation/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas/personal-injury/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas/insurance-litgation/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas/professional-negligence/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas/family-law/ → no referrer-policy
    • https://www.lairdcowley.com/practice-areas/employment-law/ → 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.lairdcowley.com/ → no permissions-policy
    • https://www.lairdcowley.com/about-us/ → no permissions-policy
    • https://www.lairdcowley.com/locations/ → no permissions-policy
    • https://www.lairdcowley.com/missoula-location/ → no permissions-policy
    • https://www.lairdcowley.com/helena-location/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas-overview/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas/commercial-litigation/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas/personal-injury/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas/insurance-litgation/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas/professional-negligence/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas/family-law/ → no permissions-policy
    • https://www.lairdcowley.com/practice-areas/employment-law/ → no permissions-policy
  • FoundVulnerable JavaScript librariesMedium

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

    • jQuery 2.8.18 in https://www.lairdcowley.com/wp-content/plugins/gravityforms/js/placeholders.jqu…: CVE-2015-9251 (XSS via cross-domain AJAX), CVE-2019-11358 (prototype pollution), CVE-2020-11022, CVE-2020-11023 (XSS via HTML passed to DOM methods); fixed in 3.5.0
  • FoundKeys and secrets in page codeMedium

    1 credential-like value found in code served to every visitor: Google API key.

    • Google API key AIzaSy…AU (39 chars) in https://www.lairdcowley.com/locations/: browser keys are expected in pages, but must be restricted by HTTP referrer and API in the Google Cloud console
  • NoteThird-party scripts

    Scripts run from 3 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 (35 script tags)
    • www.google.com (35 script tags)
    • maps.googleapis.com (2 script tags)
6 checks passed, 1 not applicable
  • OKHTTPS

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

    39 forms found, all on HTTPS pages posting to HTTPS addresses.

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

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

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