How Whitelabel CSS Works - Technical Setup and Architecture

Setting up a whitelabel CSS involves several steps, but the process is more structured than complex. The provider handles the technical heavy lifting, while you provide the branding direction and domain access. Here is a detailed walkthrough of how the entire system comes together, from initial setup through to live operation.

The Step-by-Step Setup Process

Every whitelabel CSS setup follows a similar sequence. The specifics vary slightly between providers, but the core steps are consistent across the industry. Here is what the process looks like from start to finish.

Step 1: Choose a Whitelabel Provider

The first decision is selecting a provider. This choice affects your setup timeline, ongoing costs, the quality of your comparison shopping website, and the level of support you receive. Providers like Cobiro offer a complete whitelabel package that includes the CSS Center setup, comparison website, management dashboard, and ongoing compliance management.

Key factors to evaluate include pricing structure (flat fee vs per-client), the quality of comparison websites they build, their track record with Google compliance, setup timeline, and the markets they support. For a detailed comparison, see our Choosing a Provider guide.

Step 2: CSS Center Creation

Once you have selected a provider, they create a Google CSS Center account for your brand. The CSS Center is the administrative hub within Google Merchant Center that manages your CSS operation. It is where client Merchant Centers are linked, where your CSS details are registered, and where Google recognises your CSS as an active partner.

The CSS Center is registered under a legal entity. Depending on the provider, this can be your own company's legal entity or the provider's entity with your brand applied. Some agencies prefer to use their own legal entity for maximum control. Others prefer to have the provider handle the legal structure, which simplifies operations especially when working across multiple European markets.

Cobiro handles the legal entity structure on their end, meaning you can operate across all supported markets without needing separate corporate registrations in each country. This is a significant practical advantage for agencies that serve clients in multiple European markets.

Step 3: Comparison Shopping Website Build

Google requires every CSS to operate a functioning comparison shopping website. This is a non-negotiable requirement. The provider builds this site on a domain or subdomain that you control.

The comparison site must meet specific criteria set by Google. It needs to display real product listings from real merchants, show current prices, provide a genuine comparison shopping experience, and link to merchants' websites where consumers can complete purchases. Google specifies that the site must include products from at least 10 different merchants to demonstrate that it is a legitimate comparison shopping service.

The provider populates the site with product data from your clients' feeds and maintains it on an ongoing basis. Product listings update automatically as your clients' inventory and pricing change. The site is designed to meet Google's quality standards while carrying your brand identity.

Step 4: DNS Configuration

To host the comparison shopping website on your domain, you need to make a simple DNS change. The typical setup involves adding an A record or CNAME record that points your chosen domain or subdomain to the provider's servers.

Common domain structures include:

• shopping.youragency.com - a subdomain of your main agency website
• compare.youragency.com - another common subdomain approach
• css.youragency.com - straightforward and descriptive
• youragency-shopping.com - a dedicated domain for the CSS operation

The DNS change itself takes minutes to configure and typically propagates within a few hours. Your provider will give you the exact record type and value to add. If you are not comfortable with DNS changes, most domain registrars have straightforward interfaces, and your provider's support team can walk you through the process.

Step 5: Google Audit and Approval

Once the CSS Center is configured and the comparison shopping website is live, Google reviews the application. The audit checks that the comparison site meets their quality requirements, that the legal entity information is correct, and that all CSS programme requirements are satisfied.

The audit timeline varies. In some cases, Google completes the review within a few days. In others, it can take two to three weeks, particularly during busy periods or if clarifications are needed. Your provider manages the communication with Google throughout this process and addresses any questions or requirements that come up during the audit.

Once approved, your CSS is officially certified and ready to accept client Merchant Centers.

Step 6: Client Onboarding

With your CSS approved, you can start adding client Merchant Centers. When a client's Merchant Center is associated with your CSS, their Shopping ads and PMax campaigns begin showing "By [Your Brand]" in the attribution line.

The association process is straightforward. Depending on the setup, it can be done through Google Merchant Center's settings where the client selects your CSS, or the provider can handle the switch through the CSS Center. The change typically takes effect within 24 hours.

Campaign data, performance history, quality scores, and all other metrics remain intact during the switch. There is no disruption to the client's live campaigns. The only visible change is the "By" attribution, which now shows your agency name.

Understanding the Google CSS Center

The CSS Center is a specialised account type within the Google Merchant Center ecosystem. It serves as the administrative hub for your CSS operation and is where Google recognises your CSS partnership.

Through the CSS Center, your provider manages the list of client Merchant Centers associated with your CSS. Each time a new client is added, their Merchant Center is linked to your CSS Center. This link tells Google that your CSS is the one representing that merchant for Shopping ad purposes, and it triggers the "By [Your Brand]" attribution on their ads.

You do not need to interact directly with the CSS Center for day-to-day operations. Your provider's management platform abstracts this complexity and gives you a simpler interface for onboarding clients and monitoring your CSS. However, understanding that the CSS Center exists and what it does helps you make sense of the overall architecture.

How Merchant Center Switching Works

One of the most common concerns agencies have is whether switching a client's Merchant Center to a new CSS will disrupt their campaigns. The short answer is no. The switch is designed to be seamless.

When a Merchant Center is moved from one CSS to another, several things remain unchanged:

• Campaign performance data - all historical metrics, conversion data, and reporting stay intact
• Quality scores - product quality scores and account-level scores are not affected
• Product approvals - approved products remain approved; there is no re-review process
• Bidding strategies - automated bidding continues to function with the same historical signals
• Feed configuration - product feeds, supplemental feeds, and feed rules all stay in place

The only change is the CSS attribution on the Shopping ads. The "By [Previous CSS]" label is replaced with "By [Your Brand]". This transition happens automatically once the Merchant Center is associated with your CSS Center.

In practice, clients rarely notice the switch unless you tell them. And when you do tell them, the change from a generic provider name to your agency's name is universally seen as a positive improvement.

Typical Setup Timeline

From initial sign-up to a fully operational whitelabel CSS, the timeline typically ranges from one to four weeks. Here is how that breaks down:

With Cobiro, most agencies complete the entire process within one to two weeks. The variable factor is Google's audit timeline, which is outside anyone's control. Some audits complete in a few days; others take longer. Your provider should keep you informed throughout the waiting period.

What Can Go Wrong

While the setup process is generally smooth, there are potential issues worth understanding so you can avoid them or address them quickly.

Google Policy Violations

If the comparison shopping website does not meet Google's requirements, the CSS application will be rejected or delayed. Common issues include insufficient product listings, missing price information, broken merchant links, or content that does not reflect a genuine comparison shopping experience. A reputable provider will build the site to Google's exact specifications, but it is worth understanding what Google looks for.

Incomplete Comparison Sites

Google requires the comparison site to feature products from at least 10 different merchants. If your client base is small at launch, the provider may need to supplement the site with additional merchant listings to meet this threshold. This is standard practice and fully compliant with Google's requirements.

Incorrect Legal Entity Setup

The legal entity associated with the CSS must match the information provided to Google. Discrepancies between the CSS application and the registered entity details can cause delays in the audit process. Your provider should handle this correctly from the start, but double-checking the details is always prudent.

DNS Propagation Delays

After making DNS changes, it can take up to 48 hours for the changes to propagate globally, though most propagation completes within a few hours. During this window, the comparison site may not be accessible to all visitors. Plan for this in your timeline and do not submit the CSS for Google audit until DNS propagation is confirmed.

After Setup: Ongoing Operations

Once your whitelabel CSS is live and your first clients are onboarded, the day-to-day operational requirements are minimal. The provider maintains the comparison shopping website, keeps the CSS in compliance with Google's evolving policies, and handles any technical issues that arise.

Your ongoing responsibilities are focused on the business side: onboarding new clients, managing client relationships, setting and adjusting pricing, and using the CSS as part of your broader service offering. The technical operations run in the background without requiring your attention.

Periodic tasks may include reviewing your comparison site to ensure it still reflects your current branding, adding new clients as your business grows, and staying informed about changes to Google's CSS programme that might affect your strategy. Your provider should proactively communicate any significant changes.

For detailed guidance on onboarding your first clients, see the Onboarding Clients guide. To understand Google's specific requirements in depth, read the Google CSS Requirements page.