Jahia CMS & SEO - Overview

Jahia CMS offers several built-in features to manage and improve your technical SEO. The following table provides a high level overview of these features: their name, description and which Jahia module is providing them. It is also a good list of features that any CMS should have regarding technical SEO. Documentation and details are available for each module.

Name of the feature	Jahia module providing the feature	Description
Robots.txt	Robots.txt	A simple UI to edit the robots.txt file
Sitemap configuration & generation	Sitemap	Configuration UI and automated generation of the sitemap files. This feature is taking languages, live roles and no index into account.
Page metadata - No index	Sitemap	A field available when editing any page, to set the content as "Noindex" in the robots page metadata and remove the page from the Sitemap
Page metadata - No follow	Sitemap	A field available when editing any page, to set the content as "Nofollow" in the robots page metadata.
Vanity & canonical URLs	Site settings SEO	A complete UI to define and manage vanity URLs & canonical for each page. Also provides a dashboard to give an overview of all used vanity URLs.
Page metadata - Alternate	Site settings SEO	Automated generation of alternate / hreflang tag, to provide information to search engines about other translations of the page
Page metadata - Canonical	Site settings SEO	Automated generation of self-referential canonical tag
Page metadata - Description	Jahia core	A description field is displayed by default in the content editor form on every content items. This is shown under SEO section for displayable content items. It is defined as localized text in `jcr:description` property of the node It can be used to define localized meta description for the displayable content using either meta property `<meta name="description" content="<jcr:description>"/>` or as one of open graph meta tags `<meta property="og:description" content="<jcr:description>"/>`, or both. To do so, retrieve the value of this field from your page templates. See https://github.com/Jahia/luxe-jahia-demo/blob/main/src/server/components/SeoMetaTags.jsx for example.
Page metadata - Keywords	Site settings SEO	A keywords field is displayed by default under SEO section in the content editor form for every displayable content item. It is defined as a localized list of keywords in `seoKeywords` property of the node. It can be used to define a list of localized keywords tag for the displayable content using meta tag `<meta name="keywords" content="<seoKeywords>"/>}`. To do so, retrieve the list of values of this field from your page templates. See https://github.com/Jahia/luxe-jahia-demo/blob/main/src/server/components/SeoMetaTags.jsx for example.
Page metadata - Open graph image	Site settings SEO	An open graph image field is displayed by default under SEO section in the content editor form for every displayable content item. It is defined as an image node reference in `openGraphImage` property of the node. This can be used to add an image reference that will be used in the Open Graph meta tag, that can enhance sharing of displayable content links within social media networks, using open graph meta tag `<meta property="og:image" content="<URL for openGraphImage>"/>` To do so, retrieve the URL for the image node reference contained in this field from your page templates. See https://github.com/Jahia/luxe-jahia-demo/blob/main/src/server/components/SeoMetaTags.jsx for example.

Note regarding page metadata fields: Twitter cards work as OpenGraph but with a different syntax in the html page header, so you can use the same <jcr:description> , <seoKeywords> and <URL for openGraphImage> tags. If you want different values for Twitter, you'll have to create the desired fields and extend the SEO section.