The CSS Comparison Shopping Website - What It Is and Why Google Requires It

Every CSS Partner must operate a comparison shopping website. This is not optional, not negotiable, and not something you can substitute with a standard marketing site or a landing page. Google requires it because the entire CSS programme is built on the premise that comparison shopping services provide consumer value by helping shoppers compare products across merchants. Your comparison website is the proof that your CSS delivers on this premise.

For most agencies exploring whitelabel CSS, the comparison website is the requirement that raises the most questions. What does it need to look like? How complex does it need to be? Who builds and maintains it? This page answers all of these questions in detail.

Why Google Requires a Comparison Website

The CSS programme exists because of a 2017 European Commission ruling that required Google to give equal access to comparison shopping services in its Shopping results. The key word is "comparison shopping services." Google must ensure that every entity operating as a CSS is, in fact, a genuine comparison shopping service, not merely a technical entity created to access Shopping ad placements.

The comparison website is Google's primary mechanism for verifying this. If you operate a CSS, you must operate a website where consumers can genuinely compare products from multiple merchants. Google reviews the site during the initial application, and they audit it periodically afterward to ensure it remains functional and compliant.

This is also why a thin or fake site will not pass review. Google has seen every variation of placeholder sites, auto-generated pages with minimal content, and marketing sites dressed up as comparison tools. Their review team knows what a genuine comparison site looks like, and they hold applicants to that standard.

What a Compliant Comparison Website Looks Like

A comparison website that meets Google's standards has several distinct features. Think of it as a specialised e-commerce search engine rather than a standard website. Here is what Google expects to see:

Product Search

Visitors must be able to search for products by name, brand, or keyword. The search results must return relevant products from multiple merchants, displayed with pricing, images, and merchant information. A comparison site without working search functionality will fail Google's review.

Category Navigation

The site should offer structured category navigation. Visitors should be able to browse by product category (electronics, fashion, home goods, and so on) and drill down into subcategories. This demonstrates the breadth of your product catalogue and makes the site usable for real consumers.

Price Comparison

This is the core function. For any given product, the site should show prices from multiple merchants side by side. Consumers should be able to see which merchant offers the best price and make an informed purchasing decision. This is what makes it a "comparison" shopping site rather than just a product directory.

Product Images and Details

Each product listing should include images, descriptions, key specifications, and pricing. Bare-bones listings with only a product name and price will not satisfy Google's quality expectations. The listings should feel complete and useful.

Merchant Ratings and Information

Where available, the site should display information about each merchant, including ratings, shipping details, and return policies. This reinforces the comparison aspect and provides genuine consumer value.

Links to Merchant Stores

Every product listing must link directly to the merchant's store where the consumer can complete the purchase. The comparison site is a discovery and comparison tool, not a checkout platform. Click-through to the merchant is the expected user journey.

Quality Standard

Think of successful comparison sites like PriceRunner, Idealo, or Google Shopping itself. Your comparison website should aim for a similar user experience, scaled to fit your market and product catalogue. It does not need to be as large, but it must feel similarly functional and professional.

Technical Requirements

Beyond the functional features, Google evaluates the technical quality of your comparison website. A site that meets all the functional requirements but performs poorly or is inaccessible on mobile will still face problems during review.

Responsive Design

The site must work well on desktop, tablet, and mobile devices. Google reviews the mobile experience specifically, as a growing majority of Shopping ad clicks originate from mobile devices. If your comparison site is not mobile-friendly, it sends the wrong signal to Google's review team.

Fast Loading Times

Page speed matters for both Google's review and for consumer experience. A site that takes more than three seconds to load on a standard connection will not make a good impression. Product search results should return quickly, and category pages should load without excessive delays.

Accessibility

The site should follow basic web accessibility standards. Alt text on images, proper heading structure, keyboard navigability, and sufficient colour contrast are all expected. While Google does not require full WCAG compliance, a site with obvious accessibility gaps will draw scrutiny.

Localisation for All Active Markets

If your CSS operates in multiple European markets, the comparison website must be localised for each market. This means translated content, local currency pricing, and market-specific product availability. A site in English only will not satisfy the requirements for CSS operations in France, Germany, or Spain.

This is one area where working with an experienced provider makes a particularly large difference. Cobiro builds comparison websites with localisation across all 21 CSS markets in Europe. Each market-specific version is fully translated, uses local currencies, and displays products available to consumers in that country. Building this yourself would require significant translation and development resources.

Content Requirements

Google evaluates the breadth and freshness of the product content on your comparison site. This is not just about having a working site; it is about having a site with enough genuine content to demonstrate value.

Minimum Merchant Count

Your comparison site should feature products from at least ten merchants with active product feeds. This demonstrates that the site serves as a genuine multi-merchant comparison tool rather than a front for a single retailer or a small group of affiliated stores. More merchants is always better from Google's perspective.

Regular Data Updates

Product pricing, availability, and merchant information must be updated regularly. Google can detect stale data, and a site with product prices that have not changed in weeks or product listings pointing to discontinued items will face compliance issues. Best practice is daily data updates, which is the standard that Cobiro maintains for all whitelabel comparison sites.

Genuine Product Data

The product data must be real. Synthetic data, placeholder products, or auto-generated listings will not pass Google's review. Every product on your comparison site should correspond to a real product available for purchase from a real merchant.

Common Pitfall

Some providers use a generic pool of product data for all their whitelabel sites, resulting in comparison websites that look identical except for the logo. Google has become increasingly attentive to this pattern. A strong provider customises the product catalogue based on your actual client mix and target markets.

Branding: Your Site, Your Identity

The entire point of whitelabel CSS is that the comparison website carries your brand, not your provider's. Every consumer-facing element of the site should reflect your agency's visual identity.

This includes your logo displayed prominently in the header and footer, your brand colours used throughout the site design, your agency name in the page titles and meta descriptions, your domain name in the URL bar, and your business details on the legal and contact pages.

A visitor to your comparison website should have no indication that the site is powered by a third-party provider. It should look and feel like a product your agency built and operates independently. This is the standard that Cobiro maintains for every whitelabel partner.

To achieve this, you will need to provide your provider with a few specific assets: your logo in SVG or high-resolution PNG format, your primary and secondary brand colours as hex codes, any typography preferences, and the domain or subdomain you want to use for the site. Most agencies use a subdomain like shopping.youragency.com or compare.yourbrand.com.

DNS Setup

The one technical task that falls to you is configuring DNS for the comparison website domain. This typically involves adding a CNAME record pointing your chosen domain to your provider's hosting infrastructure. Your provider will give you the specific DNS record to add, and the process takes five minutes in most domain registrar control panels. If you have managed a website before, this will be familiar.

How Cobiro Builds and Maintains Your Comparison Site

Understanding how a provider like Cobiro handles the comparison website helps illustrate what you should expect from any whitelabel partner. Here is the typical process:

  1. You provide branding assets. Logo, colours, domain name, and any design preferences. This takes most agencies less than an hour to prepare.
  2. Cobiro builds the site. Using your branding, Cobiro creates a fully functional comparison website with search, categories, product listings, and merchant links. The build typically takes two to five business days.
  3. Product data is populated. The site is populated with product data from your clients' feeds and from Cobiro's broader merchant network. This ensures the site has enough content to pass Google's review from day one.
  4. Localisation is applied. If you operate in multiple markets, the site is localised for each country with translated content, local currencies, and market-specific products.
  5. DNS is configured. You add the CNAME record for your domain, and the site goes live on your URL.
  6. Ongoing maintenance. Product data is updated daily. The site is monitored for uptime and functionality. Localisation is maintained as you expand to new markets. Compliance is managed proactively.

This end-to-end approach is what allows agencies to launch a CSS in one to two weeks rather than months. The comparison website, which would be the most time-consuming element to build independently, is handled entirely by the provider.

21 Markets, One Build

Cobiro's whitelabel comparison websites support all 21 CSS-eligible markets in Europe out of the box. You do not need to request localisation for individual countries. When you onboard a client in a new market, the comparison site already covers that country with local language content and local product data.

What Happens After Launch

Once the comparison website is live and your CSS is approved, the site continues to serve two important functions. First, it maintains your CSS compliance with Google. As long as the site is active, updated, and functional, your CSS remains in good standing. Second, it captures traffic from the "By [Your Brand]" links on your clients' Shopping ads.

As covered in our free clicks and traffic guide, approximately 3% of Shopping ad clicks go to the CSS comparison website rather than the product listing. For an agency with 50 clients, this can translate to thousands of free, qualified visitors to your branded comparison site every month. That traffic is yours to monetise through affiliate links, lead generation, or brand awareness.

The comparison website is not just a compliance checkbox. When done well, it becomes a genuine asset for your agency: a consumer-facing platform that reinforces your brand and generates traffic at no additional cost.

Build Your Own CSS Brand

Launch your whitelabel CSS with Cobiro.

Start your free trial