Google Merchant Center

TL;DR — Google Merchant Center (GMC) is a free Google tool where online stores upload their product data. Most people think it’s only for paid Shopping ads — but it also powers free product listings that show up in normal Google searches, Images, and more. That makes it an SEO tool, not just an ads tool.

What Google Merchant Center is

Google Merchant Center is where retailers send Google their product information — titles, prices, images, availability, and so on. Google then uses that data to show your products in lots of places: the Shopping tab, regular Google Search (those product grids you see at the top of shopping searches), Google Images, Lens, and newer AI experiences. Evidence for this claim Merchant Center lets retailers provide product data for eligible Google surfaces. Scope: Surface availability varies by program, country, and eligibility. Confidence: high · Verified: 2026-07-14 Google Merchant Center Help: Get started

For years GMC was thought of as “the place you set up Google Shopping ads.” It still does that. But since 2020 it also powers free listings — your products can appear organically, for free, across those same surfaces. That’s the part most SEOs miss.

The big surprise: you might not even need a GMC account for some surfaces

Here’s the thing that trips people up. Since September 2022, you don’t strictly need a Google Merchant Center account to show up in some rich product results like Popular Products. If your product pages have proper Product structured data (schema markup), Google can use that alone to qualify a purchasable page. That said, a GMC account is still required for other surfaces — the Shopping tab is the big one — so “no GMC account” only covers part of the picture.

Google still recommends doing both — structured data on your pages and a Merchant Center feed — because together they give Google the most complete, most up-to-date picture. Evidence for this claim Google recommends combining Merchant Center data with on-page Product structured data. Scope: Using both maximizes eligibility but does not guarantee display. Confidence: high · Verified: 2026-07-14 Google Search: Product structured data But the myth that “you must have GMC for any organic shopping visibility” hasn’t been true for years.

Why an SEO should care

• Free listings are organic traffic. They show up in search, they’re free, and they’re influenced by the same things you already work on — good product pages, accurate data, and structured data.
• The product feed affects eligibility and matching. For those product grids, the quality of your feed (complete attributes, correct product IDs, competitive prices) is a real factor in whether and how well you show up — not just an ad setting.
• There’s a weird tracking parameter to watch. Google adds a tag called srsltid to some product URLs in search. It can make your analytics report this traffic strangely (more on that in the Advanced tab), but Google’s John Mueller has said it doesn’t hurt your crawling, indexing, or ranking.

Want the full technical picture — Offer vs. AggregateOffer, the srsltid fix, the Search Console Merchant Listings report, and how feeds and schema differ? Switch to the Advanced tab.

TL;DR — GMC manages product data across Google’s surfaces and powers free (organic) product listings, not just paid Shopping. Since September 2022, valid Product structured data alone can qualify a purchasable page for merchant listing experiences (Popular Products, etc.) — no GMC account required for that path — though GMC is still required for other surfaces (the Shopping tab, notably), and Google recommends using both feed and schema. Feed quality (GTIN/MPN coverage, complete attributes, title consistency, competitive pricing) affects eligibility and matching for organic product grids, and practitioner analysis associates it with stronger placement — Google hasn’t published this as an official ranking-factor list. Using AggregateOffer instead of Offer on a direct-purchase page blocks merchant listing eligibility. The srsltid parameter Google has appended to organic shopping URLs since August 2024, as reported by industry sources, is linked to GA4 attribution and canonical confusion but — per John Mueller — doesn’t affect crawling, indexing, or ranking; fix it with clean canonicals.

What GMC actually is, and the history that matters

Google Merchant Center is the platform where retailers upload, manage, and optimize product data so products can appear across Google: the Shopping tab, organic Search (Popular Products and product grids), Images, YouTube, Lens, Maps local inventory, and other eligible Google surfaces. Evidence for this claim Merchant Center product data can support unpaid and paid product experiences across eligible Google surfaces. Scope: Current surface coverage is documented by Google and can change. Confidence: high · Verified: 2026-07-14 Google Merchant Center: Free listings

The history is the part that reframes everything for an SEO. GMC started as a paid-Shopping tool. Then in 2020 Google added free product listings (US-first in April as a COVID-era response, then globally in October), and they’re enabled by default for new accounts. So GMC stopped being purely an ads console and became a direct organic-search surface. If you only think of it as “the ads thing,” you’re leaving organic visibility on the table.

Where free listings show up

Free listings aren’t one placement — they span Google’s shopping surfaces:

• Shopping tab (shopping.google.com).
• Organic Search — Popular Products / product grids. These appear on a large share of retail queries and frequently sit at the very top of the page, above the blue links.
• Google Images (product labels were added in 2024).
• YouTube, Lens, and Maps (“In stores nearby” needs a local inventory feed).
• AI surfaces — AI Overviews, AI Mode, and the Gemini app, expanding through 2025–2026.

This is a list of possible placements, not a guarantee — Google names these as eligible marketing surfaces, and where a given product actually shows up still depends on eligibility, market availability, and Google’s own matching for that query.

The September 2022 shift most guides still get wrong

Before September 2022, merchant listing experiences like Popular Products and Shopping knowledge panels required a GMC account with a product feed. After September 2022, Google changed that: a purchasable page can qualify for merchant listing experiences using only Product structured data on the page, with no GMC account at all. Evidence for this claim Product structured data can make purchasable pages eligible for merchant listing experiences without a Merchant Center account. Scope: Eligibility requires compliance with Google requirements and does not guarantee appearance. Confidence: high · Verified: 2026-07-14 Google Search: Product structured data

That schema-only path doesn’t cover every surface, though. Google’s own guidance on sharing product data still lists Merchant Center as a required way to reach some surfaces — the Shopping tab is the clearest example. So “you might not need GMC” is accurate for merchant listing eligibility on your own product pages, but it isn’t the same as full participation across every free-listing surface.

Google announced it plainly: “If you sell products and do not use Google Merchant Center, your products may now show up in more places, in a more rich way, than before.” At the same time, Google split the old combined “Product” report in Search Console into two: a Merchant Listings report and a Product Rich Results report.

This is the single most under-explained fact in GMC content. Most competing guides still write as if a feed is a prerequisite for organic shopping visibility. It isn’t — structured data alone is now a valid path. That said, Google’s official position is to use both: “Providing both structured data on web pages and a Merchant Center feed maximizes your eligibility to experiences and helps Google correctly understand and verify your data.”

Merchant Listings vs. Product Snippets — and the AggregateOffer trap

Google’s product structured data supports two distinct experience families, and the difference is about whether a user can buy on the page:

• Product Snippets — for pages where direct purchase is not possible (editorial reviews, comparison/aggregator pages). Eligibility is broader.
• Merchant Listings — for pages where users can purchase. These unlock the richer displays: apparel sizing, shipping and return details, and Popular Products carousels. Google: “Only pages where a shopper can purchase a product are eligible for merchant listing experiences, not pages with links to other sites that sell the product.”

The eligibility blocker almost nobody mentions: using AggregateOffer instead of Offer in your structured data disqualifies a page from merchant listing experiences. A page that lists multiple sellers with AggregateOffer gets product snippets at best. If it’s a direct-purchase page, it must use Offer. This is one of the most common reasons a product “won’t show in Popular Products” despite otherwise valid markup.

Feed vs. structured data: complementary, not redundant

These aren’t two ways to do the same thing — they have different strengths:

The practical takeaway: structured data mainly drives eligibility; the feed mainly drives freshness and broader surface coverage — that’s a useful generalization, not an absolute split. Google reconciles both sources before deciding eligibility, and neither one guarantees a product will actually appear. Use both, keep them consistent, and treat mismatches between them as something to reconcile rather than ignore — which is also Google’s recommendation.

Feed quality: eligibility, matching, and practitioner-observed placement

For Popular Products grids, the feed isn’t just plumbing for ads — its completeness and quality affect eligibility and matching, and practitioner analysis ties it to where you place. Google’s own documentation supports the eligibility and data-quality recommendations below; it doesn’t publish this exact list as a formal ranking-factor specification. From Brodie Clark’s analysis of organic product grids, the recurring factors practitioners observe are:

1. Valid items / eligibility — pass all merchant listing requirements.
2. Grid type match — Popular Products vs. Deals vs. Fast Pickup, etc.
3. Exact product match via GTIN/MPN — strongly preferred (and required for exact match in some grids).
4. Comprehensive attributes — fill the optional fields, not just the required ones.
5. Title consistency across the feed, the product page, and the title tag.
6. Aggregated reviews / ratings from multiple sources.
7. Competitive pricing, shipping, and return policy.

Merchant-level trust signals matter too, roughly in order of leverage: the Top Quality Store badge, seller ratings, promotions/coupons, and Google Pay acceptance. The blunt implication: the SEO team should own — or at least co-own — feed quality. It’s SEO work that happens to live in an ads tool.

The srsltid parameter: the 2024 attribution and canonical problem

As reported by industry sources (Search Engine Land and others), srsltid started in February 2022 for paid Shopping attribution via auto-tagging, and the SEO-relevant change came in August 2024, when Google expanded it to organic shopping results — so organic product impressions can now generate URLs carrying a unique srsltid value. The exact rollout dates and the following list come from that practitioner reporting rather than a first-party Google changelog, so treat them as well-sourced but not Google-confirmed. The reported headaches:

1. Organic clicks get credited to a “Organic Shopping” channel in GA4 instead of “Organic Search.”
2. Users sharing srsltid-tagged URLs can pollute backlink signals.
3. It runs against Google’s own long-standing advice to avoid session-specific URL parameters.
4. It creates URL variants that can complicate rel=canonical.
5. Merchants have limited direct control over it.
6. It was a rare case of a non-Search team modifying organic result URLs.

The reassuring part is straight from Google. John Mueller said of the parameter that “it doesn’t affect crawling, indexation or ranking,” and suggested disabling auto-tagging in GMC to reduce the attribution mess, calling that “useful.”

The fix: make sure every product page has a correctly formed canonical tag pointing to the clean URL, so the srsltid variants consolidate. Optionally disable GMC auto-tagging if the analytics noise outweighs the attribution you get from it.

Search Console and GA4 reporting

Not all of these numbers come from the same kind of source, and it’s worth knowing which is which before you act on them:

• Search Console — Merchant Listings. Google split the old combined “Product Results” filter (late 2024) into Product Snippets and Merchant Listings, so you can finally track free-listing performance — impressions, clicks, and queries — separately, for your own property. Find it under Search Results, filter by Search Type → Shopping.
• GA4 attribution. Free-listing traffic arrives as source google / medium organic. When srsltid is present, GA4’s default channel grouping is reported to file it under “Organic Shopping” rather than “Organic Search” — confirm this against your own GA4 channel configuration and a sample of tagged sessions rather than assuming it applies unchanged to every property.

2026 and the AI frontier

Google is steadily turning GMC into the control panel for AI shopping visibility:

• AI Performance Insights (launched May 2026) — a GMC report tracking brand performance across AI surfaces: share of voice in AI Mode / AI Overviews / Gemini, a Discovery → Evaluation → Purchase funnel, product-term insights, and an Attribute Completeness Score that flags what’s missing and hurting AI visibility.
• Conversational Attributes — natural-language product descriptions in GMC tuned for AI Mode and conversational shopping queries.
• AI Product Import (beta) — Google AI scans your site to auto-populate the feed.
• Universal Cart / agentic commerce — a cart spanning Search and Gemini, plus the Agent Payments Protocol for agentic transactions.

The through-line for SEOs: attribute completeness is becoming the new technical SEO for AI shopping. The same feed discipline that wins Popular Products is what feeds AI shopping answers.

How GMC fits the ecommerce SEO stack

Think of GMC as the missing piece many ecommerce SEO programs leave to the ads team. It connects directly to the work you already do — ecommerce site architecture, product and category pages, and schema markup. And it depends on the basics of how Google crawls and processes your product pages in the first place. Own the feed and the structured data together, and you own organic shopping visibility end to end.

AI summary

A condensed take on the Advanced version:

• GMC = product data across Google’s surfaces, and it powers free (organic) listings, not just paid Shopping. Free listings are on by default and span possible placements on the Shopping tab, organic Popular Products grids, Images, Lens, Maps, and AI surfaces — subject to eligibility and market availability.
• Sept 2022 shift: valid Product structured data alone can qualify a purchasable page for merchant listing experiences — no GMC account required for that path — but GMC is still required for some surfaces (the Shopping tab), and Google recommends using both feed and schema.
• Merchant Listings vs. Product Snippets: merchant listings need a purchasable page; snippets cover any product page. Using AggregateOffer instead of Offer on a direct-purchase page blocks merchant listing eligibility.
• Feed vs. schema: schema gives eligibility but lags the crawl; the feed is near-real-time and covers more surfaces (Shopping tab, local, ads, AI). Google reconciles both before deciding eligibility, and neither guarantees display.
• Feed quality affects eligibility and matching for product grids: GTIN/MPN match, complete attributes, title consistency (feed = page = title tag), reviews, and competitive pricing — plus merchant trust signals like the Top Quality Store badge. Practitioner analysis (Brodie Clark) ties these to placement; Google hasn’t published this exact list as an official ranking-factor specification.
• srsltid (reported on organic shopping URLs since Aug 2024, per industry sources) is linked to GA4 “Organic Shopping” misattribution and canonical confusion, but per John Mueller doesn’t affect crawling/indexing/ranking. Fix with clean canonicals; optionally disable auto-tagging.
• Reporting: Search Console split Merchant Listings from Product Snippets; filter Search Type → Shopping.
• 2026 AI: AI Performance Insights, Conversational Attributes, and an Attribute Completeness Score make feed completeness the new technical SEO for AI shopping.

Official documentation

Primary-source documentation from Google.

Google Merchant Center / Shopping

• Free listings on Google (Merchant Center Help) — what free product listings are and how they help product pages appear in results.

Google Search Central — structured data

• Product structured data — the overview of Product markup, including Google’s recommendation to use both structured data and a Merchant Center feed.
• Merchant listing (Product) structured data — the requirements for merchant listing experiences, and why only purchasable pages qualify.

Google Search Central — blog

• New ways to reach more shoppers, plus new Search Console reports (Sept 2022) — the announcement that Product structured data alone can qualify for merchant listing experiences, and the new Merchant Listings / Product Snippets reports.

Quotes from the source

On-the-record statements from Google. Where possible each link is a deep link that jumps to the quoted passage on the source page.

Google — free listings

• “Free listings for products help your product pages appear in search results, not other pages.” — Google Merchant Center Help. Jump to quote

Google — the September 2022 eligibility shift

• “If you sell products and do not use Google Merchant Center, your products may now show up in more places, in a more rich way, than before.” — Google Search Central Blog. Jump to quote

Google — use both structured data and a feed

• “Providing both structured data on web pages and a Merchant Center feed maximizes your eligibility to experiences and helps Google correctly understand and verify your data.” — Google Search Central docs. Jump to quote

Google — merchant listings require a purchasable page

• “Only pages where a shopper can purchase a product are eligible for merchant listing experiences, not pages with links to other sites that sell the product.” — Google Search Central docs. Jump to quote

John Mueller, Google — on the srsltid parameter (2024)

• “It doesn’t affect crawling, indexation or ranking.” Mueller also suggested disabling auto-tagging in Merchant Center to mitigate attribution issues, calling it “useful.” — via Search Engine Land. Read the coverage

GMC + free-listings setup checklist

• Merchant Center account created and the business/website verified and claimed.
• Free product listings confirmed enabled (on by default, but verify).
• Product feed submitted (Merchant API, scheduled fetch, Sheets, or a feed file/app — Content API is the legacy name for what’s now the Merchant API).
• Required attributes present: id, title, link, image_link, price, description, availability (plus condition for used/refurbished).
• gtin or mpn populated wherever they exist (needed for exact-match grids).
• Shipping configured (mandatory in many countries, including US/UK/CA/AU).
• No disapprovals or policy issues sitting in the Merchant Center diagnostics.

SEO optimization checklist

• Product structured data implemented on every product page (so you qualify even without a feed, per the Sept 2022 change).
• Using Offer — not AggregateOffer — on direct-purchase pages.
• Title consistency audited across feed, product page H1, and title tag.
• All relevant optional attributes filled, not just required ones.
• Aggregated reviews/ratings wired up where available.
• Pricing, shipping, and return policy reviewed for competitiveness.
• Canonical tags correct on all product pages (the srsltid fix).
• GSC → Merchant Listings report checked for errors and query/impression data (Search Type → Shopping).
• GA4 channel grouping understood: free listings land in “Organic Shopping” when srsltid is present.
• Apparel attributes (size, color, gender, age group) complete for apparel feeds.

GMC as an SEO asset — the mental models

1. The feed is an SEO surface, not an ads setting. Free listings are organic. Feed completeness, attribute quality, title consistency, and competitive pricing affect eligibility and matching for product grids — and practitioner analysis ties them to placement — the same kind of work you already do for product pages, just expressed in feed fields. If the ads team “owns the feed,” SEO still owns feed SEO.

2. Eligibility vs. freshness — two jobs, two tools. Structured data gets you eligible for merchant listing experiences (and, since Sept 2022, can do it without a GMC account). The feed keeps price/availability fresh and covers more surfaces (Shopping tab, local inventory, ads, AI). Don’t pick one — they do different jobs. Google recommends both.

3. Offer vs. AggregateOffer is a gate, not a detail. On a page where a shopper can buy, Offer keeps you eligible for merchant listings; AggregateOffer demotes you to product snippets at best. Treat the Offer type as a pass/fail eligibility check, not a cosmetic schema choice.

4. srsltid is an analytics problem, not a ranking problem. Mueller is clear it doesn’t touch crawling, indexing, or ranking. So solve it where it actually hurts — reporting and canonicals — with clean canonical tags and (optionally) turning off auto-tagging. Don’t over-engineer a “ranking fix” for something that doesn’t affect rankings.

5. The audit order that finds problems fastest. Eligibility (Offer type + required attributes) → exact match (GTIN/MPN) → consistency (feed = page = title tag) → completeness (optional attributes) → competitiveness (price/shipping/returns) → trust (badges/ratings) → reporting (GSC Merchant Listings + GA4 channel). Work top-down; the early items block everything below them.

6. Feed completeness is becoming AI-shopping SEO. The Attribute Completeness Score and conversational attributes in GMC mean the same feed discipline that wins Popular Products is what feeds AI Mode and Gemini shopping answers. Optimizing the feed is future-proofing for AI surfaces.

Google Merchant Center — quick reference

Structured data vs. feed — when each matters

Merchant Listings vs. Product Snippets

Free-listing eligibility — core attributes

• Required: id, title, link, image_link, price, description, availability.
• condition for used/refurbished items.
• gtin / mpn strongly preferred (needed for exact-match grids).
• shipping mandatory in many countries (US, UK, CA, AU, and 25+ more).

Fast facts

• Free listings: added 2020, on by default for new accounts.
• Schema-only eligibility for merchant listings: since Sept 2022.
• srsltid on organic shopping URLs: since Aug 2024; per Mueller, no effect on crawling/indexing/ranking. Fix with clean canonicals.
• GA4 channel for free listings with srsltid: “Organic Shopping” (not Organic Search).
• GSC: Merchant Listings split from Product Snippets (late 2024); Search Type → Shopping.

Which product-data path should you use?

How should you handle srsltid?

Merchant Center mistakes that block organic shopping

Treating the feed as an ads-only asset

Why it fails: Free listings and organic product grids use the same product data. Leaving feed quality entirely outside SEO creates gaps in titles, identifiers, attributes, pricing, and reporting.

Do this instead: Co-own feed quality across SEO, merchandising, and paid media, with one definition of the product and its offer.

Assuming a feed is the only eligibility path

Why it fails: Product structured data alone can qualify pages for merchant listing experiences since September 2022.

Do this instead: Implement accurate on-page Product markup even when a feed exists; use both because they solve eligibility, freshness, and coverage differently.

Using AggregateOffer on a direct-purchase page

Why it fails: AggregateOffer describes a collection of offers and blocks the page from purchase-focused Merchant Listing eligibility.

Do this instead: Use an accurate Offer for the product a shopper can buy on the page, with price, currency, and availability matching the visible offer.

Letting the feed and page disagree

Why it fails: Price, availability, title, or identifier mismatches undermine Google’s ability to verify the item and can create disapprovals.

Do this instead: Reconcile feed, structured data, visible landing page, and checkout for the same SKU and market as one release check.

Treating srsltid as a ranking penalty

Why it fails: It directs effort toward a ranking fix for a parameter Google says does not affect crawling, indexing, or ranking.

Do this instead: Solve the actual concerns with clean canonicals, an explicit GA4 Organic Shopping view, and an informed auto-tagging choice.

Stopping at required attributes

Why it fails: Bare eligibility does not create strong matching. Optional product attributes, exact identifiers, reviews, shipping, returns, and competitive offers add the context organic shopping surfaces use.

Do this instead: Work from eligibility to exact match, consistency, completeness, competitiveness, and trust — in that order.

Prove the Merchant Center implementation works

Merchant Listing eligibility test

Test to run: Run a direct-purchase product URL through the Rich Results Test and inspect the Product object and offer type.

Expected result: The page is eligible for merchant listing experiences and emits one valid Offer whose price, currency, and availability match the visible page.

Failure interpretation: The page may use AggregateOffer, omit a required field, inject markup too late, or describe a different offer.

Monitoring window: Immediate after structured-data or product-template changes, then after Google recrawls for Search Console reporting.

Rollback trigger: A template release removes Merchant Listing eligibility or creates product-data mismatches across a material SKU set.

Feed-to-page parity test

Test to run: Sample products across markets and compare Merchant Center item data with the landing page, structured data, and checkout for title, identifier, price, currency, and availability.

Expected result: All four representations describe the same current offer.

Failure interpretation: A stale feed, cache, market/currency mapping, or product source is out of sync.

Monitoring window: After every feed/template release and continuously for price/availability changes.

Rollback trigger: Shoppers or Google receive a different price or availability from the submitted item data.

Clean-canonical parameter test

Test to run: Open a product URL with an srsltid value and inspect the rendered and raw canonical.

Expected result: The canonical points to the clean product URL without the tracking parameter, and the clean URL returns 200.

Failure interpretation: The canonical is missing, self-canonicalizes the tracking variant, or points to a different product.

Monitoring window: Immediate after canonical or routing changes.

Rollback trigger: Parameterized URLs begin declaring themselves canonical or the canonical release affects clean product pages.

Reporting-path test

Test to run: Verify the same test product appears in GSC Merchant Listings and that a tagged click is classified according to the documented GA4 channel setup.

Expected result: GSC exposes shopping performance/eligibility, while GA4 records the visit in the expected Organic Shopping or intentionally customized channel.

Failure interpretation: The property/filter is wrong, processing is incomplete, or the analytics channel definition changed.

Monitoring window: After the normal processing delay for each platform and after analytics configuration changes.

Rollback trigger: A reporting change silently removes organic shopping from the business’s organic totals or duplicates it across channels.

Resources worth your time

My writing

• This is a new topic area for me, so the closest companions on this site are the Ecommerce SEO pillar (architecture, category and product pages, faceted nav) and schema markup for AI — GMC sits right where those two meet.

My speaking

• My How Search Works walkthrough (SlideShare) covers the crawl → render → index → serve pipeline that every product page — fed by GMC or by structured data — still has to pass through.

From around the industry

• Merchant Listings (Brodie Clark) — the best technical deep-dive on the GSC Merchant Listings report.
• Google Organic Product Grids (Brodie Clark) — the ranking factors behind Popular Products grids.
• Google’s srsltid parameter and SEO attribution (Search Engine Land) — the srsltid analysis plus Mueller’s statement.
• Google expands enhanced product experiences + new Search Console reports (Search Engine Land) — coverage of the Sept 2022 eligibility shift.
• Ecommerce product structured data (iPullRank) — structured-data implementation, including the shipping-from-feed behavior.
• How to audit Google Merchant Center feeds (Uproer) — a practical feed-audit framing for SEOs.

Test yourself: Google Merchant Center

Five quick questions on GMC, free listings, and the SEO angle. Pick an answer for each, then check.

Google Merchant Center

Google Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads.

Related: Ecommerce SEO, Schema Markup for AI

Google Merchant Center

Google Merchant Center is the platform where retailers upload, manage, and optimize product data so those products can appear across Google’s surfaces — the Shopping tab, organic Search (Popular Products and product grids), Images, Lens, Maps local inventory, and increasingly AI Overviews, AI Mode, and the Gemini app. It’s long been associated with paid Shopping ads, but since 2020 it also powers free product listings, which makes it a direct organic-search tool, not just an ads console.

Two things make GMC matter to SEOs specifically. First, since September 2022 you no longer need a GMC account to qualify for merchant listing experiences like Popular Products — valid Product structured data on your pages can be enough on its own (Google still recommends using both the feed and structured data). Second, the srsltid parameter Google began appending to organic shopping result URLs in August 2024 creates GA4 attribution and canonical headaches that land on the SEO team’s desk, even though John Mueller has confirmed it doesn’t affect crawling, indexing, or ranking.

Related: Ecommerce SEO, Schema Markup for AI

Changelog