A PrestaShop sitemap tells search engines which product, category, and CMS URLs matter on your store. Without one, Google still crawls links it finds, but larger catalogs and new pages often get discovered slower. This guide covers the XML sitemap for crawlers and the public Sitemap page for shoppers, plus how to generate, submit, and maintain the file.
PrestaShop supports two different “sitemaps,” and mixing them up causes confusion:
- XML sitemap – a machine-readable file (usually from the native Google Sitemap / gsitemap module) meant for Google, Bing, and other crawlers.
- Sitemap page – an HTML page on the storefront that lists categories and CMS links for visitors. Useful for navigation; it does not replace the XML file.
If crawl coverage is your goal, focus on the XML file first. Pair it with a clean robots.txt setup in PrestaShop so crawlers can reach the sitemap URL and the pages you want indexed.
Working with the XML PrestaShop sitemap
Generate the XML PrestaShop sitemap with the standard Google Sitemap module (technical name: gsitemap). Steps:
- Install Google Sitemap in the Back Office. If it is missing from the catalog, download a release from the official gsitemap GitHub releases.
- Open the module configuration. On save or cron, it builds an XML file listing products, categories, manufacturers, CMS pages, and (when supported) module-created pages.
- Submit the sitemap URL in Google Search Console (Sitemaps report), or reference it from robots.txt with a
Sitemap:line. - On large catalogs, generating everything in one browser request can time out. Use the module’s cron option so regeneration runs on a schedule instead of blocking the BO.
- In Configure your sitemap, include or exclude page types you do not want crawled (for example thin CMS pages or duplicate brand pages).
- If third-party modules add custom pages, check whether they hook into gsitemap or ship their own sitemap. Orphan URLs never appear in Search Console coverage if nothing lists them.
Where to find the sitemap URL
After generation, the module shows the sitemap index URL (often something like https://your-shop.com/1_index_sitemap.xml – the exact path depends on shop ID and module version). Copy that exact URL into Search Console. Re-submit only when the URL changes; daily regenerations do not require a new manual submit every time.
Friendly URLs and rewriting also affect whether listed links resolve cleanly. If products return 404 after a server move, fix rewriting before you chase sitemap settings – see solving PrestaShop SEO URL rewriting problems.
The HTML Sitemap page in PrestaShop
Besides XML, PrestaShop ships a public Sitemap CMS-style page that shows categories, account links, and CMS pages. It helps humans browse; it is not a substitute for the XML PrestaShop sitemap used by crawlers.
- You cannot fully redesign that page from the BO alone. Defaults usually group “Our offers,” categories, account links, and CMS pages. Deeper layout changes go in the theme template, typically
/themes/YOUR_THEME_NAME/templates/cms/sitemap.tpl. - Keep both: HTML for navigation, XML for discovery. Improving one does not remove the need for the other.
Maintenance checklist
A one-time generate-and-forget habit is why many stores keep a stale PrestaShop sitemap full of outdated URLs. A short routine works better:
- Regenerate on a schedule (cron) after catalog imports or bulk price/status changes.
- Exclude noindex or private pages so the file stays honest.
- After major URL changes, confirm rewriting and then check Search Console for sitemap errors (not found, redirected, excluded).
- When you move hosts or change the domain, update the sitemap URL in Search Console and robots.txt.
That is the practical loop: generate XML with gsitemap, submit the index URL once, keep cron + exclusions sane, and treat the HTML Sitemap page as a separate navigation aid – not as your crawling strategy.