Scanned sites / wentevineyards.com / 2026-09-15-1900
wentevineyards.com scan from 9/15/2026, 7:00:02 PM
Scan 2026-09-15-1900
Scanned 9/15/2026, 7:00:02 PM, finished 9/15/2026, 7:24:56 PM. 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.
On September 15, 2026 the Site Spider crawled 554 pages and 1019 assets of wentevineyards.com, starting from https://wentevineyards.com/. It scored 64 out of 100, a result that needs work. 13 of 14 checks found something to fix, led by image alt text (1985), meta descriptions (317), sitemap coverage (317); 1 check passed. The list below shows each check's result, and the fix plan, when present, explains what to do first.
- Pages crawled
- 554
- Assets fetched
- 1019
- Status
- Completed
- Checks with issues
- 13 of 14
- Title tags126 issues126 of 317 pages have title issues. 26 noindex or canonicalized pages excluded.
- Meta descriptions317 issues317 of 317 pages have meta description issues. 26 noindex or canonicalized pages excluded.
- Headings61 issues61 of 317 pages have heading issues. 26 noindex or canonicalized pages excluded.
- Broken links41 issues398 internal links point at 41 broken URLs.
- Redirects170 issues172 redirecting URLs, 1 of them chained.
- Non-200 responses41 issues215 URLs did not return a 2xx response.
- Rate limitedOKThe site did not rate limit the crawler.
- Indexability34 issues34 of 343 indexable pages have indexability warnings.
- Image alt text1985 issues1985 of 3759 image references have no alt attribute. 499 use an empty alt (decorative), which is fine.
- Heavy assets198 issues100 assets larger than 500 KB among the 100 heaviest.
- Orphan pages125 issues125 pages have no internal links pointing at them.
- Sitemap coverage317 issues1 sitemap listing 0 URLs: 317 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
- Thin content18 issues18 of 317 pages have fewer than 200 words. 26 noindex or canonicalized pages excluded.
- Duplicate content41 issues2 groups of pages with identical HTML.
Where this scan sits among all scanned sites
1030 sites, median 82%, average 80%
wentevineyards.com scores 64%, higher than 6% of the 1030 scanned sites. See the full ranking.
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...
Fix plan
Written by gpt-4o-mini from the scan findingsThe 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
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
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
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
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
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
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.
This report was produced by the DIY SEO Hub Site Spider crawling wentevineyards.com from its public pages. Anyone can run a scan of any site they own or are authorised to check. Is this your site? Claim it to manage the listing, or ask for removal through the support form.