Rebuild the shared flavor-page template, piloting on Lime
Shared flavor template (/lime/, /vanilla/, …)
Why this comes first
It is the most direct way to help people discover flavors (the stated goal), the defect is verified on inspected pages, and one template change covers every flavor page. The collection and finder work depend on flavor pages that can stand on their own.
- Observed problem
- Sampled flavor pages repeat “{Flavor} - Polar Seltzer” titles and “{Flavor} Polar Seltzer” descriptions, use a flavor H2 with no H1, carry sparse descriptive content, link to the finder through a generic FIND button, and reference a shared nutrition image that returns 404.
- Proposed action
- Give each flavor page a descriptive title and description using customer vocabulary, a real H1, an introduction built from verified ingredients and attributes, readable product-fact sections, related-flavor links, and a labeled path to the existing store finder. Remove the broken nutrition image reference rather than inventing a replacement panel.
- Customer question or intent
- Product/flavor searches such as “lime sparkling water” and “polar lime seltzer”, and AI questions like “Which seltzer brands are sodium free?”
- Confidence
- high in the observation. The repeated fields and the 404 asset were observed directly on multiple flavor pages.Outcome uncertainty: Better pages do not guarantee rankings or new AI citations. Retailers dominate some branded results.
Facts needing confirmation
- Approved sensory description for each flavor
- Pack sizes and formats currently sold
- Whether a flavor-filtered store locator exists or is feasible
- Replacement nutrition information from Polar (not invented here)
Evidence · method rules M3.1 M3.2 M8.1 M8.2 M8.3 M8.4