Duplicating Supplier Copy Across Product Pages
Observable evidence: sample live bottle pages and compare their descriptions with winery, importer, distributor, and competing retailer pages. Flag products where tasting notes and producer copy are materially identical and the shop adds little about curation, availability, service, storage, pairing, or the reason the bottle belongs in its range.
Consequence: the source previously attached a 20-40% organic-reach loss to this pattern, but no supporting study or source URL appears in this JSON. Keep that range as historical editorial material requiring reconciliation. The directly verifiable problem is that several retailers can publish interchangeable text while the independent shop contributes little distinctive information for the searcher.
Correction: retain accurate producer facts, then add original retailer context that can be substantiated: tasting observations from staff, serving or food-pairing guidance, storage considerations, appellation context, and a clear explanation of why the wine is part of the shop's selection.
Owner: merchandising or wine-content lead, with SEO review for differentiation and internal linking.
Verification: repeat the duplication check and manually compare the revised page with competing listings. A 2019 Barolo entry should explain the bottle the retailer actually carries and the decisions a buyer may need to make, rather than reproducing the same paragraph found elsewhere.
Severity: critical
Running Vintage URLs Without a Lifecycle Rule
Observable evidence: crawl current and historical product URLs, then review discontinued stock, obsolete internal links, canonical targets, and indexable pages that no longer help a shopper. The source examples /product/bordeaux-2018/ and /product/bordeaux-2019/ illustrate the type of split to inspect. Determine whether the 2018 page and the 2019 page are intentionally distinct records or merely successive URLs created as inventory changes.
Consequence: the catalog can fragment internal links, external references, and user journeys across several thin or outdated versions of the same underlying wine.
Correction: choose a documented rule. A stable master page can work when vintages are selectable product variants. Separate vintage pages can also work when each page has materially different information and continuing value. When a discontinued URL no longer serves a purpose and a genuinely equivalent replacement exists, a 301 redirect can be appropriate.
Owner: ecommerce product owner with development and technical SEO support.
Verification: recrawl old and current vintages, confirm redirects and canonicals, inspect inbound internal links, and test the destination a shopper reaches after stock transitions. Do not redirect merely to remove an error if the new destination does not satisfy the same need.
Severity: high
Exposing Uncontrolled Faceted Navigation to Search
Observable evidence: crawl combinations of region, grape, style, price, closure, availability, and other filters. Compare the resulting URL set with the small number of combinations that have distinct inventory, user value, and genuine search demand. Look for parameter loops, empty or near-empty listings, repeated titles, contradictory canonicals, and filter pages with no useful search activity.
Consequence: uncontrolled combinations can increase duplicate or low-value URLs, complicate internal linking, consume crawl attention, and blur the intended category hierarchy.
Correction: define which filters exist only for browsing and which combinations deserve indexable landing pages. Use internal-link rules, canonicalization, crawl handling, and indexation controls appropriate to the platform. No single robots directive should be assumed to solve every facet case.
Owner: technical SEO and ecommerce development.
Verification: rerun representative crawl paths and inspect index coverage. A filter state progressing through 10, 20, and 30 should become a search landing page only when the retailer intentionally maintains that combination as a useful destination.
Severity: critical
Publishing Wine Expertise Without Verifiable Attribution
Observable evidence: inspect tasting notes, buying guides, region explainers, producer profiles, and vintage commentary for bylines, reviewer identity, relevant experience, and a clear distinction between merchant opinion and sourced fact. Anonymous specialist claims are a warning when trust depends on who made the judgment.
Consequence: readers receive less context for evaluating advice, and the retailer fails to document the real people responsible for selection and commentary.
Correction: attribute specialist content to the staff member who produced or reviewed it, publish a concise bio containing only substantiated experience, and cite appropriate sources where factual claims need external support. Do not invent credentials or describe authorship as an automatic ranking signal.
Owner: editorial lead or wine buyer, with additional review when claims require it.
Verification: audit bylines and author pages, confirm experience statements are accurate, and check that tasting opinion, retailer interpretation, and sourced factual information remain distinguishable.
Severity: medium
Overloading Mobile Pages With Bottle Media
Observable evidence: test representative product and collection templates on mobile with network and performance diagnostics. Check oversized image sources, missing responsive variants, eager loading below the fold, layout shifts, repeated downloads, and scripts that delay interaction.
Consequence: slow or unstable templates make browsing harder and can weaken Core Web Vitals. The source uses more than 3 seconds as a warning for product-grid loading, but that figure should not be presented as a universal ranking cutoff.
Correction: resize and compress bottle images, use efficient formats where appropriate, declare dimensions, defer non-critical media, prioritize the primary visible image correctly, and use a CDN where it improves delivery for the shop's audience.
Owner: front-end or ecommerce performance owner.
Verification: retest the same pages after deployment and compare transfer size, visual stability, and loading behavior. On a 4G connection, a shopper should not face a 5 second blank experience while 2MB bottle images finish loading.
Severity: high
Leaving Real Local Shopping Intent Poorly Supported
Observable evidence: for a genuine storefront, compare the site with the Google Business Profile, published hours, address, phone, pickup details, and local inventory paths. Review actual local results for the shop's location and the nearby areas it genuinely serves rather than assuming every geographic term deserves a page.
Consequence: nearby shoppers can encounter inconsistent or incomplete information when deciding whether to visit, call, reserve, or purchase.
Correction: keep eligible profile details and website information accurate, provide useful location and pickup context, and expose local stock information only where it can be maintained. Create a dedicated location page only for a real location with distinct information. Paid inventory advertising should not be described as an organic ranking tactic.
Owner: retail operations or local-search owner.
Verification: compare profile and website details, test directions and contact paths, and inspect representative local searches. The pass condition is accurate discovery and a useful path to the store, not a guaranteed map position.
Severity: high
Publishing Structured Data That Conflicts With the Product Page
Observable evidence: compare rendered Product and Offer markup with the visible wine page and the catalog source of truth. Check name, price, currency, availability, review information, merchant details, and any additional attributes. Flag stale values, hidden claims, unsupported properties, or markup that says something different from the page.
Consequence: inconsistent structured data can create validation or eligibility problems and make product information harder for search systems to interpret. It should not be described as a direct ranking boost or a guarantee of rich results.
Correction: use supported Product and Offer properties that reflect visible, accurate facts. Wine characteristics such as grape, origin, color, or vintage should be expressed only through appropriate supported properties or clear on-page content, not invented schema fields.
Owner: technical SEO or developer with merchandising data ownership.
Verification: validate the rendered markup and compare it with the visible page and catalog data. If the source example refers to a 5-star rating, that rating must genuinely exist and satisfy applicable requirements before it is represented in structured data.
Severity: medium
