SEO for ecommerce product pages: Google and AI shopping
SEO for ecommerce product pages, step by step: titles, descriptions, Product schema, GTINs and variants, with a worked example for Google and AI shopping.

On this page 11 sections
- What SEO for ecommerce product pages is, and why it matters for Google and AI shopping
- Product titles and meta descriptions that match how people search
- Product descriptions that answer buyers' questions
- Images, alt text and short videos
- Product structured data: Product, Offer, reviews, shipping and returns
- Reviews, questions and trust signals on the product page
- Product data that AI shopping reads: GTINs, attributes and feeds
- Product variants and out-of-stock products
- Internal links and site structure for product pages
- A product page SEO checklist
- Check one product page against its markup and feed
Short answer: SEO for ecommerce product pages means making each product page easy for Google and AI shopping assistants to find, understand and trust. Write a specific title and meta description, a description that answers buyers' questions and descriptive alt text. Then add complete Product and Offer structured data, real reviews, and GTINs and attributes that match your product feed.
What SEO for ecommerce product pages is, and why it matters for Google and AI shopping
Product page SEO is the work of making each product URL rank in Google Search, appear in Google's shopping results and get picked by AI shopping assistants such as ChatGPT. It matters because product pages are the only pages Google's free listings show. They are also where a purchase that starts in ChatGPT finishes.
Google's Merchant Center Help (opens in a new tab) is explicit: "Free listings for products help your product pages to appear in search results, not other pages like homepages, delivery and return policies, or product category pages." The product URL has to carry the price, the stock status and the detail on its own.
AI shopping follows the same pattern. OpenAI's merchants page (opens in a new tab) says its merchant feed programme is live for ChatGPT users in the US so far (read 13 November 2026) and that "purchases are completed on merchant-owned websites or apps." A buyer who shortlists your product in ChatGPT still lands on your product page to pay.
One page, three readers
Three kinds of system read every product page, and each relies on different parts of it:
- Google Search ranks the page from its title, text, links and structured data.
- Google's shopping results draw on your Merchant Center feed and the Product markup on the page.
- AI shopping answers in ChatGPT and Google AI Mode draw on product data from feeds, markup and page text.
The work for each reader overlaps heavily. Google's AI optimisation guide (opens in a new tab) puts it plainly: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add." The same markup still makes the page eligible for rich results in classic search, so one accurate page serves all three readers.
The worked example in this guide
Each section below applies ecommerce on-page SEO to one illustrative product: the Ridge women's waterproof walking boot from Northfell, a made-up brand, priced at $149. The before-and-after details were invented to show the method, so they are not a measured result.
To see where one of your own product pages stands first, test its markup in Google's Rich Results Test (opens in a new tab).
Product titles and meta descriptions that match how people search
A product title should name the product type, the brand and product name, and the one or two attributes people search with, such as gender, colour or material. Put the most important words first. The meta description should add the facts that earn the click: price, delivery, returns and stock.
- Title tag
Before: Ridge Boot - Northfell. After: Ridge Women's Waterproof Walking Boots, Brown - Northfell.
- Meta description
Before: None set. After: Sizes, $149, free US delivery, free 30-day returns, stock.
- URL
Before: /products/ridge-v2-final. After: /products/ridge-womens-waterproof-walking-boot.
Illustrative example: the made-up Northfell Ridge boot's title tag, meta description and URL before and after applying this guide.
Find the words buyers use
Start from how buyers phrase the search. In Google Search Console, open the Performance report, filter to the product URL and read the Queries tab. The long-tail keywords there show which attributes people type, and your store's internal search log and customer service emails fill the gaps.
Title tag, H1 and feed title
Three titles describe one product. The title tag is what Google usually shows as the clickable title link, the H1 is the heading on the page, and the feed title is what Merchant Center shows in shopping results. Keep the three consistent: the title tag can end with the store name, while the feed title leads with brand and attributes.
Google may shorten a long title link to fit the screen, and may rewrite one that does not match the page. Put the product type and name in the first few words so a shortened title still makes sense.
Before and after for the illustrative boot
Element | Before | After |
|---|---|---|
Title tag | Ridge Boot - Northfell | Ridge Women's Waterproof Walking Boots, Brown - Northfell |
Meta description | None set, so Google picks text from the page | Waterproof leather walking boots for women, US sizes 5 to 11. $149 with free US delivery and free 30-day returns. In stock in brown and slate. |
URL | /products/ridge-v2-final | /products/ridge-womens-waterproof-walking-boot |
Keep the URL short and stable
The URL should be short and readable, with no variant or campaign parameters. Shopify puts product URLs under /products/, and WooCommerce uses /product/ unless you change the permalink base. If you change a live URL, add a 301 redirect from the old one, or the page loses the links it has earned.
Product descriptions that answer buyers' questions
A product description should be as long as it takes to answer the questions a buyer asks before paying. Google does not publish a word count for it. In practice, write a plain first paragraph saying what the product is and who it suits, then cover specifications, sizing, care and what comes in the box.
Write the first paragraph for a skimmer
The first two sentences carry the most weight, for a shopper and for an AI answer quoting the page. Name the product, who it is for and the fact that sets it apart.
- Before (illustrative): "Our Ridge boot is perfect for all your adventures."
- After (illustrative): "The Ridge is a women's waterproof leather walking boot for day hikes on wet, rocky ground. It weighs 520g per boot in a US size 7, has a seam-sealed waterproof membrane and fits a medium-width foot."
Answer what buyers ask
Collect the questions from reviews, support emails and returns reasons, then answer them in the text:
- Fit and sizing: does it run small, and who should size up?
- Materials and care: what it is made of and how to clean it.
- Use and compatibility: what it works with, and what it is not designed for.
- What is in the box, plus delivery and returns.
Put specifications in an HTML table rather than an image of a table, so search engines and screen readers can read them.
Rewrite manufacturer copy
Stores selling the same product often publish the same manufacturer description. Bing's webmaster team describes the risk (opens in a new tab): "Duplicate content doesn't trigger search penalties on its own, but it does reduce visibility by diluting authority, confusing intent, and slowing how updates reach" search engines and the systems that find and surface content in AI answers. Rewrite at least the opening and the fit notes in your own words, and add what only you know.
Put the text in the HTML
Keep the description and specifications in the HTML the server sends. Crawlers that do not run scripts may never read text that appears only after a JavaScript tab loads on click. How AI crawlers read your website covers the detail.
If AI drafts the copy
For Merchant Center, Google's guidance on generative AI content (opens in a new tab) sets a rule: "AI-generated product data such as title and description attributes must be specified separately and labeled as AI-generated." Check every AI draft against the product itself before it goes live. A wrong size or material costs you returns as well as trust.
Images, alt text and short videos
Product images need to be crawlable, sharp and described, because Google shows them in image search and shopping results, and merchant listings require an image. Use several angles on a plain background plus in-use shots, a descriptive file name and alt text that says what each image shows. Add a short video where fit or movement matters.
Images Google can find and load fast
- Use standard formats such as JPEG, PNG or WebP, served in an
<img>element. Google does not index images set as CSS backgrounds. - Name files for what they show, such as ridge-womens-walking-boot-brown-side.jpg instead of IMG_4482.jpg.
- Set width and height and compress the files. Do not lazy-load the main image, which is often the page's Largest Contentful Paint element in Core Web Vitals.
- Use the same main image in the page, the markup and the feed.
Alt text that describes
Alt text is for screen-reader users first and search engines second. Describe the image in one plain sentence and leave out keyword lists.
- Before (illustrative): boot
- After (illustrative): Ridge women's walking boot in brown leather, side view showing the lug sole
Video where a still falls short
A short video showing fit, flex or assembly answers what a photo cannot. Put it on the product page itself, give it a title and description, and add VideoObject markup so Google can find and understand it.
Product structured data: Product, Offer, reviews, shipping and returns
A product page needs Product structured data in JSON-LD, with a nested Offer stating the price, currency, availability and condition of what the page sells. Add brand, GTIN, SKU and images. Add Review or AggregateRating only for reviews shown on the page, and add shipping and return details for merchant listings.
- Product-level feeds submitted in Merchant Center
Strongest source in Google's order
- Settings in the Content API for Shopping
Second in Google's order
- Settings in Merchant Center or Search Console
Third in Google's order
- Product-level merchant listing markup
Fourth in Google's order
- Organization-level markup
Weakest source in Google's order
Google's merchant listing documentation ranks shipping and returns sources from strongest to weakest.
Product snippets and merchant listings
Google's Product structured data documentation (opens in a new tab) describes two result types. Product snippets suit pages that review or describe a product. Merchant listings suit pages where a shopper can buy it, and can show price, availability, shipping and returns.
For merchant listings, the merchant listing documentation (opens in a new tab) marks name, image and offers, with a price and currency, as required. It lists brand, GTIN, availability, shipping details and return policy among the recommended properties.
Markup for the illustrative boot
This is JSON-LD for one variant of the illustrative Ridge boot. The GTIN is a widely used example code, so replace it with the one printed on your barcode.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Ridge Women's Waterproof Walking Boots",
"brand": { "@type": "Brand", "name": "Northfell" },
"sku": "RDG-W-BRN-7",
"gtin": "012345678905",
"color": "Brown",
"material": "Leather",
"size": "7",
"image": ["https://example.com/images/ridge-womens-walking-boot-brown-side.jpg"],
"description": "Women's waterproof leather walking boot for day hikes on wet, rocky ground.",
"offers": {
"@type": "Offer",
"url": "https://example.com/products/ridge-womens-waterproof-walking-boot",
"price": "149.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"shippingDetails": {
"@type": "OfferShippingDetails",
"shippingRate": { "@type": "MonetaryAmount", "value": "0", "currency": "USD" },
"shippingDestination": { "@type": "DefinedRegion", "addressCountry": "US" },
"deliveryTime": {
"@type": "ShippingDeliveryTime",
"handlingTime": { "@type": "QuantitativeValue", "minValue": 0, "maxValue": 1, "unitCode": "DAY" },
"transitTime": { "@type": "QuantitativeValue", "minValue": 1, "maxValue": 5, "unitCode": "DAY" }
}
},
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30,
"returnFees": "https://schema.org/FreeReturn"
}
}
}The deliveryTime block follows Google's merchant listing documentation. handlingTime is "the typical delay between the receipt of the order and the goods leaving the warehouse", and transitTime is the delay from dispatch until the goods reach the customer. Each takes a minValue and maxValue in whole days with a unitCode of DAY, and the day counts here are illustrative.
For a sale price, the merchant listing documentation marks when it starts with validFrom and when it ends with either validThrough or priceValidUntil.
Shipping and returns: which source Google uses
You can state shipping and returns in Merchant Center, in Search Console, in product markup or in organisation-level markup. Google's merchant listing documentation states: "If you define shipping or return policies in multiple places, Google uses the following order of precedence (from strongest to weakest)".
It then lists, in this order: "Product-level feeds submitted in Merchant Center", "Settings in the Content API for Shopping", "Settings in Merchant Center or Search Console", "Product-level merchant listing markup" and "Organization-level markup". Keep every source consistent.
Test before and after publishing
Test a URL in Google's Rich Results Test, then watch the Merchant listings and Product snippets reports in Google Search Console for errors across the range.
On Shopify and WooCommerce, see what the theme or SEO plugin already prints before you add more markup. Two Product blocks on one page with different prices send Google conflicting values. For WooCommerce product SEO on WordPress, WordPress SEO in the AI era covers the wider setup.
From RankX AICompare the plans that track your products in AI shopping.Fix the template or feed rule behind each mismatch first, because one fix reaches every product that uses it, then work down the checklist.See pricingReviews, questions and trust signals on the product page
Product reviews help a page in two practical ways. They add specific text in buyers' own words, and real reviews marked up with Review or AggregateRating make the page eligible for review stars in Google's product results. Google has not said reviews are a direct ranking factor, and we do not know of published evidence that they are one.
Collect reviews that answer questions
Ask for a review after the product has been used, and ask about the details the next buyer needs: fit, durability and what they used it for. Show reviews in the page's HTML as well as in any widget that loads by JavaScript.
Google's review snippet guidelines (opens in a new tab) expect marked-up reviews to be visible to users on the page. The same guidelines say a review given in exchange for a benefit, such as a discount or a free product, must clearly disclose that incentive. Never write, buy or filter reviews to inflate a rating.
Questions and answers on the page
A short questions-and-answers block built from real customer questions adds user-generated content that answers follow-up searches, such as whether a boot runs true to size. Keep each answer accurate, and update it when the product changes.
Trust signals buyers look for
These details answer the questions that would otherwise send a buyer back to search:
- The full price, including any extra fees.
- Delivery cost and an estimated delivery date.
- The returns window, linked to the full policy.
- Stock status for the selected variant.
- A way to contact the store before buying.
Product data that AI shopping reads: GTINs, attributes and feeds
AI shopping in Google and ChatGPT draws on structured product data. That data covers identifiers such as GTIN, brand and MPN, attributes such as colour, size, material and gender, and the price and availability in your feed. You control whether those values are complete and identical across the page, the markup and the feed.
GTINs
A GTIN (Global Trade Item Number) is the number behind a product's barcode, issued through GS1. In North America it is usually a UPC, and in most other markets an EAN. It lets Google match your offer to the same product sold elsewhere, so use the manufacturer's GTIN and never invent one.
If a product has no GTIN, submit its brand and MPN where it has them. If it has no manufacturer identifiers at all, such as a handmade item, set identifier_exists to no in Merchant Center.
Attributes in three places
Attribute | Illustrative value | Where it goes |
|---|---|---|
Brand | Northfell | Page, markup, feed |
GTIN | 012345678905 | Markup, feed |
Colour | Brown | Page, markup (color), feed (color) |
Size | US 5 to 11 | Page, variant markup, feed (size) |
Material | Leather | Page, markup, feed |
Gender | Female | Page, feed (gender) |
Condition | New | Markup (itemCondition), feed |
Availability | In stock | Page, markup, feed |
Feeds and freshness
The Merchant Center feed is Google's main source of shopping product data. ChatGPT shopping has its own merchant routes, which the ChatGPT shopping product feed guide covers.
Update the feed whenever price or stock changes, and keep page and feed in step. If the price on the page differs from the price in the feed, Merchant Center can disapprove the product.
How AI shopping assistants choose products
Neither OpenAI nor Google publishes how its AI shopping ranks products, so we do not know the weights. What merchants control is the inputs: feeds, structured data and their own product pages. Make those inputs complete, then measure which products appear for the prompts that matter to you over time, because answers change between runs.
Product variants and out-of-stock products
Product variants such as sizes and colours should share one product group with one canonical URL. Each variant needs its own SKU, GTIN, price and availability in the markup and the feed. A product that is temporarily out of stock should stay live and say so, and a discontinued product should redirect to its closest replacement.
Variants
Google's product variant documentation (opens in a new tab) says that where all variants share one page, "there must be only one distinct canonical URL for the overall" product group, normally the base URL with no variant preselected. Mark the group up as a ProductGroup with productGroupID, variesBy (for example size and color) and hasVariant, and mark up each variant as its own Product.
Separate near-identical pages for each colour split links and signals across URLs, which is the dilution Bing describes above. Give a variant its own indexable page only when people search for it on its own and the page says something different.
Out-of-stock products
Keep a temporarily out-of-stock page live and indexed. Set availability to OutOfStock, or to BackOrder or PreOrder with a date, and show a restock estimate or close alternatives. Removing the page and adding it back later throws away its links and history.
Situation | Availability value | URL action | What to show on the page |
|---|---|---|---|
Temporarily out of stock | OutOfStock | Keep live and indexed | Restock estimate or close alternatives |
Orders taken for later dispatch | BackOrder | Keep live and indexed | Expected dispatch date |
Not yet released | PreOrder | Keep live and indexed | Release date |
Discontinued, with a successor | None (the URL redirects) | 301 to the successor | Nothing, the successor page loads |
Discontinued, no successor | Discontinued | Keep live while people search, then 404 or 410 | Discontinued notice and alternatives |
Discontinued products
When a product is gone for good, 301-redirect its URL to the direct successor or the closest equivalent. If none exists, keep a page that says the product is discontinued and links to alternatives while people still search for it. Otherwise, return a 404 or 410.
Avoid redirecting every old product to the homepage, because Google can treat that as a soft 404.
Internal links and site structure for product pages
Product pages need links from the rest of the store so Google can find them and see where they sit. Link every product from its category page, mark up breadcrumbs with BreadcrumbList and add related-product blocks. Then look for product pages that nothing links to, and give a product that sits in several categories one canonical URL.
Link products from their category pages
Google's ecommerce site structure guidance (opens in a new tab) recommends links "from menus to category pages, from category pages to sub-category pages, and finally from sub-category pages to all product pages." It also warns: "If category pages don't include direct links to all products in a category, Googlebot might not find all of your products by crawling alone."
Related-product blocks, such as matching items or alternatives, add more paths to each product. Put them in the server-rendered HTML as standard <a href> links so crawlers can follow them.
Breadcrumbs with BreadcrumbList
A breadcrumb trail such as Home > Women's boots > Walking boots > Ridge shows where the product sits and links back up to its categories. Google's breadcrumb documentation (opens in a new tab) says a trail "may help users understand and explore a site effectively", and that Google Search uses breadcrumb markup "to categorize the information from the page in search results." Mark the trail up as BreadcrumbList, with the same steps the page shows.
Find orphaned product pages
An orphaned product page is one that no other page on the store links to, so a crawler following links cannot reach it. Google's guidance states: "It's strongly recommended to link to all products that you wish indexed." To find orphans, compare a full export of live product URLs from your platform with the URLs a crawler reaches by following links from the homepage, then link any missing product from its category page.
Products in several categories
A boot listed under both walking boots and waterproof boots should still have one product URL. If your platform creates a separate URL for each category path, point a canonical link on every version at the main product URL, and link to that URL from the category pages.
Google's ecommerce URL structure guidance (opens in a new tab) explains the cost of skipping this: "The same content may be retrieved multiple times by the crawler if Google thinks two URLs are different but result in the same page being returned."
A product page SEO checklist
To optimise a product page for SEO, work through one URL at a time. Fix the title, meta description and URL, rewrite the opening of the description and describe the images. Then add complete Product and Offer markup, show real reviews and trust details, and make the GTIN, attributes, price and stock match your feed.
- Title tag
Product type, brand, name and key attribute first
- Meta description
Price, delivery, returns and stock
- URL
Short, readable, no parameters
- Description
Answers fit, materials, care and box contents in HTML
- Images
Several angles, descriptive file names and alt text
- Markup
Product and Offer with GTIN, shipping and returns
- Reviews and trust
Real reviews on the page, policies linked
- Feed and variants
Values match the page, one canonical URL per group
Work through these eight checks on one product page, then repeat across the range.
The checklist
- Title tag: product type, brand, product name and key attribute, with the most important words first.
- Meta description: price, delivery, returns and stock.
- URL: short, readable and free of parameters.
- Description: answers fit, materials, care and what is in the box, in server-rendered HTML.
- Images: several angles, descriptive file names and alt text.
- Markup: Product and Offer with price, currency, availability, GTIN, shipping and returns.
- Reviews and trust: real reviews visible on the page, with policies linked.
- Feed and variants: GTIN, attributes, price and stock that match the page, with one canonical URL per product group.
The illustrative boot, start to finish
Element | Before | After |
|---|---|---|
Title tag | Ridge Boot - Northfell | Ridge Women's Waterproof Walking Boots, Brown - Northfell |
Meta description | None set | Price, free US delivery, free 30-day returns, sizes and stock |
First paragraph | "Perfect for all your adventures" | Product, who it suits, weight, membrane and fit |
Attributes | Brand only | Brand, GTIN, colour, size, material, gender, condition, availability |
Schema | Name and price | Product and Offer with GTIN, availability, shipping and returns |
Check the result the same way each time. Use the Rich Results Test for the markup and Search Console for the whole range, then read the page, markup and feed side by side to confirm the values match.
Where RankX AI fits
A checklist fixes one page; tracking how your products show in AI shopping over weeks needs a schedule. RankX AI's AI Shopping is a module you switch on per website, and it checks the shopping prompts you choose in ChatGPT and Google AI Mode.
Each check runs on a schedule you choose (daily, every 3 days, weekly, fortnightly or monthly), up to the fastest schedule your plan allows. rankxai.com/pricing lists each plan's allowances, including how many shopping prompts and monitored products it covers. A check costs 5 credits per shopping prompt, per surface, per run, according to the same page, so a prompt checked in both ChatGPT and Google AI Mode costs 10 credits a run.
RankX AI's web app offers a 7-day free trial with 1,000 credits and no card, and the trial starts when you finish onboarding, not at signup. On Shopify, the RankX AI Shopify app has its own 7-day trial with 1,000 credits, once per store, which starts when the store picks a plan and is billed through Shopify (how the trial works). See pricing to compare plans and credits.
Summary
SEO for ecommerce product pages comes down to one accurate, complete page per product. Write the title and description the way buyers search, describe the images and publish Product and Offer markup that matches the page, with real reviews and GTINs, attributes, prices and stock that agree with your feed.
Start with your highest-value product, check its markup in Google's Rich Results Test (opens in a new tab), then repeat the pattern across the range.
Check one product page against its markup and feed
Pick one best-selling product. Open its page, the Product markup the page prints (view the source or run the Rich Results Test) and its row in the Merchant Center feed side by side. Compare the title, price, currency, availability, GTIN, brand, colour and size, and note every value that differs or is missing.
Fix the template or feed rule behind each mismatch first, because one fix reaches every product that uses it, then work down the checklist. Repeat the comparison after the next price change or theme update, and watch the Merchant listings report in Search Console across the range. Matching values make the page eligible and readable; they do not guarantee a rich result, a place in an AI answer or a sale.
Next, optimise the rest of a Shopify store or get product data ready for AI shopping agents.
Questions about Ecommerce & Technical SEO
How do I optimise a product page for SEO?
Work through one URL at a time. Write a specific title and meta description, rewrite the description so it answers buyers' questions, and add alt text to the images. Then publish complete Product and Offer structured data, show real reviews, and make the GTIN, attributes, price and stock on the page match your Merchant Center feed.
What should a product page title include?
Include the product type, the brand and product name, and the one or two attributes buyers search with, such as gender, colour, size or material. Put the most important words first, because Google can shorten long title links to fit the screen. Keep the title tag, the H1 and the feed title consistent.
How long should a product description be for SEO?
Google does not publish a minimum or ideal length for product descriptions. Keep writing until the common buyer questions are answered: what the product is, who it suits, specifications, sizing, care and what is in the box. A short, specific description is more useful than a long generic one copied from the manufacturer.
Do product reviews help SEO?
Reviews add specific text in buyers' own words. When they are marked up and shown on the page, they also make the page eligible for review stars in Google's product results. Google has not said reviews are a direct ranking factor, and you should never mark up reviews that are not visible on the page.
How do AI shopping assistants choose which products to show?
Neither OpenAI nor Google publishes how its AI shopping ranks products, so the weights are not known. Both draw on product data from feeds, structured data and the merchant's own pages, including GTINs, attributes, price and availability. Make that data complete and consistent, then watch which products appear for your most important prompts over time.
What structured data does a product page need?
A product page needs Product markup in JSON-LD with a nested Offer giving the price, currency and availability. Google's merchant listing documentation lists brand, GTIN, shipping details and return policy as recommended properties. Use Review or AggregateRating only where real reviews appear on the page.
Sources
- Google Search Central: Product variant structured data (opens in a new tab) Checked 2026-11-13.
- Google Search Central: AI optimisation guide (opens in a new tab) Checked 2026-11-13.
- Google Merchant Center Help: Free listings (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Merchant listing structured data (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Product structured data (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Review snippet structured data (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Guidance on using generative AI content (opens in a new tab) Checked 2026-11-13.
- OpenAI: ChatGPT for merchants (opens in a new tab) Checked 2026-11-13.
- Bing Webmaster Blog: Does duplicate content hurt SEO and AI search visibility? (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Help Google understand your ecommerce site structure (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Breadcrumb structured data (opens in a new tab) Checked 2026-11-13.
- Google Search Central: Designing a URL structure for ecommerce sites (opens in a new tab) Checked 2026-11-13.
- OpenAI Help Center: ChatGPT release notes (opens in a new tab) Checked 2026-11-13.
- RankX AI docs: Free trial Checked 2026-11-13.
CoversThis article covers the Ecommerce & Technical SEO topic, the AI Shopping feature and the AI Readiness Score tool.
Terms usedSchema Markup (Structured Data), Product feed, AI shopping visibility, Canonical Tag, Internal Linking, Google AI Mode and Core Web Vitals.
Read this page asMarkdown: /blog/ecommerce-product-page-seo.md.
All articlesEverything RankX AI publishes is listed on the blog index.
Ask an assistantAsk ChatGPT (opens in a new tab), Ask Claude (opens in a new tab) or Ask Perplexity (opens in a new tab).
Preferred sourceIf Google is your front door, you can add RankX AI as a preferred source (opens in a new tab), which asks your own results to surface more of what we publish.


