SEO view configuration

general this section explains the possibilities of configuring data for search engine optimization open graph keys prefixed with og are there to set open graph metadata they are generally rendered as follows { og description "some description" }\<meta property="og\ description" content="some description"> twitter keys prefixed with twitter can be used to set twitter metadata they are generally rendered as follows { twitter site "@username" }\<meta name="twitter\ site" content="@username"> it is also possible to provide additional label and data values setting twitter misc as an object in that case, meta tags will be rendered in a way that for each key value pair, there will be two meta tags with name="twitter\ labelx " and "twitter\ valuex" with their content values being the corresponding key and value, e g twitter misc { "written by" "author", "est reading time" "5 minutes" }\<meta name="twitter\ label1" content="written by"> \<meta name="twitter\ data1" content="author"> \<meta name="twitter\ label2" content="est reading time"> \<meta name="twitter\ data2" content="5 minutes"> languages language sets the language on the html tag falls back to the value set in experience config json or 'en' if none is set alternates sets alternate language links for the current page path has to be a relative url and the full url will be calculated at runtime robots sets the robots value for search engines to prevent accidental indexing of sites, the value of robots is only set on custom domains and only, if preview is not set, otherwise "noindex, nofollow" is set custom meta tags it is also possible to provide additional custom tags those will be rendered as follows { "key" "value" }\<meta name="key" content="value"> content seo metadata on pages where the content body component is used (e g article pages), additional seo metadata might be set automatically, if the content provides it via the yoast plugin the configuration on the view level always supersedes the one from the content, e g if the view has a title configured, the content will not attempt to set its own title as metadata exceptions some keys should not be configured in the seo object canonical & og url experience will generate the canonical url automatically, therefore setting canonical or og url manually will not have any effect title the title should be set using the corresponding field on the view docid jl6ufl2jd2us8qkfrbpp configuration field instead