Google CSS Partnership Requirements - What You Need to Know

Before you can operate as a Google CSS Partner, your CSS must meet a specific set of requirements laid out by Google. These requirements cover your business entity, your comparison shopping website, your technical infrastructure, and your ongoing compliance practices. This page details every requirement and clarifies what your whitelabel provider handles versus what falls to you.

Understanding these requirements matters even if your provider manages the application process. You need to know what Google expects so you can prepare the right materials, avoid delays, and communicate accurately with stakeholders inside your organisation.

1. A Functional Comparison Shopping Website

This is Google's primary and most scrutinised requirement. Every CSS Partner must operate a genuine comparison shopping website that allows consumers to compare products from multiple merchants. Google is explicit about what "genuine" means in this context: the site must offer real value to consumers, not merely exist as a technical formality.

The comparison website must include product listings from multiple merchants, a search function that returns relevant results, category navigation, price comparison features, product images, and direct links to merchant stores where consumers can complete purchases. Google reviews these elements during the approval process and periodically audits them afterward.

A thin site with a handful of products and no real functionality will not pass Google's review. Neither will a site that looks like a placeholder or a marketing brochure. Google wants to see a tool that consumers would genuinely use to compare products and find deals.

This is the requirement that deters many agencies from attempting to run their own CSS independently. Building and maintaining a compliant comparison website requires significant development effort, product data infrastructure, and ongoing updates. It is also the primary reason agencies choose a whitelabel provider. Providers like Cobiro build the comparison site for you, populate it with product data, and maintain it to Google's standards on an ongoing basis. For a full breakdown of comparison site requirements, see our comparison website guide.

2. A Registered Business Entity in an Eligible Market

Google's CSS programme operates in EU/EEA countries, the United Kingdom, and Switzerland. To qualify as a CSS Partner, you must be a registered business entity in one of these markets. This means having a legal business registration, a registered office address, and the ability to enter into commercial agreements.

Sole traders, limited companies, partnerships, and other standard business structures are all eligible. Google does not impose a minimum company size or revenue requirement. However, you do need to be able to provide standard business documentation during the application process.

If your agency is based outside the eligible markets, you may still be able to participate through a subsidiary or local entity in an eligible country. This is a niche scenario, but it is worth discussing with your provider if it applies to your situation.

3. Google Merchant Center Access (CSS Center Account)

A CSS Partner operates through a special type of Google Merchant Center account called a CSS Center. This account serves as the administrative hub for your CSS operation. Through it, you manage client Merchant Center accounts, submit CSS switch requests, and monitor compliance status.

The CSS Center account is created as part of the CSS application process. Your provider typically sets this up on your behalf and grants you the appropriate access levels. With Cobiro, your CSS Center account is configured and ready to use by the time Google approval comes through.

It is important to understand the relationship between the CSS Center and your clients' existing Merchant Center accounts. Switching a client to your CSS does not move or copy their Merchant Center. It simply associates their existing account with your CSS for the purpose of Shopping ad placement. The client retains full ownership and control of their Merchant Center at all times.

4. Compliance with Google CSS Policies

Google maintains a set of policies specifically for CSS Partners, separate from the general Google Ads and Merchant Center policies. These cover areas such as transparency with merchants, fair representation, data handling, and advertising practices.

Key policy areas include:

• Transparency. You must be transparent with merchants about the nature of the CSS service and how their data is used.
• Fair representation. Product data displayed on your comparison site must accurately reflect actual pricing and availability.
• No misleading claims. You cannot misrepresent the benefits of CSS or make guarantees about performance that are not substantiated.
• Data handling. Merchant product data must be handled in accordance with applicable data protection regulations.
• Attribution accuracy. The "By [CSS Name]" attribution must accurately reflect the CSS that submitted the product data.

Your provider should maintain compliance with these policies as part of their service. This includes keeping the comparison website updated, ensuring product data accuracy, and adapting to any policy changes Google introduces. When evaluating providers, ask specifically how they handle ongoing compliance.

5. Ongoing Maintenance and Updates

CSS Partnership is not a one-time certification. Google expects ongoing activity and maintenance. Your comparison shopping website must remain functional, product data must stay current, and your CSS must continue to serve merchants actively.

Specifically, Google looks for regular product data updates across your comparison site. Stale data, broken product links, or a site that has not been updated in months can trigger a review. Similarly, a CSS that has no active merchants or very low activity may draw attention during audits.

With a whitelabel provider, ongoing maintenance is part of the service. Product feeds are updated automatically, the comparison website is monitored for uptime and functionality, and compliance is reviewed regularly. This is one of the core value propositions of using a provider rather than building your own CSS infrastructure from scratch.

What Your Provider Handles vs What You Handle

With a whitelabel setup, the division of responsibilities is clear. Understanding this split helps set expectations and avoids confusion during the setup process.

The takeaway is that the provider handles the technical and compliance-heavy work, while you handle the business relationship and branding aspects. This is the entire point of the whitelabel model: you get the benefits of operating a CSS without the infrastructure burden.

Common Compliance Pitfalls

Even with a provider managing the process, it helps to be aware of the issues that most commonly cause delays or problems during Google's review:

Thin Comparison Sites

A comparison website with too few products, too few merchants, or minimal functionality is the single most common reason for application rejection or delay. Google expects a site that looks and functions like a genuine consumer tool. A page with 50 products from two merchants will not pass.

Stale Product Data

Product listings with outdated prices, discontinued items, or broken merchant links signal that the site is not actively maintained. Google checks for data freshness during reviews and audits. A good provider updates product data daily or more frequently.

Broken Links and Technical Errors

Links that lead to 404 pages, product images that fail to load, and search functions that return errors all create problems during Google's review. These issues also affect the consumer experience, which is what Google ultimately cares about.

Design and Usability Issues

A comparison site that is not responsive, loads slowly, or has an unusable interface on mobile devices will face scrutiny. Google expects sites that work well across devices and provide a smooth user experience. Your provider should build the site to modern web standards.

Missing Legal Pages

Google expects standard legal pages including a privacy policy, terms of service, and clear business contact information. These must be present and accurate for your registered business entity. Your provider typically generates templates for these pages, but you should review them for accuracy.

Premium vs Standard CSS Partner Status

Google distinguishes between Premium and Standard CSS Partners. Premium status is awarded to CSS Partners who meet additional criteria around volume, quality, and operational maturity. The exact criteria for Premium status are not publicly documented in detail, but they involve factors like the number of active merchants, geographic coverage, and the quality of the comparison website.

The practical difference matters for whitelabel. When you use a Premium CSS Partner like Cobiro as your whitelabel provider, your CSS inherits the benefits of that Premium designation. This can include faster processing of applications and changes, priority access to new features, and additional support from Google's CSS team.

Standard CSS Partners still operate fully functional CSS services. The distinction is more about operational maturity and the level of Google support available. When evaluating providers, Premium status is one indicator of a provider's track record and scale.