Search engine sitemaps.xml for EPiServer CMS

This tool allows you to generate xml sitemaps for search engines to better index your EPiServer sites. Although there are several EPiServer sitemap tools available like [SearchEngineSitemaps] (https://www.coderesort.com/p/epicode/wiki/SearchEngineSitemaps) and EPiSiteMap which have inspired this project this tool gives you some additional specific features:

• sitemap generation as a scheduled job
• filtering pages by virtual directories
• ability to include pages that are in a different branch than the one of the start page
• ability to generate sitemaps for mobile pages It also supports multi-site and multi-language environments.

The latest version is available on the EPiServer NuGet feed. You can find it by searching the term Geta.SEO.Sitemaps.

From nuget.episerver.com feed.

1. Install Sitemap plugin via NuGet in Visual Studio. Ensure that you also install the required dependencies.
2. Rebuild your solution.
3. Configure sitemap settings and schedule the sitemap generation process. Configuration available at CMS -> Admin Mode -> Search engine sitemap settings.

Add a new sitemap definition and fill values for sitemap host and other fields:

• Path to include - only pages that have external url in the specified virtual path will be included in the sitemap
• Path to avoid - pages that have external url in the specified virtual path will not be included in the sitemap. If Path to include specified this will be ignored.
• Root page id - the specified page and it's descendants will be listed in the sitemap. You can leave 0 to list all pages.
• Debug info - if checked sitemap will contain info about page id, language and name as a comment for each entry
• Format - currently standard or mobile (to specify [mobile content] (http://support.google.com/webmasters/bin/answer.py?hl=en&answer=34648))

In case of multiple sites you choose for which site to host this sitemap:

Each sitemap configuration must have a unique host name:

When configuration done go to the scheduled task "Generate search engine sitemaps" and run/schedule it to run in the necessary frequency. After the scheduled job has been run successfully you can view the sitemap(-s) by either opening the configured sitemap host or clicking "View" next to the sitemap configuration.

Add this to your web.config file:

<configuration>
<configSections>
<section name="Geta.SEO.Sitemaps" type="Geta.SEO.Sitemaps.Configuration.SitemapConfigurationSection, Geta.SEO.Sitemaps"/>
</configSections>

  <Geta.SEO.Sitemaps>
    <settings enableLanguageDropDownInAdmin="true" />
  </Geta.SEO.Sitemaps>
</configuration>

You can specify page specific sitemap properties (like change frequency, priority or inclulde/disinclude the specific page in any sitemap) for each EPiServer page by defining a dynamic property with type SEOSitemaps (and the same name):

and specify values for the dynamic property:

As of EPiServer 9, the Dynamic Properties is disabled by default. If you don't want to run on Dynamic Properties you can add the SEOSitemaps peoperty to a content type as below:

[UIHint(UIHint.Legacy, PresentationLayer.Edit)]
[BackingType(typeof(PropertySEOSitemaps))]
public virtual string SEOSitemaps { get; set; }

• Each sitemap will contain max 50k entries (according to sitemaps.org protocol) so if the site in which you are using this plugin contains more active pages then you should split them over multiple sitemaps (by specifying a different root page or include/avoid paths for each).

See CONTRIBUTING.md

1.0.0. Initial version

1.4.1.

1. Added support for alternate language pages. See details at https://support.google.com/webmasters/answer/2620865?hl=en.
2. Added sitemap index support (/sitemapindex.xml) that might be useful if you have more than one sitemap on your site.
3. Added a new sitemap format, Standard and Commerce, including both standard and commerce pages in one single sitemap (requires the Geta.Seo.Sitemaps.Commerce NuGet package).
4. Added ability to create language specific sitemaps.

1.5.0.

1. Added support for EPiServer 9
2. Removed depedency on log4net

1.6.1.

1. Added support for Episerver 10