Magnolia 5.3 reached end of life on June 30, 2017. This branch is no longer supported, see End-of-life policy.
The Google Sitemap app is installed by the Google Sitemap module.
Note that using Google Sitemaps does not guarantee that all links will be crawled, and even crawling does not guarantee indexing. Nevertheless, a Google Sitemap is still the best insurance for visibility in search engines. Webmasters can include additional information about each URL, such as when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Google Sitemaps adhere to the Sitemaps protocol and are ready to be submitted to search engines.
The Google Sitemap app is installed by the Google Sitemap module . The app is based on the content app framework so its configuration is typical of any content app. The app is configured at
The Google Sitemap app operates on the
googleSitemaps workspace that stores the sitemaps.
The Google Sitemap module registers a custom
mgnl:siteMap node type. The Google Sitemap app operates on nodes of this type and on folders.
Sitemaps are created in the Sitemaps app.
To create a new sitemap,
Mobile. Google recommends that you use separate sitemaps for different content types. Mobile sitemaps use compliant mobile-specific tag and namespace requirements.
Sites: Select the relevant site in the Pages chooser. You can also select subpages as the root node to, for example, create different sitemaps for site sections.
The root node of the selection will not be included in the site map. Assume you have the following trees:
/a/b/d. If you select
/a/b as the root of the sitemap, only pages under
d will be included in the map. The root node
b will not be included.
Sitemap links are generated using the protocol that is defined in your site definition. The default protocol is HTTP. If you want HTTPS define the protocol in domain mapping.
The default values displayed in the Default Values Selection tab are configured in
To edit the individual sitemap entries click Edit site map entries. The site pages display in an expandable tree and you can set properties for each page.
To define properties for the entries click Edit entry properties:
priorityin XML Sitemap protocol.
never. Use the value
alwaysfor pages that change each time they are accessed. Use
neverfor archived pages that will never change. See
changefreqin XML Sitemap protocol.
hideIngoogleSiteMapproperty is stored in the page itself. This means you need to activate the page. Publishing the sitemap only is not enough.
If you included virtual URIs in the sitemap you can edit their properties. Click Edit virtual URI entries to open the Virtual URIs subapp. The pages display as individual entries (as opposed to a tree) and you can set the same properties that are available for pages, except Hide children that is inapplicable.
Hide default mappings defined in the
ui-admincentral module, such as those for accessing AdminCentral. Public users will not access AdminCentral, so these URLs do not need to appear in the sitemap. Also, hide mappings that use regular expressions in the
toURI property. These are not understood by search engines as regular expressions.
Publish the sitemap to the public instance to ensure that it is accessible to the search engines.
You can view the XML sitemap on the author or public instance at
/<CATALINA_HOME>/<contextPath>/sitemaps/<sitemap name>.xml, for example,
. Note that a filter mechanism removes duplicate urls.
Here's the rendered XML for a
Mobile sitemap for the
demo-project site. Note the use of the
siteMapsConfiguration page template renders the sitemap. The configuration is at
SiteMapModelis the main model class for site map templates.
includestwo alternative scripts,
mainConfiguration.ftl(GIT) that renders Text or XML content dependent on the URL extension.
The virtual URI mapping configuration is at
compares source URI to names of sitemaps available in
googleSitemaps workspace and prepends the prefix.
Add the following line in your
robots.txt file. Include the full URL to the sitemap:
Submit the sitemap to major search engines via the webmaster tools of each engine or wait for the engines to find the sitemap on their own.