Generate valid PrestaShop XML sitemaps with canonical, noindex and hreflang checks
Advanced SEO Sitemap Builder is a module for PrestaShop stores that creates and maintains XML sitemaps made only from pages that are ready for search engines. Installation adds one clear settings screen, and the first verified sitemap starts with one button.
A useful sitemap settles which store addresses deserve to be sent for indexing. Removed products, redirects, duplicate addresses and pages excluded from search stay outside, while the current products, categories and content that matter remain easy for search engines to reach.
The module covers products, categories, content pages, brands, suppliers, shop pages and addresses supplied by other modules. You choose the content types and languages, include or exclude individual addresses or whole address families, set importance and update frequency by page type, and keep separate maps for each page type and selected language.
Every address is verified before publication, with its response, canonical address, indexing instruction and exclusion reason kept in the administration panel. Product, category and brand images receive dedicated image maps, language counterparts are connected, each shop keeps its own files, and catalogue changes trigger a fresh run in the background.
The result is cleaner indexing signals, fewer hidden sitemap errors, evidence for every decision, reliable coverage across languages and shops, and an automated process that remains simple to start and precise to configure.
What does Advanced SEO Sitemap Builder manage?
Advanced SEO Sitemap Builder gathers the pages of a PrestaShop store, verifies whether they belong in search, and publishes a complete set of sitemaps with an audit trail for every decision. The overview below maps the six parts of that work.
- Scope: the full catalogue, store content, images and pages supplied by other modules.
- Qualification: a page enters only after its address, response, indexing instruction and canonical address agree.
- Control: content types, languages, individual addresses, address families, importance and update frequency remain configurable.
- International stores: language counterparts and separate shops retain the correct relationships without mixing data.
- Freshness and scale: catalogue changes start a bounded background run, while large stores are processed in batches.
- Publication: the module creates the files, keeps the previous valid set safe, registers the index and reports the outcome.
Which pages are allowed into the sitemap?
Every candidate page passes the same verification before publication. The module confirms that the address belongs to the shop, opens successfully, is not blocked from indexing and names itself as the preferred address. Redirects, missing pages, addresses blocked by store rules and canonical conflicts remain outside.
The decision is visible for each address. Its page type, result, preferred address, indexing instruction, exclusion reason and verification time stay in one history, with filters that turn a vague indexing problem into a specific page to correct. A recent successful result is reused when nothing changed, while a fixed sample is verified again so old assumptions never become permanent.
How much of the store is covered?
The module gathers the homepage, products, categories, content pages, brands, suppliers and available shop pages such as contact, stores and the public sitemap. Blog and specialist pages supplied by other modules join the same process. Exact include and exclude rules handle one address, while prefix rules handle a complete family.
Output is separated by page type and chosen language, and large sets are divided into valid files under one index. Product, category and brand images each have their own switch and dedicated image map. Image addresses follow the store's chosen media source, and any unreachable source appears in the address audit. An optional public HTML map gives visitors a grouped route through verified pages, while a feed publishes the most recently changed verified addresses.
How do languages and shops remain correctly separated?
Each selected language has its own set of addresses. Matching translations are connected only after both versions pass verification, so search engines receive real counterparts instead of guessed links. A language that is not meant for indexing stays out without affecting the others.
In a multistore installation, discovery, rules, history and filenames belong to the current shop. One store never changes another store's result, while the same administration area still provides a consistent workflow for the whole installation.
How does the sitemap stay current without endangering a large store?
Changes to products, categories and content mark the relevant addresses for fresh verification, and a background runner publishes the update without external scheduling work. Frequency profiles show the next run and the result of the last one. Manual generation remains available whenever an immediate refresh matters.
Large catalogues move through persistent batches with bounded resource use. Verification limits simultaneous requests and slows down when the shop responds more slowly. New files are prepared and validated as one complete set, then published together, so an interrupted or failed run leaves the previous valid sitemap online.
Where are the sitemaps published and the results reported?
The first run requires only the content selection and a refresh profile. The dashboard then shows progress, duration, included and excluded totals, generated files and the public index address. The address list and history remain available for deeper work, so a simple start does not remove advanced control.
The completed index is added to the store's robots.txt file and submitted through Google Search Console, with delivery status and retries recorded beside the generation result. The storefront receives no added interaction code, and the module stores public page addresses and verification results rather than customer or order data.
-
Referencemprseositemapbuilder
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.7 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront & Back-office
-
GDPR RelevantNo
-
Business GoalIncrease Traffic
-
External Account NeededNo
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageAttract Visitors
-
Works With PlatformNo 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
Advanced SEO Sitemap Builder creates XML sitemaps from your real PrestaShop catalog and checks URLs before they are sent to search engines. It helps keep indexed URLs focused on active, crawlable pages instead of broken, redirected, canonicalized, or noindex pages.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1321
questions
9
categories
2014
building modules since
1.6–9
PrestaShop versions
v1.2.142026-05-27
- AddedAdd generation-scoped sitemap validation
- Addedcomplete FR/DE/ES/IT/PL translations
- ImprovedMigrate all config from ps_configuration to ConfigTable
Loading full changelog...
Works Well With Advanced SEO Sitemap Builder
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
A merchant running Advanced SEO Sitemap Builder has already done the work of telling search engines which products, categories, CMS pages, brands and suppliers actually exist and deserve crawling. The sitemap gets the right URLs discovered, but discovery alone does not tell Google what each page is about once a crawler arrives.
Automatic SEO Schema Rich Snippets works alongside it on the understanding side, adding structured data for products, categories, CMS pages, breadcrumbs and site identity so the pages your sitemap surfaces are also described in a machine-readable way. The two tools cover different stages: one helps pages get found, the other helps them be understood, each managed from its own back office.
Run together, you cover both discovery and interpretation. Pages a crawler reaches through your sitemap arrive with clearer structured context, which can make them eligible for richer search presentation while the final display still depends on the search engine. It is a practical pairing for a store that wants its catalogue both crawled efficiently and described accurately.
Complement
With Advanced SEO Sitemap Builder feeding search engines a clean list of products, categories, CMS, brand and supplier URLs, you are actively inviting crawlers to those pages. The risk on a real PrestaShop store is that some of those URLs are duplicate or near-duplicate variants, and a sitemap cannot decide which version should carry the search signal.
Product Canonical Manager covers that gap separately, letting you set canonical, noindex, nofollow and hreflang rules per entity or by broader selection from the back office. It does not change what your sitemap submits; it clarifies which of several similar pages should be treated as the primary one. The two work as complementary controls over how your catalogue is presented to search.
The payoff is fewer mixed signals: the pages you submit for crawling are also the pages you have explicitly marked as canonical, so duplicate-content confusion is reduced and crawl attention is less likely to be split across variant URLs that you never wanted competing in the first place.
Complement
A store using Advanced SEO Sitemap Builder is investing in clean discovery, but the URLs it lists are only as readable as PrestaShop generates them. Default addresses can be cluttered and technical, which makes links harder to share and easier to break if the catalogue structure shifts later.
Smart SEO Friendly URL Manager handles the address layer itself, letting you define cleaner URL patterns for products, categories, CMS pages, manufacturers and suppliers from the back office. It works alongside the sitemap rather than feeding it: one tool shapes how addresses read, the other lists addresses for crawlers, each doing its own job.
Used together, the URLs you submit for crawling are also the cleaner, more shareable ones shoppers see, and old traffic is less likely to be lost when addresses change. You get a catalogue that looks more professional in search results and in shared links, while your sitemap keeps those tidy URLs in front of search engines.
Governance
Advanced SEO Sitemap Builder keeps its XML output useful when it is regenerated as your catalogue changes, so new products and removed pages are reflected rather than served stale to crawlers. Where that regeneration is set up as a recurring job, a job that fails silently is easy to miss until rankings drift.
Cron Manager covers the oversight side, giving you one back office place to check whether MPR scheduled tasks are actually running, with protected scheduling links, manual runs and visible task status. It centralizes and monitors these jobs generically rather than running any specific module's work for it.
The benefit is fewer blind spots. If and where the sitemap builder or another MPR module exposes a scheduled task, Cron Manager gives you a single place to confirm its status and trigger a manual run if something stalled, so recurring maintenance is less likely to quietly fail between checks.
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
You might also like
