GEO for e-commerce: how I optimized a product page to appear in ChatGPT, Gemini and Perplexity answers
The article discusses the importance of optimizing e-commerce product pages for visibility in AI-generated answers. It highlights a case study where a client's product page was not mentioned by popular AI engines despite good SEO rankings. The author outlines a step-by-step process to enhance AI visibility through Generative Engine Optimization (GEO).
- ▪Many consumers are now using AI engines like ChatGPT and Gemini instead of traditional search engines like Google.
- ▪The author's client had a product page that ranked well on Google but was not mentioned by any AI when queried about trail running shoes.
- ▪GEO focuses on optimizing content for AI engines, which requires different strategies compared to traditional SEO.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/ndabene/geo-for-e-commerce-how-i-optimized-a-product-page-to-appear-in-chatgpt-gemini-and-perplexity-16id |
| Publication time | Thu, 28 May 2026 21:15:03 +0000 |
| Retrieval time | 2026-05-28T21:29:38.368Z |
| Last seen | 2026-05-28T21:29:38.368Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 1vun_vxHxtco |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3605489) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Nicolas Dabene Posted on May 28 • Originally published at nicolas-dabene.fr GEO for e-commerce: how I optimized a product page to appear in ChatGPT, Gemini and Perplexity answers #geo #seo #ecommerce #chatgpt A step-by-step case study with before/after measurements Reading time: 20 minLast updated: February 2026 You invest time and money in SEO for your PrestaShop store. Your product pages rank well on Google.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
