Product Canonical Manager gives your PrestaShop pages one reference address for search engines and connects competing versions to it. A guided setup establishes your first shopwide policy in minutes.
Filters, campaign parameters and language paths create several addresses for the same content. The module groups these duplicates in a report and assigns the destination that should collect their search signals.
You choose whether rules replace an existing canonical address, fill a missing one or use your own destination. Priorities resolve overlaps, and destinations are stored per language and shop. Address cleanup leaves catalogue records unchanged.
The coverage dashboard shows which rule handled each page, so your team traces address decisions after catalogue changes from one place.
Product Canonical Manager turns canonical addresses, hreflang relationships and search engine indexing instructions into one store policy. A guided setup handles the common case in minutes, while the visual rule editor covers complex catalogues with previews, priorities and store scope.
A rule targets one page, a selected group or every matching page. Products, categories, CMS pages, CMS categories, manufacturers, suppliers, the home page, search results, module pages and custom routes all use the same editor. Product selections include categories, brands, suppliers, tags, attributes and features, with inclusions and exclusions shown before the rule is saved.
Broad and narrow rules work together because every rule has a priority. The first matching address rule decides the canonical destination, while compatible indexing instructions from other matching rules remain in force. A German product family, one supplier range and a single exception therefore stay understandable inside the same policy.
The built in scan finds pages whose content is reachable through several addresses and groups the alternatives under the chosen destination. Its report identifies tracking values, referral values, session values, sorting, filters, pagination, secure and non secure forms, and duplicate canonical declarations. Each row shows the affected page and the rule that resolves it.
On the storefront, the module leaves one deterministic canonical address even when the theme supplied none, one or several. It removes only the parameters listed in the settings, handles pagination separately, and applies the chosen lowercase and trailing slash conventions without changing the catalogue record. Ranking signals therefore gather around the address selected for sale and search.
Custom canonical destinations are stored per language. The module builds a complete hreflang relationship for active languages, adds one x-default destination and validates the self reference and return links. Regional domains and language specific addresses remain separate, so a local product page is not folded into the wrong master version.
In a multistore installation, a policy is global or belongs to a selected store. Shared rules provide the common foundation, store rules handle local catalogues and domains, and explicit precedence resolves overlaps. The dashboard reports each store separately as well as the inherited policy.
Each rule uses one of three clear conflict policies: replace the existing canonical address, add the clean address only when none exists, or use a custom destination. The same rule marks matching pages noindex, nofollow or both while preserving other compatible search engine instructions already present on the page.
Rules are paused, their priorities are changed and they are deleted from the list. Import and export move multilingual destinations, selections, priorities, states and store scope between shops, with a dry run that identifies conflicts before anything changes. When a product, category, CMS page, manufacturer or supplier disappears, its direct rules disappear with it.
The dashboard reports active rules, exact page coverage by type and store, pages excluded from results, language relationship status, cleanup settings and recent changes. A generated address journal records which rule handled each page and which canonical and hreflang entries were written, so a theme change, catalogue import or campaign has a visible before and after result.
Installation diagnostics confirm that the rule data and storefront processing are intact. All changes are applied as the page is prepared, with nothing extra loading for shoppers and no customer, order or browsing profile stored. The quick start remains small, while the evidence and configuration stay detailed enough for a large international catalogue.
30 days return right
Plug & Play Modules
Dedicated Support First
Built and maintained by David Miller and mypresta.rocks. David Miller has worked with PrestaShop since 2013, and the company behind this shop has been registered since 3 December 2018. Every module in this catalogue is our own work, so your questions to support reach the people who wrote the code. The changelog on this page lists every update with its date.
Filter Revolution creates many filtered views of your categories on SEO-friendly URLs, and Product Canonical Manager gives you control over canonical URLs and noindex or nofollow directives. You decide which pages should rank and which only serve shoppers.
Smart Search Revolution can publish indexable search landing pages, and Product Canonical Manager gives you control over canonical URLs and noindex or nofollow directives. Search pages that help you rank without creating duplicate content.
Category Listing Rules sets products per page and the default sort order for each category, and Product Canonical Manager keeps duplicate URLs under control with canonical tags and noindex or nofollow directives. Shoppers get well-organized listings and search engines see one clear version of each page.
Compliance & Legal
News & Updates
News & Updates
News & Updates
News & Updates
News & Updates
