Scanned sites / www.lairdcowley.com

SEO report for www.lairdcowley.com

The latest Site Spider scan of www.lairdcowley.com, with 1 scan on record. Each scan is at its own address, for example /domain/www-lairdcowley-com/2026-10-01-0232.

Latest scan

Scanned 10/1/2026, 2:32:18 AM, finished 10/1/2026, 3:54:10 AM. Found on page 1 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 October 1, 2026 the Site Spider crawled 108 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 16 checks found something to fix, led by meta descriptions (28), heavy assets (6), title tags (17); 4 checks passed. Most of the points went to meta descriptions (−3.7), heavy assets (−3.6), title tags (−2.8). 2 checks 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: Medium5 medium, 2 low and 1 info findings. See the security findings ↓

Pages crawled
108
Assets fetched
233
Status
Completed
Checks with issues
10 of 16
CoverageComplete crawl

341 of 344 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 45 pages have title issues. 16 noindex or canonicalized pages excluded.
    −2.8 points
  • Meta descriptions28 issues
    28 of 45 pages have meta description issues. 16 noindex or canonicalized pages excluded.
    −3.7 points
  • Headings1 issue
    1 of 45 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.6 points
  • Links to other sites111 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 45 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 121 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 50 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 7 reachable only via the sitemap.
    −1.2 points
  • Internal link countsOK
    Internal link counts for 61 pages.
  • Thin contentOK
    0 of 45 pages have fewer than 200 words. 16 noindex or canonicalized pages excluded.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this site sits among all scanned sites

1422 sites, median 80%, average 79%

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

043850%: 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%: 1 site36%: 1 site37%: 1 site38%: 1 site39%: 0 sites40%: 1 site41%: 0 sites42%: 0 sites43%: 1 site44%: 0 sites45%: 3 sites46%: 2 sites47%: 2 sites48%: 2 sites49%: 3 sites50%: 3 sites51%: 5 sites52%: 6 sites53%: 5 sites54%: 6 sites55%: 4 sites56%: 3 sites57%: 5 sites58%: 10 sites59%: 5 sites60%: 8 sites61%: 10 sites62%: 15 sites63%: 14 sites64%: 8 sites65%: 14 sites66%: 15 sites67%: 26 sites68%: 24 sites69%: 17 sites70%: 34 sites71%: 33 sites72%: 42 sites73%: 33 sites74%: 41 sites75%: 46 sites76%: 52 sites77%: 47 sites78%: 65 sites79%: 51 sites80%: 71 sites81%: 85 sites82%: 69 sites83%: 67 sites84%: 61 sites85%: 44 sites86%: 49 sites87%: 49 sites88%: 51 sites89%: 37 sites90%: 30 sites91%: 33 sites92%: 19 sites93%: 8 sites94%: 10 sites95%: 7 sites96%: 6 sites97%: 5 sites98%: 1 site99%: 2 sites100%: 51 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

Several SEO issues require attention, including broken links, redirect chains, missing meta descriptions, and heavy assets. Addressing these will enhance site performance and user experience.

  1. 1

    Fix Broken Links

    Why: Redirecting internal links to broken pages can harm user experience and SEO.

    How: Update or remove the 8 broken links identified in the crawl.

    Checks: broken-links

  2. 2

    Resolve Redirect Chains

    Why: Chained redirects can slow down site performance and confuse visitors.

    How: Streamline the 7 chained redirects to go directly to the final URL.

    Checks: redirects

  3. 3

    Add Missing Meta Descriptions

    Why: Meta descriptions improve click-through rates from search results.

    How: Create unique meta descriptions for 24 pages that currently lack them.

    Checks: meta-descriptions

  4. 4

    Shrink Heavy Assets

    Why: Large assets can hinder performance and increase load time.

    How: Optimize the large assets identified, reducing their size where possible.

    Checks: heavy-assets

  5. 5

    Simplify Indexability Warnings

    Why: Noindex pages in the sitemap can confuse search engines.

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

    Checks: indexability

  6. 6

    Address Heading Issues

    Why: Proper heading structure is important for SEO and accessibility.

    How: Revise the page with multiple H1s to have a single H1 and appropriate subheadings.

    Checks: headings

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 security vulnerabilities including missing HTTP headers and a vulnerable JavaScript library. Implementing these fixes will enhance the protection of your site against common attacks. It’s crucial to address the most severe issues first to safeguard user data and interactions.

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

    Missing HTTP Strict Transport Security HeaderMedium

    Why it matters: Without this header, visitors can be intercepted when not using HTTPS.

    Fix: Add 'Strict-Transport-Security: max-age=31536000; includeSubDomains' to your HTTP headers.

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security PolicyMedium

    Why it matters: Absence of CSP allows unrestricted loading of scripts and styles, increasing XSS risk.

    Fix: Add 'Content-Security-Policy: default-src 'self'; script-src 'self';' to your HTTP headers.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: No clickjacking protection means your site can be embedded in iframes on malicious sites.

    Fix: Add 'X-Frame-Options: DENY' to your HTTP headers.

    Evidence: Clickjacking protection

  4. 4

    Vulnerable JavaScript LibraryMedium

    Why it matters: Using jQuery 2.8.18 exposes your site to multiple vulnerabilities.

    Fix: Upgrade jQuery to version 3.5.0 or later.

    Evidence: Vulnerable JavaScript libraries

  5. 5

    Leaked Google API KeyMedium

    Why it matters: Exposing API keys may lead to unauthorized use of your Google services.

    Fix: Restrict this API key in the Google Cloud console by setting appropriate referrer restrictions.

    Evidence: Keys and secrets in page code

  6. 6

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Absence of this header may allow browsers to interpret files as scripts, posing risks.

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

    Evidence: MIME sniffing protection

  7. 7

    Missing Referrer Policy HeaderLow

    Why it matters: No policy set can lead to exposure of sensitive URLs on external sites.

    Fix: Add 'Referrer-Policy: no-referrer' to your HTTP headers.

    Evidence: Referrer policy

  8. 8

    Missing Permissions Policy HeaderInfo

    Why it matters: A missing header allows scripts full access to potentially sensitive browser features.

    Fix: Add 'Permissions-Policy: geolocation=(self), camera=()' to your HTTP headers.

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

Earlier scans of www.lairdcowley.com

No other scans of this site yet.

Sites scoring near www.lairdcowley.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.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.
www.lairdcowley.com SEO report | DIY SEO Hub