The sitemap in Hummerce is an automatically generated XML file with the store's addresses - items, categories and static pages - which helps search engines, above all Google, find and index the whole product offer. The store serves the sitemap at a fixed address and updates it on a schedule in the background, without adding load to the store each time a search engine crawler makes a request.
As of Hummerce 2.16 (image addresses in the sitemap), background generation from version 2.30, updated 2026-09-29.
¶ Benefits and use cases
- Automatically informing search engines about store addresses - items, categories and static pages - without manually preparing a list of addresses.
- Separate sitemaps for items, categories and pages - easier indexing diagnostics in Google Search Console, e.g. when categories are being indexed but items aren't.
- Product image addresses in the sitemap - supports indexing in Google Images.
- Background generation - the sitemap is ready to read at any time, without adding load to the store when a search engine crawler visits.
- Matched criteria - the sitemap only includes objects that are visible in the store and not marked as excluded from indexing.
- By default the sitemap covers static pages, categories and items (without variants and sub-items); producers can optionally be included too.
- The criteria for selecting objects are configurable separately for pages, items and categories - by default, only objects visible in the store and not marked as excluded from indexing.
- Addresses in the sitemap match the canonical address and the store's Friendly URLs, if enabled.
- The standard configuration serves four sitemaps at separate addresses: a full sitemap plus separate ones for categories, pages and items - useful for a large catalog and for diagnosing in Google Search Console which types of addresses are being indexed.
- Adding another sitemap with its own set of criteria and address is a configuration change made during implementation.
- From version 2.30 the sitemap is built on a recurring schedule in the background (once a day by default, frequency configurable), instead of being rebuilt from scratch on every search engine crawler request - this reduces the load on the store.
- The task that generates the sitemap is added and configured the same way as other data exports (feeds).
- From version 2.16 the sitemap can also include item image addresses (the image sitemap extension) - this helps with indexing images in Google Images.
- Which images (item properties) are included in the sitemap is set in the sitemap configuration, as a comma-separated list of properties.
- A core platform feature - available in all current versions.
- Image addresses in the sitemap - from version 2.16.
- Background generation (as a feed) - from version 2.30.
- A fix for empty sitemaps and exports in selected configurations - version 2.35.
- The data export (feed) mechanism - background sitemap generation uses the same solution as other exports.
- Friendly URLs - the sitemap uses friendly URLs, if the store has enabled them.
- Submitting the sitemap address in Google Search Console - the store's own responsibility, requires a Google account and a verified domain.
- The module is installed by default in every store - it works from store launch, with no extra configuration.
- Changing the scope (a different set of objects, different criteria, another sitemap, enabling images) requires a configuration change.
- Minimum estimated time: the standard configuration works from store launch, at no extra time; changing the criteria or adding another sitemap is quoted individually.
- What the time depends on: the number of extra sitemaps, the choice of criteria and objects (including images), the background generation schedule.
- A multi-domain store has one shared sitemap, not a separate one for each domain (see Multi-domain).
- Item variants and sub-items don't appear in the sitemap - only parent items do.
- The priority attribute, even though the store can generate it, is no longer taken into account by Google for indexing.
- Changing the criteria and adding another sitemap is configuration carried out by the implementation team, not self-service in the panel.
- We do not verify the configuration for legal compliance - the choice of addresses and content in the sitemap is decided by the store.
- A separate sitemap for each domain in a multi-domain store.
- Managing criteria and additional sitemaps from the panel, without a configuration change by the implementation team.
Does Hummerce generate a sitemap automatically?
Yes. The module is installed by default in every store and immediately serves a sitemap with items, categories and static pages.
Does the sitemap affect the store's performance?
No. From version 2.30 the sitemap is built on a recurring schedule in the background, instead of being generated from scratch on every search engine crawler request.
Are product images included in the sitemap?
Yes, from version 2.16 - the addresses of chosen item images are included in the sitemap, supporting indexing in Google Images.
Does each domain of a multi-domain store have its own sitemap?
No. All domains share one common sitemap.
How long does it take to set up the sitemap?
The standard configuration works from store launch, at no extra time. An additional sitemap or a change of criteria is quoted individually.
Can a separate sitemap be added with different criteria than the default ones?
Yes. This is a configuration change carried out by the implementation team.
Want to check what the sitemap looks like in your store? Contact the Hummerce team (in Polish).
- Default configuration (
conf/passage-sitemap.xml, outside the panel): four sitemaps with the symbols sitemap (full), sitemap_categories, sitemap_pages, sitemap_products - each with its own page, item and category criteria and export toggles for the homepage, producers, pages, categories and items.
- Background generation: Marketing -> Feeds - a task with a symbol matching the sitemap symbol from the configuration, plus a schedule (frequency and generation times).
- Images in the sitemap: Configuration -> Settings, the Sitemap group - a comma-separated list of image properties included in the sitemap.
- Submitting the sitemap to Google: Google Search Console, the Indexing -> Sitemaps section - outside the store panel.
¶ REST API and MCP
No dedicated operations for the sitemap in REST API or in the AI assistant (MCP) - the sitemap is generated automatically and available at a fixed address.
The module has no messages visible to the customer - the sitemap file isn't a store page.
The default criteria exclude from the sitemap any objects not visible in the store, and - if the store has configured such a property - any item, category or static page marked as excluded from indexing (_noIndex).