This app provides two ways of generating a sitemaps:
Check Enonic Market for further details on installing apps in XP. You have multiple options. The easiest way is to just go to the Application admin tool inside Enonic XP and hit the "Install" button, now find this app and click "Install". Done!
This app comes with a controller mapping to the path of sitemap.xml on the root of the site - [yoursite.something]/sitemap.xml.
This means that any request that matches, for example https://www.example.com/sitemap.xml, will be sent to this app's sitemap controller.
The sitemap controller will respond with a sitemap.xml file.
It includes the required tags of a sitemap.xml (<loc>, <lastmod>, <changefreq> and <priority>).
Be aware that only content from the current site will be added to a site's sitemap.
NOTE: The order of the controller mapping is set to 50.
When doing external rendering, via for example Next.XP, you can fetch the data needed to generate a sitemap.xml file via a Guillotine Extension.
Use the Query playground in Content Studio to study the Guillotine Schema. You can find a field named sitemap on the HeadlessCms object type.
You may also study how we did it in our own site-enonic-next.
TIP: In the Next.XP app there is a controller mapping with a order of 11, so that it can provide it's own sitemap.xml
The app has a site configuration where you can add content types and configure their change frequency and priority.
The app will automatically add the site content, if not already added in the site configuration mappings.
Limit the number of items in the file. Default: 10000. Max: 50000.
WARNING: The number of included items will affect the time it takes to generate the sitemap.xml file.
By default, the app will use the domain name of the site. If you want to override this, you can specify a custom domain name in this field.
Here you can specify which content types you want to include in the file and their change frequency and priority per content type.
The <priority> tag has the default value of 0.5.
The site content itself will be added automatically with a priority set to 1.0 and changeFrequency set to hourly. If you want to overwrite these defaults, please add portal:site as a mapping manually and customize the settings.
Here you can add exclusion patterns for specific content paths.
For example, to exclude all paths ending with /foo, you can add the following pattern: */foo
To exclude a specific content use: /full/path
To exclude just the children of a specific folder use: /some/folder/*
To exclude a specific folder AND it's children use two patterns:
/some/folder/some/folder/*
CAUTION: Using a single pattern "/some/folder*", could be problematic as it also matches "/some/folderOrContentWithLongerName*"
To exclude all content that has a string anywhere in the path use: *hasInTheMiddle*
To exlude all content that ends with a string use: *endsWith
Check out Sitemaps XML format to learn more about how it all works.
In version 2.0.0 the sitemap service has been removed in favour of a Guillotine Extension.
If you are using the controller mapping, this doesn't affect you.
If however you are doing external rendering, see Headless integration.
See the Market page