SEO for consumer packaged goods: an operator’s field guide
Quick answer. CPG SEO means making a brand’s product, variant and category pages findable and quotable, then routing that demand to a retailer or a checkout. Three constraints shape it: most category demand is owned by marketplaces, variants split one product across many URLs, and product copy is syndicated to retail partners. Win brand, size and comparison queries with unique pages and accurate product markup instead of chasing Amazon on head terms.
What matters most
- For most CPG brands the brand site should target brand, product-name, size, suitability and where-to-buy queries, not head category terms owned by retailers.
- One URL per purchase option a shopper can actually buy, each self-canonical, with real GTINs and Offer markup that matches the page.
- Copy syndicated to retail partners competes with your own product page, so keep the original descriptions, sourcing detail and comparisons on your domain.
- A where-to-buy page needs a current stockist list and a last-checked date; a stale partner list sends shoppers to dead ends.
- Organic search cannot be directly attributed to retail sell-through, so report branded query share, stockist clicks and retailer-side search data separately.
What makes SEO for consumer packaged goods different?
Consumer packaged goods brands sell repeat-purchase products through channels they do not control. That one fact explains most of what works in search. Someone who wants a twelve-pack of a specific drink searches the product name, the format, or the shop they already use. The retailer page answers that query more often than the brand page does. Your work is to be the clearest answer when the shopper is checking the brand, the size or the difference between two products.
Four constraints run through every CPG programme:
And the sale usually completes somewhere else. Organic sessions, where-to-buy clicks and retail sell-through are three different numbers. Only the first two belong to you. Build the plan around that gap rather than hoping a dashboard closes it.
- Margin per unit is thin, so paid search cannot carry product discovery indefinitely.
- The query set per SKU is thin while the range is wide; many variants share a handful of head terms and a long tail of size and format searches.
- Product copy is syndicated to retail partners, so your description may be indexed on five other domains before it is indexed on yours.
- Claims in food, drink, supplements and cosmetics have to clear legal review, which rules out publishing fast and correcting later.
Where to go next
- CPG SEO for brands selling through retail and direct
- e-commerce SEO across commerce platforms
- analytics and attribution for off-site sales
- the commerce platforms we work on
Which pages does a CPG brand actually need?
Most CPG sites have more page templates than jobs. What they need is one page per job, carrying the fields that job requires. This is the starting set we would use for a brand selling through retail and direct.
The category page is where most brands underinvest. A page that ranks explains the buying decision: format, pack size, dietary fit, price per unit and how the range differs. Put that copy on the page and keep the tiles. A grid alone gives a search engine nothing to read and a shopper nothing to compare.
| Page type | Queries it should answer | Fields that must be on the page | Usual mistake |
|---|---|---|---|
| Brand hub | Brand name, brand plus product | Original brand copy, range links, packaging images with alt text | Descriptions lifted from retailer listings |
| Category or format page | Format and category terms such as cold brew concentrate | Buying criteria, pack sizes, price per unit, range comparison | A grid of product tiles with no copy |
| Product page per purchase option | Brand plus product plus size or pack count | GTIN, size, servings, ingredients, allergens, availability, price | One page per flavour with near-identical copy |
| Where to buy | Brand plus where to buy, stockists, stockists near me | Real stockist list, store locator, date last checked | A partner list that has not changed since launch |
| Usage and comparison content | How to use, product versus product, is it suitable for | Named author, review date, link to the product page | Publishing without claims review |
How should variants and multipacks be split into URLs?
A purchase option is anything a shopper can add to a basket on its own: a size, a pack count, a format, sometimes a flavour. If people search for it and buy it separately, give it a URL. If it exists only as a filter value, keep it out of the index and let the facet do the work.
Case packs need their own discipline. A wholesale case is not a consumer page. Keep it in the product feed, out of the sitemap, and let the retail-facing pack sizes take the traffic.
- One URL per buyable option, self-canonical. Do not canonicalise a live variant to its parent.
- Keep out-of-stock pages live at 200 with availability set to OutOfStock. Reserve permanent redirects for discontinued lines with a real replacement.
- Write copy a merchandiser would recognise: flavour profile, macros, serving size, pack composition. Swapping one word between variants creates near-duplicates that compete with each other.
- For multipacks you assemble yourself, use your own SKU and describe the pack contents. Do not invent a GTIN to fill a field.
- Index facets that match real searches, such as size or dietary suitability. Noindex the combinations nobody types.
What product markup and feed data does Google need?
Every purchasable URL should carry Product and Offer markup that matches what is visible on the page: name, brand, gtin13 or gtin, sku, price, priceCurrency, availability and condition. Google’s product structured data documentation lists the required and recommended properties, and the schema.org Product and Offer types are the vocabulary behind them.
Where the brand sells direct, merchant listing requirements apply. Those need a price, availability and condition for the specific offer, and they must agree with the Merchant Center feed. A feed that says in stock while the page says sold out is a common cause of disapprovals, and it also removes the richer result.
Two limits worth stating plainly. There is no nutrition or allergen rich result, so additionalProperty can describe serving size or dietary suitability for machines but will not produce a visible enhancement. And review markup must describe reviews you collected on that product yourself. Aggregating ratings from retailer pages into your own markup is a policy problem, not a shortcut.
Can a brand outrank Amazon and the retailers?
For head category terms, usually not, and it is rarely the best use of the budget. Retailer and marketplace domains carry more links, fresher stock signals and more branded search than a single-brand site. A brand spending a quarter on a category head term is paying to lose slowly.
Win the queries where being the brand is the advantage:
Then defend the branded result. Consistent product naming across the site, pack shots with descriptive alt text, an accurate knowledge panel and clean sitelinks do more for brand queries than another blog post. Your syndicated titles on retailer sites matter too. If their title and GTIN are right, the shopper still lands on the right product when they search it.
- Exact product names with size or pack count, including common misspellings.
- Brand plus where to buy, including city variants where you have verified stockists.
- Comparisons between your own products, and against the category’s default alternative.
- Suitability questions: is it gluten free, how many servings per pack, how should it be stored.
- Support queries: delivery, subscription, cancellation and returns.
What earns links and trust in a regulated category?
In supplements, food, drink and cosmetics, the content that ranks is the content that can be defended. That means a named author with credentials where the topic touches health, sources cited on the page, and a review date that is visible and true. Claims that cannot be substantiated should not go on the page. Legal review belongs inside the publishing workflow, not after it.
Images do heavy lifting in this category and also cause damage. Packaging renders are large. Compress them, serve the right dimensions, and keep alt text descriptive rather than stuffed. Core Web Vitals on product templates usually move with image weight and third-party tags, not with copy.
- Data you own: formulation changes, packaging trials, your own sales or survey figures, published with the method.
- Sourcing and process pages that show origin, certification and manufacturing.
- Tools that solve a real task, such as a serving calculator or a recipe scaler.
- Packaging and recycling explainers for each material you use, with instructions.
- Commentary on regulation or category standards, attributed to a named person.
How do you measure CPG SEO when the sale happens elsewhere?
Direct attribution from organic search to retail sell-through does not exist in a reliable form. Anyone showing you a clean number is showing you a model. What you can measure:
Keep the promotion calendar next to the traffic chart. A price cut moves branded search, and without annotation you will credit content for a discount. If you need causal evidence, geo holdouts are the honest method, and they are slow and imperfect. Say so when you report.
The most useful habit is reviewing query classes rather than average position: brand, product name, size and format, suitability, where to buy. Each class has a different fix and a different owner.
- Search Console query mix split by brand and non-brand, by market and by page group.
- Entrances to product and where-to-buy pages, and clicks on stockist links.
- Merchant Center disapprovals and missing-attribute counts, tracked weekly.
- Retailer-side search terms and click share, where you are enrolled in a brand analytics programme.
- Retail sell-through plotted against the content calendar, treated as correlation unless a holdout has run.
Frequently asked questions
Does a CPG brand need its own website for SEO?
Only if the site has a job. For a brand sold entirely through supermarkets, that job is usually to own brand and product-name queries, host accurate where-to-buy information and publish content retailers will not. That is worth doing. Launching a full direct-to-consumer store with thin margins and no operational support is a separate decision, and search visibility alone will not make it work.
Should every flavour and pack size get its own page?
Only when a shopper can buy it on its own and someone searches for it. Give those options a unique URL with their own copy, price and availability. Options that exist only as filters should stay out of the index. The test is simple: does it have a distinct product name, barcode or price? If yes, it is a page. If no, it is a facet.
How do I do SEO for products only sold in shops?
Focus on brand and product-name queries, then make the path to a shop short. Build a where-to-buy page per product or range with a real stockist list and a store locator, keep the data current, and mark up the list so search engines can read it. Publish the usage, sourcing and comparison content retailers will not. Do not build a checkout you cannot support.
Can a brand outrank Amazon for its own product name?
Usually for the exact product name plus size or pack count, because the brand can offer the canonical description, the full ingredient list and the packaging images. It is less reliable for the shorter product name, where a retailer with stock and links often leads. Track the two separately, and keep your page accurate rather than duplicating a marketplace listing.
Do GTINs affect search rankings?
Not directly. Google does not rank pages by barcode. GTINs matter because they connect your product to the same product on retailer sites, in Merchant Center feeds and in image search. A missing or wrong GTIN causes feed disapprovals and weakens product identity across the web, which costs visibility in merchant listings. Use the real barcode, and leave the field empty if you do not have one.
Sources
- Required and recommended properties for product structured data, including name, brand, gtin and offers
- Merchant listing markup requirements for price, availability and condition on purchasable pages
- schema.org Product type used for product name, brand, GTIN and variant relationships
- schema.org Offer type used for price, price currency, availability and condition
Start with the catalogue, not the keyword list
The audit checks variant URLs, product markup, feed accuracy and where-to-buy pages against the queries your buyers actually use. You get a prioritised fix list with an owner for each item.