Scanned sites / hepworthfarms.com / 2026-10-01-0800

hepworthfarms.com scan from 10/1/2026, 8:00:01 AM

Scan 2026-10-01-0800

Scanned 10/1/2026, 8:00:01 AM, finished 10/1/2026, 5:47:47 PM. Found on page 1 of chatgpt for browser (api usage) results

Site: https://hepworthfarms.com/

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

49/ 100Poor

On October 1, 2026 the Site Spider crawled 63 pages and 1022 assets of hepworthfarms.com, starting from https://hepworthfarms.com/. It scored 49 out of 100, a poor result. 13 of 16 checks found something to fix, led by title tags (60), indexability (60), duplicate content (62); 2 checks passed. Most of the points went to title tags (−10), indexability (−10), meta descriptions (−8). 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
63
Assets fetched
1022
Status
Completed
Checks with issues
13 of 16
CoverageJob finished, partial coverage

1,085 of 1,085 discovered URLs were fetched, 843 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. 63 link destinations on other sites were checked.

  • Title tags60 issues
    60 of 60 pages have title issues.
    −10 points
  • Meta descriptions60 issues
    60 of 60 pages have meta description issues.
    −8 points
  • Headings22 issues
    22 of 60 pages have heading issues.
    −2.2 points
  • Broken links2 issues
    2 internal links point at 2 broken URLs.
    −0.7 points
  • Links to other sites5 issues
    5 destinations answered with an error, 20 could not be determined (timeouts, rate limits or refusals), of 63 destinations checked.
    −2 points
  • Redirects1 issue
    1 redirecting URL, 0 of them chained.
    −0.1 points
  • Non-200 responses2 issues
    10 URLs did not return a 2xx response. 3 of them are pages, 2 with an error status; the rest are assets or redirects.
    −0.3 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability60 issues
    60 of 60 indexable pages have indexability warnings.
    −10 points
  • Image alt textOK
    0 of 2036 image references have no alt attribute. 316 use an empty alt (decorative), which is fine.
  • Heavy assets20 issues
    20 assets larger than 500 KB among 1022 fetched assets. 14 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages1 issue
    1 page have no internal links pointing at them.
    −0.1 points
  • Sitemap coverage30 issues
    No sitemap found. Tried: https://hepworthfarms.com/sitemap.xml (404). Add one at /sitemap.xml or list it in robots.txt.
    −3 points
  • Internal link countsOK
    Internal link counts for 60 pages.
  • Thin content18 issues
    18 of 60 pages have fewer than 200 words.
    −2.4 points
  • Duplicate content62 issues
    30 groups of pages with identical HTML.
    −8 points

Where this scan sits among all scanned sites

1904 sites, median 80%, average 79%

hepworthfarms.com scores 49%, higher than 1% of the 1904 scanned sites. See the full ranking.

0561110%: 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%: 7 sites57%: 6 sites58%: 15 sites59%: 7 sites60%: 10 sites61%: 12 sites62%: 17 sites63%: 16 sites64%: 11 sites65%: 21 sites66%: 22 sites67%: 37 sites68%: 30 sites69%: 26 sites70%: 39 sites71%: 40 sites72%: 56 sites73%: 52 sites74%: 49 sites75%: 61 sites76%: 76 sites77%: 73 sites78%: 88 sites79%: 69 sites80%: 91 sites81%: 111 sites82%: 85 sites83%: 86 sites84%: 87 sites85%: 65 sites86%: 75 sites87%: 63 sites88%: 64 sites89%: 54 sites90%: 36 sites91%: 36 sites92%: 29 sites93%: 15 sites94%: 13 sites95%: 13 sites96%: 7 sites97%: 8 sites98%: 2 sites99%: 2 sites100%: 55 sites49% 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 several critical issues impacting SEO, including broken links, redirects, and duplicate content across all pages. Addressing these can significantly improve your site's health score.

  1. 1

    Fix Broken Links

    Why: Broken links harm user experience and SEO.

    How: Update or remove the links pointing to broken URLs. Specifically, check the links on https://hepworthfarms.com/press.html.

    Checks: broken-links

  2. 2

    Resolve Non-200 Responses

    Why: Non-200 status codes can prevent pages from being indexed.

    How: Identify broken pages and assets (e.g., ParkSlopeArticle.pdf) and replace or remove them.

    Checks: status-codes

  3. 3

    Create Unique Title Tags

    Why: Unique titles help with indexing and relevance.

    How: Develop distinct titles for the 60 pages and avoid duplication. Review existing content for effective title creation.

    Checks: titles

  4. 4

    Implement Meta Descriptions

    Why: Generic meta descriptions reduce click-through rates.

    How: Craft unique meta descriptions for each page to improve visibility in search results.

    Checks: meta-descriptions

  5. 5

    Ensure Indexability

    Why: Proper indexability ensures search engines can crawl your content.

    How: Add canonical tags and language attributes to the affected pages.

    Checks: indexability

  6. 6

    Address Duplicate Content

    Why: Duplicate content can confuse search engines and dilute value.

    How: Identify duplicates and use canonical tags to indicate preferred versions.

    Checks: duplicate-content

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 essential security headers, exposing users to potential risks such as interception and clickjacking. Implementing recommended security headers will significantly enhance the site's protection against various attacks.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, users typing the site address without HTTPS can be intercepted.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: The lack of CSP allows scripts and styles to load from any source, increasing XSS risks.

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

    Evidence: Content Security Policy

  3. 3

    Missing Clickjacking ProtectionMedium

    Why it matters: Without X-Frame-Options, the site can be framed by malicious pages.

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

    Evidence: Clickjacking protection

  4. 4

    Missing MIME Sniffing ProtectionLow

    Why it matters: Without X-Content-Type-Options, browsers may misinterpret file types.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer PolicyLow

    Why it matters: Not using a Referrer-Policy exposes users' full URLs to external sites.

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

    Evidence: Referrer policy

  6. 6

    Third-party Scripts Without Subresource Integrity (SRI)Low

    Why it matters: Third-party scripts lack integrity checks, which could lead to exploitation if compromised.

    Fix: Implement a CSP that whitelists trusted domains or consider using SRI for scripts when possible.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions PolicyInfo

    Why it matters: The absence of a permissions-policy could allow misuse of browser features by injected scripts.

    Fix: Add the header: Permissions-Policy: interest-cohort=(), camera=(self).

    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://hepworthfarms.com/ → no strict-transport-security
    • https://hepworthfarms.com/index.html → no strict-transport-security
    • https://hepworthfarms.com/about.html → no strict-transport-security
    • https://hepworthfarms.com/weeklyfarmreport.html → no strict-transport-security
    • https://hepworthfarms.com/tomatoes.html → no strict-transport-security
    • https://hepworthfarms.com/beans.html → no strict-transport-security
    • https://hepworthfarms.com/broccoli.html → no strict-transport-security
    • https://hepworthfarms.com/brusselsprouts.html → no strict-transport-security
    • https://hepworthfarms.com/cabbage.html → no strict-transport-security
    • https://hepworthfarms.com/cauliflower.html → no strict-transport-security
    • https://hepworthfarms.com/cucumber.html → no strict-transport-security
    • https://hepworthfarms.com/eggplant.html → 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://hepworthfarms.com/ → no content-security-policy
    • https://hepworthfarms.com/index.html → no content-security-policy
    • https://hepworthfarms.com/about.html → no content-security-policy
    • https://hepworthfarms.com/weeklyfarmreport.html → no content-security-policy
    • https://hepworthfarms.com/tomatoes.html → no content-security-policy
    • https://hepworthfarms.com/beans.html → no content-security-policy
    • https://hepworthfarms.com/broccoli.html → no content-security-policy
    • https://hepworthfarms.com/brusselsprouts.html → no content-security-policy
    • https://hepworthfarms.com/cabbage.html → no content-security-policy
    • https://hepworthfarms.com/cauliflower.html → no content-security-policy
    • https://hepworthfarms.com/cucumber.html → no content-security-policy
    • https://hepworthfarms.com/eggplant.html → 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://hepworthfarms.com/ → no x-frame-options
    • https://hepworthfarms.com/index.html → no x-frame-options
    • https://hepworthfarms.com/about.html → no x-frame-options
    • https://hepworthfarms.com/weeklyfarmreport.html → no x-frame-options
    • https://hepworthfarms.com/tomatoes.html → no x-frame-options
    • https://hepworthfarms.com/beans.html → no x-frame-options
    • https://hepworthfarms.com/broccoli.html → no x-frame-options
    • https://hepworthfarms.com/brusselsprouts.html → no x-frame-options
    • https://hepworthfarms.com/cabbage.html → no x-frame-options
    • https://hepworthfarms.com/cauliflower.html → no x-frame-options
    • https://hepworthfarms.com/cucumber.html → no x-frame-options
    • https://hepworthfarms.com/eggplant.html → 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://hepworthfarms.com/ → no x-content-type-options
    • https://hepworthfarms.com/index.html → no x-content-type-options
    • https://hepworthfarms.com/about.html → no x-content-type-options
    • https://hepworthfarms.com/weeklyfarmreport.html → no x-content-type-options
    • https://hepworthfarms.com/tomatoes.html → no x-content-type-options
    • https://hepworthfarms.com/beans.html → no x-content-type-options
    • https://hepworthfarms.com/broccoli.html → no x-content-type-options
    • https://hepworthfarms.com/brusselsprouts.html → no x-content-type-options
    • https://hepworthfarms.com/cabbage.html → no x-content-type-options
    • https://hepworthfarms.com/cauliflower.html → no x-content-type-options
    • https://hepworthfarms.com/cucumber.html → no x-content-type-options
    • https://hepworthfarms.com/eggplant.html → 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://hepworthfarms.com/ → no referrer-policy
    • https://hepworthfarms.com/index.html → no referrer-policy
    • https://hepworthfarms.com/about.html → no referrer-policy
    • https://hepworthfarms.com/weeklyfarmreport.html → no referrer-policy
    • https://hepworthfarms.com/tomatoes.html → no referrer-policy
    • https://hepworthfarms.com/beans.html → no referrer-policy
    • https://hepworthfarms.com/broccoli.html → no referrer-policy
    • https://hepworthfarms.com/brusselsprouts.html → no referrer-policy
    • https://hepworthfarms.com/cabbage.html → no referrer-policy
    • https://hepworthfarms.com/cauliflower.html → no referrer-policy
    • https://hepworthfarms.com/cucumber.html → no referrer-policy
    • https://hepworthfarms.com/eggplant.html → 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://hepworthfarms.com/ → no permissions-policy
    • https://hepworthfarms.com/index.html → no permissions-policy
    • https://hepworthfarms.com/about.html → no permissions-policy
    • https://hepworthfarms.com/weeklyfarmreport.html → no permissions-policy
    • https://hepworthfarms.com/tomatoes.html → no permissions-policy
    • https://hepworthfarms.com/beans.html → no permissions-policy
    • https://hepworthfarms.com/broccoli.html → no permissions-policy
    • https://hepworthfarms.com/brusselsprouts.html → no permissions-policy
    • https://hepworthfarms.com/cabbage.html → no permissions-policy
    • https://hepworthfarms.com/cauliflower.html → no permissions-policy
    • https://hepworthfarms.com/cucumber.html → no permissions-policy
    • https://hepworthfarms.com/eggplant.html → no permissions-policy
  • NoteThird-party scripts

    Scripts run from 1 other domain 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)
5 checks passed, 4 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.

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

  • Not applicableVulnerable JavaScript libraries

    No recognisable library versions were found in the sampled scripts.

  • Not applicableSensitive paths in robots.txt

    No robots.txt was fetched.

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

Own hepworthfarms.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 hepworthfarms.com. Removal needs no account and no proof of purchase.
hepworthfarms.com scan 2026-10-01-0800 | DIY SEO Hub