The supplier's description on your product pages: why it doesn't rank and where to start

You import the supplier’s catalogue from their CSV or XML and in one afternoon you have thousands of product pages with name, photo, price and description. It is convenient, and it is what almost everyone does. That is exactly why those pages compete at a disadvantage: the same text is on the manufacturer’s website, on the marketplaces and on every store that works with that distributor.

It is not a penalty. It is that, faced with several nearly identical pages, the search engine has to choose one, and it will rarely be yours.

What really happens with duplicate text

It is worth clearing up a misunderstanding: Google does not penalise a store for using the manufacturer’s description. What it does is group the pages that say the same thing and show one in the results, usually the one it considers most relevant or authoritative. The rest stay in the background for that search.

Who usually wins that share-out?

• The manufacturer’s website, which is the original source.
• The big marketplaces, with enormous domain authority.
• Stores with more links, more reviews or more history in that niche.

A mid-sized store with the same text as all of them has few options. And even if it does appear, the customer comparing sees the same content in five tabs: the decision ends up being about price alone.

This problem is different from internal duplicate content (the same product page reachable through several URLs, filters that generate near-identical pages, combinations indexed separately), which is solved with canonicals and indexing control. Here we are talking about external duplication: your text exists outside your store.

What the supplier does not give you

The manufacturer’s description is designed to serve every distributor at once. That is why it lacks what makes a particular store sell:

• Who it is for in your market: a German manufacturer does not know what your customers ask.
• Comparison with what sits next to it in your catalogue: when to choose this one and when the other.
• Hands-on experience: what your team knows from having sold it, assembled it or had it returned.
• Practical information: lead times, compatibility with what you sell, which accessory it needs.
• Adapted language: many descriptions arrive machine-translated or simply in English.

They also often come with formatting problems: messy HTML pasted from a PDF, tables that break on mobile, capital letters everywhere, or texts that mention manufacturer promotions or guarantees that do not apply in your store.

How to prioritise: don’t rewrite eight thousand pages

Rewriting the whole catalogue at once is not realistic, nor necessary. Most sales and visits tend to be concentrated in a small share of the products. Start there.

1. Products that already sell

These get the most out of a better page: if they already convert with the supplier’s text, your own can help them convert more and defend their position.

2. Products with impressions and few clicks

In Search Console, the Performance report filtered by page shows product pages that appear in searches but are not chosen. They usually have a generic title and meta description, sometimes the same as every other store. A good title and meta of your own are the first change, and the cheapest.

3. High-margin or exclusive products

If you have a product that few stores sell, an excellent page can take that search almost on its own.

4. Categories before individual products

Your own useful text on the category (what types there are, how to choose) benefits all its products and usually competes for broader searches.

5. The long tail, methodically

For the rest, an AI-assisted rewrite based on the real features, with a template per family and spot-check reviews, gives correct and distinct pages without spending hours on them.

What to keep from the supplier

Not everything from the manufacturer needs throwing away. Some data must be exact and is best kept as is:

• Technical specifications, ideally as PrestaShop features rather than text: they are used for filtering and for structured data.
• Legal or safety information: warnings, composition, mandatory instructions.
• References and codes: EAN, manufacturer reference, official compatibility.

The structure that usually works: an opening paragraph of your own that answers who it is for and why to choose it, benefits as a list, specifications as features and, if the product calls for it, a few FAQs.

Watch out for the next import

The classic mistake: you rewrite two hundred pages and the supplier’s next catalogue update overwrites them with the original text. Before you start, review your import process and set it to update price and stock but not descriptions for products you have already worked on. If the importer does not allow that, it is a good reason to change method.

And one more general recommendation: if your store is still on an old version of PrestaShop, many current connectors and import modules no longer support it, and you end up with fragile manual processes. Keeping the store up to date also protects your content work.

How to measure whether it worked

• Note which pages you rewrite and when.
• In Search Console, compare impressions, clicks and CTR for that group in the following weeks against the previous ones, and against a similar group you have not touched.
• Look at the conversion of those pages in your analytics and at returns for “not what I expected”.

Changes in search engines take weeks and depend on many factors. Nobody can guarantee you rankings; what you can do is make sure your pages give a reason to be chosen.

How to solve it in PrestaShop

Easy AI Magic Catalog Suite is designed for catalogues with descriptions copied from the supplier: it generates texts in bulk as drafts that you review before applying, with a history to undo, extracts specifications from descriptions and turns them into features, fills in pages with data by EAN and adds bullets and FAQs. Its AI Category Audit cross-references sales, stock, clicks and Search Console average position by category, which helps decide where to start. If you would rather we did it, Rekire’s AI-powered technical SEO service works directly on your PrestaShop: product pages and categories, metadata, architecture and indexing, applying the changes in the store instead of handing you a report.