Presentation · Matt MCP

0:00 – 0:30

Matt still had to investigate the site before the advice became actionable

Recorded on polarseltzer.com/lime/

title: Lime - Polar Seltzer
description: Lime Polar Seltzer
h1: none

No H1; the flavor name is an H2 (“Lime”).
Generic call to action: “Find”, “FIND”.
References a shared nutrition image that returns 404.
16 words of page-specific text.

0:30 – 1:15

Add Matt to the assistant — then ask

Prompt in the connected host

Use Matt MCP to analyze Polar Seltzer using the saved Polar research. What should we improve first, why, and what should the Lime page become?

External assistant connection

Last seen: verify-script 1 · Oct 3, 2026, 10:32 PM UTC · last tool analyze_business

Open the returned report URL

1:15 – 2:15

The decision becomes a page

1

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.

Verified affected pages

/lime//ruby-red-grapefruit//vanilla/

Possible rollout (not verified)

Possible rollout to the 20 flavor pages linked from /seltzers/ (verified). Only inspected pages are verified.

Effort — planning estimate

M · Planning estimate: one template change plus per-flavor copy review.

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

What each source changed

Website inspectionImported research
Website inspection established the template need
- Identified the repeated title/description/H2 pattern across sampled flavor pages
- Found the broken shared nutrition image (404 over HTTP and HTTPS)
- Confirmed the store finder already exists, so the fix is a better path — not a new page
Google demand & SERPsImported research
Google demand informed vocabulary and sequencing
- Chose “sparkling water” and “seltzer water” vocabulary for the proposed title and H1
- Kept the finder third: purchase-intent demand is small (170/mo) relative to flavor queries
- Lime chosen as a pilot with demand and AI evidence — not as the highest-demand flavor (grapefruit is higher)
ProfoundCached response
Live Profound data, alongside imported research
- Polar Seltzer appears in 19.3% of tracked AI answers (7 days)
- Lowest visibility: “What are the best drinks to replace sparkling hard seltzer if I'm going alcohol-free?” (0.0%)
- 17 owned page(s) cited; most cited polarseltzer.com/limitededition
- Sodium-Free stays prominent: /lime/ was cited in 3 ChatGPT runs for “Which seltzer brands are sodium free?”
- No owned citation for “What is the best lime seltzer?” — supports clearer Lime product context

2:15 – 3:00

Review and refine — the same persisted proposal

Revision 3 · last saved by the MCP host · Oct 3, 2026, 09:37 PM UTCOpen proposal Download change package

FieldCurrent — recorded on the live pageProposed — not published

Title tag

Current: Lime - Polar Seltzer

Proposed: Lime Sparkling Water | Polar Seltzer36 chars

Meta description

Current: Lime Polar Seltzer

Proposed: Explore Lime Polar Seltzer, made with carbonated water and natural flavors. See product facts, discover more flavors, and find Polar near you.142 chars

H1

Current: None

Proposed: Lime Seltzer Water18 chars

Canonical

Current: https://polarseltzer.com/lime/

Proposed: https://polarseltzer.com/lime/(unchanged)

Current page observations

· No H1; the flavor name is an H2 (“Lime”).
· Generic call to action: “Find”, “FIND”.
· References a shared nutrition image that returns 404.
· 16 words of page-specific text.

Introduction

Lime Polar Seltzer is made with carbonated water and natural flavors. It is listed as Calorie-Free, Sodium-Free, Gluten-Free, Vegan and Kosher. Use the Polar store finder to find it near you.

Ingredients & product facts

Carbonated water, natural flavors.

Section · More Polar flavors with lime

Cranberry Lime is another Polar flavor with lime in the name. The Seltzers page links to 20 flavors in total.

Purchase · Find Polar near you

Use the Polar store finder to look for retailers near you.

Button: “Open the Polar store finder” → https://polarseltzer.com/find/

Questions answered from evidence

What are the ingredients in Lime Polar Seltzer?: Carbonated water, natural flavors.
Is Lime Polar Seltzer sodium free?: Yes. Sodium-Free is one of the verified attributes for Polar Seltzer, along with Calorie-Free, Gluten-Free, Vegan and Kosher.
Where can I buy Lime Polar Seltzer?: Use the Polar store finder to look for retailers near you.

Structured data (JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Lime Polar Seltzer",
  "brand": {
    "@type": "Brand",
    "name": "Polar Seltzer"
  },
  "url": "https://polarseltzer.com/lime/",
  "description": "Explore Lime Polar Seltzer, made with carbonated water and natural flavors. See product facts, discover more flavors, and find Polar near you.",
  "image": "https://polarseltzer.com/wp-content/uploads/PolarSeltzer_12oz_Master_2024_Lime.webp"
}

Valid Product markup with no offers, ratings or reviews. That makes it ineligible for product rich results; we do not fabricate them to qualify.

3:00 – 3:40

Evidence and honest impact

Programmatic checks · Lime rev 3

7 Pass1 Needs confirmation0 Fail0 Not checked

C1Material factual claims have supporting evidence
Needs confirmation — 11 blocks linked to evidence; 1 claim(s) pending confirmation.
C2Current and proposed fields are clearly distinguished
Pass — Current fields cite 2 observation(s); 3 field(s) change.
C3Proposed title, description and H1 exist and fit the page
Pass — Title 36 chars, description 142 chars, H1 names “Lime”.
C4Chosen links and assets have a recorded verification result
Pass — All 7 links and assets returned 2xx when checked.
C5Unverified claims are excluded or explicitly pending
Pass — No prices, reviews, invented nutrition, health benefits or extra certifications in public copy.
C6Search estimates, rankings and AI metrics keep distinct definitions
Pass — 1 volume, 1 ranking and 2 AI-visibility record(s) each carry their own period, market and definition.
C7A shared-template claim names the inspected sample
Pass — Sample named: /lime/, /ruby-red-grapefruit/, /vanilla/.
C8MCP and UI return the same persisted proposal revision
Pass — MCP last returned revision 3 (Sat, 03 Oct 2026 21:37:00 GMT), matching the UI.

Pages Matt MCP inspected: 3
Issues verified: 7
Proposed fields changed: 3
Checks passing: 7 of 8
New processing time: 2 min 38 s
Provider cost: None — imported research

How outcomes will be measured (future, not observed)

· Organic impressions and clicks by query and page, once Search Console is connected
· Flavor-to-finder clicks through real analytics events
· Qualified purchase outcomes only where attribution data exists

Unresolved review items

· Add an approved sensory description for Lime (not drafted — no verified source).
· Confirm which pack sizes and formats are currently sold before listing them.
· Confirm whether the store finder can filter by flavor; keep flavor-level availability conditional until then.
· Shared nutrition image returns 404. Supply verified nutrition information from Polar; no replacement values are drafted.
· Confirm the chosen product image is the preferred hero asset.

3:40 – 4:00

Scale the judgment

Pilot · /lime/

Proposed title: Lime Sparkling Water | Polar Seltzer
Proposed H1: Lime Seltzer Water
Was: Lime - Polar Seltzer

Open proposal

Same method, second flavor · /ruby-red-grapefruit/

Proposed title: Ruby Red Grapefruit Sparkling Water | Polar Seltzer
Proposed H1: Ruby Red Grapefruit Seltzer Water
Was: Ruby Red Grapefruit - Polar Seltzer