Magento Sitemap Configuration: Priorities, Frequencies, and Image Sitemaps

Case StudieseCommerce PlatformsMagentoSEO

A Magento XML sitemap is best understood as a crawl map, not a ranking switch. It gives search engine crawlers a clean list of URLs you want discovered, along with optional signals about how important those URLs are relative to each other and how often they tend to change. That helps with discovery and crawl planning, especially on stores with large catalogs, seasonal landing pages, or products buried several levels deep.

The important limitation is that sitemap values do not force indexing, guarantee crawling, or make a page rank higher by themselves. A product page marked with a high priority still needs to be indexable, canonical, internally linked, useful, and technically accessible. Likewise, setting every URL to update “daily” does not make crawlers return daily if the content rarely changes. Weak configuration creates noise; strong configuration makes your sitemap more believable and easier to interpret.

Magento sitemap configuration matters because Magento 2 and Adobe Commerce give you controls that affect what gets exposed in the XML file and how those URLs are described. Priority values express relative importance, change frequency values describe expected update cadence, generation scheduling determines how often the file is refreshed, and image sitemap options decide whether product images are included for discovery.

The practical goal is consistency. Your homepage, key categories, active product pages, evergreen CMS content, discontinued products, and low-value filtered URLs should not all send the same signal. This guide treats those settings as crawler-friendly hints, then shows how to choose values that reflect real merchandising importance and real update behavior.

Where Magento 2 sitemap settings live and what they control

In the admin, the useful distinction is between the rules Magento uses to build sitemap entries and the specific sitemap file Magento writes to disk. The global rules live under Stores > Configuration > Catalog > XML Sitemap. That area is where Magento XML sitemap settings define the default priority and change frequency values for categories, products, and CMS pages, along with product image inclusion and scheduled generation behavior.

Those page-type sections matter because they set the baseline metadata Magento attaches to each URL class. Category settings apply to category landing pages, product settings apply to product detail pages, and CMS page settings apply to content pages such as About, Shipping, or buyer guides. The practical takeaway is that these defaults should reflect the role of each page type before you fine-tune edge cases: a frequently merchandised category behaves differently from an evergreen policy page, and Magento gives you separate controls so they do not need to send identical signals.

The same configuration area also controls automated generation settings. Generation frequency determines how often Magento attempts to rebuild the sitemap on its schedule; the error email recipient is the address Magento uses when sitemap generation fails; and related sender/template fields control how that notification is delivered. These settings do not decide which pages deserve inclusion, but they do affect whether the file stays current enough to match catalog and content changes.

The individual sitemap file is handled separately in Marketing > SEO & Search > Site Map, where you create or manage a sitemap record with a filename and path. The filename is the XML file crawlers will request, such as sitemap.xml; the path is the location where Magento writes it. This is the operational layer of Magento 2 sitemap configuration: the global settings describe the entries, while the site map record determines the actual generated file.

Store-view scope is the checkpoint many teams miss. If a Magento installation has multiple websites, stores, languages, or base URLs, sitemap choices should be reviewed in the relevant scope rather than treated as one universal file for every storefront. A strong setup keeps each store view’s sitemap aligned with its own URLs and content; a weak setup exposes mismatched URLs, missing localized pages, or a sitemap generated in a path crawlers are not meant to use.

How to set Magento sitemap priority values by page type

Treat the priority field as an internal weighting system for your own storefront. A higher Magento sitemap priority should mean “this URL matters more than other URLs on this same site,” not “this page should outrank competitors.” Search engines may use sitemap metadata as a discovery and crawl-planning hint, but a higher priority value does not override page quality, relevance, links, canonical signals, or indexability.

Priority and frequency settings by page type

Magento lets you set default priority values for categories, products, and CMS pages, so start with page-type intent before adjusting individual exceptions. The useful range is usually narrow: most well-maintained stores can express enough difference between URL types with values from about 0.3 to 1.0.

  • Homepage: 1.0. The homepage is normally the strongest internal hub and the main entry point to brand, category, and promotional paths. Give it the top value, but do not assign 1.0 to every major page or the signal becomes meaningless.
  • Top-level category pages: 0.8 to 0.9. Use the higher end for categories that drive revenue, contain stable inventory, and are linked prominently in navigation. Use the lower end for secondary categories with thinner demand or less strategic value.
  • Important product pages: 0.6 to 0.8. Active, in-stock, canonical product pages deserve a stronger signal than routine support content, especially when they are core products, high-margin items, or evergreen sellers.
  • Routine product pages: 0.5 to 0.6. This is a sensible default when the catalog is large and products are valuable but not all equally important. It avoids flattening the sitemap while still keeping products visible.
  • CMS pages: 0.3 to 0.6. Policy pages, contact pages, and basic service pages usually belong below commercial categories and products. Buyer guides, sizing resources, or comparison pages can sit higher if they support search demand and purchasing decisions.
  • Blog or guide content: 0.4 to 0.7. If your Magento store includes educational content, prioritize evergreen guides above announcements, expired campaigns, or short-lived posts. The distinction should follow usefulness, not publication volume.
  • Discontinued products: 0.0 to 0.3, or exclude them. If a discontinued URL still helps users find replacements, keep it low. If it is not indexable, redirects elsewhere, or has no search value, it should not be treated as an important sitemap URL.
  • Low-value filtered URLs: usually exclude, not downgrade. Faceted, sorted, parameterized, and duplicate-like URLs should not be kept in the XML sitemap just because they have a low priority value. If they are not canonical, indexable landing pages, leaving them out is cleaner than assigning 0.1.

A good Magento sitemap priority setup has visible separation between commercial hubs, active products, useful content, and marginal URLs. A weak setup gives every URL 1.0, which removes the relative meaning of the field, or pushes low-value pages into the sitemap with token low scores instead of excluding them.

Choosing change frequency values that match real update patterns

The frequency field should describe the rhythm of meaningful content changes, not how aggressively you want crawlers to return. In Magento sitemap configuration, change frequency is metadata attached to URL types such as categories, products, and CMS pages. It helps describe update patterns, but it should be treated as a hint rather than a command.

Use the available values as plain-language cadence labels. Daily fits URLs that genuinely change most days; weekly fits pages refreshed during regular merchandising cycles; monthly fits stable pages with occasional edits; yearly or a very low-change setting fits pages that rarely change after publication. The practical takeaway is simple: a page should earn a higher Magento sitemap frequency because its visible content, product mix, pricing, availability, or merchandising copy changes often, not because the page is commercially important.

  • Frequently updated categories: use daily when category listings, featured products, promotions, or availability shift often. Use weekly when the category is active but not changing every day.
  • Seasonal landing pages: use weekly during the active season or campaign build-up, then reduce to monthly or exclude the URL if the page becomes stale, expired, or non-indexable after the season.
  • Stable CMS pages: use monthly or lower for About, Contact, shipping, returns, and policy-style pages unless your team edits them regularly.
  • Products with price or stock changes: use daily only when those changes are frequent and visible on the product page. For ordinary catalog items with occasional edits, weekly or monthly is usually cleaner.
  • Rarely changed pages: use a low-frequency value rather than pretending the page changes often. Old informational pages, evergreen buying guides, and static brand pages do not need a noisy freshness hint.

Overstating change frequency weakens the signal. If every product, category, and CMS page is marked daily, the sitemap no longer helps distinguish genuinely active inventory from static content. Better indexing signals come from consistency: the sitemap metadata should align with what crawlers can see when they revisit the URL.

Do not confuse the frequency value with Magento’s sitemap generation schedule. The field describes how often a URL tends to change; the generation schedule controls when Magento rebuilds the XML sitemap file. A store can regenerate its sitemap daily while still marking stable CMS pages as monthly, or mark fast-changing categories as daily while relying on scheduled generation to keep the file current.

Magento image sitemap settings: base image vs all product images

Product images deserve their own decision because they can expand a sitemap quickly without always adding equal discovery value. In the Product Options area of Magento sitemap configuration, the image setting determines whether product entries carry no image references, only the main product photo, or a broader set of product gallery images where that option is available.

Product image sitemap decision

  • Exclude images: Magento writes the product URL without product image references. Use this for catalogs where the media is repetitive, supplier-provided, low quality, or not useful for image search discovery. It can also be sensible when many products reuse the same pack shot, logo, swatch, or placeholder image.
  • Include the base image: Magento adds the primary product image associated with the product. This is usually the cleanest default for stores that want efficient discovery without bloating the sitemap. The base image should represent the product clearly, not a placeholder, lifestyle banner, or duplicated thumbnail.
  • Include all product images: Magento can add multiple gallery image URLs for each product where the configuration supports it. This is most useful for visual catalogs, apparel, furniture, jewelry, parts, collectibles, and other products where alternate angles, colors, close-ups, or in-use photos help search engines discover distinct image assets.

The tradeoff is coverage versus efficiency. A Magento image sitemap that includes only the base image keeps each product entry lean and points crawlers to the most representative media. A sitemap that includes all product images exposes more assets, but it also increases XML size and can fill the file with near-duplicate shots if every product has multiple similar angles, repeated manufacturer images, or color variants that differ only slightly.

Choose the broader option when the extra images are genuinely distinct and valuable. A sofa with fabric close-ups, room scenes, and angle shots is a better candidate for all images than a commodity replacement part with six nearly identical supplier photos. For configurable products, also consider whether child products or variants create repeated image URLs; duplication does not make the sitemap stronger.

Image sitemap inclusion improves discoverability of image URLs, not the quality of the images themselves. Strong candidates have descriptive filenames, relevant alt text on the page, crawlable media URLs, and a product page that clearly matches the image. The practical rule is simple: include enough product imagery to help discovery, but do not turn the sitemap into a dump of every reusable or low-value media asset in the catalog.

Which Magento URLs should be in the XML sitemap

The same selectivity should apply to page URLs: the sitemap should be a curated list of pages you want crawled and indexed, not a dump of every address Magento can generate.

For products, include active, canonical product URLs that represent real buying opportunities or useful evergreen product information. A clean Magento product sitemap points crawlers to the preferred product page version, not every duplicate path created by category assignments, URL rewrites, configurable children, or variant-specific URLs. If a configurable product is the canonical selling page, list that URL and avoid adding child variants that canonicalize back to it.

Category URLs belong in the Magento category sitemap when they are indexable merchandising hubs: meaningful collections, strong internal-link destinations, and pages with stable search demand. Include top-level and important subcategory pages, but avoid thin categories, empty categories, temporary test categories, and duplicate category paths that do not serve a distinct purpose.

CMS pages should be included when they have standalone value, such as buying guides, brand information, shipping policies, store information, or evergreen landing pages. Exclude utility pages that should not compete in search, such as account pages, cart pages, checkout-related pages, thank-you pages, and other pages intended for logged-in or transactional use.

  • Out-of-stock products: keep them in the Magento XML sitemap when they remain indexable, are expected to return, and still help shoppers compare or research. Remove or deindex them when they are permanently unavailable and have no useful replacement path.
  • Discontinued products: do not leave them in the sitemap by habit. If the page has demand and points users to successors or alternatives, it may remain useful; if it is a dead-end page, remove it from the sitemap and handle it with a redirect, noindex, or removal strategy consistent with the page’s purpose.
  • Filtered and layered navigation URLs: exclude most parameterized filter combinations, such as color-size-price-sort URLs, unless a filtered page is intentionally built as a canonical landing page. These URLs can multiply quickly and dilute crawl attention.
  • Internal search pages: keep them out. Search-result URLs are generated by user queries and rarely make good canonical landing pages.
  • Noindex or blocked pages: do not include pages that tell crawlers not to index them or that cannot be crawled. A sitemap entry and a noindex directive send conflicting signals about whether the URL is meant for search discovery.

Store-view structure is the final checkpoint. Each Magento XML sitemap should use the correct base URL, language or regional URL pattern, and canonical URL for that store view. A strong setup keeps the sitemap, canonical tag, hreflang structure where used, and robots directives aligned so crawlers see one preferred version of each valuable page.

Generation, submission, and troubleshooting when Magento sitemaps don’t update

A clean URL set still has to be written to the right file at the right time. In practice, sitemap generation has four moving parts: the Magento rules that decide what belongs in the file, the schedule that rebuilds it, the filesystem location where the XML is saved, and the search-engine submissions that help crawlers discover it.

Sitemap generation and troubleshooting

Scheduled generation is the automated option. Use it when the catalog changes often enough that a manually refreshed sitemap would fall behind, such as stores with frequent product additions, inventory-driven category changes, or seasonal CMS landing pages. Manual generation is better as a controlled action after a launch, migration, URL rewrite cleanup, or major merchandising update. The tradeoff is simple: scheduled generation reduces maintenance risk, while manual generation gives you a deliberate checkpoint before search engines see a changed URL set.

Cron is the usual first place to look when a sitemap is stale. Magento’s scheduled jobs depend on cron running reliably; if cron is stopped, delayed, or overloaded, the sitemap file may not rebuild even though the XML Sitemap settings look correct in the admin. A good signal is a sitemap timestamp that advances after the scheduled window. A weak signal is an old file date paired with recent catalog changes that should already be reflected.

File path and permissions are the next checkpoint. The sitemap record defines where Magento writes the XML file, such as a public web path for a specific store view. If the directory is not writable by the web process, generation can fail or leave the old file in place. In multi-store setups, each sitemap should be reviewed against its own base URL and store-view scope; a missing product may simply belong to a different website, language, or catalog assignment than the sitemap being inspected.

  • Missing products: review status, visibility, website assignment, stock/indexing assumptions, and whether the product resolves to the canonical URL you expect. A disabled product or a product not assigned to that store view should not be treated the same as an active storefront product.
  • Missing categories: look for disabled categories, empty or hidden merchandising branches, incorrect store-view settings, and categories that are not part of the active navigation structure you intend crawlers to discover.
  • Wrong URLs: inspect base URLs, URL rewrites, canonical behavior, and store-code patterns. If the sitemap shows staging, HTTP, duplicate category paths, or the wrong language path, fix the store-view configuration before resubmitting.
  • Generation failures: use Magento’s error notification settings so the right recipient sees failed scheduled generation instead of discovering the problem weeks later in search reports.

Submission is the final handoff, not the fix for a bad file. Reference the sitemap in robots.txt when it is stable and publicly accessible, then submit the sitemap URL in Google Search Console and Bing Webmaster Tools. If either platform reports fetch errors, redirects, blocked access, or URLs excluded for indexability reasons, treat that feedback as a diagnostic layer over your Magento sitemap configuration rather than proof that the priority or frequency values need to be raised.

A practical baseline configuration for most Magento stores

For most stores, the baseline should be conservative rather than clever: make the file clean, keep the signals realistic, and let the sitemap support discovery without trying to force search rankings.

  • URL inclusion: include canonical, indexable storefront URLs only. Good candidates are active product pages, useful category hubs, and CMS pages that serve search or shopping intent. Weak candidates are filtered URLs, duplicate category-path product URLs, internal search pages, disabled products, thin campaign pages, and anything blocked or marked noindex.
  • Priority values: use a consistent hierarchy instead of giving every page the same score. A practical pattern is highest for the homepage, strong values for core categories, moderate values for active products, and lower values for supporting CMS pages. The takeaway is relative importance inside your own site, not a direct ranking boost.
  • Change frequencies: match the value to real update cadence. Daily can fit fast-moving categories or products with frequent price, availability, or merchandising changes. Weekly or monthly is more believable for stable products, evergreen CMS pages, and informational content. The goal is to avoid noisy signals that describe wishful crawling rather than actual page changes.
  • Product images: include at least the base image for product pages so the primary product visual is exposed in the XML sitemap. Use all product images when gallery images are distinct, crawlable, and commercially useful; stay with base images when alternate views are repetitive or the catalog is large enough that image volume creates unnecessary bloat.
  • Generation cadence: daily generation is a reasonable default for active Magento catalogs. Stores with rare catalog changes can use a slower schedule, while high-volatility catalogs may need more frequent rebuilds tied to dependable cron execution.
  • Discovery handoff: reference the sitemap URL in robots.txt and submit it through search engine webmaster tools once the file is stable, accessible, and representative of the live store.

As a final baseline, treat Magento sitemap configuration as one part of disciplined Magento SEO settings: a clean XML sitemap should expose the right URLs, describe them honestly, include useful product imagery, and stay current enough that crawlers are not working from stale assumptions.

Make Magento sitemaps clean, realistic, and useful

The durable habit is to review the sitemap as an output of storefront quality, not as a place to hide weak architecture. A strong file contains the preferred canonical version of each page, only pages meant for indexing, and no crawl traps from filters, duplicate paths, internal search, or expired promotions. More URLs do not make the sitemap stronger; better-selected URLs make it easier for crawlers to understand what the store actually wants surfaced.

The same standard applies to the metadata around those URLs. Priority should preserve a believable hierarchy between the homepage, category hubs, products, and supporting content. Change frequency should match real merchandising and content updates, not aspirational crawl demand. Image inclusion should serve product discovery: base images are usually the efficient minimum, while all product images make sense when the gallery adds distinct commercial value and does not overload the file.

Make sitemap review part of ongoing online store SEO maintenance. After catalog changes, launches, migrations, or product page optimization projects, confirm that Magento generated the current file, the file is reachable, and submitted sitemap reports are not showing preventable errors. The takeaway is simple: a well-maintained Magento sitemap configuration improves crawl efficiency and cleaner technical SEO signals, but it supports ranking work rather than replacing it.

Marina Lippincott

Written by Marina Lippincott

Tech-savvy and innovative, Marina is a full-stack developer with a passion for crafting seamless digital experiences. From intuitive front-end designs to rock-solid back-end solutions, she brings ideas to life with code. A problem-solver at heart, she thrives on challenges and is always exploring the latest tech trends to stay ahead of the curve. When she's not coding, you'll find her brainstorming the next big thing or mentoring others to unlock their tech potential.

Ask away, we’re here to help!

Here are quick answers related to this post to clarify key points and help you apply the ideas.

Where are XML sitemap settings in Magento 2?

Global XML sitemap settings are in Stores > Configuration > Catalog > XML Sitemap. The actual sitemap file record, including filename such as sitemap.xml and its path, is managed in Marketing > SEO & Search > Site Map.

Does Magento sitemap priority affect SEO rankings?

Magento sitemap priority does not directly make a page rank higher or force indexing. It is a relative crawl planning hint within the same site, so values like 1.0 for the homepage and 0.6 to 0.8 for important products only help describe internal importance.

What priority should product pages have in a Magento sitemap?

Important active, in-stock, canonical product pages should usually use a priority of 0.6 to 0.8. Routine product pages often fit 0.5 to 0.6, while discontinued products should be 0.0 to 0.3 or excluded if they are not useful or indexable.

How often should Magento generate an XML sitemap?

Daily generation is a reasonable default for active Magento catalogs with frequent product, inventory, category, or seasonal page changes. Stores with rare catalog changes can use a slower schedule, while high-volatility stores may need more frequent generation as long as cron runs reliably.

Should Magento include all product images or only the base image in the sitemap?

Including the base image is usually the cleanest default because it exposes the primary product visual without bloating the XML file. Include all product images when gallery images are distinct and valuable, such as alternate angles, colors, close-ups, or in-use photos for apparel, furniture, jewelry, parts, or collectibles.

Start Your Project With Us

Share some details, and our team will follow up.

Please write at least 20 characters.

Click to upload or drag and dropUp to 5 files, 10 MB each

    Get the MAK Digital Newsletter

    eCommerce design, development, SEO, and marketing insights, a few times a month. No spam, unsubscribe any time.

    By subscribing you agree to our privacy policy.