Google CSS Requirements: Complete Approval Checklist

Launching a Comparison Shopping Service requires more than a branded website and access to several Merchant Center accounts. Google expects every CSS to operate a genuine, public product comparison platform that helps shoppers search, filter and compare offers from multiple retailers.

This guide explains the official Google CSS requirements in practical terms. It covers business registration, website functionality, the 50-merchant rule, product data, country expansion and the additional criteria needed to earn Google CSS Partner status.

If you are still deciding how to structure the project, start with our guide on how to become a Google CSS Partner. The article below focuses specifically on compliance and approval readiness.

Google CSS requirements: an overview

The Comparison Shopping Services programme is designed for businesses that operate product comparison websites. A qualifying CSS collects offers from online retailers, displays them in a useful comparison environment and sends users to merchant websites where they can complete a purchase.

The minimum requirements can be grouped into six areas:

• Business eligibility — the operator must be registered in a country where the programme is available.
• Comparison functionality — the website must allow users to search and compare products and offers.
• Merchant coverage — the site must show products from at least 50 distinct merchant domains per target country.
• Product data quality — prices, availability, product details and destination links must be accurate and useful.
• Public accessibility — users must be able to access the service without mandatory registration.
• Policy compliance — the CSS and its merchants must comply with applicable Google Shopping requirements.

Business registration and company information

The CSS operator must have a business registration in at least one country where the programme is available. The website must display a business address that corresponds to that registration.

The business identity should be consistent across:

• the comparison website and contact page;
• terms of service and privacy documentation;
• the CSS programme application;
• billing and company records;
• Merchant Center and CSS Center details where applicable.

A vague contact form without a visible company name and address is not a strong foundation for an approval review. The site should make it clear who owns the comparison service, how users can contact the operator and what role the business plays between merchants and shoppers.

Can a marketing agency operate a CSS?

Yes. A PPC or digital agency can operate a CSS, but its comparison platform must meet the same requirements as any other participant. Being a Google Ads agency, Google Partner or Google Premier Partner does not replace the CSS approval process.

The agency must operate a genuine comparison service. A sales landing page describing lower Shopping costs is not enough.

Comparison website functionality

The website is the core of the CSS application. It needs to provide real value to shoppers rather than exist only as a technical destination behind Shopping ads.

Product search

The site must offer a search box and return relevant product results through a primarily dynamic and automated process. The search experience cannot be substantially based on technology licensed or syndicated from Google.

A useful search experience should:

• interpret clear product queries;
• return products related to the user’s request;
• avoid empty or unrelated result pages;
• allow the shopper to progress without entering another query;
• work across the product categories presented on the site.

Price and offer comparison

The platform must help users compare different products. It should also make it possible to compare the price and selling conditions of the same product offered by different merchants when multiple offers are available.

Each offer should clearly identify the merchant and provide enough information for the shopper to understand the basic commercial conditions before leaving the CSS.

Sorting and filtering

Users must be able to sort or filter results by price and at least one other relevant dimension. The second dimension should support a genuine purchase decision, for example:

• brand or manufacturer;
• merchant;
• shipping time;
• availability;
• product category;
• size, colour or another category-specific attribute.

Public access

The comparison service must be accessible without sign-up. Users should not be forced to create an account, provide an email address or request access before they can search and compare offers.

Links to purchase pages

The CSS must lead users to pages where the displayed products can be purchased. A product result should link to the relevant merchant product page, not an unrelated homepage, a general category or another intermediary that prevents the user from completing the task.

The 50-merchant requirement explained

For every country in which a CSS wants to participate, its website must display products from at least 50 distinct merchant domains. This is one of the most important requirements and one of the most common barriers for smaller agencies.

The condition applies per target country. If a CSS wants to participate in Germany, it needs offers from at least 50 merchants that deliver to German consumers. If it later expands to France, the platform must also meet the merchant requirement for France.

What counts as a distinct merchant domain?

The requirement concerns different merchant domains, not separate Merchant Center accounts belonging to the same online store. Creating multiple accounts for one retailer does not turn that retailer into multiple distinct merchants.

The merchants must be real sellers whose products can be purchased and delivered in the relevant country. Their offers should be current, accessible and integrated into the comparison experience.

Website merchants vs active Shopping Ads merchants

Two different thresholds are often confused:

A website may therefore satisfy the minimum merchant coverage needed to operate a CSS without automatically qualifying for the official Partner badge.

Product data and feed requirements

A CSS depends on product data collected from multiple retailers. The platform needs a reliable process for importing, normalising, updating and monitoring those offers.

Information displayed to shoppers

Product listings should provide useful and accurate information, including:

• product title and relevant attributes;
• current price and currency;
• availability where applicable;
• merchant name;
• product image;
• a working link to the merchant’s purchase page.

Feed freshness

Retailers change prices, stock availability, variants and landing pages continuously. The CSS needs an update process frequent enough to prevent the comparison website from becoming misleading or unusable.

Typical infrastructure includes XML or CSV imports, API connections, scheduled updates and automated checks for broken destinations or inconsistent values.

Product matching

To compare multiple offers for the same item, the platform needs a way to identify equivalent products. Product identifiers such as GTIN, brand and MPN can support matching, but the system must also cope with incomplete or inconsistent merchant data.

Merchant Center compliance

Products submitted through Merchant Center must follow the applicable product data specification and Shopping policies. Incorrect prices, unavailable products, misleading descriptions or broken landing pages can lead to item disapprovals and account-level problems.

The official Google product data specification should be treated as an operational reference, not only something checked during initial onboarding.

Country and market requirements

The CSS programme is available in Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Spain, Sweden, Switzerland and the United Kingdom.

Supporting a country means more than translating the interface. The CSS must ensure that:

• the required number of merchants deliver to that country;
• prices and currencies are appropriate for the market;
• product information is understandable to local users;
• destination pages allow consumers in that country to buy the products;
• shipping and selling conditions are not misleading;
• the comparison experience works correctly for the selected locale.

A staged expansion is usually safer than launching every country simultaneously. Start with markets where merchant coverage and product data can be controlled, then add new countries after the operating model has been tested.

Policies, transparency and user trust

Google does not allow Comparison Shopping Services that provide misleading information about products, businesses or services. The platform must clearly explain its role and must not create false expectations about the merchants, offers or relationship with Google.

Business transparency

• Show the legal business name and address.
• Provide working contact information.
• Publish privacy and terms documentation.
• Explain that purchases are completed on merchant websites.
• Describe how offers are collected and compared.

Brand and naming restrictions

A CSS cannot share a name or logo with a brand or business that sells physical goods listed on the CSS website. The comparison service must remain distinguishable from merchants whose offers it presents.

Marketplace distinction

A business whose primary activity is operating a marketplace where transactions take place on its own domain cannot participate as a CSS under that marketplace model. It may instead work with one or more CSS providers.

Requirements for the Google CSS Partner badge

Programme approval and CSS Partner status are separate. Approval allows a business to participate as a Comparison Shopping Service. The Partner and Premium Partner tiers recognise CSS providers that also meet additional scale and activity criteria.

Google currently describes the Partner tier as reserved for CSS providers within the leading 10–20% by Shopping ad impression volume, with at least 50 active merchants. Premium Partner is reserved for the top 10% and includes additional cooperation requirements.

Always verify the current criteria on the official Comparison Shopping Partners portal, as programme thresholds and benefits may change.

Google CSS approval checklist

Before applying, review the platform as both a programme operator and a normal shopper.

1. Confirm company eligibility. The business is registered in a supported country and the matching address is visible on the website.
2. Verify merchant coverage. At least 50 distinct merchant domains offer products to consumers in every selected country.
3. Test product search. Common queries return relevant, useful results without relying on Google search technology.
4. Test comparison features. Users can compare offers and sort or filter by price and another relevant dimension.
5. Check public access. Search and comparison work without registration, login or email submission.
6. Audit destination links. Product offers lead to working merchant pages where the products can be purchased.
7. Validate product data. Prices, availability, images, merchants and descriptions reflect the destination pages.
8. Review legal pages. Contact details, privacy information and terms clearly identify the CSS operator.
9. Test every target country. Merchant delivery, language, currency and purchase availability match the selected market.
10. Prepare ongoing monitoring. Feed errors, broken links, missing offers and merchant changes can be detected after approval.

Common reasons a CSS setup is not ready

• The website is only a landing page. It describes CSS benefits but does not provide real product search and comparison.
• Merchant coverage is too low. The platform has several agency clients but does not contain 50 distinct merchant domains for the target country.
• Search results are weak. Queries return irrelevant products, empty pages or generic categories.
• Filters do not support comparison. The site lacks price sorting or a second useful product dimension.
• Offers are outdated. Prices, availability or landing pages no longer match the merchant website.
• The same merchants are assumed to cover every country. The platform does not verify whether each store delivers to consumers in each market.
• Company information is inconsistent. The legal entity, address or contact details differ across the website and application.
• Partner status is promised too early. Approval as a CSS is presented as if it automatically included the Partner badge.

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

Meeting the requirements through White Label CSS

Building the comparison platform, feed infrastructure and country coverage internally can become a separate technology project. A White Label CSS allows an agency or e-commerce group to launch a branded service using existing infrastructure.

Depending on the implementation model, the provider can support:

• the comparison website and product search technology;
• merchant feed imports and product updates;
• domain and CSS configuration;
• Merchant Center onboarding and migration;
• multi-country product coverage;
• technical maintenance and operational support.

The agency retains its own CSS brand, client relationship, commercial offer and resale price while avoiding the need to develop the platform from the ground up.

Frequently asked questions

How many merchant domains does a Google CSS need?

The comparison website must 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.

Does a landing page qualify as a CSS website?

No. A qualifying CSS needs a genuine comparison shopping website with searchable product offers, price comparison, useful filters and links to merchant purchase pages.

Do the 50 merchants need active Shopping campaigns?

For the programme website requirement, the platform needs products from 50 distinct merchant domains per target country. The separate Partner and Premium Partner tiers require at least 50 merchants running active Shopping Ads campaigns and meeting the current activity criteria.

Can the same 50 merchants cover several countries?

Potentially, but only when those merchants genuinely sell and deliver products to consumers in every relevant country. Coverage must be verified market by market.

Is Google CSS approval permanent?

Participation depends on continuing to satisfy programme requirements. A CSS should monitor merchant coverage, product quality, website functionality and policy compliance after approval.

Do I need my own product feed technology?

You need reliable infrastructure capable of importing, updating and presenting merchant offers. It can be developed internally or provided through a White Label CSS platform.

Is approval the same as the Google CSS Partner badge?

No. Approval allows the business to operate a Comparison Shopping Service. Partner status has additional active-merchant and Shopping ad volume requirements.

Can an agency with fewer than 50 clients launch White Label CSS?

A White Label provider may support smaller agencies through existing technology, programme infrastructure and a broader merchant portfolio. The exact structure and eligibility requirements should be confirmed with the provider.