How does structured data / schema markup help my store?

PrestaShop schema, also called structured data, is a small extra layer of code that tells search engines what each piece of content on your page represents: a price, a stock state, a product, a rating, a breadcrumb trail or an FAQ entry. Search engines can use that data for eligible rich result features such as product price and stock snippets, review stars where supported, breadcrumb links, or FAQ-style presentation where the search engine still supports it.Rich results do not push your page higher in the ranking on their own, but they can make the listing more useful and easier to trust. For a store, the schema types that usually matter are Product, Offer, AggregateRating/Review, BreadcrumbList, Organization, WebSite, CollectionPage, Article and, where appropriate, FAQPage.Our Automatic SEO Schema Rich Snippets module attempts to add Product, Offer, rating/review, breadcrumb, Organization, WebSite, category and CMS-page markup without template editing. The same schema functionality is also part of the Smart SEO Revolution Suite if you also want sitemaps, canonicals and meta-tag automation in one place.Important current-code caveat: the module outputs JSON-LD from hookDisplayHeader, but clean_existing_jsonld is enabled by default and the final-output cleanup preserves only JSON-LD scripts containing the marker. The header hook currently emits unmarked JSON-LD, so with JSON-LD cleanup active the final HTML can remove the module's own schema. Until the renderer marks its scripts or the cleanup logic is disabled/fixed, verify the final page source before treating the JSON-LD as reliably present.On product pages, the Product schema can include the product name, URL, description, SKU, GTIN/UPC/ISBN/MPN identifiers, manufacturer/supplier/feature-based brand data, images, item condition, offer data, weight, category and review data when the shop has that data. The brand generator uses the configured catalogue source, such as manufacturer, supplier or a feature named like Brand, with a manufacturer fallback; the declared override-brand field is not used by the current generator. Offer data can include price, currency, availability, seller, shipping details and return policy. For products with combinations, the implementation can build aggregate offer data instead of pretending every variant has one identical offer.Category pages are handled differently: they are rendered as CollectionPage data with a category name, URL, description, image, number of items and an ItemList sample of products. CMS pages are rendered as Article schema with headline, URL, description, article body, word count, dates, author, publisher, logo, language and main entity URL.The practical merchant rule is to fill the underlying data, not just switch schema on. If a product has no identifier, weak images, no stock state, no reviews or an empty description, the schema can only describe that weak data. Structured data works best when your catalogue data is already clean, and in the current module you should also check that cleanup settings are not removing the JSON-LD you expect to publish.

Can I add hreflang and noindex rules to PrestaShop pages?

Yes. With the Product Canonical Manager you set per-entity rules for products, categories, manufacturers, suppliers and CMS pages, and it writes noindex and nofollow into the page's robots meta tag. The same module regenerates hreflang tags from your active shop languages and adds x-default for your default language, so each language version points at the right alternates.Product Canonical Manager, per-entity canonical, noindex and hreflang rules, with auto-hreflang and parameter stripping.In the page the rules render as the standard tags search engines read, a single canonical, the robots directive, and one hreflang alternate per language plus x-default: This keeps thin or duplicate pages (filtered listings, internal search, account pages) out of Google's index while your real products stay indexable, and it tells Google which language to serve to which audience. A common mistake is adding noindex and a canonical that point in different directions on the same URL; decide per page whether you want it indexed-but-canonicalised or fully noindexed, not both at cross purposes.The Smart SEO Revolution Suite shares the same canonical, hreflang and noindex engine, so the same per-entity rules are available there too.Rules have a priority and shop scope. The lookup accepts the exact entity ID or entity ID 0, and exact or shop-global rules can be ordered by priority. That lets you create a broad rule for all products, then override one important product, category or CMS page without duplicating every setting.The robots tag is built only from the directives you choose. If you tick noindex, the module adds noindex; if you tick nofollow, it adds nofollow; if neither is selected, it does not invent a robots tag just to be visible. Existing robots tags are replaced when a rule applies, so you avoid two conflicting robots meta tags in the same head.Hreflang generation only makes sense on multilingual shops. The module checks active languages, generates alternate URLs for each active language and adds x-default for the configured default language. It also removes existing hreflang tags before inserting its own, which helps avoid duplicate alternate clusters from the theme and the module both trying to own the same signal.Use noindex carefully with sitemaps. A noindexed URL should not be promoted as an indexable sitemap URL, and the SEO Suite's policy tables include separate index, hreflang, sitemap and schema overrides for that reason. Keep the signals aligned: indexable pages get canonical and hreflang; intentionally hidden pages get noindex and should normally stay out of the XML sitemap.

What is the difference between an XML sitemap and an HTML sitemap?

An XML sitemap is a machine-readable file written for search engines. It lists URLs together with metadata (last-modified date, hreflang alternates, image references) and is submitted to Google Search Console or Bing Webmaster Tools. Its job is discovery: helping crawlers find and prioritise pages they might otherwise miss.An HTML sitemap is an ordinary page on your shop, made for human visitors. It lists links to categories, products, CMS pages and manufacturers in a readable structure. Its job is navigation and internal linking. It gives visitors a backup index and gives crawlers another set of links into deeper pages.You generally want both: the XML sitemap is the one search engines actually consume, while the HTML sitemap is optional but handy on large catalogues. Our Advanced SEO Sitemap Builder generates XML sitemaps with hreflang alternates and image entries, automatically splits large catalogues at the 50,000-URL search-engine limit into a sitemap index, and can publish an HTML sitemap page as well.The sitemap builder is not just a URL dump. Its module description and pipeline are built around verified XML sitemaps: URLs can be crawled and checked for HTTP status, canonical and noindex before being written. The stored URL rows include entity type, language, shop, status, canonical and image/hreflang metadata, so the final sitemap can be based on URLs that passed verification rather than every possible catalogue URL.For XML output, the writer includes the standard sitemap namespace and adds image and XHTML namespaces when image or hreflang output is enabled. Each URL can receive , , , , image entries and alternate-language links. Large output is split by the configured maximum URL count and file size, and a sitemap index points crawlers at the generated files.The HTML sitemap is different by design. It uses verified URLs for the current shop and language, groups them by type such as home, product, category, CMS, manufacturer, supplier, core, hook or custom, and renders them as a normal page. In the inspected front controller the HTML sitemap page is marked noindex, so treat it mainly as a user navigation and internal-linking page, not as another landing page you expect to rank.For merchants, the practical setup is: enable the entity types you actually want indexed, keep image and hreflang output on for multilingual/image-heavy catalogues, submit the XML sitemap index in Search Console, and link the HTML sitemap only where it helps visitors.

How long does it take to see SEO improvements after installing a module?

Be realistic: an SEO module puts the technical signals in place, schema markup, cleaner URLs, canonical tags and internal linking, but when those changes show up in search results depends on Google, not the module. Google has to recrawl and reprocess your pages first, and that timing varies from store to store: it can be days for some pages and much longer for others, depending on how often Google revisits your store. No one can put a fixed date on it.A few things help the early signals along: submitting a fresh XML sitemap, fixing 404s and redirecting old URLs so crawl budget lands on pages that matter. Those are exactly the levers our Smart SEO Revolution Suite handles. What no module can do is promise rankings on a fixed date. Anyone selling overnight results is misleading you. We run shops too, so we set expectations honestly: SEO is a long game, and a good module shortens the technical part of it, not Google's clock.

Does the Alt Tags module handle images I add in the future?

Yes. That is exactly how it works. Automatic SEO Images Alt Tags does not write alt text into your database when you install it. It sets the alt (legend) on the fly, every time a product, listing or category page is rendered, by hooking into PrestaShop's presenter layer. Upload a new product image and it is covered automatically. No re-run, no batch job.Templates combine tokens like {product_name}, {category}, {category_name}, {manufacturer}, {image_position} and product identifiers ({reference}, {ean13}, {isbn}, {upc}, {mpn}), with a separate template per shop language so each storefront gets a localised alt tag.One safety rule: by default the module never overwrites alt text you typed by hand, it only fills empty fields. You can switch on override if you want every image driven by the template. The default max length is 125 characters.The module registers presenter hooks for product pages, product listings and category pages. On a product page it updates the cover image, default image and gallery images. On listings it updates the presented product cover/default image and image list. On category pages it updates the category image legend. Because this happens in the presented data, it stays compatible with cache and does not require scanning or rewriting rendered HTML.The default templates are simple and safe: product pages use {product_name} - {manufacturer}, listing pages use {product_name} - {category}, and category pages use {category_name}. You can change them to include references or identifiers, but keep the result readable. Search engines and screen readers both prefer useful text over a stuffed list of attributes.The builder cleans the generated alt text before returning it: it replaces variables, strips HTML, decodes entities, collapses repeated spaces and trims separators left empty by missing variables. It then truncates to the configured maximum length at a word boundary where possible. That means a missing manufacturer should not leave an ugly dangling template, and a very long product name should not produce an oversized alt attribute.The practical workflow is to set a product template, listing template and category template once, leave override off unless you want to replace hand-written legends, then check a product page and a listing page in the browser source. Future images follow the same rules automatically because the hook runs every time the page is presented.

Can I use your SEO modules together with Yoast or another SEO plugin?

Short version: Yoast is a WordPress plugin and has no PrestaShop equivalent, so there's nothing to integrate with there. If you mean another PrestaShop SEO module, our modules can run alongside it. The thing to manage is overlap.The risk with any two SEO tools is duplicate output: two canonical tags, two sets of Open Graph tags, two JSON-LD blocks. Search engines dislike that. So decide, per feature, which tool is the source of truth and turn the duplicate off in the other.Our own modules are built to cooperate, not collide. The Smart SEO Revolution Suite actively de-duplicates against the theme: when it renders its own hreflang or Open Graph tags, it strips the theme's matching tags from the page head, and it can optionally clean foreign JSON-LD too. Blog Revolution goes further and hands blog structured data over to SEO Revolution when that module is set to emit it, so you never get two blog schemas.Common mistake: enabling the same feature in two modules and assuming "more is better." Pick one owner per feature and you'll have clean, single output.

My Google Search Console shows many "Page is not indexed" warnings. Can your modules help?

Partly, and it depends on the reason Google lists next to each URL. Be honest with yourself first: no module can force Google to index a page. What we can do is fix the technical reasons Google often gives.Discovered/crawled, not indexed, or missing sitemap: the Advanced SEO Sitemap Builder generates a verified XML sitemap and can ping Google and Bing when it changes, so good URLs are easy to find.Duplicate / alternate page with canonical: handled by the canonical and noindex rules in the Smart SEO Revolution Suite, which also manages 301/302 redirects for URLs that moved.The rest is content and server work the module can't do for you: thin or near-empty pages, pages Google judges low value, or server errors. Open the exact reason in Search Console per URL, fix that cause, then resubmit. A common mistake is keeping pages in the sitemap that you've also set to noindex, the sitemap builder skips noindexed and non-200 URLs so you don't send Google mixed signals.

Does a PrestaShop canonical manager create 301 redirects?

No. The Product Canonical Manager does not issue 301 redirects. It rewrites the HTML head of your storefront pages instead: it replaces or adds the canonical tag, sets robots noindex/nofollow where you choose, regenerates hreflang tags from your active languages, and tidies canonical conventions (strip parameters, force lowercase or trailing slash). The URL the visitor requested stays the same.This matters because canonical tags and 301 redirects solve different problems. A canonical tag tells Google which version to index while every variant stays reachable; a 301 actually moves a URL and is the right tool when an address has permanently changed. A common mistake is reaching for redirects to fix duplicate parameter URLs (sorting, filters, tracking tags) when a canonical is the cleaner fix and keeps those pages working for shoppers. The Product Canonical Manager modifies the head tags only and leaves the requested URL unchanged.In the code, the module works through hookActionOutputHTMLBefore. That hook receives the finished HTML, checks that a section exists, resolves the current page entity, and then changes the canonical, robots and hreflang tags before the response is sent. There is no redirect response, no HTTP status change and no request URL rewrite in that path.Rules are stored by entity type and entity ID, with shop scope, priority, active flag and language-specific custom canonical URL. The supported entity types are products, categories, CMS pages, manufacturers and suppliers. A rule can target one specific entity or use entity ID 0 as an all-entities rule, so you can create a broad fallback and then override it with a higher-priority specific rule.The canonical action also matters:override replaces an existing canonical with the computed or custom URL.custom uses the custom URL stored for the language.add missing only inserts a canonical when the page has none.Parameter stripping is applied to the canonical URL, not to the shopper's visible URL. The default stripped parameters include common tracking values such as utm_source, utm_medium, utm_campaign, fbclid, gclid and msclkid. That is why the module is useful for duplicate URL cleanup without breaking filter, sort or campaign URLs that customers may still use.

Does the Internal Linker module add links automatically or do I have to configure every link?

Yes. Internal Linker can automatically insert links when the page is rendered, based on link groups that map keywords to a target URL. It does not need you to manually edit every product, category, CMS, or blog description, and it does not rewrite the saved text in the database.A typical link group could look like this:Group name: Shower screen SEOTarget URL: /en/shower-screensKeywords: shower screen, walk-in screen, glass shower panel, shower enclosure|shower partition, shower*Page types: product, category, cmsContent zones: product description, category description, CMS contentMax links from this group: 2Link position: firstKeywords can be comma-separated, language-specific, and can use variants with |. Wildcard-style terms such as shower* are supported by the module keyword configuration.The module also has safeguards to keep the output natural: it can skip the current URL, avoid headings, avoid already-linked text, prevent duplicate target URLs, and limit the total number of links per page or per group. This makes it useful for SEO linking patterns such as linking repeated product terms to important category or guide pages without creating excessive internal links.The module runs on actionOutputHTMLBefore, so it receives the final storefront HTML and modifies only the response sent to the visitor. It skips non-front-office output, AJAX requests, non-HTML responses and content that does not look like HTML. The shared injector then extracts the and works inside configured content regions, leaving the , scripts and JSON-LD alone.Default settings are conservative: max_links_per_page is 5, max_links_per_group is 3, default selectors include product descriptions, description blocks, page content and post content, and default allowed tags are p, div, span, blockquote, li and td. The default class for generated links is mpr-autolink, current-page targets are skipped, headings are excluded, and multiple autolinks in the same element are prevented.Content zones make the setup easier than writing selectors by hand. The resolver maps merchant labels such as product description, category description, CMS content, blog content, manufacturer description and supplier description to common theme selectors, and it filters them by page type. You can still override CSS selectors and HTML tags per group if your theme has unusual markup.The injector counts existing links inside the target content regions and reduces the available budget for a group when the page already links to the same target URL. It also supports link placement strategies: first, middle, last and spread. This is useful when a keyword appears many times in a long guide and you want only one natural link rather than every occurrence becoming an anchor.For target URLs, you can enter a URL manually or choose a PrestaShop entity. The admin form supports products, categories, CMS pages, manufacturers and suppliers, and can resolve the selected entity to its front-office URL. Language-specific keyword and target URL overrides are available, so a multilingual store can use local anchor text instead of forcing one language's phrases into every storefront.

Will hreflang tags fix my multilingual SEO problems?

Hreflang tags fix one specific problem well: they tell Google which language or country version of a page to show each visitor, so your translated pages stop competing with each other as near-duplicate content. For a multilingual PrestaShop store they are not optional, but they are one part of the job, not the whole of it.Hreflang settings, language/country alternates for multilingual SEO.What hreflang will not do is rescue thin or machine-quality translations, fill in pages that only exist in one language, or fix inconsistent URL structures across your shops. Those need real content and clean URLs underneath the tags. Our Smart SEO Revolution Suite generates hreflang automatically for every active language, adds a proper x-default, stays multi-shop aware, and also includes the same references inside your XML sitemap. Get those signals right and Google can match the correct version to each searcher; the translation quality is still your call.In the SEO Suite, hreflang output is part of the header hook. When HREFLANG_ENABLED is on, the module calls its Hreflang manager and renders tags for the alternate URLs it can build. If more than one alternate exists, it also adds an x-default URL. If the current robots decision contains noindex, the suite returns no hreflang output for that page, which keeps noindexed pages from sending mixed signals. https://example.com/en/product.html The sitemap side is separate but aligned. The sitemap writer can emit xhtml:link rel='alternate' entries when it finds matching URLs for the same entity in other languages. The sitemap configuration has an INCLUDE_HREFLANG switch, so header hreflang and XML sitemap hreflang can both be controlled deliberately.There are still real limits. Hreflang works only when there is a real alternate URL to point to. If a product exists in English but the French product is missing, disabled, noindexed or has poor translated content, the tag cannot create a good French landing page for you. Likewise, hreflang does not replace canonical tags; each language page should normally canonicalize to itself and then list its alternates.A good multilingual SEO checklist is: keep each language URL crawlable, use self-referencing canonicals, publish complete translations for important products and categories, keep language switcher URLs consistent, include alternates in the XML sitemap, and avoid noindex on pages that are meant to participate in the hreflang cluster.

Can I use your SEO Revolution Suite instead of buying individual SEO modules?

Yes. The Smart SEO Revolution Suite is our all-in-one SEO module for PrestaShop: it pulls our main SEO line into one back-office dashboard, under a single licence and one update channel, so you are not juggling several modules that each want their own settings page.The Suite ships what these standalone modules do, plus extras:Advanced SEO Sitemap Builder, XML/HTML sitemaps, hreflang and image entries, with automatic splitting at the 50,000-URL limit.Automatic SEO Schema Rich Snippets, Product, Offer, BreadcrumbList, Organization, Article, FAQ and Review markup.Product Canonical Manager, canonicals, hreflang and noindex/nofollow control.Automatic Internal SEO Linker, keyword-to-URL internal linking suggestions across your content.On top of that it adds meta title/description templates with token placeholders, a 301/302/410 redirect manager with hit logging, 404 monitoring, robots.txt and llms.txt editors, Open Graph and Twitter Card output, Google Search Console import, and AI bulk meta generation that can use OpenAI, Claude or Gemini.The buying logic is simple: if you only need one feature in isolation, say, just canonicals, the matching standalone module may be the leaner choice. The Suite bundles these SEO features into one module and dashboard, so compare it against the standalone modules based on the features you actually need.

My product images are not showing in Google Image search. Why?

Usually it comes down to a few fixable things, and the most common is missing or empty alt text. Google leans heavily on the alt attribute and surrounding context to understand what an image shows, so images with no descriptive alt rarely surface in Image search. Walk through this list:Empty or generic alt text, the biggest factor; fix this first.robots.txt blocks the image folder, Google can't index what it can't fetch.Images only loaded by lazy-loading JavaScript the crawler doesn't run (less common now with native lazy loading).No image entries in your sitemap, so discovery is slower.Very small or low-quality images Google may choose not to index.Start with the alt text. Automatic SEO Images Alt Tags generates it from your catalog data, product name, manufacturer, category, reference and more, and can fill only the empty legends or replace existing ones. Note it gives Google clean alt text to read; it does not guarantee indexing or rankings.In the module, the default product template is {product_name} - {manufacturer}, listing pages use {product_name} - {category}, categories use {category_name}, and the default maximum length is 125 characters. You can add placeholders such as {reference}, {ean13}, {mpn} and {image_position} to make gallery images more distinct. The builder removes empty separators and cuts long text at a word boundary, so a template like {product_name} - {manufacturer} - {reference} stays readable even when one field is missing.The module fills the image legend/alt value at presentation time for product cover images, product gallery images, listing images and supported category images. By default it fills empty values without overwriting hand-written legends; enable replacement only after checking that your manual alt text is not better. After changing templates, clear cache and inspect the rendered img alt attributes on a product and category page. This is not an image sitemap generator and it cannot force Google to index an image, but it removes one of the main catalog-side blockers.

How do I know if my structured data is working correctly?

Run one of your product URLs through Google's Rich Results Test - it shows which structured data Google finds on the page and flags errors or warnings. You can also monitor coverage over time in Google Search Console under the Enhancements reports. After installing our Schema & Rich Snippets module, test a few product, category and CMS pages before relying on the storefront output.In the module back office, the preview screen lets you choose a page type and generate JSON-LD before you rely on the live page. Product, Organization, WebSite, Breadcrumb, Category and CMS schema are enabled by default, while FAQ markup is off by default because FAQ content must match visible page content. Product schema uses catalog data such as manufacturer/brand, SKU-style identifiers, condition, reviews, variants and up to five images unless you change the image-limit setting.Important current-code caveat: live storefront schema should be verified with existing JSON-LD cleanup disabled, or after the module output is marked so the cleaner preserves it. The module outputs JSON-LD scripts in displayHeader, but the cleanup step runs on the final HTML and removes application/ld+json blocks unless they contain the module marker comment. The current header output does not include that marker, so default cleanup can remove the schema the module just rendered.That means you should validate both the preview output and the real public URL after cache, theme hooks and other SEO modules have run. If cleanup is enabled, check the actual page source to confirm the JSON-LD is still present. Warnings for optional fields do not always block eligibility, but errors in required Product fields should be fixed before expecting rich results. Even valid schema is not a guarantee that Google will show rich results; it only makes the page eligible.

Can the Friendly URL Manager fix URLs that are already indexed by Google?

Yes. The module records old URLs when product/category/CMS/manufacturer/supplier URLs change and serves redirects from the history table. That is exactly for protecting indexed Google URLs after slug or pattern changes. Use 301 redirects for permanent moves, keep redirect history enabled, and avoid changing URL patterns repeatedly unless you are ready to manage the redirect chain.The history table stores the old URL, new URL, redirect type, entity type, entity ID, shop ID, active flag, hit count, last hit date, and change reason. The lifecycle handler captures old URLs before entity updates, compares them after the update, and records URL changes for products, categories, CMS pages, manufacturers, and suppliers. It also has delete and disable behavior that can redirect to a parent, homepage, 410 Gone, or nothing, depending on configuration.At request time, the router checks overrides and history entries and returns the configured redirect URL and redirect type when an old URL is matched. For SEO migrations, keep the old history rows enabled long enough for search engines and external links to settle, prefer 301 for permanent slug changes, and test important indexed URLs with a direct HTTP request to confirm they return one clean redirect to the final destination.

How many sitemaps does the Sitemap Builder create?

As many as your shop needs. Advanced SEO Sitemap Builder does not use a fixed number of sitemap files, and it does not name child files by entity type. It collects the enabled URL sources, verifies them, writes chunked XML files, then writes a sitemap index for the shop.By default the module includes products, categories, CMS pages, core pages, product images and hreflang alternates. Manufacturers and suppliers are available URL sources too, but they are disabled by default in the module defaults. The writer splits output when the configured URL limit is reached, with 50,000 URLs per file as the default, and also protects the sitemap protocol's 50 MB file-size limit.Example generated files for shop ID 1:modules/mprsitemapbuilder/sitemaps/sitemap_index_1.xmlmodules/mprsitemapbuilder/sitemaps/sitemap_1_1.xmlmodules/mprsitemapbuilder/sitemaps/sitemap_1_2.xmlmodules/mprsitemapbuilder/sitemaps/sitemap_1_3.xml https://www.example.com/modules/mprsitemapbuilder/sitemaps/sitemap_1_1.xml 2026-06-17T10:00:00+00:00 https://www.example.com/modules/mprsitemapbuilder/sitemaps/sitemap_1_2.xml 2026-06-17T10:00:00+00:00 Submit only the index URL in Google Search Console. Google reads the child files from the index, so you do not have to manage each generated XML file by hand. On multistore installations, each shop gets its own shop-ID-based index and child files.

My SEO module shows "missing schema markup" in some tools. Is this a problem?

A missing markup warning means the tool did not find the schema type or required field on that URL. In Schema Revolution, first check that the schema type is enabled for that page type, then compare the module preview with the final page source after cache is cleared, and finally test the live URL in Google's Rich Results Test or Schema.org's validator.Schema warnings should be checked against the SEO module's structured data settings.The module builds JSON-LD based on the detected page type. Depending on configuration it can output Organization and WebSite on the homepage, BreadcrumbList on non-home pages, Product schema on product pages, CollectionPage for categories, and Article for CMS pages. Product schema can include name, URL, description, SKU, GTIN, MPN, brand from the configured catalogue source, images, condition, offers, availability, shipping details, return policy, ratings, reviews, weight and category data when the shop has that data available.{ "@context": "https://schema.org", "@type": "Product", "name": "Example product", "url": "https://example.com/product.html", "description": "Short product description", "sku": "REF-123", "gtin13": "1234567890123", "offers": { "@type": "Offer", "price": "29.99", "priceCurrency": "EUR", "availability": "https://schema.org/InStock" } }If Google reports missing fields, compare three things: the module preview, the final HTML source after PrestaShop and external caches are cleared, and the live URL fetched by the test tool. A field can be absent because the schema type is disabled, the page detector does not identify the page as expected, the product lacks source data such as brand or GTIN, cached HTML is still being served, or another theme/module changes the final output.Be careful with the cleanup options. They are intended to remove older microdata and duplicate JSON-LD, but the current JSON-LD cleanup preserves only scripts marked with , while the module's header output is unmarked. With clean_existing_jsonld enabled, including its default state, the cleanup can remove the module's own schema from the final HTML. If tools show missing schema, disable/fix JSON-LD cleanup or add the expected marker before assuming another module is at fault.In the module configuration, open Schema Revolution > Configuration > Schema Types. Enable the missing type there: Product Schema, Organization Schema, WebSite Schema, Breadcrumb Schema, Category Schema or CMS Article Schema, depending on the URL being tested.If the schema exists in preview but disappears from the final HTML, disable Remove Existing JSON-LD in the same Schema Types tab while testing. That option removes unmarked application/ld+json scripts from the page before output, so it is the first setting to check when validators report that all JSON-LD is missing.

How is Smart SEO Revolution Suite different from separate SEO modules?

Smart SEO Revolution Suite is one module that owns the main technical-SEO jobs together, instead of stitching several single-purpose modules into a chain. You configure it from one place and the pieces share one set of rules.What's bundled in the one module:Meta title and description templates for products, categories, CMS and more.XML sitemap, robots.txt editor and canonical handling.Schema.org structured data, Open Graph and Twitter Cards, and hreflang for multi-language stores.301/302 redirects and 404 monitoring.Image SEO, internal-linking tools and SEO scoring.Separate modules make sense when you genuinely need only one narrow job, say image alt text, or just a sitemap. The advantage of the suite is that these features know about each other: because one module renders the head, it can strip duplicate theme tags and keep a single clean canonical, hreflang and schema set. With several independent modules you have to coordinate that yourself, and duplicate-tag conflicts are the usual result.Common mistake: buying the suite and a standalone overlapping module, then enabling the same feature in both. Let one own each job. See the Smart SEO Revolution Suite.

Manage all your PrestaShop SEO in one place, metadata, canonicals, redirects, schema and hreflang

Smart SEO Revolution Suite - PrestaShop all-in-one SEO management suite

Smart SEO Revolution Suite - Recover traffic lost to technical SEO problems

All-in-One SEO Module for PrestaShop - Admin Structured Data

Smart SEO Revolution Suite - Give search engines clearer page information

Smart SEO Revolution Suite - Fix 404 errors and manage 301 redirects in PrestaShop

Smart SEO Revolution Suite - Control indexing and robots rules per page type

Manage all your PrestaShop SEO in one place, metadata, canonicals, redirects, schema and hreflang

SEO Revolution

Name: SEO Revolution
Brand: mypresta.rocks
SKU: mprseorevolution
Price: 299.00 EUR
Availability: InStock

PrestaShop all-in-one SEO, canonicals, hreflang, JSON-LD, sitemaps and Search Console in one policy matrix

No reviews

PrestaShop 1.7.6PHP 7.2+Version 2.28.33Released 12/24/2025Updated 07/26/2026

€299.00

Tax excluded

SEO Revolution is a module for PrestaShop stores that turns search data, catalogue changes and indexing into one controlled workflow. After installation, its action centre guides the first page inventory, analysis, sitemap generation and integrity review.

Google Search Console supplies clicks, impressions, click rate, average position, queries, pages, countries and devices. Google and Bing receive changed addresses through the merchant's own connections, while OpenAI, Claude and Gemini provide optional writing suggestions through the merchant's access key. Any charges from the chosen writing service remain separate.

The module is straightforward to start and extensive to configure. You choose which pages belong in search, which address is canonical, which language versions are published, what enters each sitemap and which information appears in rich results. Shared rules cover the catalogue quickly, while page-level values handle exceptions.

SEO Revolution also protects work already earned by the catalogue. Inactive, hidden and deleted products keep their former addresses in every language and lead to an approved replacement or a live parent category, broken stored links are corrected after review, and every page receives both an SEO score and a separate readability grade.

The shop gains a clear order of work, consistent instructions for search engines and less visibility lost during catalogue changes. A small team controls a large multilingual or multistore catalogue without turning every correction into a separate project.

Instant download after purchase

Instant Live Demo Real store, ready in ~1 min

5 demo installs ready · refills every 48h

Request Quote

Lifetime license per domain, yours forever. Includes 3 months support & updates. Learn more

The demo is the complete module: buy anytime and activate the same installation, nothing to reinstall and nothing lost. Open the module's License tab and click "Activate from mypresta.rocks" (or paste your key); your settings and data stay exactly as they are. Updates install in one click from the Update tab.

Support & Updates

6 months +€49.00 9 months +€79.00 1 year +€109.00

Auto-renew support

+€29.90/mo

Additional Services

Professional Setup We fully configure the module to your needs: all options set, tested & verified within 1 business day. +€29.00

Visual Integration CSS & template adjustments to match your theme: includes cross-device verification and screenshot review. +€49.00

Options total: €0.00

Selected total: €299.00

Summary of what SEO Revolution offers

SEO Revolution manages the shop's complete SEO workflow inside PrestaShop and joins Search Console evidence, catalogue corrections, search-engine submission and later verification in one traceable process. Installation opens a guided action centre for the first inventory, analysis, sitemap and integrity tasks, while detailed rules remain available as the catalogue grows.

Priorities from real search data: the next section shows how queries, pages, countries, devices, scores and alerts create an ordered task list.
Protection when addresses disappear: retired products, missing pages and broken links keep earned traffic connected to a useful destination.
Work across the catalogue: templates, bulk editing, reviewed writing suggestions and internal links replace repetitive page-by-page changes.
One answer for search engines: indexability, canonical addresses, language versions, sitemaps and rich-result information follow the same policy.
Control as the shop grows: multistore rules, link monitoring, conversion records and the wider toolset remain in one administration area.
Clear physical workflow: the work happens in a dedicated SEO area in the PrestaShop back office, while shoppers see only the corrected pages and search output.

The SEO Revolution configuration screen in the PrestaShop back office

Which page needs attention first?

The Search Console area brings clicks, impressions, click rate and average position into the back office. Queries and landing pages have separate views, with countries and devices alongside them, so a decline has a phrase, an address and a scale.

The page inventory adds page type, search status, preferred address, sitemap presence and a score. Keyword records retain position history, deindexation alerts flag lost visibility, and a separate readability grade explains where dense or difficult writing weakens the page. You choose the affected item from evidence instead of working through the catalogue in an arbitrary order.

page inventory showing the preferred address, search status and sitemap status together

What happens when an address stops working?

An inactive, hidden or deleted product enters the retirement workflow with its former addresses in every shop language. SEO Revolution sends each address to an approved replacement or a live parent category. When no honest destination exists, it marks the old page as permanently removed, blocks redirect loops and leaves a merchant-created redirect untouched.

The missing-page monitor records the failed address, visit count and referring page. The internal-link audit also finds stored links that now redirect or fail, then replaces them with the approved final address or removes them after review, with a preview and rollback history. Catalogue maintenance becomes a controlled repair rather than a trail of forgotten links.

retired products screen with replacement, action, status and verification

How does one decision reach a large catalogue?

Title, description and page-heading templates work by page type and language, while an individual product, category or content page keeps its own value when needed. Bulk operations apply a chosen template and exchange meta titles, meta descriptions and rewritten addresses through CSV. A live search-result preview shows the result before it is saved.

Writing suggestions for titles and descriptions come from OpenAI, Claude or Gemini after you add your own access key. The provider bills any usage separately, and every suggestion waits for acceptance or rejection. Internal-link rules use language-specific wording, chosen page types, content areas, destinations and link limits.

Blog Revolution publishes the articles, while SEO Revolution controls their indexing, preferred addresses, internal links and search presentation, keeping content production and search management as two clear jobs.

SEO dashboard with page, indexing, redirect and error counters above the action center tasks

How do Google and Bing receive one consistent answer?

You choose whether a page is indexed, which address represents it, which language versions are published and added to the sitemap, and which rich-result information matches the content. The same policy controls robots treatment, preferred addresses, language alternatives, sitemaps and structured page information. When the module publishes its own output, it removes duplicate language, social-sharing and structured entries from the theme.

Separate Google and Bing queues show the reason, state, attempts and next action for changed and retired addresses. External submission starts after the relevant service is enabled and connected. Google indexing uses the merchant's service-account credentials, while the Bing connection creates or accepts its own key.

Structured data settings with separate toggles for product, category, article, breadcrumb, organization and website schema

What stays under control as the shop grows?

SEO Revolution includes page inventory and scoring, Search Console reports, metadata, headings and subtitles, address patterns and canonicals, redirects and missing-page monitoring, retired products, robots rules, XML and HTML sitemaps, language alternatives, social and structured information, llms.txt, internal and external link tools, image descriptions, backlink monitoring, disavow records, indexing queues, server-side analytics and advertising conversion records.

You choose separate policies and values for every shop and language, with explicit inheritance for shared settings and a read-only all-shops view. The result is one extensive workspace that remains simple for the first scan and precise enough for a multilingual catalogue, several storefronts and a team with divided responsibilities.

Illustration: What stays under control as the shop grows

Reference

mprseorevolution
In stock

2147483647 Items
PrestaShop Compatibility

PS 1.7 – 9.x
Pricing Model

One-time Purchase
Module Type

Front & Back-office
GDPR Relevant

No
Business Goal

Increase Traffic
External Account Needed

No
Module Complexity

Complete Solution
Customer Journey Stage

Attract Visitors
Works With Platform

No External Platform

What customers say about us

Company reviews

5.0 ★ ★ ★ ★ ★ (4 reviews)

Loading customer reviews...

No product reviews yet

Be the first to share your experience with this module.

Write a Review

Your Rating *

★ ★ ★ ★ ★

Rate specific aspects (optional)

Quality

★ ★ ★ ★ ★

Price / Quality

★ ★ ★ ★ ★

Stability

★ ★ ★ ★ ★

Compatibility

★ ★ ★ ★ ★

Support

★ ★ ★ ★ ★

Your Name *

Your Email *

Review Title

Your Review *

Add Photos (max 3)

Click to upload or drag & drop

MPR SEO Revolution centralizes the SEO work of a PrestaShop store: meta templates, structured data, sitemaps, redirects, robots.txt, indexing, internal links, backlinks, and conversion tracking. It helps merchants keep product, category, CMS, manufacturer, supplier, filtered, search, and blog pages easier to crawl, index, and share.

Read Full Documentation Download PDF

Have a question about this product? Our experts are here to help. Ask anything about installation, compatibility, or specifications.

1301 questions

9 categories

2013 building modules since

1.6–9 PrestaShop versions

See all questions

v2.3.552026-05-27

AddedAdd internal link audit
AddedFinalize SEO technical controller cleanup
AddedAdd enhanced Ads conversion identifiers

Works Well With SEO Revolution

Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.

Automatically generate SEO alt tags for PrestaShop product and category images

Automatic SEO Images Alt Tags

€99.00

★ ★ ★ ★ ★

Complement

Smart SEO Revolution Suite already centralises the technical SEO signals that affect crawling, indexing and search presentation, including meta templates, structured data, canonicals and redirects. What sits a little outside that technical spine is the repetitive job of describing thousands of catalogue images, which is its own distinct task.

Automatic SEO Images Alt Tags handles exactly that, generating alt text from templates for product, listing and category images without manual field editing. It complements the suite by covering image descriptions specifically, working alongside it as a separate, focused tool rather than duplicating its controls.

Together your store has both broad technical SEO management and automated image-description coverage. The suite keeps page-level signals organised while the alt-tag module quietly improves accessibility and image context across the catalogue, so a part of on-page SEO that the suite does not specialise in is handled without hand-editing every image field.

Publish posts, categories and authors with SEO-friendly routes using a PrestaShop blog

Blog Revolution

€299.00

★ ★ ★ ★ ★

Complement

Smart SEO Revolution Suite gives your store one place to manage page details, structured data, canonicals, redirects and discovery workflows, which is the technical backbone of SEO. It does not, however, produce the editorial content that earns earlier-stage search traffic; that needs a dedicated publishing surface.

Blog Revolution adds it, keeping native articles, categories, tags, authors, comments and clean blog pages inside the shop so content can attract search traffic and lead readers toward products. It complements the suite by supplying content where the suite supplies technical control, each owning a different layer.

Used together, you cover both sides of SEO that often get separated: the technical signals on existing pages and a stream of new, topical content. The suite keeps your catalogue's signals tidy while the blog grows the store's footprint with guides and advice, so technical hygiene and content growth advance in parallel rather than one waiting on the other.

Speed up busy PrestaShop stores with Redis, APCu or file caching and asset optimisation

Performance Revolution

€299.00

★ ★ ★ ★ ★

Complement

Smart SEO Revolution Suite organises the signals that influence crawling, indexing and search presentation, but search performance also depends on how fast pages actually load, which is a separate discipline. Slow pages can undercut otherwise sound SEO by wasting crawl budget and losing shoppers.

Performance Revolution covers speed, giving your team controls for caching, warming, asset handling and bottleneck analysis in one back office area, with Redis, APCu and auto-detect options. It complements the SEO suite without overlapping: one manages search signals, the other manages page speed, each in its own workspace.

Together you address two things search engines and shoppers both care about. The suite keeps your technical SEO consistent while Performance Revolution works on the load times behind those pages, so well-optimised pages are also fast, reducing the chance that slow delivery quietly drags down rankings and conversions despite solid on-page SEO.

Collect product ratings, reviews, criteria and images right inside PrestaShop

Product and Store Reviews

€149.00

★ ★ ★ ★ ★

Complement

Smart SEO Revolution Suite handles your store's technical SEO signals, including structured data and page details, but it does not generate the review content that often makes product listings more persuasive and gives pages genuine, fresh on-page material.

Reviews & Ratings adds that, with native moderated ratings, written feedback, optional photo reviews and review criteria for products, categories, CMS pages and the store itself, all kept inside PrestaShop. It complements the suite as a separate trust-building tool; it does not feed data into the suite, and you moderate submissions yourself.

Used together, your store pairs organised technical SEO with genuine customer-contributed content. The suite keeps signals tidy while Reviews & Ratings builds visible proof where buying decisions happen, so pages benefit both from clean structure and from real review content, with each tool clearly responsible for its own job.

View all known issues

1 Under Review

1 Planned

23 Implemented

25 requests

Loading feature requests...

View full roadmap

30 days return right
Easy return - no questions asked

Plug & Play Modules
Install, set up and take profit

Dedicated Support First
Priority Help & Satisfaction Over Sales

Create clean SEO-friendly URLs in PrestaShop with redirects and duplicate URL control

Smart SEO Friendly URL Manager

€149.00

★ ★ ★ ★ ★

Blog Revolution

€299.00

★ ★ ★ ★ ★

Add JSON-LD structured data to PrestaShop for richer Google search results

Automatic SEO Schema Rich Snippets

€149.00

★ ★ ★ ★ ★

Generate valid PrestaShop XML sitemaps with canonical, noindex and hreflang checks

Advanced SEO Sitemap Builder

€149.00

★ ★ ★ ★ ★

Cookie	Provider	Purpose	Duration
PrestaShop-*	PrestaShop	Session management and cart functionality	Session
PHPSESSID	PHP	PHP session identifier	Session
mprcr_consent	MPR Cookies Revolution	Stores cookie consent preferences	365 day(s)
mprcr_version	MPR Cookies Revolution	Tracks consent configuration version	365 day(s)

Cookie	Provider	Purpose	Duration
TawkConnectionTime	Tawk.to	Tracks chat session connection time	Session
__tawkuuid	Tawk.to	Identifies returning chat visitors across sessions	6 month(s)

Cookie	Provider	Purpose	Duration
_ga	Google Analytics	Distinguishes unique users by assigning a randomly generated number	2 year(s)
_ga_*	Google Analytics	Used to persist session state across page requests	2 year(s)
_gid	Google Analytics	Distinguishes unique users for 24 hours	24 hour(s)

SEO Revolution

PrestaShop all-in-one SEO, canonicals, hreflang, JSON-LD, sitemaps and Search Console in one policy matrix

Summary of what SEO Revolution offers

Which page needs attention first?

What happens when an address stops working?

How does one decision reach a large catalogue?

How do Google and Bing receive one consistent answer?

What stays under control as the shop grows?

What customers say about us

Works Well With SEO Revolution

You might also like