CSS: FAQs and myths
Straight answers to the most common questions and misconceptions about Comparison Shopping Services, ranking, whether you leave Google Shopping, coverage outside Europe, campaign disruption, cost, and running multiple CSSs.
A CSS changes what you pay per click, roughly 20% less, and nothing else. It doesn't change your ranking, it doesn't take you off Google Shopping, and it doesn't disrupt your campaigns or Merchant Center. This page clears up the misconceptions merchants worry about most before switching on RPCSS.
How to read this page
Most hesitation about CSS comes from a handful of myths, usually the product of how CSS was sold in the agency era. The truth is simpler than the sales pitch: a CSS changes what you pay per click and nothing else. Below are the questions merchants ask most, answered plainly.
If you want the underlying mechanics first, start with What a CSS is, and the ~20% CPC saving. When you're ready to switch it on, see Activating RPCSS.
Deep dive The "cheaper clicks, not more traffic" distinction
The most useful mental model is this: a CSS is a discount on the price of each click, not a lever on how much traffic you get.
It's tempting to hear "20% saving" and assume it means 20% more visibility or more sales: but a CSS doesn't touch the auction that decides those things. What it does is remove a margin from the cost of the clicks you were already winning. So the honest framing is cheaper clicks, not more of them.
Where that turns into more sales is indirect but real. If you hold your budget flat, a 20% lower CPC buys you more clicks within the same spend, which can mean more conversions. And if you run a target-ROAS strategy, cheaper clicks improve your return on ad spend directly, which can give your bidding room to compete for auctions it previously couldn't afford. Either way the mechanism is the CPC saving: not a change to ranking or coverage. See target ROAS explained for how the saving flows through automated bidding.
Still unsure?
The safest way to settle any lingering doubt is to activate RPCSS, wait a few days, and compare your average CPC for the same positions before and after. Because there's no migration and you can switch back at any time, the test costs you nothing but a few days. See Activating RPCSS.
Frequently asked questions
Does a CSS change my ranking or how many products show?
No, this is the single biggest misconception. Ad rank, auction position and which products appear are all decided by the same Shopping auction, and a CSS doesn't influence any of it. The only thing that changes is your cost-per-click, which drops by roughly 20% for the same position. If someone promises a CSS will lift your ranking or show more products, they're describing something a CSS can't do.
Do I leave Google Shopping if I switch CSS?
No. Your ads still appear in exactly the same Google Shopping placements, to the same shoppers, looking identical. "Google Shopping" is simply Google's own CSS, every Shopping ad already runs through some CSS. Moving to RPCSS changes which service places the ad, not where the ad shows.
Does CSS work outside Europe, for example in the US?
No, and it's worth understanding why. CSS exists because of an EU antitrust remedy, so it only applies in the European Economic Area, the UK and Switzerland. In those markets Google removes the margin it takes on its own placements when a rival CSS places the ad, that's the saving. Outside that zone there's no such margin to remove, so the saving simply doesn't arise. It isn't lost; it just doesn't exist there.
Will activating a CSS disrupt my campaigns or Merchant Center?
No. Your campaigns keep running without interruption, and you keep the same Merchant Center account and feed. Activation links the CSS to the account you already own, there's no migration, no rebuild, no downtime and no loss of history or approvals. You can also switch back at any time with the same continuity.
Is CSS really included free with my /tools plan?
Yes. RPCSS is included for every paying subscriber at no extra cost, it's part of the £89/month per-store subscription. There's no separate CSS contract, no agency fee and no per-click surcharge. You activate it in-app in a couple of clicks.
Can I run more than one CSS at the same time?
In practice you place your Shopping ads through one CSS at a time, and RPCSS is designed to be that CSS for /tools merchants, activated in-app with no agency. Trying to juggle multiple CSSs adds complexity without adding saving, since the ~20% CPC reduction comes from placing through an independent CSS, not from stacking several. Keep it simple, one CSS, cheaper clicks.
If the saving is real, why isn't everyone already using a CSS?
Mostly because the old route was painful, a separate agency contract, a Merchant Center migration and real risk of breaking a working setup. Plenty of merchants decided the hassle wasn't worth it. /tools removes the hassle, RPCSS is built in, activates in a couple of clicks, and carries no migration risk, so the saving is there for the taking.
Does the CPC saving mean lower-quality or fewer clicks?
No. It's the same clicks from the same shoppers in the same auction, you simply pay less for each one. Nothing about the traffic changes; only its price does.