Optimizing for AI search

Shoppers increasingly ask an assistant instead of running a search. ChatGPT, Google AI Overviews, Perplexity, and Copilot answer the question directly and name a few sources, so the outcome you are competing for is a citation rather than a click.

Most of what earns a citation is ordinary good SEO. What differs is the failure mode: an assistant reads a stripped-down version of your page, so anything your site reveals only after a click or a script has run is invisible to it. That single fact drives most of this page.

Test any change on a staging storefront before you apply it to a live one.

Keep your content visible without JavaScript

This is the change worth making first. Assistants generally read the HTML your server returns and do not wait for scripts, so content hidden behind an accordion, a tab, or a "Read more" link may never be read at all.

Check a product page two ways:

• View the page source with Ctrl+U (Cmd+Option+U on a Mac) and search for your key product details. If they are not in the source, an assistant cannot see them.
• Disable JavaScript in your browser settings and reload. Whatever disappears is content you are hiding from AI search.

Then move the important material into the page itself:

Hidden from assistants	Visible to assistants
Specifications inside an accordion	All specifications rendered on load
Reviews behind "Show More"	The first three to five reviews shown
Features split across tabs	Features listed plainly
Description truncated with "Read More"	The full description in the page

Write content only you can write

Assistants favour material with genuine expertise behind it, and they discount text that reads as though it were generated. Original detail is the differentiator.

• Product guides based on real testing. Say who tested the product, against what criteria, and what happened. Add the detail to the item description under Main Menu → Items → Item Management.
• Customer stories. Collect real use cases through item reviews or write them up as blog posts in Content Management.
• Comparisons. A table of your product against its alternatives answers the question shoppers actually ask.
• Questions and answers. Put the question in an H3 heading and the answer immediately below it, in full. That shape is easy to quote.
• Topic clusters. Group related guides and link them from the relevant category pages.

What to avoid: manufacturer specifications copied verbatim, keyword stuffing, and bulk generated text. Write for the phrasing a shopper would actually use, such as "best yoga mat for beginners", rather than a keyword string.

Add structured data

Structured data tells an assistant what the numbers on your page mean, so a price is a price and a rating is a rating. Turn it on and add the item element as described in Structured data with schema.org. Product, FAQ, and review markup are the ones that matter most for a store.

You do not need to hand-write JSON-LD to get this. UltraCart generates the markup once you enable the setting and place the ITEMSTRUCTUREDDATA element.

Structure pages so answers can be extracted

Assistants pull passages out of a page rather than reading it end to end, so give them clean units to pull.

• Write descriptive headings. "Capacity options" beats "Specs".
• Use lists and tables. Bullets for features, tables for comparisons.
• Lead with a summary. A short overview near the top of the page gives an assistant something quotable before it reaches the detail.
• Caption and name your images properly. yoga-mat-grip-test.jpg with real alt text carries meaning that IMG_4821.jpg does not.

A product page that works well for this tends to run: a quick overview, who the product suits, key features, a comparison table, questions and answers, then full specifications.

Control which assistants can read your site

AI crawlers have their own names, and you allow or block them in robots.txt. See Allow or block AI crawlers for a file you can copy.

Blocking them is a real choice with a real cost: a crawler you turn away cannot cite you.

Build a presence off your own site

Assistants weight discussion and coverage elsewhere, not only what you publish yourself.

• Answer questions on the forums where your customers already ask them, under your own name, and link to your guides when the link genuinely helps.
• Publish videos or long-form guides with transcripts, and embed them on your blog.
• Earn third-party mentions through reviews, guest articles, and press coverage.
• Point your email campaigns at the content you publish elsewhere.

Specific, honest answers work. Promotional posts get filtered out by the communities and carry little weight anyway.

Measure citations, not clicks

Traffic reporting will not show you this directly, so check by hand.

1. Ask the assistants the questions your customers ask: "best [category] for [need]", or your brand against a competitor. Record whether you were mentioned, in what context, and whether the description was accurate.
2. In Google Search Console, watch for impressions rising while clicks stay flat. That pattern usually means you are being read and summarised rather than visited.
3. Track branded search volume over time. Assistants that recommend you produce searches for your name.
4. Set up alerts for unlinked brand mentions so you can see coverage that never became a link.

Do this monthly. The useful signal is the direction each measure moves, not any single reading.

Where to start

Audit one product page first. Check it with JavaScript disabled, fix whatever vanishes, add structured data, and rewrite the description with detail only you could supply. Then measure that page for a month before you roll the pattern across the catalogue.