Saw a 60-day GEO playbook from Noah Greenberg . Solid read, but the commerce ver
By Toddpie · May 29, 2026 · Curated by George's Blog
Saw a 60-day GEO playbook from Noah Greenberg. Solid read, but the commerce version looks different and I haven't seen anyone lay it out.
One important thing to know before you start: The surface your shopper uses isn't the surface your monitoring tool checks. You can't whip up a tracking tool using API calls and expect it to mimic real user reality (Petra Labs confirmed this and ran 900 trials of the same product research prompt across ChatGPT paid, ChatGPT free, and the Responses API. Same model, same day. Brand visibility swung up to 32 percentage points across surfaces. One brand that showed up in 15-18% of chat trials was completely absent from the API).
Honestly surprised more people aren't talking about this one.
Anyways, here's the commerce version:
Get the model right first. ChatGPT recommends 1-3 products inside the chat. If
you're not in that carousel, you were considered and rejected and never knew. Most brands populate maybe 14 of OpenAI's 85 feed fields. What about the other 71? Open optimization surface.
Fix the catalog before you touch OpenAI. Don't start with "upload your catalog to OpenAI." Wrong order. A clean GMC feed gets you ~70% of OpenAI for free -plus Gemini, AI Mode, and Copilot in the same move.
Submit the merchant form (chatgpt.com/merchants). While you wait, fix PDP structure, add comparison content (cited 2.4x more than blog posts), clean up schema. Being indexed isn't being recommended.
Monitor at the SKU level, not the brand level. Brand visibility tools track mentions. Useless for commerce. What matters: which of your SKUs show up when a shopper asks about your category, where they rank, which competitors appear instead. Outputs shift weekly with model updates so keep monitoring.
The land grab Noah describes is happening. The brands I see getting ahead of
it are treating this as a catalog operations project. A visibility dashboard to check once a week doesn't cut it.