---
schema_version: "1"
id: b7cecde987e1605860ac3587b431e3428ff963d0675ee5162825d060f171f338
title: Sitemap Attribute Options in B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_sitemap_attribute_options.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_sitemap_attribute_options.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f2d528f183f7b3f7abb2ef7d3538e85df7cd8468d84c696da104fc1ceb476b0b
description: Your store’s sitemap has attributes that control how frequently search engines crawl your pages, what priority to crawl them in, and what content to include.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Sitemap Attribute Options in B2C Commerce

Your store’s sitemap has attributes that control how frequently search engines crawl your pages, what priority to crawl them in, and what content to include.

## Change Frequency Attribute

The change frequency of a page indicates to search engines how frequently the page can change. However, this doesn’t dictate how often the search engine crawls the page. You can set the `Change Frequency` attribute to one of the following values:

- always: Use this value to describe documents that change each time they’re accessed.
- hourly
- daily
- weekly
- monthly
- yearly
- never: Use this value to describe archived URLs.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png)

Note If you’re using content slots, make sure that the frequency matches that of the scheduled changes to content.

The order of precedence for `Change Frequency` and `Priority` values are:

1. The page-specific attributes of the item.
2. Then the classification category of the product.
3. Then the primary category of the product.
4. If no category attributes are found, the default settings configured in the catalog feed are used.

## Priority Attribute

Set the Priority value from 0.0 to 1.0 for one digit past the decimal (for example, 0.1, 0.2). Search engines use this to determine which pages to crawl first. While this has no effect on the rank of your page in search results, it does make sure that if a page is important, that it's more likely to be present in the search index. If no value is specified, then the search engine assumes the default priority of the page is .5. Pages with higher values are assumed to be more important and pages with lower values are assumed to be less important.

## Included Attribute

The `Included` attribute is set to `NONE` by default.

- If all objects are set to `NONE`, the system default has Content excluded and Folder URLs included, and require the sitemap-included-flag set to false at the Content object to be included or Folder object to be excluded.
- If all objects are set to `NONE`, the system default has Product URLs _not_ included.
- If all objects are set to `NONE`, the system default has Catalog URLs included.

Set the `Included` attribute to one of the following values:

- NONE: Undefined by the item, so a fallback occurs using the assigned catalog category, via the order of precedence described below.
- 1 (YES): The item is always included in the sitemap, no matter what setting a parent category has.
- 0 (NO): The item is always excluded from the sitemap. Salesforce recommends setting content snippets, such as footers and headers, to NO.

The order of precedence for `Included` values is as follows:

1. If the classification category exists, retrieve a value from this category or one of the parent categories up to the root category. If the classification category is a root category, the item is included.
2. Then, if the product has a primary category in the current storefront catalog, retrieve a value from this category or one of the parent categories up to the root category
3. Else, the item is excluded.