Scanned sites / wentevineyards.com

SEO report for wentevineyards.com DR 61

The latest Site Spider scan of wentevineyards.com, with 1 scan on record. Each scan is at its own address, for example /domain/wentevineyards-com/2026-09-15-1900.

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

Latest scan

Scanned 2026-09-15 19:00:02 UTC, finished 2026-09-15 19:24:56 UTC. Found on page 3 of chatgpt for browser (api usage) results

Site: https://wentevineyards.com/

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

60/ 100Needs work

On September 15, 2026 the Site Spider crawled 554 pages and 1019 assets of wentevineyards.com, starting from https://wentevineyards.com/. It scored 60 out of 100, a result that needs work. 14 of 27 checks found something to fix, led by meta descriptions (317), heavy assets (198), sitemap coverage (317); 4 checks passed. Most of the points went to meta descriptions (−7.4), heavy assets (−6), sitemap coverage (−5.5). 9 checks found something the score does not count, listed as noted. 10 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: Medium3 medium, 3 low and 2 info findings. See the security findings ↓

Pages crawled
554
Assets fetched
1019
Status
Completed
Checks with issues
14 of 27
CoverageJob finished, partial coverage

1,573 of 1,582 discovered URLs were fetched, 153 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. 157 link destinations on other sites were checked.

  • Title tags126 issues
    126 of 317 pages have title issues. 26 noindex or canonicalized pages excluded.
    −3.7 points
  • Meta descriptions317 issues
    317 of 317 pages have meta description issues. 26 noindex or canonicalized pages excluded.
    −7.4 points
  • Headings61 issues
    61 of 317 pages have heading issues. 26 noindex or canonicalized pages excluded.
    −1.1 points
  • Broken links41 issues
    398 internal links point at 41 broken URLs.
    −2.4 points
  • Links to other sites49 issues
    49 destinations answered with an error, 44 could not be determined (timeouts, rate limits or refusals), of 133 destinations checked.
    −4 points
  • Redirects170 issues
    172 redirecting URLs, 1 of them chained.
    −2 points
  • Non-200 responses41 issues
    215 URLs did not return a 2xx response. 211 of them are pages, 41 with an error status; the rest are assets or redirects.
    −1.2 points
  • Rate limitedOK
    The site did not rate limit the crawler.
  • Indexability34 issues
    34 of 343 indexable pages have indexability warnings.
    −1 points
  • Image alt text1,985 issues
    1985 of 3759 image references have no alt attribute. 499 use an empty alt (decorative), which is fine.
    −3.2 points
  • Heavy assets198 issues
    198 assets larger than 500 KB among 1019 fetched assets. 18 documents over that size are listed but not counted: downloads are not page weight.
    −6 points
  • Orphan pages125 issues
    125 pages have no internal links pointing at them.
    −1.5 points
  • Sitemap coverage317 issues
    1 sitemap listing 0 URLs: 317 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
    −5.5 points
  • Internal link counts107 noted
    Internal link counts for 343 pages; 107 worth a look.
  • Thin content18 issues
    18 of 317 pages have fewer than 200 words. 26 noindex or canonicalized pages excluded.
    −0.4 points
  • Duplicate content41 issues
    2 groups of pages with identical HTML.
    −1 points
  • URL format30 noted
    30 of 554 page URLs are harder to read, share or cache than they need to be.
  • Canonicals48 noted
    48 of 343 pages have a canonical worth checking.
  • Robots directives343 noted
    343 pages carry a robots directive; 0 carry none.
  • Anchor text141 noted
    141 destinations are linked without useful anchor text, or with nofollow.
  • Title and heading structure108 noted
    108 of 317 pages could use the title, heading and snippet space better. 26 noindex or canonicalized pages excluded.
  • Image weight and alt length330 noted
    326 images over 100 KB; 4 with alt text over 100 characters.
  • Response anomalies161 noted
    161 URLs answered in a way worth looking at.
  • HTML and head validationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • hreflangNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Structured dataNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Near duplicatesNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Soft 404sOK
    None of 343 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 positionsNot checked
    Not checked: this scan was crawled before link positions were recorded. Scan the site again to run it.
  • PaginationNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.
  • Headers and cookiesOK
    1 cookie set by the site; 10 response headers recorded across 1573 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 343 pages; 278 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 Insights5 noted
    Mobile performance 51 on average across 5 pages; 5 below Google's good thresholds.
  • SpellingNot checked
    Not checked: this scan was crawled before this check existed. Scan the site again to run it.

Where this site sits among all scanned sites

2868 sites, median 80%, average 79%

wentevineyards.com scores 60%, higher than 5% of the 2868 scanned sites. See the full ranking.

0751490%: 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%: 2 sites45%: 6 sites46%: 5 sites47%: 5 sites48%: 6 sites49%: 8 sites50%: 6 sites51%: 7 sites52%: 8 sites53%: 9 sites54%: 9 sites55%: 9 sites56%: 8 sites57%: 17 sites58%: 18 sites59%: 10 sites60%: 15 sites61%: 13 sites62%: 20 sites63%: 29 sites64%: 22 sites65%: 33 sites66%: 43 sites67%: 42 sites68%: 42 sites69%: 52 sites70%: 46 sites71%: 80 sites72%: 76 sites73%: 81 sites74%: 82 sites75%: 87 sites76%: 95 sites77%: 109 sites78%: 132 sites79%: 111 sites80%: 128 sites81%: 125 sites82%: 132 sites83%: 119 sites84%: 130 sites85%: 105 sites86%: 96 sites87%: 95 sites88%: 81 sites89%: 75 sites90%: 55 sites91%: 58 sites92%: 43 sites93%: 29 sites94%: 25 sites95%: 15 sites96%: 17 sites97%: 16 sites98%: 7 sites99%: 3 sites100%: 149 sites60% 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

Written from an earlier version of the analysis. The findings on this page have been recomputed since, so counts and labels here may differ from what the plan describes. The advice still points at the same checks.

The site has critical SEO issues, especially with broken links, redirects, and missing titles and meta descriptions. Address these for better performance and user experience.

  1. 1

    Fix Broken Links

    Why: 398 internal links lead to 41 broken URLs, harming user experience and SEO.

    How: Identify and replace fixed URLs or remove links to broken pages.

    Checks: broken-links

  2. 2

    Resolve Redirects

    Why: 172 redirects, including one chained, can slow down the site.

    How: Update links to point directly to the final destination, eliminating unnecessary redirects.

    Checks: redirects

  3. 3

    Address Non-200 Responses

    Why: 215 URLs aren't returning 2xx responses, affecting accessibility.

    How: Review these URLs and fix any misconfigurations or update link paths.

    Checks: status-codes

  4. 4

    Improve Title Tags

    Why: 126 pages with title issues can affect search visibility.

    How: Ensure all pages have unique, descriptive titles over 30 characters.

    Checks: titles

  5. 5

    Add Meta Descriptions

    Why: 317 pages missing meta descriptions impact click-through rates.

    How: Create unique meta descriptions for each page that summarize the content.

    Checks: meta-descriptions

  6. 6

    Fix Missing Headings

    Why: 61 pages have heading issues, which can confuse users and search engines.

    How: Ensure every page has a clear H1 heading and follow with relevant 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 lacks critical security headers that help protect users and data. Implementing these will improve security against various attacks such as data interception and clickjacking. The recommendations need to be prioritized and addressed promptly.

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

    Missing HTTP Strict Transport Security (HSTS)Medium

    Why it matters: Without HSTS, visitors can be intercepted on the first request if they don't use HTTPS.

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

    Evidence: HTTP Strict Transport Security

  2. 2

    Missing Content Security Policy (CSP)Medium

    Why it matters: Without a CSP, scripts and resources can be loaded from any source, increasing vulnerability to attacks.

    Fix: Implement 'Content-Security-Policy: default-src 'self';' in HTTP response headers.

    Evidence: Content Security Policy

  3. 3

    Missing X-Frame-Options HeaderMedium

    Why it matters: No X-Frame-Options prevents clickjacking, allowing your site to be embedded maliciously in frames.

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

    Evidence: Clickjacking protection

  4. 4

    Missing X-Content-Type-Options HeaderLow

    Why it matters: Without this header, browsers may incorrectly execute scripts based on content type.

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

    Evidence: MIME sniffing protection

  5. 5

    Missing Referrer-Policy HeaderLow

    Why it matters: Not having this header exposes full site addresses to external websites, risking privacy.

    Fix: Implement 'Referrer-Policy: no-referrer' or similar in your HTTP response headers.

    Evidence: Referrer policy

  6. 6

    Third-Party Scripts Without SRILow

    Why it matters: Scripts from external domains can be compromised, affecting your site's security.

    Fix: Implement a Content Security Policy that specifies trusted sources, or ensure scripts use Subresource Integrity.

    Evidence: Third-party scripts

  7. 7

    Missing Permissions-Policy HeaderInfo

    Why it matters: Lacking this header allows scripts unrestricted access to browser features.

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

    Evidence: Permissions policy

  8. 8

    Sensitive Paths in robots.txtInfo

    Why it matters: Publicly listed paths may expose private information, despite access restrictions.

    Fix: Restrict access to sensitive paths through proper authentication instead of relying on robots.txt.

    Evidence: Sensitive paths in robots.txt

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://wentevineyards.com/ → no strict-transport-security
    • https://wentevineyards.com/events/2026-live-music-series/ → no strict-transport-security
    • https://wentevineyards.com/visit/ → no strict-transport-security
    • https://wentevineyards.com/the-grill/ → no strict-transport-security
    • https://wentevineyards.com/events/ → no strict-transport-security
    • https://wentevineyards.com/plan-your-wedding/ → no strict-transport-security
    • https://wentevineyards.com/corporate-events/ → no strict-transport-security
    • https://wentevineyards.com/plan-your-event/ → no strict-transport-security
    • https://wentevineyards.com/our-story/ → no strict-transport-security
    • https://wentevineyards.com/family/ → no strict-transport-security
    • https://wentevineyards.com/wente-vineyards/ → no strict-transport-security
    • https://wentevineyards.com/sustainability/ → no strict-transport-security
  • FoundContent Security PolicyMedium

    None of the 343 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://wentevineyards.com/ → no content-security-policy
    • https://wentevineyards.com/events/2026-live-music-series/ → no content-security-policy
    • https://wentevineyards.com/visit/ → no content-security-policy
    • https://wentevineyards.com/the-grill/ → no content-security-policy
    • https://wentevineyards.com/events/ → no content-security-policy
    • https://wentevineyards.com/plan-your-wedding/ → no content-security-policy
    • https://wentevineyards.com/corporate-events/ → no content-security-policy
    • https://wentevineyards.com/plan-your-event/ → no content-security-policy
    • https://wentevineyards.com/our-story/ → no content-security-policy
    • https://wentevineyards.com/family/ → no content-security-policy
    • https://wentevineyards.com/wente-vineyards/ → no content-security-policy
    • https://wentevineyards.com/sustainability/ → 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://wentevineyards.com/ → no x-frame-options
    • https://wentevineyards.com/events/2026-live-music-series/ → no x-frame-options
    • https://wentevineyards.com/visit/ → no x-frame-options
    • https://wentevineyards.com/the-grill/ → no x-frame-options
    • https://wentevineyards.com/events/ → no x-frame-options
    • https://wentevineyards.com/plan-your-wedding/ → no x-frame-options
    • https://wentevineyards.com/corporate-events/ → no x-frame-options
    • https://wentevineyards.com/plan-your-event/ → no x-frame-options
    • https://wentevineyards.com/our-story/ → no x-frame-options
    • https://wentevineyards.com/family/ → no x-frame-options
    • https://wentevineyards.com/wente-vineyards/ → no x-frame-options
    • https://wentevineyards.com/sustainability/ → 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://wentevineyards.com/ → no x-content-type-options
    • https://wentevineyards.com/events/2026-live-music-series/ → no x-content-type-options
    • https://wentevineyards.com/visit/ → no x-content-type-options
    • https://wentevineyards.com/the-grill/ → no x-content-type-options
    • https://wentevineyards.com/events/ → no x-content-type-options
    • https://wentevineyards.com/plan-your-wedding/ → no x-content-type-options
    • https://wentevineyards.com/corporate-events/ → no x-content-type-options
    • https://wentevineyards.com/plan-your-event/ → no x-content-type-options
    • https://wentevineyards.com/our-story/ → no x-content-type-options
    • https://wentevineyards.com/family/ → no x-content-type-options
    • https://wentevineyards.com/wente-vineyards/ → no x-content-type-options
    • https://wentevineyards.com/sustainability/ → 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://wentevineyards.com/ → no referrer-policy
    • https://wentevineyards.com/events/2026-live-music-series/ → no referrer-policy
    • https://wentevineyards.com/visit/ → no referrer-policy
    • https://wentevineyards.com/the-grill/ → no referrer-policy
    • https://wentevineyards.com/events/ → no referrer-policy
    • https://wentevineyards.com/plan-your-wedding/ → no referrer-policy
    • https://wentevineyards.com/corporate-events/ → no referrer-policy
    • https://wentevineyards.com/plan-your-event/ → no referrer-policy
    • https://wentevineyards.com/our-story/ → no referrer-policy
    • https://wentevineyards.com/family/ → no referrer-policy
    • https://wentevineyards.com/wente-vineyards/ → no referrer-policy
    • https://wentevineyards.com/sustainability/ → 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://wentevineyards.com/ → no permissions-policy
    • https://wentevineyards.com/events/2026-live-music-series/ → no permissions-policy
    • https://wentevineyards.com/visit/ → no permissions-policy
    • https://wentevineyards.com/the-grill/ → no permissions-policy
    • https://wentevineyards.com/events/ → no permissions-policy
    • https://wentevineyards.com/plan-your-wedding/ → no permissions-policy
    • https://wentevineyards.com/corporate-events/ → no permissions-policy
    • https://wentevineyards.com/plan-your-event/ → no permissions-policy
    • https://wentevineyards.com/our-story/ → no permissions-policy
    • https://wentevineyards.com/family/ → no permissions-policy
    • https://wentevineyards.com/wente-vineyards/ → no permissions-policy
    • https://wentevineyards.com/sustainability/ → no permissions-policy
  • NoteThird-party scripts

    Scripts run from 4 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.klaviyo.com (40 script tags)
    • cdnjs.cloudflare.com (40 script tags)
    • cdn.commerce7.com (80 script tags)
    • wente.dailydeals.golf (1 script tag)
  • NoteSensitive paths in robots.txt

    robots.txt lists 1 path that look private. robots.txt is public and does not restrict access, so it doubles as a map for anyone probing the site; those paths need real access control.

    • Disallow: /wp-admin/
8 checks passed
  • OKHTTPS

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

  • OKCookie flags

    All 1 cookie carry Secure, HttpOnly and SameSite flags.

  • OKMixed content

    No HTTPS page loads a script, stylesheet, font or image over plain HTTP.

  • OKForms over HTTPS

    1 form found, all on HTTPS pages posting to HTTPS addresses.

  • OKVulnerable JavaScript libraries

    1 library version 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.

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

No other scans of this site yet.

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

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