# GEO product-information checklist (not a ranking guarantee)

Companion to **Generative engine optimization for eCommerce**.

**GEO is not a guaranteed ranking technique.** Completing this list does not buy a position in ChatGPT, Perplexity, Google AI Overviews, or any shopping agent. It makes product facts **available and consistent** so a generative engine **can** represent you accurately if it retrieves you.

Do not cite Presenc AI or SEO-blog GEO case studies. Industry visibility rates below are **Adobe Analytics** via [Digital Commerce 360 (19 Aug 2026)](https://www.digitalcommerce360.com/2026/08/19/adobe-ai-referral-traffic-data-july-2026/).

## Score one category (not the homepage only)

Adobe's expanded July 2026 cohort: **39%** of U.S. retail **homepages** were not machine-readable; apparel **76%** LLM visibility. Your job is **PDP + offer facts**, not a homepage slogan.

Check a box only if the fact is **structured** (field, JSON-LD, feed, or API) **and** matches checkout.

### Identity and relationships

- [ ] Unique SKU / GTIN where required
- [ ] Canonical product URL (stable)
- [ ] Parent/child variant graph (color/size as variants, not duplicate products)
- [ ] Compatible-with / used-with / replacement-for as IDs, not only prose

### Attributes and copy

- [ ] Required attributes per category (apparel: size, material, color, care)
- [ ] Description that does not contradict attributes
- [ ] No uncertified claims ("organic", "medical") without a certified flag
- [ ] Alt text matches the primary image (not keyword stuffing)

### Offer and availability

- [ ] Price, currency, tax/shipping disclosure aligned with checkout
- [ ] Availability as `in_stock` / `out_of_stock` / `unknown` with `asOf`
- [ ] Shipping / delivery window as data
- [ ] Return window and restocking rules versioned

### Evidence and trust

- [ ] Review count + rating as structured values, or honest absence
- [ ] Merchant/policy URLs for shipping, returns, warranty
- [ ] Restricted-category flags
- [ ] FAQ answers that cite the same policy documents (not a second legal text)

### Machine-readable packaging

- [ ] Product JSON-LD (`Product` + `Offer`) on SSR HTML, not only after hydration
- [ ] Feed or API a partner/agent can fetch without executing your storefront JS
- [ ] robots / bot policy reviewed — you know what you allow
- [ ] Homepage and category pages do not contradict PDP facts

## When NOT to "do GEO"

- You plan to buy a GEO rank package with no catalog contract
- Required attributes are still missing — generate FAQ schema anyway
- You will stuff reviews or FAQs with keywords the SKU does not support
- You treat Adobe's apparel **76%** as a score you will "beat this quarter"

## Fail closed

If price, stock, or a required attribute is missing, the record is **not** GEO-ready. A generated meta description does not substitute. Catalog draft/validate/publish stays in [`catalog-validation-rules.md`](catalog-validation-rules.md); this list is the **downstream contract**.