We’ve been analyzing thousands of shopping and recommendation responses across ChatGPT, Gemini, Claude, and Perplexity, and the biggest takeaway for me is:

Stop treating AI visibility as just a score. Start looking at what causes the score.

One of the strongest signals we found was website retrieval.

Across several brands:

• When the brand’s own website was retrieved, the brand was mentioned 89% of the time
• When the website wasn’t retrieved, the brand was mentioned only 24% of the time

So imagine this:

AI Visibility: 37%
Website Retrieval: 13%
Mention when Retrieved: 92%

That tells a very different story than “your visibility is 37%.”

The AI already seems comfortable mentioning the brand when it reaches the site. The real problem is retrieval.

But retrieval is only one part of it.

We also found brands that were strongly associated with one product category while being almost invisible for other categories they clearly sell.

So two brands can have exactly the same visibility score for completely different reasons:

• One isn’t being retrieved enough
• One gets retrieved but still isn’t recommended
• One is only understood in part of its catalog
• One is being measured against prompts where brands are rarely mentioned at all

The content being retrieved was also interesting.

For one brand, 116 of 165 own-site citations came from blog content, while only 3 came from product pages. One roundup article alone was cited 37 times.

That makes sense when you think about what users actually ask:

“Best [category] brands”
“Best [product] for [use case]”
“[Brand] vs [competitor]”
“Top alternatives to [brand]”

A PDP is often great at explaining a product.

It’s not necessarily built to answer those questions.

Another thing we learned: don’t overreact to a single visibility test.

In one dataset, roughly a quarter of identical prompt/model combinations changed between repeated runs.

So a move from 53% to 47% doesn’t automatically mean something broke. Trends, repeated runs, and confidence matter.

And the same applies off-site.

Instead of assuming “Reddit is good for GEO” or “YouTube is important,” it makes more sense to look at the actual prompts where competitors win and ask:

Which external sources are showing up in those answers?

Sometimes it’s Reddit. Sometimes a niche publisher, retailer, review site, YouTube video, or comparison page.

So I’m increasingly thinking the useful questions aren’t:

“What’s my AI visibility?”

But:

Why is my visibility what it is?
Is AI retrieving me?
Does it recommend me when it does?
Which categories does it associate me with?
Which sources are influencing the prompts I care about?

The score is the output.

The interesting part is diagnosing the inputs that created it.

Curious how others working on GEO/AEO are thinking about this - are you already separating retrieval, mentions, category association, and prompt quality, or mostly tracking one overall visibility metric?

We’ve been analyzing thousands of shopping and recommendation responses across ChatGPT, Gemini, Claude, and Perplexity, and the biggest takeaway for me is:

Stop treating AI visibility as just a score. Start looking at what causes the score.

One of the strongest signals we found was website retrieval.

Across several brands:

• When the brand’s own website was retrieved, the brand was mentioned 89% of the time
• When the website wasn’t retrieved, the brand was mentioned only 24% of the time

So imagine this:

AI Visibility: 37%
Website Retrieval: 13%
Mention when Retrieved: 92%

That tells a very different story than “your visibility is 37%.”

The AI already seems comfortable mentioning the brand when it reaches the site. The real problem is retrieval.

But retrieval is only one part of it.

We also found brands that were strongly associated with one product category while being almost invisible for other categories they clearly sell.

So two brands can have exactly the same visibility score for completely different reasons:

• One isn’t being retrieved enough
• One gets retrieved but still isn’t recommended
• One is only understood in part of its catalog
• One is being measured against prompts where brands are rarely mentioned at all

The content being retrieved was also interesting.

For one brand, 116 of 165 own-site citations came from blog content, while only 3 came from product pages. One roundup article alone was cited 37 times.

That makes sense when you think about what users actually ask:

“Best [category] brands”
“Best [product] for [use case]”
“[Brand] vs [competitor]”
“Top alternatives to [brand]”

A PDP is often great at explaining a product.

It’s not necessarily built to answer those questions.

Another thing we learned: don’t overreact to a single visibility test.

In one dataset, roughly a quarter of identical prompt/model combinations changed between repeated runs.

So a move from 53% to 47% doesn’t automatically mean something broke. Trends, repeated runs, and confidence matter.

And the same applies off-site.

Instead of assuming “Reddit is good for GEO” or “YouTube is important,” it makes more sense to look at the actual prompts where competitors win and ask:

Which external sources are showing up in those answers?

Sometimes it’s Reddit. Sometimes a niche publisher, retailer, review site, YouTube video, or comparison page.

So I’m increasingly thinking the useful questions aren’t:

“What’s my AI visibility?”

But:

Why is my visibility what it is?
Is AI retrieving me?
Does it recommend me when it does?
Which categories does it associate me with?
Which sources are influencing the prompts I care about?

The score is the output.

The interesting part is diagnosing the inputs that created it.

Curious how others working on GEO/AEO are thinking about this — are you already separating retrieval, mentions, category association, and prompt quality, or mostly tracking one overall visibility metric?

Could be conversion rate, SEO, AI visibility, retention, site speed - anything.

I’m curious what’s actually working for merchants right now, beyond the usual “best practices.”

I’ll start: sometimes the smallest changes to how product information is structured can make a surprisingly big difference.

The fastest way to increase AI traffic to your ecommerce store is to make your products easy for AI engines to read, quote, and recommend: publish complete product JSON-LD on every page, rewrite product and category content to answer real buyer questions in plain language, add FAQ sections, keep content fresh and visibly dated, and earn mentions in the comparison posts and listicles that ChatGPT, Gemini, Perplexity, and Claude actually cite. Then measure your visibility across all four engines on a schedule, find the buying prompts you are losing, and fix them one by one. None of these tactics requires a big budget — but together they determine whether an AI assistant recommends your store or a competitor's.

TL;DR: these are the nine tactics that reliably increase AI traffic to an ecommerce store in 2026.

1. Publish complete product JSON-LD on every product page.
2. Rewrite product content to answer buyer questions conversationally.
3. Add FAQ sections to product and category pages.
4. Publish an llms.txt file.
5. Earn mentions in the listicles and comparison posts AI engines cite.
6. Keep your content fresh and visibly dated.
7. Build category and buying-guide pages that match real buyer prompts.
8. Keep your store fast and crawlable, with no JavaScript walls.
9. Measure your AI visibility continuously and fix the prompts you are losing.

Why is AI traffic different from search traffic?

Search sends a visitor a list of ten blue links; an AI engine sends a verdict. When a shopper asks ChatGPT or Perplexity what to buy, the answer usually names a handful of products — sometimes just one — and most shoppers never look past it. That makes AI visibility a winner-take-most game: either you are in the answer, or you do not exist for that buyer.

The ranking signals differ too. Search rewards keywords and backlinks; AI engines reward being retrievable, quotable, and independently corroborated. They pull structured data to ground factual claims, lift passages that directly answer the question, and lean heavily on third-party sources that mention you. And because the assistant has already done the comparing before anyone clicks, the visitors who do arrive from an AI answer tend to be unusually far down the funnel — they show up pre-sold, looking for a specific product rather than browsing.

The practical consequence: tactics that worked for classic SEO are necessary but not sufficient. You also have to optimize for how models retrieve, chunk, and cite content — which is what the rest of this guide covers.

How did we figure out what actually works?

In August 2026 we ran a structured visibility test: 32 real buying prompts across ChatGPT, Gemini, Perplexity, and Claude — 128 AI answers — and analyzed which sources each engine recommended. The clearest pattern was hard to miss: for buying prompts, nearly every cited source was blog-style comparison content — listicles, buying guides, head-to-head reviews — not product pages. Product pages inform the answer; editorial pages earn the citation. That finding shapes several of the tactics below, especially tactics five and seven.

The 9 tactics that increase AI traffic in 2026

Work through these roughly in order. The first four are on-site changes you control entirely; five and six are about the wider web; seven and eight round out your content and technical foundation; nine is the feedback loop that ties it all together.

1. Complete your product JSON-LD

Most Shopify themes emit partial Product schema by default — usually name, price, and availability, and not much else. Audit yours and fill in the gaps: description, brand, SKU and GTIN, images, aggregateRating and review markup, shipping details, and return policy. Validate every template with a schema validator, and make sure variants do not produce conflicting offers on the same page.

Why it works: AI engines ground product recommendations in structured data because it is unambiguous. A complete Product object lets an engine state your price, availability, and rating without guessing — and engines are far more willing to recommend a product they can describe with confidence. Incomplete markup forces the model to infer, and a model that has to infer tends to pick the competitor it does not have to infer about.

2. Write conversational, question-answering product content

Rewrite product descriptions to answer the questions a buyer would actually ask an assistant: Who is this for? How does it fit or size? What is it made of? How does it compare to the obvious alternative? When should you not buy it? Use plain, declarative sentences a model can lift verbatim, and put the most decision-relevant facts in the first hundred words rather than burying them under brand storytelling.

Why it works: AI engines retrieve passages, not pages. When a shopper asks whether a jacket is warm enough for winter commuting, the engine looks for a chunk of text that answers exactly that. Adjective-heavy brand copy rarely matches the question; a direct, factual answer often does. The stores winning AI referrals write like helpful salespeople, not like billboards.

3. Add FAQ sections to product and category pages

Mine your support inbox, chat logs, and customer review questions for the ten questions buyers really ask about each product or category, then answer them on-page in roughly 40–80 words each. Add FAQPage structured data where your theme supports it. Keep the answers honest, including the cases where the product is not the right choice — that candor is exactly what makes the content citable.

Why it works: an FAQ is pre-chunked content in the exact question-and-answer shape AI prompts take. Each pair is a self-contained, quotable unit that maps one-to-one to a real prompt, which makes it cheap for an engine to retrieve and safe for it to repeat.

4. Publish an llms.txt file

llms.txt is an emerging convention: a plain-markdown file at yourstore.com/llms.txt that lists your most important pages — top categories, best-selling products, buying guides, shipping and returns policies — each with a one-line description. It takes about an hour to create and minutes a month to maintain.

Why it works: with a caveat — engine adoption is still uneven, so treat this as a cheap hedge rather than a guaranteed win. But the AI crawlers and shopping agents that do look for it get a clean, theme-free map of your store instead of having to parse a heavy Shopify template, and the cost of being early here is close to zero.

5. Earn mentions in the listicles and comparison posts AI engines cite

In our testing this was the single highest-leverage tactic. Ask the engines the buying prompts that matter to you and note which roundups, comparison posts, and review sites they cite today. Then work to get included: pitch the authors with something genuinely useful, offer product samples to credible reviewers, and publish your own honest comparison content that names competitors fairly and earns links on its merits.

Why it works: for buying prompts, engines overwhelmingly synthesize from third-party editorial sources — best-of lists, comparison posts, buying guides — rather than from product pages. If you are absent from the sources an engine reads, you are absent from its answer, no matter how well-optimized your own site is. Being in the source set is the entry ticket.

6. Keep your content fresh — and visibly dated

Refresh your buying guides and comparison content on a schedule, update year references in titles and headings, and show a visible last-updated date on the page. Retire or redirect stale posts that contradict your current catalog — an old guide recommending a discontinued product actively hurts you when an engine quotes it.

Why it works: for commercial queries, AI engines show a strong preference for recent sources — a guide dated 2026 tends to beat a near-identical one dated 2023. Visible dates also let the engine present your content as current, which matters when a shopper asks what is best right now.

7. Build category and buying-guide content that matches buyer prompts

Buyers rarely ask AI engines about your brand; they ask in category language — best crib mattress for a small nursery, lightweight waterproof hiking boots for wide feet, gifts for a coffee-obsessed friend. List the prompts your buyers actually use, then write a guide page that answers each one head-on, with clear recommendations and reasoning. Map each target prompt to exactly one page that owns it, and interlink guides with the products they recommend.

Why it works: this is how you get cited for top-of-funnel prompts your product pages never will be. A well-structured buying guide can become the editorial source an engine quotes — including when it recommends your own products — and it pairs naturally with tactic five: the comparison content engines love can live on your domain too.

8. Keep your store fast and crawlable

Check robots.txt to make sure you are not blocking GPTBot, ClaudeBot, PerplexityBot, or Google-Extended unintentionally — plenty of stores are, thanks to old bot-blocking rules or overzealous firewalls. Serve product content in server-rendered HTML, keep key facts out of tabs and accordions that only render with JavaScript, and keep pages fast on cheap mobile connections.

Why it works: several AI crawlers execute little or no JavaScript, and retrieval systems give up on slow pages. Content that only appears after client-side rendering may simply not exist as far as an AI engine is concerned. Clean, fast, semantic HTML is the difference between being readable and being invisible.

9. Measure continuously and fix what you are losing

AI answers are probabilistic and change week to week, so a one-time audit goes stale fast. Run a recurring set of real buying prompts across ChatGPT, Gemini, Perplexity, and Claude, track whether you are mentioned and which sources each engine cites, then remediate the losing prompts using tactics one through eight. Vizby automates this loop for Shopify stores; Otterly and Profound are solid alternatives, particularly if your store runs on another platform.

Why it works: visibility work only compounds when you can see cause and effect. Measurement turns a vague ambition into a concrete backlog — which prompts you lose, which competitor wins them, and which cited source you need to appear in next.

How do you measure AI traffic?

Start with the referral data you already have. In GA4 or Shopify analytics, filter sessions by referrer for chatgpt.com, perplexity.ai, gemini.google.com, and claude.ai. Triple Whale can tie those sessions to revenue, which is what ultimately justifies the work. Expect undercounting: a meaningful share of AI-referred visits arrives with no referrer at all and hides inside your direct traffic.

Referrals only tell you the outcome, though. To see the cause, you need visibility testing — asking the engines real buying prompts and recording who they recommend and why. That is what Vizby does for Shopify stores, on a schedule, with competitor tracking built in. One honest limitation: Vizby samples a fixed prompt set at intervals, so its share-of-voice numbers are a directional benchmark, not a census of every real conversation — no tool can observe those.

Frequently asked questions

How long does it take to increase AI traffic?

On-site changes such as JSON-LD, FAQs, and rewritten product content can start showing up in AI answers within a few weeks, once engines recrawl your pages. Earning third-party citations in listicles and comparison posts typically takes longer — often a few months of steady outreach. Treat it like SEO: the results compound rather than arrive overnight.

Does traditional SEO still matter for AI visibility?

Yes. Every major engine leans on conventional search indexes and web crawls to find candidate sources, so pages that rank well and earn links are more likely to be retrieved and cited. GEO is not a replacement for SEO; it is a layer on top that optimizes how retrievable, quotable, and corroborated your content is.

Which AI engine sends the most traffic to ecommerce stores?

It varies by niche and audience. ChatGPT has the largest user base, Perplexity is the most citation-forward and tends to send outbound clicks, and Gemini benefits from Google's shopping infrastructure. Rather than guessing, segment your own referral data by engine and invest where your buyers actually show up — the split surprises most merchants.

Do I really need an llms.txt file?

No — it is optional, and engine support remains inconsistent. But it costs about an hour, carries no downside, and gives AI crawlers a clean map of your store. Do it after the fundamentals are in place: structured data, conversational content, FAQs, and crawlability all matter more than any emerging file standard.

Can I track AI traffic in Google Analytics or Shopify?

Yes. Create a channel group or segment that filters referrers such as chatgpt.com, perplexity.ai, gemini.google.com, and claude.ai. Just be aware of undercounting: visits from in-app browsers or copied links often arrive as direct traffic, so your true AI-referred volume is usually higher than the report shows.

The bottom line

Increasing AI traffic is not a single hack — it is making your store the easiest, safest recommendation an engine can give: complete structured data, content that answers real questions, a presence in the sources engines already trust, and a technical foundation that lets crawlers actually read it all. The stores that win treat it as a loop: measure, fix, re-measure.

If you run on Shopify, the quickest way to find out where you stand is to run a Vizby visibility test: see which buying prompts you win today, which ones you are losing to competitors, and exactly what to fix first. Most merchants are surprised by what the first report shows — and that surprise is where the growth starts.

A few numbers from Harley’s post that stood out to me:
• AI-referred sessions grew 197% YoY
• AI shoppers reaching PDPs converted ~80% better than organic traffic
• In research-heavy categories, that was roughly 2x
• Structured Shopify Catalog data drove 2x better conversion than scraped or third-party data.

The interesting part is that AI search isn’t replacing organic search. It’s doing a different job.

Shoppers are using AI to research and compare, then arriving at product pages much further down the funnel.

And the work doesn’t stop on your website. AI also learns about your brand from Reddit, YouTube, LinkedIn, third-party editorial/PR, and review platforms like Trustpilot.

The brands that get both sides right: their own product data and how they’re represented across the web - will be much better positioned as AI search keeps growing.

A few numbers from Harley’s post that stood out to me:
• AI-referred sessions grew 197% YoY
• AI shoppers reaching PDPs converted ~80% better than organic traffic
• In research-heavy categories, that was roughly 2x
• Structured Shopify Catalog data drove 2x better conversion than scraped or third-party data.

The interesting part is that AI search isn’t replacing organic search. It’s doing a different job.

Shoppers are using AI to research and compare, then arriving at product pages much further down the funnel.

And the work doesn’t stop on your website. AI also learns about your brand from Reddit, YouTube, LinkedIn, third-party editorial/PR, and review platforms like Trustpilot.

The brands that get both sides right: their own product data and how they’re represented across the web - will be much better positioned as AI search keeps growing.

We’ve been spending a lot of time looking at what actually makes a Shopify store easier for AI agents to understand, and one thing I think is still pretty overlooked is the Shopify Knowledge Base.

Most GEO/AEO discussions focus on product descriptions, blogs, schema, Reddit, etc.

But u/Shopify now has another layer: information that can be provided directly to AI agents through its agentic infrastructure. Shopify’s Knowledge Base lets you define answers around things like shipping, returns, sizing, warranties and other questions - and those answers don’t even need to appear on your website.

This matters because a shopping prompt is rarely just:

“What’s the best running shoe?”

It can be:

“What’s a good running shoe under $150 that comes in wide sizes, ships quickly, and has an easy return policy?”

At that point, your return policy, shipping information and sizing guidance become part of your GEO - not just your product description.

Shopify’s Storefront MCP actually exposes policies and FAQs specifically so AI shopping agents can query this information.

So one thing we’ve started paying much more attention to is whether the whole store gives AI enough certainty to recommend a product - not only whether the PDP is optimized.

Worth checking your Shopify Knowledge Base and asking:

What questions could stop an AI agent from confidently recommending my store?

Then make sure those answers actually exist.

Curious if anyone here has already been actively optimizing their Knowledge Base for this?

We’ve been spending a lot of time looking at what actually makes a Shopify store easier for AI agents to understand, and one thing I think is still pretty overlooked is the Shopify Knowledge Base.

Most GEO/AEO discussions focus on product descriptions, blogs, schema, Reddit, etc.

But u/Shopify now has another layer: information that can be provided directly to AI agents through its agentic infrastructure. Shopify’s Knowledge Base lets you define answers around things like shipping, returns, sizing, warranties and other questions - and those answers don’t even need to appear on your website.

This matters because a shopping prompt is rarely just:

“What’s the best running shoe?”

It can be:

“What’s a good running shoe under $150 that comes in wide sizes, ships quickly, and has an easy return policy?”

At that point, your return policy, shipping information and sizing guidance become part of your GEO - not just your product description.

Shopify’s Storefront MCP actually exposes policies and FAQs specifically so AI shopping agents can query this information.

So one thing we’ve started paying much more attention to is whether the whole store gives AI enough certainty to recommend a product - not only whether the PDP is optimized.

Worth checking your Shopify Knowledge Base and asking:

What questions could stop an AI agent from confidently recommending my store?

Then make sure those answers actually exist.

Curious if anyone here has already been actively optimizing their Knowledge Base for this?

We’ve been spending a lot of time looking at what actually makes a Shopify store easier for AI agents to understand, and one thing I think is still pretty overlooked is the Shopify Knowledge Base.

Most GEO/AEO discussions focus on product descriptions, blogs, schema, Reddit, etc.

But u/Shopify now has another layer: information that can be provided directly to AI agents through its agentic infrastructure. Shopify’s Knowledge Base lets you define answers around things like shipping, returns, sizing, warranties and other questions - and those answers don’t even need to appear on your website.

This matters because a shopping prompt is rarely just:

“What’s the best running shoe?”

It can be:

“What’s a good running shoe under $150 that comes in wide sizes, ships quickly, and has an easy return policy?”

At that point, your return policy, shipping information and sizing guidance become part of your GEO - not just your product description.

Shopify’s Storefront MCP actually exposes policies and FAQs specifically so AI shopping agents can query this information.

So one thing we’ve started paying much more attention to is whether the whole store gives AI enough certainty to recommend a product - not only whether the PDP is optimized.

Worth checking your Shopify Knowledge Base and asking:

What questions could stop an AI agent from confidently recommending my store?

Then make sure those answers actually exist.

Curious if anyone here has already been actively optimizing their Knowledge Base for this?

https://preview.redd.it/h4i2g3bhciih1.png?width=1200&format=png&auto=webp&s=ff098c0ca7dd8832fc17677ffbadde8de7920b9f

I’ve been testing this a lot lately, and the biggest thing I’ve learned is that AEO for Shopify is much more than adding schema or writing more blogs.

The areas I’m focusing on most are:

* Product pages that answer real buyer questions
* Collection pages with better context, FAQs and use cases
* Clean structured data and product information
* Off-site authority from Reddit, YouTube, blogs and reviews
* Making the store easier for AI agents to understand

Curious what others here are testing.

What has actually worked for you so far? And what felt like a waste of time?

Most merchants are optimizing for rankings.
AI is optimizing for confidence.

When ChatGPT, Gemini, Claude, or Perplexity recommend a product, they don’t just look for the page with the “best SEO.”

They’re looking for enough evidence to feel comfortable recommending your brand.

That usually comes from a combination of things:

• Product pages that actually answer buyers’ questions (not just list features).
• Collection pages with useful context instead of only product grids.
• Structured data that helps AI understand your catalog.
• Real discussions on places like Reddit.
• Reviews and third-party mentions.
• Clear comparisons, FAQs, and use cases.

The interesting part is that none of these tactics are particularly new.

What’s changing is how important they become when the “customer” reading your content is an AI assistant before it’s a human.

I’m curious what everyone else is seeing.

Have you made any changes specifically because of ChatGPT or other AI assistants?
If so, what actually moved the needle?

[supprimé]

Has anyone here already built an integration with Shopify Sidekick?

I’m trying to understand whether third-party apps can let merchants take actions directly through Sidekick, or whether integrations are currently limited to answering questions and surfacing app data.

For example, could a merchant ask Sidekick to run a report, update something, or trigger an action inside the app - or can Sidekick only explain what’s happening?

Would love to hear from anyone who has already worked with the integration.