Should I disable PrestaShop's Google sitemap module?

Yes. Both modules would produce competing sitemaps. Disable gsitemap, delete its files at the shop root, then submit the index URL shown by this module in Google Search Console and Bing Webmaster Tools. The module shows a warning for as long as gsitemap is enabled.

Does generation hold up on a large catalogue?

Yes. It moves in batches within a time budget per request (20 seconds by default, 15 at most from the back office), then the next request picks up. On our test server, 30,000 products in two languages gave 60,038 URLs in about thirty seconds. With SSH access, the command-line script runs the whole job in one go.

Why are some CMS pages missing?

A CMS page whose Indexation by search engines option is off is served by PrestaShop with a noindex tag. Listing it in the sitemap would create a contradiction that Google reports, so the module leaves it out and shows how many pages are affected. Turn the option on for the pages that should be indexed.

Does Google use IndexNow?

No. IndexNow is used by Bing, Yandex, Seznam, Naver and other engines. Google keeps reading the sitemap, which the module keeps up to date through regeneration after changes. The IndexNow option is off by default and takes one click to enable.

How do I exclude a whole category?

Create a Categories: a category and all its subcategories rule to remove the category pages of the branch, and a Products: in a category rule to also remove the products associated with it. Rules apply at the next generation.

Is the module compatible with PrestaShop 9?

Yes, from PrestaShop 8.0 to PrestaShop 9.x with the same ZIP, in multistore and multilingual setups. It relies on ModuleAdminController and uses no Composer dependency. Module strings ship in eight languages.

PrestaShop XML Sitemap Module 8 & 9: Images, Hreflang

PrestaShop XML Sitemap Module 8 & 9: Images, Videos, Hreflang and IndexNow

A complete, up-to-date sitemap with no timeout, whatever the size of the catalogue.

Google finds your products through links and through the sitemap. When the sitemap is incomplete, does not announce translations or crashes on a large catalogue, pages stay out of the index. This module builds one sitemap per language and per content type, links every page to its translations with hreflang tags, adds images and videos, and removes what you do not want indexed through rules. Generation moves forward in batches of a few seconds: it never hits the server execution limit, resumes where it stopped, and the old files stay online until the new ones are published.

At a glance

Products, categories, CMS pages, brands, suppliers, static pages and custom URLs
Product images and YouTube, Vimeo or self-hosted videos in the sitemap
Hreflang and x-default tags across every language of the shop
15 exclusion rules by ID, category, stock, price, URL text or regular expression
Batch generation with no timeout, cron, regeneration after changes and IndexNow

PrestaShop 8 & 9 Hreflang IndexNow Multistore

30-day refund

12 months updates

24h support

The long version

Everything you'd want to know before you install.

A detailed look at how PrestaShop XML Sitemap Module 8 & 9: Images, Videos, Hreflang and IndexNow works, why we built it the way we did, and the thinking behind the features above.

§ 01

What the native sitemap is missing

The Google sitemap module shipped with PrestaShop produces a list of URLs per language. It does not link translations together with hreflang, knows nothing about videos and offers no exclusion rule beyond static pages. On a catalogue of tens of thousands of products, its generation also depends on the patience of the browser and the server. This module rebuilds the sitemap from scratch with those needs in mind.

§ 02

Clean files that are easy to check

Each shop has its own index, pointing to one file per language and per content type: products, categories, CMS, brands and so on. When a file reaches the limit you set, the rest goes into a new file. Open the index in a browser and a stylesheet shows a readable table with the number of URLs, images, videos and languages per page. Search engines ignore that stylesheet.

§ 03

Generation that never breaks the live site

Files are built in a temporary folder, then published shop by shop. Meanwhile the old sitemaps stay in place. An error stops the job without replacing anything, logs it in the PrestaShop log and shows it in the back office. A lock prevents two generations from running at once, for example the cron and a click in the back office.

§ 04

Multistore and multilingual

Each shop has its own settings, its own languages, its own index on its own domain, and a /sitemap.xml address that serves the right index for the domain called. Exclusion rules and videos apply to all shops or to one. A Sitemap line per shop is added to robots.txt, and the block survives when PrestaShop regenerates the file.

§ 05

Built to grow with the shop

Regeneration after changes and IndexNow mean you no longer wait for the next cron to announce a new product. Sitemaps from a blog or a neighbouring WordPress site can be added to the index, and a hook lets other modules register their pages with their translations. The code follows PrestaShop conventions, uses no Composer dependency, and runs from PrestaShop 8.0 to 9.x with the same ZIP.

PrestaShop XML Sitemap Module 8 & 9: Images, Videos, Hreflang and IndexNow

The short version.

Every translation announced to Google

No timeout, even on a large catalogue

You decide what gets indexed

A sitemap that follows your catalogue