Scanned sites / www.chasefarmswells.com / 2026-09-23-1900

www.chasefarmswells.com scan from 9/23/2026, 7:00:02 PM

Scan 2026-09-23-1900

Scanned 9/23/2026, 7:00:02 PM, finished 9/23/2026, 7:04:44 PM. Found on page 1 of chatgpt for browser (api usage) results

Site: https://www.chasefarmswells.com/

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

73/ 100Needs work

On September 23, 2026 the Site Spider crawled 7 pages and 160 assets of www.chasefarmswells.com, starting from https://www.chasefarmswells.com/. It scored 73 out of 100, a result that needs work. 4 of 14 checks found something to fix, led by title tags (7), meta descriptions (7), thin content (7); 10 checks passed. 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
7
Assets fetched
160
Status
Completed
Checks with issues
4 of 14
  • Title tags7 issues
    7 of 7 pages have title issues.
  • Meta descriptions7 issues
    7 of 7 pages have meta description issues.
  • Headings1 issue
    1 of 7 pages have heading issues.
  • Broken linksOK
    0 internal links point at 0 broken URLs.
  • RedirectsOK
    7 redirecting URLs, 0 of them chained.
  • Non-200 responsesOK
    157 URLs did not return a 2xx response.
  • Rate limitedOK
    The site did not rate limit the crawler.
  • IndexabilityOK
    0 of 7 indexable pages have indexability warnings.
  • Image alt textOK
    0 of 71 image references have no alt attribute. 11 use an empty alt (decorative), which is fine.
  • Heavy assetsOK
    0 assets larger than 500 KB among the 100 heaviest.
  • Orphan pagesOK
    0 pages have no internal links pointing at them.
  • Sitemap coverageOK
    2 sitemaps listing 7 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
  • Thin content7 issues
    7 of 7 pages have fewer than 200 words.
  • Duplicate contentOK
    0 groups of pages with identical HTML.

Where this scan sits among all scanned sites

1237 sites, median 82%, average 80%

www.chasefarmswells.com scores 73%, higher than 20% of the 1237 scanned sites. See the full ranking.

031620%: 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%: 0 sites38%: 0 sites39%: 0 sites40%: 0 sites41%: 0 sites42%: 0 sites43%: 0 sites44%: 0 sites45%: 2 sites46%: 1 site47%: 1 site48%: 1 site49%: 0 sites50%: 3 sites51%: 4 sites52%: 4 sites53%: 3 sites54%: 4 sites55%: 1 site56%: 2 sites57%: 3 sites58%: 8 sites59%: 4 sites60%: 7 sites61%: 9 sites62%: 12 sites63%: 4 sites64%: 9 sites65%: 10 sites66%: 10 sites67%: 16 sites68%: 28 sites69%: 15 sites70%: 26 sites71%: 25 sites72%: 28 sites73%: 29 sites74%: 33 sites75%: 29 sites76%: 41 sites77%: 42 sites78%: 39 sites79%: 36 sites80%: 50 sites81%: 57 sites82%: 55 sites83%: 54 sites84%: 60 sites85%: 53 sites86%: 50 sites87%: 53 sites88%: 58 sites89%: 41 sites90%: 62 sites91%: 40 sites92%: 24 sites93%: 20 sites94%: 15 sites95%: 10 sites96%: 11 sites97%: 4 sites98%: 3 sites99%: 2 sites100%: 22 sites73% 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 has multiple SEO issues, primarily with non-200 responses, title tags, meta descriptions, and thin content. Addressing these will improve usability and search ranking.

  1. 1

    Fix Non-200 Responses

    Why: 157 URLs return non-200 responses, damaging user experience.

    How: Identify and remove or correct broken URLs in your site's content.

    Checks: status-codes

  2. 2

    Optimize Title Tags

    Why: All pages have short title tags, limiting visibility in search results.

    How: Update each title tag with relevant keywords, aiming for 50-60 characters.

    Checks: titles

  3. 3

    Add Meta Descriptions

    Why: Missing meta descriptions reduce click-through rates from search results.

    How: Create concise, informative meta descriptions for each page, using relevant keywords.

    Checks: meta-descriptions

  4. 4

    Implement H1 Headings

    Why: Contact page lacks an H1 tag, important for both SEO and accessibility.

    How: Add a descriptive H1 tag to the contact page.

    Checks: headings

  5. 5

    Enhance Thin Content

    Why: All pages have fewer than 200 words, which affects SEO ranking.

    How: Expand content on each page with useful information relevant to the topics.

    Checks: thin-content

  6. 6

    Review Redirects

    Why: Existing redirects point to 404 errors, leading to user frustration.

    How: Remove or fix all redirect URLs that result in 404 errors.

    Checks: redirects

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 site has multiple security issues, including missing security headers and inadequate cookie protections. Implementing a Content Security Policy and enhancing cookie security are crucial to protect user data and prevent attacks like clickjacking and script injection.

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

    Missing Content Security Policy (CSP)Medium

    Why it matters: No CSP header is present, allowing untrusted sources to inject scripts, risking data theft.

    Fix: Add a CSP header, e.g., `Content-Security-Policy: default-src 'self';`.

    Evidence: Content Security Policy

  2. 2

    Missing Clickjacking ProtectionMedium

    Why it matters: Absence of X-Frame-Options allows your site to be embedded in frames, which can lead to clickjacking attacks.

    Fix: Include the header `X-Frame-Options: DENY` or use CSP frame-ancestors directive.

    Evidence: Clickjacking protection

  3. 3

    Cookies Lack Security FlagsMedium

    Why it matters: Cookies missing HttpOnly and Secure flags increase vulnerability to theft and attacks.

    Fix: Set flags: `HttpOnly`, `Secure`, and `SameSite=Lax` for cookies.

    Evidence: Cookie flags

  4. 4

    Missing Referrer PolicyLow

    Why it matters: Without a referrer policy, sensitive URL information can be shared with external sites.

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

    Evidence: Referrer policy

  5. 5

    Third-Party Scripts Without Subresource IntegrityLow

    Why it matters: Using external scripts without integrity checks poses a risk if those sources are compromised.

    Fix: Consider implementing Subresource Integrity (SRI) where possible or adding a CSP.

    Evidence: Third-party scripts

  6. 6

    Missing Permissions PolicyInfo

    Why it matters: No policy in place to limit unused browser features, increasing risk if the site is compromised.

    Fix: Add `Permissions-Policy: geolocation=(self), microphone=()`, adjusting as needed.

    Evidence: Permissions policy

What the checks found

  • FoundContent Security PolicyMedium

    None of the 7 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.chasefarmswells.com/ → no content-security-policy
    • https://www.chasefarmswells.com/farm-stand → no content-security-policy
    • https://www.chasefarmswells.com/produce → no content-security-policy
    • https://www.chasefarmswells.com/meats → no content-security-policy
    • https://www.chasefarmswells.com/greenhouse → no content-security-policy
    • https://www.chasefarmswells.com/our-story → no content-security-policy
    • https://www.chasefarmswells.com/contact → 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.chasefarmswells.com/ → no x-frame-options
    • https://www.chasefarmswells.com/farm-stand → no x-frame-options
    • https://www.chasefarmswells.com/produce → no x-frame-options
    • https://www.chasefarmswells.com/meats → no x-frame-options
    • https://www.chasefarmswells.com/greenhouse → no x-frame-options
    • https://www.chasefarmswells.com/our-story → no x-frame-options
    • https://www.chasefarmswells.com/contact → no x-frame-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.chasefarmswells.com/ → no referrer-policy
    • https://www.chasefarmswells.com/farm-stand → no referrer-policy
    • https://www.chasefarmswells.com/produce → no referrer-policy
    • https://www.chasefarmswells.com/meats → no referrer-policy
    • https://www.chasefarmswells.com/greenhouse → no referrer-policy
    • https://www.chasefarmswells.com/our-story → no referrer-policy
    • https://www.chasefarmswells.com/contact → 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.chasefarmswells.com/ → no permissions-policy
    • https://www.chasefarmswells.com/farm-stand → no permissions-policy
    • https://www.chasefarmswells.com/produce → no permissions-policy
    • https://www.chasefarmswells.com/meats → no permissions-policy
    • https://www.chasefarmswells.com/greenhouse → no permissions-policy
    • https://www.chasefarmswells.com/our-story → no permissions-policy
    • https://www.chasefarmswells.com/contact → no permissions-policy
  • FoundCookie flagsMedium

    2 of 2 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.

    • XSRF-TOKEN (set by https://www.chasefarmswells.com/) lacks HttpOnly
    • ssr-caching (set by https://www.chasefarmswells.com/) lacks Secure, HttpOnly, SameSite
  • 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.)

    • static.parastorage.com (70 script tags)
    • browser.sentry-cdn.com (7 script tags)
8 checks passed, 2 not applicable
  • OKHTTPS

    All 7 crawled pages were served over HTTPS.

  • OKHTTP Strict Transport Security

    strict-transport-security is set on all 7 HTML pages.

  • OKMIME sniffing protection

    x-content-type-options is set on all 7 HTML pages.

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

  • 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 applicableForms over HTTPS

    No forms were found on the sampled pages.

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

Own www.chasefarmswells.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.chasefarmswells.com. Removal needs no account and no proof of purchase.
www.chasefarmswells.com scan 2026-09-23-1900 | DIY SEO Hub