Most PrestaShop SEO problems come from seven default settings. Three affect URLs: ID numbers, filter URLs and combination URLs. Two affect languages: copied meta tags and empty image captions. The last two are the 404 page for offline products and hreflang that stops at one shop. You fix each one in the back office, robots.txt, the theme or a module.
Key takeaways
- URLs: PrestaShop keeps an ID number in every product and category URL. Keep it, unless you plan a full move with 301 redirects.
- Redirects: a new install sends duplicate URLs to the canonical URL with a 302. PrestaShop’s own label recommends 301 once the store is live.
- Filters: PrestaShop 9 blocks filter URLs in the robots.txt it generates. PrestaShop 8 does not, so you add two lines by hand.
- Languages: a new language starts as a copy of the default language, with its meta tags, friendly URLs and image captions.
- Multistore: PrestaShop adds hreflang only for the languages of the current shop, with no x-default.
- Bottom line: fix the redirect setting and robots.txt first, then write titles and captions per language for your best-selling products.
PrestaShop SEO problems and fixes
Seven PrestaShop SEO problems come from how the software builds URLs, copies texts between languages and handles old products. Each one has a fix in the back office, robots.txt, the theme or a module. Some defaults changed in PrestaShop 9, so check your version before you change anything. The table lists what PrestaShop does in each case and the first fix to make.
The sections below explain each fix and the setting behind it.
| Problem | What PrestaShop does | First fix |
|---|---|---|
| ID numbers in URLs | Adds the product or category ID to every friendly URL | Keep them, unless you plan a full move with 301 redirects |
| Filter URLs | Writes filters into a q parameter, which PrestaShop 8 leaves open to Google | Block ?q= and &q= in robots.txt |
| Combinations | Gives each combination its own URL, with a canonical tag to the main product | Keep the canonical tag and add ProductGroup variant markup |
| Copied meta tags | Copies all texts of the default language into each new language | Write titles and descriptions for each language |
| Image captions | Uses the caption as alt text, or the product name when the caption is empty | Write one caption per photo and per language |
| Discontinued products | Shows a 404 error page by default when a product is offline | 301 to a replacement, or 404 or 410 when none exists |
| Multistore and hreflang | Adds hreflang only for the languages of the current shop | Add hreflang between shops and an x-default |
PrestaShop friendly URLs and ID numbers
PrestaShop puts an ID number in every product and category URL, such as 27-red-dress.html, and the core settings cannot remove it. Keep the number. The URL still has readable words, and removing the ID changes every product and category URL at once. Two settings in Shop Parameters > Traffic & SEO matter more: Friendly URL and Redirect to the canonical URL.
Google asks for readable words instead of long ID numbers. Its example of a bad URL is a long string of parameters, such as topic=42&area=3a5ebc944f41daa6f849f730f1. A short number in front of the product name is far from that.
Turn on Friendly URL, so URLs show words instead of parameters such as id_product=27. Then set Redirect to the canonical URL to 301. A new install starts at 302, and PrestaShop’s own label recommends 301 once the store is live.
If you still want to remove the ID, you need a module. Google asks you to redirect each old URL with a 301 and keep the redirects for at least a year. It also says to expect rankings to move while it crawls the new URLs.
- Open Shop Parameters > Traffic & SEO and check that Friendly URL is on.
- Set Redirect to the canonical URL to 301 Moved Permanently.
- Write the friendly URL of your top products by hand, with the words people search for in each language.
PrestaShop faceted search and filter URLs
The Faceted search module writes every filter into a q parameter, such as ?q=Color-Red. Each mix of filters makes a new URL. Google says these URLs make crawlers spend time on pages that bring little or no benefit. Its first advice is to block them in robots.txt. PrestaShop 9 does this by default. PrestaShop 8 does not, so you add the rules yourself.
In PrestaShop 9, filtered and sorted pages also get a noindex tag, and the robots.txt that PrestaShop 9 generates blocks ?q= and &q=. PrestaShop 8 has neither.
In PrestaShop 8, the module adds nofollow to the filter links. Google says nofollow works only when every link to a URL carries it. It also calls nofollow and canonical tags less effective in the long term than robots.txt.
- Open yourstore.com/robots.txt and check that it contains Disallow: /*?q= and Disallow: /*&q=.
- If the lines are missing, copy your custom lines first, because Generate robots.txt file replaces the old file. PrestaShop 9 adds the q lines itself. On PrestaShop 8, add them by hand after you generate the file.
- For a filter that people search for, such as one brand in one category, create a real category with its own text. Google asks for & between parameters in filter URLs you want indexed, and the q format joins filters with a slash.
PrestaShop combinations and canonical tags
Each combination of a PrestaShop product has its own URL, such as 12-45-t-shirt.html, where 45 is the combination ID. The canonical tag on every combination points to the main product URL. That tells Google to index one page for all sizes and colours, which is right for most products. Change it only for colours or versions that people search for by name.
Google lists redirects and canonical tags as strong signals for the URL it should index. The Classic theme prints the canonical tag on every product page, so you need no module for it.
The structured data in the Classic theme describes one Product with one offer. For products with variants, Google asks for ProductGroup markup with hasVariant and variesBy, so each variant has its own URL and offer. Google also asks that each variant opens directly at its own URL, and PrestaShop combination URLs already do that.
A colour that gets its own product page also needs its own photos. Our AI content service makes product and catalogue images for pages like these.
- Sizes: one page per product is right, so keep the canonical tag as it is.
- Colours that people search for, such as “red leather bag”: make that colour a separate product with its own text and photos.
- Variant markup: add ProductGroup in the theme or with a module, then test a product page in Google’s Rich Results Test.
PrestaShop meta titles and descriptions per language
When you add a language, PrestaShop copies every text of the default language into it. That includes meta titles, meta descriptions, friendly URLs and image captions. Until you translate them, the new language shows the words of the old one. Google tries to show a title in the language of the page. It can replace a title left in the wrong language with other text.
Google decides the language of a page from its visible text. It does not use the lang attribute or the URL to decide it.
Empty fields have a fallback. An empty meta title becomes the product name, and an empty meta description becomes the Summary text without HTML. Neither one uses the words that people type in each country.
- Check the meta title and meta description of your best-selling products first, one language at a time.
- Write titles and descriptions with the words people search for in each country, instead of a word-for-word translation.
- Translate the friendly URL too, and keep the ID number in front of it.
PrestaShop image alt text and captions
PrestaShop uses each image caption as the alt text of the photo. When the caption is empty, the Classic theme uses the product name, so six photos of one product share one alt text. Write one caption per photo and per language that says what the photo shows. Google uses alt text and the content of the page to understand an image.
Google also asks you not to fill alt text with keywords. It says keyword stuffing gives people a bad experience and can make the site look like spam.
- Write what the photo shows, such as “black leather bag, side view”.
- Write captions in each language, because a new language copies the captions of the default language.
- Start with the cover photo, the first image people see on the product page.
Out-of-stock and discontinued products in PrestaShop
Keep out-of-stock products online, and use a redirect or an error code only for products that will not return. An online product without stock keeps its page. PrestaShop marks it OutOfStock in structured data, or BackOrder when you allow orders. For an offline product, a new install shows a 404 error page unless you choose another option.
The SEO tab of each product has a field called Redirection when offline. You can show a 404 or 410 error page, or redirect with a 301 or 302 to a product or category. You can also keep the product page with a discontinued label and a 200, 404 or 410 code.
Google treats 410 like 404 and says 404 errors do not harm your indexing or ranking. It warns against sending old URLs to the home page instead of returning a 404.
- A replacement exists: 301 to the new product.
- No replacement, but a close category exists: 301 to that category.
- Nothing related exists: a 404 or 410 error page.
- Avoid 302 for products that will not return, because Google keeps showing the old URL in search results.
PrestaShop multistore and hreflang
PrestaShop adds hreflang links for the active languages of the current shop. It adds no x-default and no links to the same product in your other shops. That works for one shop with several languages. When each country has its own shop, such as one on .es and one on .fr, you add hreflang between the shops yourself.
Google uses hreflang only when the pages point to each other. Each version must list itself and every other version, and the alternate URLs can sit on different domains. You can put the links in the page head, in HTTP headers or in the XML sitemap. Google treats the three methods the same.
We use the sitemap method on the RNJ Transport website we built: 11 languages, with x-default pointing to the English pages. RNJ does not run PrestaShop, but the hreflang rules are the same for any site.
- Add hreflang between shops with a module, a theme change or the XML sitemap.
- Link each version of a product to all the others, and add an x-default for visitors whose language has no version.
- In PrestaShop 8, a second language adds a code such as /en/ to every friendly URL, also in the default language. Check that each old URL redirects with a 301. In PrestaShop 9, check that Use prefix for default language is off. It is off on a new install.
- When you remove a language, redirect its URLs with a 301. CreatorFlow, the SaaS company that our co-founder Vytas runs, did this with Romanian and Czech, which now redirect to English.
PrestaShop SEO checks in Google Search Console
Google Search Console shows most of these problems in the Page indexing report. Open it before you change anything and again after each fix. Read the reasons why pages are not indexed. Duplicate URLs, old products sent to the home page and blocked filter pages each have their own reason. That shows you which fix to make first.
Two reasons point to duplicate URLs: Duplicate without user-selected canonical, and Duplicate, Google chose different canonical than user. In a PrestaShop store, check combinations and URLs without the 301 canonical redirect first.
Soft 404 lists pages that Google reads as errors, such as old products redirected to the home page. Indexed, though blocked by robots.txt lists blocked URLs that Google indexed anyway, such as filter pages that other pages link to.
Before every discovery call, AI for Marketing Ops checks the top 10 SEO problems on your product pages. Our PrestaShop SEO and catalogue management service fixes problems like these inside your store. Our SEO service for online stores covers category pages, guides and AI search. You can also read how we work with ecommerce companies.
Common questions
Is PrestaShop good for SEO?
Yes. PrestaShop has friendly URLs, canonical tags, meta fields in each language, product structured data and hreflang inside a shop. The problems in this guide come from default behaviour and empty fields. You can fix each one in the back office, the theme, a module or robots.txt.
Can I remove the ID numbers from PrestaShop URLs?
Not with the core settings. The PrestaShop documentation says the ID cannot be removed by default, so you need a module. Every product and category URL then changes. Google asks you to redirect each old URL with a 301 and keep the redirects for at least a year. Expect rankings to move for a while.
Should the canonical redirect be 301 or 302 in PrestaShop?
Use 301 once the store is live. A new install starts at 302, which PrestaShop labels as the choice while you build the store. For a temporary redirect, Google keeps showing the source page in search results. A permanent redirect tells Google to index the target URL.
Should I let Google index PrestaShop filter pages?
Only filters that match real searches, such as one brand in one category. Make those real categories with their own text and title. Block the other filter URLs in robots.txt. Google says crawling most filtered URLs brings little or no benefit and costs server resources.
What should I do with out-of-stock products in PrestaShop?
Keep them online. The page stays, and PrestaShop marks the product OutOfStock in structured data, or BackOrder when you allow orders. Use a 301 redirect, a 404 or a 410 only for products that will not return.
Does PrestaShop add hreflang tags by itself?
Yes, inside one shop. The default themes add hreflang for every active language of the current shop. They add no x-default and no links between shops in a multistore setup. You add those with a module, a theme change or the XML sitemap.
Do you work with PrestaShop stores?
Yes. PrestaShop SEO and catalogue management is one of our services, and we work with stores on PrestaShop, WooCommerce, Magento and Shopify. We work in Spain and the rest of Europe, in Spanish and English. Most projects go live in 10 working days. We agree the scope and the price in writing before work starts.
Sources and checks (35)
- PrestaShop documentation: SEO and URLs
- PrestaShop documentation: Managing products
- PrestaShop documentation: Setting a store’s URL (multistore)
- PrestaShop 9.0.1 source code: default URL routes
- PrestaShop 9.0.1 source code: settings on a new install
- PrestaShop 9.0.1 source code: canonical redirect options
- PrestaShop 9.0.1 source code: noindex on filtered and sorted pages
- PrestaShop 8.2 source code: listing pages without noindex
- PrestaShop 9.0.1 source code: robots.txt rules
- PrestaShop 8.2 source code: robots.txt rules
- PrestaShop Faceted search module: filter URL format
- PrestaShop Faceted search module: nofollow on filter links
- PrestaShop 9.0.1 source code: new languages copy the default language
- PrestaShop 9.0.1 source code: meta title and description fallbacks
- PrestaShop Classic theme 3.0.6: image alt text
- PrestaShop Classic theme 3.0.6: product structured data
- PrestaShop 9.0.1 source code: canonical URL and stock status in structured data
- PrestaShop 9.0.1 source code: Redirection when offline options
- PrestaShop 9.0.1 source code: hreflang languages of the current shop
- PrestaShop Classic theme 3.0.6: hreflang and canonical tags
- PrestaShop 8.2 source code: language code in URLs
- PrestaShop 9.0.1 source code: Use prefix for default language
- Google Search Central: URL structure best practices
- Google Search Central: Site moves with URL changes
- Google Search Central: Managing crawling of faceted navigation URLs
- Google Search Central: How to specify a canonical URL
- Google Search Central: Product variant structured data
- Google Search Central: Influencing your title links
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Image SEO best practices
- Google Search Central: Merchant listing structured data
- Search Console Help: 404 errors
- Google Search Central: Redirects and Google Search
- Google Search Central: Localized versions of your pages
- Search Console Help: Page indexing report