The GEO Directory · 18 November 2026
Your products can be found by an AI assistant. Can a customer actually buy them?
A product feed, a current offer, a working checkout and a confirmed order answer different questions. Give each its own evidence before calling your store ready for AI shopping.
The marketing report says your products are ready for AI search. The feed has been accepted. A product appears in a response. Then a customer chooses a size that is sold out, a checkout cannot handle the delivery option, or an order never reaches the report your team uses.
These are different failures. More visibility does not fix all of them. Nor does adding a checkout protocol prove that a customer can discover the right item.
Start with one product variant, one market and one purchase route. Follow it through four states: discovery, offer, checkout and order. Keep a failed or unknown state visible rather than averaging the path into a readiness score.
ONE VARIANT / FOUR DIFFERENT CHECKS
Found.
Available?
Buyable?
Ordered?
01 / Evidence
A feed is a discovery input, not a sale
OpenAI says ChatGPT can use product feeds and other retail and public-web sources for discovery. Its feed guide explicitly separates the catalog snapshot from actions: the feed does not update a cart or confirm a purchase. The live website or plugin still checks the current offer when a customer acts. [1]
This corrects two tempting shortcuts. A submitted feed is not the only possible discovery source, and an accepted feed is not a promise that every product will appear. The current schema explicitly says search eligibility does not guarantee display. Checkout needs a separately enabled integration. [1][2]
Start at variant level. OpenAI's schema asks for a row per purchasable item or variant, with a stable item ID and its own price, availability, URL and images. A parent product page is not enough evidence that the selected size, color or capacity is the item being offered. [2]
Record the accepted or rejected feed row and the exact variant ID. Separately retain a dated observation of the product appearing in the intended surface and market, if you have one. If you have not observed it, write "appearance not observed". Do not convert ingestion success into an appearance claim.
02 / Evidence
Check the offer when the customer acts
A discovery record describes an offer at a point in time. It does not reserve inventory or lock the eventual total. Recheck the exact variant, quantity, market, currency and current availability when the buyer moves toward purchase. [1][2]
Then distinguish the item price from the amount the buyer will pay. Shipping, tax, discounts and delivery choices can depend on information that discovery has not collected. Google's native-checkout documentation separates checkout-session creation and updates, including totals and an initial tax estimate. A displayed estimate is not evidence of the final authorized amount. [3]
An operational rule for the audit: retain the current offer response or checkout evidence with a timestamp, and record what is still missing. If a shipping destination has not been supplied, do not mark the delivered total verified. If a variant is unavailable, stop this path or present a clearly identified alternative. Silently substituting another variant would change the purchase.
Teaching packet: one item, not a fabricated test
Use a fictional blue, 350 mL ceramic mug as a teaching example. The chosen identifier is MUG-350-BLUE. The market is the United States and the currency is USD. These are example values, not a real listing or tested integration.
The feed row and product URL identify MUG-350-BLUE, not the whole mug range.
Evidence: not tested
A current response confirms this variant, quantity, price and stock for the selected market.
Evidence: not tested
The supported route resolves delivery, total and any required buyer review.
Evidence: not tested
The merchant returns an order reference and state matching the approved purchase.
Evidence: not tested
The untested status on each card is deliberate. A plausible-looking example ID or checkout payload is not evidence that any of these steps worked.
03 / Evidence
Choose the route before writing the integration brief
"Supports agentic commerce" is too broad to be a useful acceptance criterion. Does this purchase finish on the merchant's website, in a platform-managed checkout, or through a custom checkout integration? Those paths have different prerequisites and failure points.
Merchant-cart handoff
The customer moves to the merchant's cart or checkout to finish. Google's current Merchant Center integration guide has a distinct transfer-to-merchant-cart path using the Cart API, with a lighter validation checklist than native checkout. It explicitly says this cart-transfer-only route does not require the full product feed setup, product warnings or customer-support information required by the broader path. Do not apply the native-checkout checklist indiscriminately. [4]
The audit question is whether the handoff preserves the intended items and context and lets the customer finish. A working link establishes a handoff, not a completed purchase.
Platform-managed direct checkout
For eligible Shopify stores, the Google AI Mode and Gemini channel can let a customer buy through a Shopify-powered checkout without visiting the merchant's online store. Turning off direct checkout can still leave discovery available, with the customer redirected to the online store to finish. Discovery and direct-purchase settings are therefore separate decisions on this route. [5]
Eligibility is product-specific too. Shopify currently lists subscription-only products, bundles, customizable products and B2B-only products as unsupported in this direct checkout. A product offering both one-time purchase and subscription can be bought as a one-time purchase there, but not as a subscription. Local delivery, in-store pickup and pickup points are also unsupported. Do not infer that an ordinary item working proves every item or delivery method works. [5]
Custom native checkout
Google's current native path calls for checkout-session creation, updates and completion, followed by order-status validation and program review. Its Merchant Center guide provides sandbox and production validation paths. Its native flow hands control to a Google interface where the customer supplies sensitive fulfillment and payment details and submits the order; the agent is not involved in that step. Treat sandbox success and production approval as separate milestones. [3][4]
For builders, Shopify's agent documentation also distinguishes a cart with estimated totals from a checkout session, and server-side Checkout MCP from browser-based Checkout WebMCP. Its response state and messages can require a buyer handoff. A tool existing is not permission to skip a payment challenge or required customer review. [6]
Keep geography tied to the route
As checked on 18 November 2026, Google's Merchant Center integration guide describes its UCP integration hub as gradually rolling out in the United States, with Australia and Canada to follow early the next year. Shopify's own Google-channel page lists eligible customers in the US, Canada and Australia, while warning that direct checkout is rolling out gradually and may not be available to a particular store. The store itself can be based elsewhere on that Shopify route. [4][5]
The Merchant Center hub rollout and customer eligibility on a commerce channel are different scopes. Do not combine those pages into one universal country list. Record which integration, account, customer market and capability you checked. Confirm actual access before committing engineering work to an assumed rollout.
04 / Evidence
Count merchant-confirmed orders, not vanished carts
A checkout screen disappearing, a success-looking response or an outbound click is not enough to reconcile a purchase. Record the merchant's order reference and state, exact line items, total and currency. Keep checkout completion separate from later fulfillment, cancellation or refund events.
Google's native validation path includes order-status updates. Shopify's agent checkout documentation describes response statuses, messages and buyer continuation URLs for non-terminal states. Use the route's actual lifecycle rather than treating every response as success. [4][6]
Measurement can fail even when the purchase succeeds. Shopify says Google Analytics and custom client-side pixels do not fire in its Google AI Mode and Gemini direct checkout; it describes server-to-server started/completed signals instead. That is a specific limitation of this checkout route, not proof that every AI purchase is unmeasurable. [5]
Reconcile orders against the appropriate platform or server-side evidence before reporting a drop in conversion. Keep the channel-attribution question separate from the order-exists question. Do not manufacture attribution when an order cannot reliably be matched to a source.
Diagnosis
Diagnostic cards
Correct product, wrong variant.
Discovery shows the blue mug but checkout opens another selection. Check the per-variant identifier and handoff mapping. Do not mark the whole product successful.
Feed accepted, item no longer available.
The latest action-time response is out of stock. Update discovery data and preserve the failed offer check. Do not present the accepted snapshot as current inventory.
Ordinary item works, subscription does not.
Check whether this route supports that purchase type. Use a supported merchant-site handoff where appropriate. Do not generalize one successful basket to the whole catalog.
Order exists, browser conversion is missing.
Check the route's analytics limitations and server-side/order evidence. Do not change the product feed to solve an attribution fault.
Hypothetical diagnosis examples, not reported incidents or tests of the named platforms.
The handoff
The handoff to your team
For this item and market, identify the discovery source and exact variant. Verify the current offer, then the supported checkout route and required buyer review. Retain the merchant-confirmed order result when a test purchase is explicitly approved. Mark untested states as unknown. Report discovery, checkout and order evidence separately.
A content owner can maintain product facts and observe appearance. A commerce engineer can validate the route and edge cases. An analytics owner can reconcile the resulting orders. They need shared identifiers and dated evidence, not one score that hides where the path breaks.
Method and sources
What this guide establishes
This is a documentation-led audit framework, checked on 18 November 2026, not a transaction benchmark. We did not submit a product feed, access a merchant account, change a setting or place an order. The teaching packet and diagnosis cards are hypothetical. No conversion lift, search volume, universal eligibility or guaranteed product appearance is claimed.
Merchant questions about whether submitted products appear and whether prices and stock are accurate predate this guide, including a November 2025 Shopify Community thread. That question helps frame the problem; it is not evidence of today's platform behavior or the size of demand. Operator documentation controls the factual claims above. [7]
- OpenAI: Submit product feeds
Discovery snapshots, other discovery sources and separate actions.
- OpenAI: Product feed schema
Variant identity, current offer fields and eligibility limits.
- Google: Native checkout
Session creation, estimated taxes, updates and customer payment review.
- Google: UCP integration in Merchant Center
Different cart-transfer and native validation paths. Updated 17 November 2026.
- Shopify: Selling on Google AI Mode and Gemini
This channel's rollout, product restrictions and analytics limitations.
- Shopify: Carts and checkout for agents
Cart versus checkout, response states and buyer handoffs.
- Shopify Community: Product feed in ChatGPT?
November 2025 merchant question, not a source of current platform behavior.
- Obi: Product overview
Vendor description of buyer research and approval-gated drafts.
- AirOps: Modern content engineering organization
Vendor description of shared context and repeatable content workflows.
- Profound: Enterprise capabilities
Vendor description of SSO and role-based access.
The GEO Directory. A product can be visible without being buyable. A checkout can complete without appearing in a browser-pixel report. Keep the evidence separate.