The Sitemap XML feature generates a dynamic sitemap XML index file, a single file for communities, and a series of XML files for each block of content. A block can have a maximum of 50,000 URLs. The currently supported content types are threads, documents, and blog posts (not including those in system or user containers), and social groups as well.
The Sitemap XML feature will only work for sites that are publicly accessible to guests.
How do I get this feature?
This feature is available automatically in Jive 7.0.1 and Jive Cloud. Older versions of Jive 7 and Jive 6 will require a plugin installation
|Jive Cloud (External communities)||Available in the product automatically|
|7.0.1 or newer||Available in the product automatically|
|7.0.0.x||Plugin installation required|
|6.0.x||Plugin installation required|
|5.0.x or older||Not available|
Overview of Sitemap Implementation
The sitemap xml feature is an implementation of the Sitemaps XML protocol in Jive, allowing for search engines to crawl content in your Jive community.
This feature uses the Sitemap Index page in Jive to expose links to individual Sitemaps. Each individual sitemap will then contain URLs to individual content items in Jive. The Sitemap Index also contains sitemaps for all guest-viewable spaces and public groups.
The sitemaps are split into one sitemap per content type per place. For example, there will be a sitemap for all discussions in “Space A” and a separate sitemap for all documents within “Space A”. A sitemap is allowed a maximum of 50,000 URLs per sitemap so if there are more than 50,000 documents in “Space A”, a second sitemap will include the next batch of 50,000.
Each entry in a sitemap has an element that indicates change frequency. The change frequency is calculate using these rules:
- if modification date < 24 hours, "hourly"
- if modification date > 24 hours and < 1 week, "daily"
- if modification date > 1 week and < 1 month, "weekly"
- if modification date > 1 month and < 1 year, "monthly"
- if modification date > 1 year, "yearly"
You can manually load the sitemap file by going to [JIVEURL]/sitemap-index.jspa
Submission to Search Engines
Search engines need to be made aware of the sitemap xml files. Each search engine can have different methods to be informed. Jive recommends informing the search engine manually the first time. For more information, read: http://www.sitemaps.org/protocol.html#informing
A scheduled task is configured to run at 3:45 AM. It will submit the location of the sitemap index file to all configured search engines. The job can be disabled via the admin console. Any errors during sending will be logged.
The Admin URL for the Sitemap settings is: <instance url>/admin/sitemap-settings.jspa. The admin page can also be found by navigating to the admin console and clicking System > Settings > Sitemap XML Settings.
The default configuration should work for most deployments. The available configurations are described below.
Editable In Sitemap Admin
Contains URLs to submit index file to. URLs are delimited by commas. The URL should be entered in its entirety excluding the URL to the index file. For example, <searchengine_URL>/ping?sitemap=. The two highest profile ones are:
The maximum number of URLs for objects that will be created in a sitemap file. This may not exceed 50,000. If there are more objects than the maximum, then another file will be generated containing the next block up until the maximum count is reached again.
If true then the scheduled task will run every 24 hours sending the index file location the configured search engines.
Extended Community Properties
Editable In Sitemap Admin
Changing Requires Clearing Sitemap Cache
Community override for the global value set in the system properties.
If set to true then the community will be excluded from the sitemap generation.