Get a custom-built store into AI shopping answers
In short: A custom-built store has no plugin doing the basics, so you do them in code: give every product its own URL, render Product JSON-LD with price, stock, brand and GTIN in the server HTML, keep it identical to the visible text, allow AI crawlers, publish a Google Merchant Center feed, and ping IndexNow when products change. Then measure.
What you need, at a glance
| Requirement | Why | Done when |
|---|---|---|
| One URL per product | Feeds, Google and AI cite a page, not a modal | Every product has a stable URL in your sitemap |
| Product JSON-LD in server HTML | Google recommends it "in the initial HTML for best results" | curl of the page shows the JSON-LD with price |
| Markup matches visible text | Google asks for it in its AI features guidance | Same price, stock and name in both |
| Crawlers allowed | Blocking OAI-SearchBot removes you from ChatGPT search | robots.txt and firewall allow them |
| Merchant Center feed | Free route into Google Shopping and its AI features | Products "Approved" in Merchant Center |
| IndexNow ping (optional) | Bing learns about changes quickly | Key file served, pings on product change |
| Measurement | You can't improve what you don't count | AI referrals tracked, baseline noted |
Step 1: give every product its own page
A product that only exists inside a modal, a ?product= query on the home page, or a #hash route is invisible as a product. In flareOps' own crawler rules, a link that only adds ?x= or #x to the same page counts as no page of its own, and such products are never sent to Merchant Center. Use clean paths like /products/blue-ceramic-mug and list them all in sitemap.xml.
Step 2: render Product JSON-LD on the server
Google's merchant listing docs require name, image and offers (with price above zero and a three-letter priceCurrency). They recommend gtin, brand.name, availability, shippingDetails and hasMerchantReturnPolicy. They also warn that JavaScript-generated markup can make shopping crawls "less frequent and less reliable" (Google, checked 4 Nov 2026).
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"Product",
"name":"Ceramic mug 350 ml, matte blue",
"image":"https://example-store.com/img/mug-blue.jpg",
"brand":{"@type":"Brand","name":"Example Pottery"},
"offers":{"@type":"Offer","price":"24.00","priceCurrency":"USD",
"availability":"https://schema.org/InStock",
"url":"https://example-store.com/products/blue-ceramic-mug"}}
</script>
All values above are made up. Add gtin13 (or the right length) only when you have a real barcode. Next.js: render this in the server component or generateMetadata path, not in a useEffect.
Test it: curl -s https://yourstore.com/products/x | grep -o '"price":"[^"]*"'. If that prints nothing, crawlers that don't run JavaScript see no price.
Step 3: keep markup and page identical
Google's AI features page lists "making sure your structured data matches the visible text on the page" (Google). Generate both from the same data, in the same render. Don't add claims to JSON-LD that the page doesn't show, such as ratings or "free shipping".
Step 4: allow the crawlers
OpenAI: OAI-SearchBot for ChatGPT search, ChatGPT-User for live fetches, GPTBot for training only (OpenAI). Also allow PerplexityBot, Googlebot and Bingbot. Check edge firewalls and bot-protection challenges, which often block these with a JavaScript test the bot can't pass. Details: allow AI crawlers.
Step 5: Google Merchant Center
- Create a free Merchant Center account.
- Verify and claim your site. Google lists email, platform, HTML tag or file, Google Tag Manager and Google Analytics as methods. One URL can be claimed by only one account (Google, checked 4 Nov 2026).
- Add products: a scheduled feed file (XML or CSV at a URL), or the Merchant API.
- Fix disapprovals: usually missing GTIN/brand, price mismatch between feed and page, or missing shipping.
Google: Google Shopping and Google AI Mode + Merchant Center.
Step 6: tell search engines about changes (optional)
Serve an IndexNow key file at your site root and POST changed product URLs to api.indexnow.org when products change (IndexNow). Batch the pings; don't ping on every page view.
Step 7: ChatGPT's own feed
Claim your business in OpenAI's Business Hub (chatgpt.com/business-hub, beta since 10 Nov 2026, free), then add a product feed as a CSV file or a hosted feed URL. OpenAI's help page describes feeds for U.S. businesses, so check whether your country is supported. For a custom site, writing the feed is usually a short script over your products table. Field list: ChatGPT product feed spec.
Step 8: measure
Track visits with utm_source=chatgpt.com and referrers from perplexity.ai in your analytics, and note how often AI answers name your store for 10–20 shopper questions, monthly. How to check.
What you can do free, without us
Everything above. It's a day or two of work for a developer, or an evening with an AI coding tool. Our free AI readiness checker tests one product page for most of it.
What flareOps does
Connect with Google sign-in and no code (ownership from your Search Console, or the Analytics or Tag Manager already on the site). flareOps reads your products daily, flags gaps like JS-only prices or missing brands, writes a ready prompt for Claude Code when a fix needs code, syncs Merchant Center (the claim needs no tag on custom sites), and on Pro runs the weekly ChatGPT and Perplexity check against a baseline taken before any change. The optional free package @flareops.ai/next adds productJsonLd() (it drops GTINs with a wrong check digit), approved FAQ and shipping lines, a feed at /api/flareops/feed.xml, AI-bot logs, IndexNow and change events. See flareOps for custom sites.
Related: the pillar guide GEO for ecommerce and product schema for AI.
Questions people ask
Do I need a special AI file like llms.txt?
No. Google says there are no additional requirements or special optimizations for AI Overviews or AI Mode, and log studies show llms.txt files get almost no requests from AI crawlers.
Is client-side rendered JSON-LD good enough?
It can work, but Google says JavaScript-generated Product markup makes shopping crawls less frequent and less reliable, especially for price and availability. Render it on the server.
Which schema.org fields matter most?
name, image and offers with price, priceCurrency and availability are required for merchant listings. Add brand, gtin, shippingDetails and hasMerchantReturnPolicy where you have real values.
Do I need Google Merchant Center if I am not on Shopify?
It is the main free way to get products into Google Shopping and Google's AI shopping features, and it works for any site. You verify and claim your website, then add a feed file or use the API.
What is IndexNow and do I need it?
IndexNow lets you tell participating search engines such as Bing that a URL changed. Bing's index feeds Copilot, and studies report heavy overlap between ChatGPT search citations and Bing results, so faster Bing updates can help. It is optional.
Can a single-page app be read by AI crawlers?
Don't count on AI crawlers running JavaScript. If your product data only appears after scripts run, assume some of them see an empty page. Server-side rendering or static generation fixes that.
Sources
- Google Search Central: merchant listing structured data (checked 4 Nov 2026)
- Google Search Central: AI features and your website (checked 4 Nov 2026)
- Google Merchant Center Help: Verify and claim your online store (checked 4 Nov 2026)
- OpenAI: overview of OpenAI crawlers (checked 4 Nov 2026)
- IndexNow documentation (checked 4 Nov 2026)
- Seer Interactive: ChatGPT search citations vs Bing results (Feb 2025, checked 4 Nov 2026)
- npm: @flareops.ai/next
Sources checked on 4 November 2026.