Ecommerce SEO for Stores That Already Run Shopping Ads

Start ecommerce SEO where organic revenue comes from: category pages for broad searches and product pages people buy from. Make sure Google can reach and index them through plain links. Then mark up product pages with the same price, availability and identifiers you send to Merchant Center, so unpaid results and Shopping ads read one product record. Let your ads data choose the categories worth the work. Unpaid results matter most where ads don’t reach: in our study of 1.4 million products, 55.0% got no ad budget in 13 months.

Ecommerce SEO is the work that gets an online store’s pages shown in Google’s unpaid results. This guide maps that work for a store that already sells through Google Shopping. The product data itself, from titles to approval, is the subject of feed optimisation. The unpaid Shopping placements built from that data have a guide of their own: Google free listings for online stores.

Where can a store’s products appear on Google without paying?

Google shows ecommerce content on several surfaces. For products, they draw on two sources: structured data on your web pages and your Merchant Center data. The table is built from two Google Search Central pages: the comparison in Share your product data with Google and, for Google Lens, Where ecommerce content can appear on Google.

Google adds that these experiences may vary by country, device and other factors. Two rules from the same page frame the rest of this guide. First, you can appear in Google Search results without uploading product data to Merchant Center, but some surfaces, such as the Shopping tab, require it. Second, Google recommends doing both: structured data on your product pages and a feed in Merchant Center.

A store with Shopping ads already has the Merchant Center half, and the same products can also show for free. Google’s introduction to Product structured data describes this route as uploading feeds to Merchant Center and opting into free listings in the Merchant Center console. The same page says that markup and a feed together maximise your eligibility and help Google understand and verify your data.

Does AI search need a separate strategy?

Google treats optimising for AI search as ordinary SEO. Its guide to optimising for generative AI features says that AI Overviews and AI Mode are rooted in the core Search ranking and quality systems. A page must be indexed and eligible to show with a snippet. Google also says a site must be included in Search generative AI features in Search Console to be eligible.

You don’t need structured data for generative AI search, and there is no special markup for it. For products, the same guide points to Merchant Center: feeds can help products show both in AI responses and in other Search results. So ordinary ecommerce SEO work covers AI search too.

More than half the products in our study got no ad budget

In our study of 1.4 million products, we followed 1,404,808 products from 130+ stores over 13 months. Across the sample, less than half of the catalogue got any ad budget, and most of the spend went to the few products that sold:

The study also tracked 1,196,357 products that started the period with zero spend. Over 13 months, 74.1% of them never received a single ad impression, and 2.59% reached a conversion. Spend is also concentrated: in the median store, the top 10% of products took 68.1% of the budget.

For a product your ads never show, the only way onto Google is unpaid: an organic result for its page, a merchant listing in Search or a free listing. These numbers describe ads only. Our data has no website analytics, so it can’t say how many of these products earn organic visits. It does show where to look first.

Example store, not client data.

A tableware shop with 3,000 products spends 40,000 a month on ads. Only 1,200 products got at least one impression that month, so 1,800 products, or 60% of the catalogue, were never shown in ads. Those products can appear on Google only if their pages are indexed or the feed takes part in free listings.

Which pages earn organic revenue in an online store?

Two kinds of pages carry a store’s organic search: category pages and product pages. They answer different searches. A category page meets a broad search, such as “linen tablecloths”. A product page meets an exact one: a model, a size, a barcode.

Google gives each page type its own job. In Where ecommerce content can appear on Google, it asks for informative product descriptions that match the words shoppers search with, and for category descriptions that cover less specific queries. Google recommends putting product markup on product pages, not on pages that list a category of products (Merchant listing structured data).

Before choosing pages to work on, measure: in your analytics, export organic search visits (sessions) and revenue by landing page for a full season. Make two lists: the pages that bring 80% of organic visits, and the pages that bring 80% of organic revenue. The second list is your revenue core, and it sets the order of all other SEO work. A traffic page that never sells can wait; a revenue page that drops out of the index can’t.

Our guide to category page SEO explains what a category page should hold, how to paginate it and what to do with categories of one to three products. The guide to product page SEO covers titles, descriptions and images on the product page, and which product pages deserve the work.

How should a store’s structure and internal links work?

Google works out a store’s structure mainly from the links between pages, not from its URLs (Help Google understand your ecommerce site structure). The more internal links a page has, the higher its relative importance on the site. The same page gives five practical rules:

1. Link down the tree. Menus link to category pages, categories to subcategories, and subcategories to all product pages.
2. Use <a href> links. Google asks you to build navigation from these links rather than from JavaScript events attached to other page elements.
3. Make products reachable without site search. Googlebot generally doesn’t type queries into a search box, so crawling alone may miss a product that only site search can reach.
4. Fill the gaps with a sitemap or a feed. If a category can’t link to every product, a sitemap or a Merchant Center feed can list the pages a crawler would otherwise miss.
5. Link to your best-selling products. A link from the home page, a blog post or a newsletter helps Google understand which products matter.

A store with Shopping ads can build one category tree and use it three times: in the site menu, in the feed’s product_type attribute and in the campaign structure. Then a category that sells in ads has the same name and the same products on the site. Our guide to internal linking for online stores shows how to build that tree and point links at the pages that bring revenue.

Which filter pages should be indexed?

Faceted navigation lets shoppers filter a category by brand, colour, size or price, and every combination can become a URL. Google’s guide to managing crawling of faceted navigation URLs names two costs: Google overcrawls useless URLs, and it discovers new useful pages more slowly. Its advice depends on whether you need filter pages in search:

Our guide to faceted navigation SEO explains which combinations deserve a page of their own and where canonical tags belong.

How should long categories be paginated?

Google’s guide to pagination and incremental page loading gives these rules for paginated categories:

• Give each page a unique URL, for example with ?page=2.
• Link each page to the next one with <a href>.
• Give each page its own canonical URL, rather than pointing the whole series to page one.
• Keep page numbers out of the # fragment, because Google ignores it.

Google no longer uses rel="next" and rel="prev". Its crawlers also don’t click buttons, so products behind a “Load more” button or infinite scroll need another path: crawlable links, a sitemap or a Merchant Center feed.

What changes for a store in several countries?

A store that sells abroad repeats its catalogue in several languages or on several domains. Google’s rules for localised versions of a page ask that each language version list itself and all the other versions, and that links between versions go both ways. Our guide to hreflang for online stores shows how to combine that with one catalogue, several feeds and the same products on a marketplace.

How do product pages get crawled and indexed?

Indexing is the step where Google decides that a page can appear in results. Crawling alone doesn’t guarantee it. According to Google’s guide to crawl budget, after crawling, Google evaluates each page, consolidates it with its duplicates and assesses it for the index.

Most stores can leave crawl budget aside. Google wrote that guide mainly for three kinds of sites:

• sites with over a million unique pages that change about once a week;
• sites with 10,000 or more pages that change daily;
• sites with a large share of URLs in the “Discovered – currently not indexed” status in Search Console.

Google calls these numbers rough estimates, not exact thresholds. For other sites, Google says, keeping the sitemap up to date and checking the Page Indexing report regularly is enough.

Many indexing problems in stores start with URLs. Google’s guide to URL structure for ecommerce sites names three patterns:

1. Different content behind a fragment. Google ignores fragments in indexing, so /product/t-shirt#black and /product/t-shirt#white are one page to Google.
2. Several URLs for one page. /product/black-t-shirt and /product?sku=1234 may show the same product. Google can’t tell that from the URLs alone, so it may fetch both.
3. Values that change on every visit. A timestamp in a URL can make the site look endless, so Google takes longer to find the useful pages. Session IDs and tracking codes in internal links can create short-lived or duplicate URLs.

For colour and size variants, Google recommends a separate URL for each variant: a path segment such as /t-shirt/green, or a query parameter such as /t-shirt?color=green.

Indexing also affects Merchant Center. Google’s guide on how to launch an ecommerce website says Merchant Center may cross-check content with the Google Search index. To avoid false verification warnings, make sure the site is indexed and its products are available to buy. The link works in the other direction too: a feed gives Google more confidence that it knows all your products, because crawling isn’t guaranteed to find every one (Share your product data with Google).

Changes take time to show. According to Google’s SEO Starter Guide, some take effect in a few hours and others take several months, so wait a few weeks before you judge one. The article on product pages that aren’t indexed explains what the Search Console statuses mean and how sitemaps help new stores and large catalogues.

What should product structured data contain?

Structured data tells Google, in a fixed format, what a page sells. Google splits product markup into two types (Introduction to Product structured data):

A store needs merchant listing markup. In general, its required properties also make the page eligible for product snippets. According to Merchant listing structured data, the product needs a name, an image and an offer with a price. Google strongly recommends a description and lists brand, GTIN, availability and return policy among the recommended properties.

Five rules from Google’s documentation matter most for stores:

1. Mark up the product page. Product rich results support only pages about one product or its variants, so category listings are the wrong place for this markup.
2. Group variants. ProductGroup with variesBy, hasVariant and productGroupID tells Google which products are variants of one parent, and makes them eligible to show with variant information (Product variant structured data).
3. Put the markup in the initial HTML. Markup generated by JavaScript can make Shopping crawls less frequent and less reliable, which can be a problem for fast-changing data like price and availability.
4. Describe store-wide policies once. Google recommends nesting the return policy and loyalty programme under Organization markup.
5. Test, then watch. Check the code in the Rich Results Test, then watch the Merchant listings report in Search Console.

You can set shipping and return details in several places, so Google applies them in this order of precedence:

1. Product-level feeds in Merchant Center.
2. Settings in the Content API for Shopping.
3. Settings in Merchant Center or Search Console.
4. Product-level markup.
5. Organisation-level markup.

Google’s page still lists the Content API for Shopping. According to its Content API migration guide, Google sunset that API on 18 August 2026 in favour of the Merchant API. Our guide to product structured data for online stores covers which warnings to fix first and how reviews and policies fit in.

One product record feeds both Shopping ads and unpaid results

The feed and the page describe the same product, and Google compares them. Structured data can make price, discount and shipping costs clearer to Google, and it can help Merchant Center verify the feed against your site (Share your product data with Google). Google combines the two sources as well. According to the Product structured data introduction, product snippets may take the price from your feed when the page markup has no price.

The weak point is lag. When a product sells out, the site usually marks it at once, while Merchant Center may update later, especially with feed files. Google’s fix is to let Merchant Center update its copy of the product data from the website when it notices a mismatch.

The same field usually lives in three places: the product feed, the page markup and the product listing a shopper sees in Shopping. The table maps the nine checks of GetProfit’s feed score to merchant listing markup. The weights are the portal’s own rule rather than a Google formula, and they add up to 100.

Eight of the nine checks have a direct counterpart in page markup. Fix a field once, in the product database behind both the feed and the pages, and the fix reaches ads and unpaid results together. For each of the nine checks, the portal’s feed analysis shows how many products are affected and what changed since last time.

What else do category and product pages need?

Product data makes a page eligible for rich results. The text and media on the page help it match searches and win the click. Google’s SEO Starter Guide and its ecommerce pages give these rules:

• A unique title for each page. A good title is unique to the page, clear and concise, and accurately describes its contents. Pages in one paginated series are the exception: Google says they can share titles and descriptions.
• A useful snippet. Google builds the snippet mostly from the page content, and sometimes from the meta description.
• Images near relevant text, with descriptive alt text. The alt text explains how the image relates to the page.
• Reviews and policies. Google suggests customer reviews, in-depth merchant reviews and clear return and shipping policies as content that helps shoppers (Where ecommerce content can appear on Google).

The same Starter Guide corrects several popular beliefs:

Pages beyond the catalogue, such as buying guides and answers to customers’ questions, reach shoppers before they choose a product. Our guide to content marketing for online stores shows how to build them from real questions.

What happens to a URL when a product sells out or a season ends?

Stock changes faster than pages. In merchant listing markup, an offer takes one availability value, such as InStock, OutOfStock, BackOrder, PreOrder or Discontinued. The feed’s availability attribute should say the same thing, so the page and the feed agree.

The URL is a separate decision: keep the page, redirect it permanently with a 301, or let it return a “not found” (404) or “gone” (410) status. The answer depends on whether the product comes back and whether the page still earns visits and links. Our guide to discontinued products and seasonal pages walks through every case.

Which SEO shortcuts put a store at risk?

A product catalogue makes it easy to generate pages in bulk, and Google’s spam policies address this directly. Scaled content abuse means generating many pages mainly to manipulate rankings rather than help users, however the pages are made. Google’s examples include pages generated with AI tools without adding value, and pages built by scraping feeds, including through automated translation, that give users little value. Doorway abuse includes substantially similar pages that sit closer to search results than to a clear, browsable hierarchy.

Google’s guide to generative AI features applies the same line to query variations. Creating separate content for every way people might search, mainly to manipulate rankings or AI responses, violates the scaled content abuse policy. In a store, the risky patterns are a page per city, near-identical pages for every filter combination and copied product descriptions rewritten with synonyms. Our article on cloaking and scaled content in ecommerce shows where Google draws the line, with a store’s domain ban as the example.

The riskiest planned change is a platform move. Google’s guide to site moves with URL changes asks you to map old URLs to new ones and set up server-side permanent redirects, such as 301. It recommends keeping the redirects for as long as possible, generally at least a year. For a medium-sized site, it can take a few weeks or more before Google shows the new URLs, and rankings can fluctuate during the move. Our guide to moving your store to a new platform has the checklist for before and after launch.

How can Google Ads data guide your SEO?

A store with Shopping ads already has a record of which searches and products brought orders. That record helps SEO in three places:

1. Keyword research. Start from the searches that led to orders in your ads, grouped by category and product, before you look at search volumes. Our guide to ecommerce keyword research explains the method.
2. Page priority. Products your ads never show are candidates for organic results and free listings. Categories that sell in ads are candidates for category content.
3. Overlap between paid and unpaid. You can split Merchant Center performance data by marketing method, ads or organic (Performance reports in the Merchant API documentation). Our article on SEO and Google Ads together looks at whether Shopping ads take sales that organic results would have made. It also covers what to do with a category that doesn’t sell in ads.

Where to start: ecommerce SEO in order of revenue impact

1. Find your revenue core. List the landing pages that bring 80% of organic revenue, separately from the pages that bring 80% of visits. Check: you know which pages bring in the revenue.
2. Check that those pages are indexed. Look up each one in Search Console. Check: every revenue page is in the index.
3. Make every category and product reachable by <a href> links. Check: you can reach each product from the menu without site search.
4. Decide which filter and sort pages Google may crawl. Block the rest. Check: crawl reports show no endless filter URLs.
5. Fix pagination. Each page gets a unique URL and links to the next. Check: page two and beyond each have their own canonical URL.
6. Add merchant listing markup to product pages, in the initial HTML. Check: the Rich Results Test shows no critical errors, and the number of valid items in the Merchant listings report grows.
7. Align the feed and the page. Price, availability, GTIN and brand should match. Check: Merchant Center shows no price or availability mismatches.
8. Write category descriptions for broad searches and product descriptions in shoppers’ words. Check: each revenue page has a unique title.
9. Plan what happens to sold-out and seasonal URLs. Check: availability in the markup and the feed changes on the same day.
10. Review the store regularly. When organic revenue drops, go through the causes in order of revenue impact with an ecommerce SEO audit.

See what Google doesn’t see in your catalogue. Sign in with Google in one click — both Google Ads and Merchant Center. We change nothing, neither in your account nor in the feed, without your consent.

Check your feed →

Sources

• Best practices for ecommerce sites in Google Search — the set of Google Search Central guides this article follows. Checked 2 October 2026.
• Share your product data with Google — Merchant Center isn’t required for Search but is required for the Shopping tab; Google recommends markup plus a feed; the surfaces table; crawling isn’t guaranteed to find all products; automatic updates against price and stock mismatches. Checked 2 October 2026.
• Where ecommerce content can appear on Google — Google Lens requirements; product and category descriptions; reviews and policies as content. Checked 2 October 2026.
• Introduction to Product structured data — merchant listings versus product snippets; opting into free listings; markup plus a feed maximises eligibility; snippets may take the price from the feed. Checked 2 October 2026.
• Merchant listing (Product, Offer) structured data — required and recommended properties, single-product pages, initial HTML, availability values, precedence of shipping and return settings, Search Console reports. Checked 2 October 2026.
• Product variant structured data — ProductGroup and its properties. Checked 2 October 2026.
• Optimizing your website for generative AI features on Google Search — AI features rely on core ranking; eligibility conditions; no special markup; Merchant Center feeds; query variations and scaled content abuse. Checked 2 October 2026.
• Help Google understand your ecommerce website structure — links over URLs, <a href>, search boxes, sitemaps and feeds, linking to bestsellers. Checked 2 October 2026.
• Managing crawling of faceted navigation URLs — costs of filter URLs and the two sets of recommendations. Checked 2 October 2026.
• Pagination, incremental page loading, and their impact on Google Search — pagination rules, shared titles in a series, rel="next" no longer used. Checked 2 October 2026.
• Tell Google about localized versions of your page — each version lists itself and all others, links go both ways. Checked 2 October 2026.
• Optimize your crawl budget — who the guide is for; crawled pages are evaluated before indexing. Checked 2 October 2026.
• Designing a URL structure for ecommerce websites — fragments, duplicate URLs, changing values, variant URLs. Checked 2 October 2026.
• How to launch a new ecommerce website — Merchant Center cross-checks content with the Search index. Checked 2 October 2026.
• SEO Starter Guide — time to impact, titles, snippets, images, meta keywords, content length, domain keywords, duplicate content. Checked 2 October 2026.
• Spam policies for Google web search — scaled content abuse and doorway abuse. Checked 2 October 2026.
• Site moves with URL changes — URL mapping, permanent redirects, how long to keep them, time to show new URLs. Checked 2 October 2026.
• Performance reports (Merchant API) — performance split by marketing method, ads or organic. Checked 2 October 2026.
• Migrate from the Content API for Shopping to the Merchant API — the Content API for Shopping was sunset on 18 August 2026. Checked 2 October 2026.
• GetProfit study: 1,404,808 products, 130+ stores, 13 months — products with and without ad budget, impressions of products that started with zero spend, concentration of spend.
• GetProfit portal methodology — the nine checks of the feed score and their weights.