How to Become a Google CSS Partner

Becoming a Google CSS Partner can help an agency build a recurring service around Google Shopping, strengthen its brand and support merchants across European markets. However, launching a Comparison Shopping Service directly requires much more than registering a domain or connecting several Merchant Center accounts.

This guide explains how the Google CSS programme works, what requirements you must meet, how the approval process looks and when a White Label CSS solution is the more practical route.

What is a Google CSS?

CSS stands for Comparison Shopping Service. It is a website that collects product offers from multiple online retailers, allows users to search and compare products, and redirects them to a merchant’s website to complete a purchase.

In countries covered by the European Google CSS programme, Shopping ads and free product listings are placed on behalf of merchants through a Comparison Shopping Service. Google Shopping is one CSS, but merchants can also work with independent providers.

When a merchant uses an independent CSS, the name of that service can appear in the “By” field displayed alongside eligible product ads. For agencies, this creates an opportunity to offer a branded Google Shopping service to multiple e-commerce clients.

Operating a CSS and becoming a Google CSS Partner are not the same

One of the most common sources of confusion is the difference between participating in the CSS programme and earning Google CSS Partner status.

CSS programme participation

The first stage is operating an approved Comparison Shopping Service. This requires a functional comparison website, the necessary business registration, product offers from multiple merchants and compliance with Google’s technical and policy requirements.

Google CSS Partner status

The Google CSS Partners programme has separate participation levels. According to the official programme criteria, the Partner tier requires, among other conditions:

• an approved CSS account;
• access to the CSS Education Hub;
• at least 50 merchants running active Shopping Ads campaigns;
• at least one Shopping ad impression for each qualifying merchant within the last 30 days;
• placement among the leading CSS providers based on Shopping ad impression volume.

The Premium Partner tier has additional volume and cooperation requirements. It is reserved for the highest-performing CSS providers and requires ongoing strategic engagement with Google.

This distinction matters because launching an approved CSS does not automatically guarantee the Google CSS Partner badge. The badge depends on the current Partner programme criteria and the performance of the CSS account.

Google CSS programme requirements

Google publishes minimum requirements for businesses that want to participate in the Comparison Shopping Services programme. Meeting them requires a genuine product comparison platform rather than a simple landing page.

1. Business registration in an eligible country

Your company must be registered in at least one country where the CSS programme is available. Your website must show a business address corresponding to that registration.

Company information should be easy to find and consistent across your website, legal documents and application details.

2. A functional comparison shopping website

Your website must allow users to search for and compare products offered by different merchants. It cannot exist only to redirect visitors to Google Shopping ads or present your agency’s services.

The platform should provide:

• individual product offers with prices and relevant selling conditions;
• merchant information and direct links to product pages;
• search, sorting and filtering functions;
• public access without mandatory registration;
• useful results that help shoppers compare available offers.

3. At least 50 merchant domains per target country

The comparison website must display products from at least 50 distinct merchant domains for every country in which the CSS wants to participate.

These cannot be arbitrary stores added only to increase the number. The merchants must sell and deliver products to consumers in the relevant target country.

If you want to operate in Germany, the website must therefore contain eligible offers from at least 50 merchants delivering to Germany. Expanding into another country requires satisfying the programme requirements for that market as well.

4. Useful product search

The website must include its own product search functionality. Results should be created primarily through a dynamic and automated process and should help users find relevant products without having to repeat the search elsewhere.

The search function cannot be substantially based on search technology licensed or syndicated from Google.

5. Sorting and filtering options

Visitors must be able to sort or filter product results by price and at least one other useful dimension. Depending on the category, this could include brand, merchant, availability, shipping time, size or colour.

6. Direct access to merchant product pages

Product offers must direct users to a page where they can purchase the advertised item. Links should lead to relevant merchant landing pages rather than unrelated categories, homepages or intermediate pages without a clear purchase path.

7. Accurate and regularly updated product data

Prices, availability, product titles and landing pages need to remain accurate. This requires a reliable system for collecting, validating and refreshing product feeds from multiple stores.

The platform must also be able to handle rejected products, broken landing pages, missing identifiers, price mismatches and other Merchant Center issues.

8. Compliance with Google policies

The CSS, its merchants and submitted product data must comply with the applicable Google Shopping policies and product data requirements. Google does not allow misleading information about products, services or businesses.

The complete minimum requirements are available in the official Google CSS programme documentation.

How to become a Google CSS: step by step

1. Define your business model. Decide whether you will charge a monthly fee, sell a managed service, use a performance model or offer CSS under an agency brand.
2. Choose your initial markets. Starting with one or several commercially important countries makes merchant coverage and localisation easier to control.
3. Register and prepare the CSS domain. Add complete business information, legal pages, contact details and a clear explanation of how the service works.
4. Build the comparison platform. The system needs feed imports, categorisation, product search, filtering, price updates and merchant redirects.
5. Add eligible merchant offers. Collect current product data from at least 50 qualifying merchant domains for every target market.
6. Test the shopping experience. Users should be able to search, compare, filter and open the correct product page without registration.
7. Apply for the Google CSS programme. Google may review the business, website functionality, merchant coverage, product data and policy compliance.
8. Configure CSS Center and Merchant Center. After approval, organise the merchant accounts assigned to the CSS and establish an onboarding process.
9. Build eligibility for Partner status. Grow an active merchant portfolio, Shopping ad volume and the operational capacity required by the current Partner criteria.

Technology typically required

• merchant feed imports through XML, CSV or API connections;
• product categorisation and offer matching;
• price and availability updates;
• product search, sorting and filters;
• merchant landing-page redirects;
• error monitoring and feed diagnostics;
• multi-country and multi-language support;
• Merchant Center account administration.

Current tier requirements can be checked on the Google Comparison Shopping Partners portal.

How much does it cost to build your own Google CSS?

Google does not charge one universal setup price for creating an independent CSS. The main costs come from developing and operating the necessary infrastructure.

These costs may include:

• comparison website development and hosting;
• product feed imports and ongoing updates;
• merchant onboarding and Merchant Center administration;
• product data validation and error monitoring;
• multi-country localisation;
• legal and compliance support;
• customer service and technical maintenance;
• ongoing development when programme requirements change.

The greatest cost is often not the first version of the website but its continuous operation. Product feeds change, merchants update their catalogues, landing pages disappear and prices become outdated. A CSS must monitor and process these changes at scale.

The White Label CSS alternative

For many agencies, building a complete comparison platform is not commercially justified. They want their own CSS brand and a recurring service for clients, but they do not want to develop feed infrastructure, comparison technology and Merchant Center administration internally.

A White Label CSS provides an alternative. The agency launches a branded Comparison Shopping Service using infrastructure operated by an existing technology provider.

What can the White Label provider handle?

• comparison website technology and hosting;
• product feed imports and platform maintenance;
• domain and CSS configuration;
• Google programme onboarding;
• Merchant Center migration;
• technical compliance and operational support.

What remains under the agency’s control?

• the CSS brand and client-facing offer;
• the client relationship and communication;
• the monthly resale price and commercial margin;
• Google Ads campaign management;
• reporting and the broader agency service.

Building your own CSS vs using White Label CSS

Building an independent CSS makes sense when the organisation wants to own the entire technology stack and has the merchant volume, budget and internal resources to maintain it.

White Label CSS is usually more practical when the primary objective is to offer the service under your own brand, improve client retention and create recurring agency revenue without building the infrastructure internally.

Where is the Google CSS programme available?

The Google CSS programme is available in 21 European markets:

• Austria, Belgium, Czech Republic, Denmark and Finland;
• France, Germany, Greece, Hungary and Ireland;
• Italy, the Netherlands, Norway, Poland and Portugal;
• Romania, Slovakia, Spain, Sweden, Switzerland and the United Kingdom.

An agency does not have to enter all markets immediately. Starting with one or several commercially important countries makes it easier to control merchant coverage, localisation and product data quality.

Is becoming a Google CSS Partner worth it for an agency?

It can be valuable when the agency manages a growing portfolio of e-commerce clients and wants to create an additional service around Google Shopping.

Potential business benefits include:

• a recurring subscription or management fee;
• stronger client retention and a more distinctive PPC offer;
• greater control over the Google Shopping setup;
• the agency’s CSS brand displayed alongside eligible product ads;
• the ability to support clients across multiple European markets.

However, becoming an independent CSS is not simply another Google Ads certification. It means operating a real comparison shopping platform and maintaining the technology, merchant portfolio and product data required by the programme.

Agencies that want the commercial benefits without building a separate technology company should consider the White Label model.

Frequently asked questions

Can a marketing agency become a Google CSS?

Yes. A marketing or PPC agency can operate a CSS if its company and comparison website meet the programme requirements. The agency must operate a genuine comparison service rather than only a page advertising Google Shopping management.

How many merchants do I need to start a CSS?

Google requires the comparison website to display products from at least 50 distinct merchant domains for every country in which the CSS wants to participate. The merchants must deliver products to consumers in that country.

How many active merchants are required for the Google CSS Partner badge?

The Partner and Premium Partner tiers currently require at least 50 merchants running active Shopping Ads campaigns. Each qualifying merchant must have generated at least one Shopping ad impression within the previous 30 days. Other impression-volume criteria also apply.

Can I become a CSS with only five client stores?

Five client stores do not satisfy Google’s direct requirement of at least 50 distinct merchant domains per target country. However, some White Label providers can support smaller agencies through existing infrastructure and a wider merchant portfolio. The exact structure should be confirmed before launch.

Does White Label CSS make my agency an official Google CSS Partner?

It can provide a branded CSS environment and access to approved infrastructure, but the official Partner tier and badge depend on Google’s current criteria and the structure and performance of the relevant CSS account.

Can merchants work with more than one CSS?

Yes. A merchant can work with multiple Comparison Shopping Services. The preferred structure depends on the merchant’s campaigns, markets and commercial agreements with each provider.

Will changing CSS remove Google Ads campaign history?

Switching the CSS associated with a Merchant Center account does not normally require rebuilding existing Google Ads campaigns. Campaign history and optimisation data remain connected to the advertising account, although every migration should be planned and verified carefully.

Is the Google CSS programme available in the United States?

The European CSS programme described in this guide applies to the 21 supported European markets listed above. The same programme requirements and auction model do not apply to the United States.

How long does it take to become a Google CSS?

There is no single guaranteed timeline. It depends on the readiness of the comparison website, merchant coverage, product data quality and any corrections required during Google’s review. Building the infrastructure from scratch can take considerably longer than launching through an existing White Label CSS platform.

What is White Label CSS in Google Ads?

White Label CSS is a price comparison service operating within the Google CSS (Comparison Shopping Service) programme under an agency’s or retailer’s own brand instead of the default “By Google” label. It enables product ads to run in Google Shopping with a lower cost per click and the agency’s branding displayed alongside each client’s ads. To avoid confusion from the outset, this is not about white-labelling an application interface with CSS as in Cascading Style Sheets. This guide focuses exclusively on Google CSS as an advertising channel, explaining how the mechanism works, when it makes financial sense and when it does not.

A White Label CSS is a price comparison service owned by an agency or retailer and approved within the Google CSS programme. Instead of the default “By Google” label beneath a Shopping ad, the name of the comparison service owner appears, while the cost per click can decrease. The entire mechanism operates through Google Ads and Google Merchant Center, not through a website’s source code.

• Your own comparison service within the Google CSS programme, with your brand shown on ads instead of “By Google”.
• A Comparison Shopping Service, meaning an advertising channel rather than interface white-labelling with CSS variables.
• A solution primarily for PPC agencies and e-commerce retailers running product campaigns in Google Shopping.

White Label CSS and Cascading Style Sheets: two different meanings of “CSS”

The abbreviation “CSS” has two meanings, and search engines often mix them together. The first is Cascading Style Sheets, which developers use to control the appearance and branding of websites and applications. The second is Comparison Shopping Service, Google’s programme for price comparison services. White Label CSS in this article refers exclusively to the second meaning.

The distinction has practical consequences. When you want to change colours and logos in a SaaS dashboard, you need a developer and CSS variables. When you want lower-cost clicks in Google Shopping and your own brand displayed on product ads, you need the Google CSS programme. These are two separate concepts connected only by the same three-letter abbreviation.

Who is White Label CSS for?

PPC agencies managing multiple e-commerce clients usually gain the greatest value from White Label CSS. An agency launches one comparison service under its own domain and connects the Merchant Center accounts of all participating clients. As a result, the agency’s name can appear on thousands of product ads, while every connected client benefits from a lower CPC.

The second group consists of individual e-commerce retailers, which more often choose Branded CSS using their own store brand. Freelancers and affiliates can also participate, provided they manage a sufficient number of shops. The common requirement is simple: you must be running product campaigns in Google Shopping, otherwise the comparison service has nothing to support.

Consider an agency with ten e-commerce clients. It connects every account to one comparison service, reduces CPC for each client from day one and displays its own brand across all of their product ads. Previously separate accounts become one shared commercial asset for the agency.

The “By” field: where the CSS brand appears

Every product ad in Google Shopping includes a small “By” label identifying the comparison service through which the ad entered the auction. By default, it reads “By Google”. After implementing your own comparison service, your brand appears in this position, for example “By Your Agency”.

The field serves two purposes. First, it builds recognition because the owner’s name appears alongside every client ad. Second, it can generate free traffic: clicking the “By” link takes the user to the comparison service rather than the retailer, and that click is not charged. With White Label CSS, the field becomes a piece of advertising inventory controlled by your agency.

White Label CSS vs Branded CSS vs default Google CSS

The Google CSS programme supports three main models. They differ in who owns the comparison service and who retains the margin associated with the cost per click. The default “By Google” model leaves that margin with Google. Branded CSS belongs to a retailer and displays the retailer’s brand on its own ads. White Label CSS belongs to an agency, whose brand can appear on the product ads of all connected clients. The selected model determines which name appears in the “By” field.

• Default Google CSS uses the “By Google” label and provides no CPC advantage over the default route.
• Branded CSS displays the retailer’s brand on its own ads and is an asset owned by the e-commerce business.
• White Label CSS displays the agency’s brand on its clients’ ads and is an asset controlled by the agency.

Comparison of the three models

The differences are easiest to understand in one table. The ads themselves do not change. What changes is who owns the comparison service and who captures the benefit of the lower CPC.

The default option is the starting point for every account. Moving to Branded CSS or White Label CSS unlocks the CPC advantage and proprietary branding in Google Shopping. Product ads look the same in every model; only the “By” label and the beneficiary of the click-cost saving change.

When should you choose Branded CSS and when White Label CSS?

The decision depends on the structure of the business. When you operate one store and want to strengthen your own brand on your own ads, Branded CSS is the natural choice. It is generally easier and less expensive to maintain, and your store appears twice in the ad: in the product listing and in the “By” field.

When you manage product campaigns for multiple clients, White Label CSS offers a stronger advantage. One comparison service can support every account, while the agency’s brand gains visibility alongside each client’s ads. White Label CSS then becomes not only a way to reduce CPC, but also a marketing tool for the agency itself. The dividing line is not absolute, but the more stores an agency manages, the stronger the case for the white-label model. In practice, agencies with five or more active e-commerce clients often choose White Label CSS because the cost of the comparison service is distributed across multiple accounts.

How White Label CSS lowers the cost per click in Google Shopping

When product ads run through your own comparison service instead of the default Google CSS route, you avoid the additional margin Google applies to the click cost. This difference is the core value of White Label CSS. Comparison service providers commonly claim CPC reductions of up to around 20%, which means that the same budget can win more auctions, generate more impressions and drive more sales through Google Shopping.

• The mechanism: your own comparison service removes Google’s additional margin from each click.
• The stated scale: CSS providers commonly report CPC reductions of up to around 20%.
• The business effect: the same media budget can purchase more clicks and therefore create more conversion opportunities.

Where the CPC advantage comes from

When a Shopping ad enters the auction through the default route, Google adds its own margin to the bid. The final click can therefore cost more than the amount created solely by competition between advertisers. A proprietary comparison service in the Google CSS programme allows that margin to be recovered and used in the auction instead.

The effect is mathematical. If the Google margin increased click costs by several or more percentage points, removing it reduces CPC by a similar amount. Some providers claim benefits of up to 25%, while others refer to approximately 20%. With a fixed budget, a lower CPC translates directly into more traffic. A budget that previously purchased one thousand visits can purchase substantially more after the click cost decreases. This mechanism underpins the White Label CSS market.

Free traffic from the “By” field

The second benefit concerns traffic rather than bids. Clicking the “By” link below an ad takes the user to the comparison service instead of the retailer and does not trigger a paid ad click. With White Label CSS, that traffic reaches your own domain rather than an external intermediary.

For an agency, this creates a free brand-awareness channel. Every client ad becomes a carrier of the agency’s name, and some users click the label and land on its comparison service. The scale depends on campaign volume, but the traffic itself is not charged because Google does not count these interactions as paid clicks.

Evidence from Double Digital campaigns

The lower-CPC mechanism is one thing; the real account result is another. In Google Shopping, the final return on ad spend matters more than provider claims. In one Double Digital fashion e-commerce campaign using Google Ads and Performance Max, ROAS reached 1,066%, sales increased by 280% and CPA decreased by 40%. In another impulse-purchase category involving toy vending machines, ROAS exceeded 1,000%, up from an initial 300%, while sales increased by 229% and conversion cost fell by 64%.

Results of this kind come from combining the right campaign structure, a clean product feed and control over click costs, with a proprietary comparison service being one of the supporting elements. As a Google Premier Partner 2026 and a top 3% agency in Poland, Double Digital treats White Label CSS as one optimisation lever, not a magic switch. The figures above come from real advertising accounts, not simulations.

White Label CSS as a revenue model for agencies

For an agency, White Label CSS is not only a way to reduce clients’ CPC. It can become a separate product and recurring revenue stream. The agency displays its own brand on the product ads of all connected clients, strengthens its position as a Google Shopping specialist and charges a recurring fee for access to the comparison service. The service can be included in a retainer or sold separately, with the margin remaining with the agency.

• Agency branding on client ads creates visibility and can generate inbound leads.
• Access to the comparison service can be sold as a recurring monthly service with the agency’s own margin.
• A stronger service relationship positions the agency as the single provider responsible for the broader Google Shopping ecosystem.

Agency branding and inbound leads

The agency’s name displayed alongside each client’s product ad acts like a permanent banner. Depending on campaign volume, users may see “By Your Agency” hundreds of thousands of times per month. These are brand impressions that do not require a separate display media budget.

This visibility can translate into leads. Other store owners see ads carrying the agency’s name and associate the brand with expertise in Google Shopping. Some contact the agency directly because White Label CSS positions it as a specialist in product campaigns. Client acquisition becomes more efficient when proof of competence circulates throughout the market without additional media spend.

Monetisation follows a straightforward model. The client benefits from a lower CPC, while the agency charges a fixed monthly fee for access to the comparison service. The difference between the cost of maintaining one comparison service and the combined subscriptions paid by all clients becomes the agency’s margin. The economics improve as more stores are connected because infrastructure costs remain relatively stable while recurring revenue increases with each account.

Protecting the client relationship

A reliable comparison service provider should never contact an agency’s clients directly or attempt to upsell them. This must be verified before signing an agreement because it determines whether White Label CSS strengthens the agency’s business or exposes it to unnecessary risk. A good provider remains invisible infrastructure, while the commercial relationship and margin stay with the agency.

The risk increases when the provider is itself an agency or offers competing services. In that situation, your clients appear in a competitor’s database, creating an opportunity for contract takeover. Ask directly about the provider’s policy on contacting end clients and whether it operates in the same service market. Also verify who owns the comparison service domain. When ownership remains with the agency, the agency controls a genuine asset rather than merely renting someone else’s infrastructure.

When White Label CSS does not pay off

White Label CSS is not suitable for every business. When you do not run product campaigns in Google Shopping, manage fewer than the required number of stores or operate with a low monthly Shopping budget, the setup and subscription costs may exceed the CPC savings. Profitability should be calculated before implementation, not afterwards.

• No Shopping campaigns means the comparison service provides no benefit.
• Too few connected stores can create additional programme or provider costs.
• A low Shopping budget may produce CPC savings smaller than the cost of maintaining the CSS.

The budget threshold: when savings exceed the cost

The calculation is straightforward. The saving generated by White Label CSS is a percentage of Google Shopping spend, while the cost consists of a fixed setup fee and a recurring subscription. As long as the percentage saving is lower than the monthly fee, the service operates at a loss. The break-even point improves as product campaign spend increases.

Across accounts managed by Double Digital, a proprietary comparison service starts to make sense with regular monthly Shopping expenditure rather than isolated tests worth a few hundred PLN. The effect of the lower click cost is best evaluated through ROAS. There is no universal threshold because profitability depends on the industry, margin and auction competition. The principle remains the same: the larger and more stable the Shopping budget, the faster White Label CSS can pay for itself.

Risks and compliance with Google policies

The comparison service must satisfy Google CSS programme requirements. A non-compliant provider can expose connected accounts to suspension. Retailers can lose CSS status when the comparison service violates programme guidelines, forcing campaigns back to more expensive clicks and creating operational disruption. When selecting a partner, ask about its compliance history and how often clients have encountered certification problems.

Also verify who owns the domain and the comparison service website. In some offers, the domain belongs to the client but the website itself cannot be transferred, creating dependency on the provider. Before committing to White Label CSS, review the terms covering compliance, transfer and termination. Those clauses determine whether the comparison service is your asset or merely a rented service that disappears when you change partner.

How to implement White Label CSS step by step

Implementation follows several structured stages: select a provider that is a Google CSS partner, choose your own domain, populate the comparison service with offers from the required number of stores, complete Google’s audit and certification, and connect clients’ Merchant Center accounts. The technical work is usually completed faster than the Google review, which is why the end-to-end process can take several weeks. White Label CSS is launched once and can then be expanded by adding further accounts.

• Implementation order: provider, domain, stores listed in the comparison service, Google audit and Merchant Center account connections.
• Timing: the full process can take several weeks because Google’s audit and certification extend the launch timeline.
• Campaign continuity: existing client campaigns continue operating while the CSS assignment is changed.

A vendor-independent implementation process

Regardless of the provider, the sequence is similar. First, you sign an agreement and specify the domain or subdomain where the comparison service will operate. The provider then builds the price comparison website and submits it for Google certification. After a successful audit, client accounts are connected and ads begin to serve with your label and the CPC advantage. The programme typically requires offers from several independent stores, so additional accounts may need to be included at launch when the agency’s own portfolio is too small.

An important detail is that switching the comparison service does not stop the campaigns. Accounts, feeds and budgets continue to run, including Performance Max campaigns; only the CSS assignment changes in the settings. When an organisation does not have the resources to manage product campaigns internally, the implementation can form part of a broader Google Ads and Shopping management service.

What you need to get started

Before launch, prepare a domain or subdomain for the comparison service, your logo and brand colours, and a list of stores to be included. For each store, the provider will usually need the business name, address, account identifier and product feed. The cleaner the feed, the faster the audit and the fewer corrections will be required. Data is connected through Google Merchant Center, while ongoing comparison service management takes place in CSS Center.

Data quality has a direct impact on performance. Even the best comparison service cannot compensate for a neglected product feed. Before connecting accounts, resolve Merchant Center errors and compare available providers and tools carefully, including the level of control they offer over the comparison service and its data.

Where the Google CSS programme came from

The Google CSS (Comparison Shopping Service) programme was created after the European Commission’s 2017 decision that Google had favoured its own comparison shopping service in Google Shopping. In response, Google opened Shopping auctions to external comparison services and introduced a difference in the effective click cost. The White Label CSS market developed from this structure, allowing agencies and retailers to operate proprietary comparison services.

• The origin: the European Commission’s 2017 antitrust decision concerning Google Shopping.
• The result: external price comparison services were allowed to participate in Google Shopping auctions.
• The market effect: the CPC difference created a commercial market for White Label CSS providers.

Why this matters to advertisers

This background explains why the CPC advantage is structural rather than merely promotional. A lower click cost is not a temporary provider discount. It results from the market framework introduced after the European Commission’s decision. As long as that framework remains in force, operating through an approved comparison service remains a legitimate way to access lower-cost clicks.

For advertisers, the conclusion is straightforward. White Label CSS is not an unofficial loophole that Google is expected to close. It is part of the platform’s formally established ecosystem. Using a proprietary comparison service is therefore compliant when the provider follows programme requirements. Understanding this context also makes it easier to distinguish reliable partners from providers making promises that conflict with Google’s policies.

The CSS market has matured. In the early years, simply using an external comparison service created a stronger competitive advantage because adoption was limited. Today, participation alone is not enough. Product feed quality, campaign structure and provider selection determine the result. White Label CSS remains a valuable tool, but it should be treated as part of professionally managed Google Shopping campaigns rather than a standalone guarantee of performance.

FAQ: frequently asked questions

Is white label legal?

Yes. White label is a legal business model in which technology supplied by one company is sold under another company’s brand. In Google Shopping, a proprietary comparison service operates within the official Google CSS programme and is reviewed by Google. Safety depends on whether the provider complies with programme guidelines, which makes partner selection critical.

What is White Label CSS in Google Shopping?

White Label CSS is a price comparison service operating within the Google CSS programme under an agency’s or retailer’s brand rather than the “By Google” label. It enables product ads to run in Google Shopping with a lower cost per click and proprietary branding. It is an advertising channel, not interface white-labelling with Cascading Style Sheets.

What is the difference between White Label CSS and Branded CSS?

The difference concerns ownership of the comparison service. Branded CSS belongs to an e-commerce retailer and displays that retailer’s brand on its own ads. White Label CSS belongs to an agency and displays the agency’s brand across the product ads of all connected clients. A retailer with one brand usually chooses Branded CSS, while an agency managing multiple accounts typically chooses White Label CSS.

How much does a proprietary CSS cost?

Pricing usually combines a one-off setup fee with a monthly subscription for maintaining the comparison service. Rates vary between providers and depend on the number of connected stores and the scope of the service. Instead of comparing price lists alone, calculate the break-even point: the CPC saving generated by your Shopping budget must exceed the recurring fee.

How long does White Label CSS implementation take?

Technical work on the provider’s side usually takes several days, but Google’s audit and certification extend the full timeline. In practice, several weeks may pass between submission and full launch. Having the domain, store details and product feeds prepared in advance can materially shorten the process.

Will switching to my own CSS stop my Shopping campaigns?

No. Changing the comparison service does not interrupt campaigns. Accounts, feeds and budgets continue running because only the CSS assignment in the account settings changes. After Google approval, the ads continue to serve with your label in the “By” field and the lower CPC structure.