Dashboard – SEO – Titles & Metas (“General” tab)
Devoda SEO makes it possible to set templates for titles for:
But in what order will that be done?
Order of importance examples
Let’s take the “Home” page as an example. You can choose to have a “Home title format” for this one. In case you leave this empty, it will use the “Default title format”. But, you may have configured a “Title format” under “Page Types”. If so, it will use that one.
Another example could be your “Contact” page. This page is not the homepage, not the search page so this will look for the “Page Types” title format. If that one is not entered, it will use the “Default title format”.
In all cases, if a “Meta Title” for a specific page is entered, this one will be used instead of title formats.
Title (segment) separator
By default, concrete5 will separate the page title and the site name with colons ( :: ). This can be configured by changing a specific file. With Devoda SEO however, you will be able to configure this separator yourself. There are 14 available separators from which you can choose. Can’t find the one you’re looking for? Do let me know!
Default value:
::
App version displayed in header
There is an extra meta tag being displayed in the “head” section of your website, which will have the version number of your concrete5 application, along with “concrete5”. Many developers/site users may think this isn’t necessary and may make your site more vulnerable if there’s a leak in a specific app version. So you can chose to disable this. Feel free to keep it the way it’s configured by concrete5’s default.
Default value:
Enabled
Title formatting (Default title format, Pagination page format & Home title format)
You can use variables here, as entered by default, like so:
{{ title }}{{ page }} {{ separator }} {{ sitename }}
Let's break this up.
You could also do other things, like use a page attribute. That can be done like this:
{{ page_attribute {% {"attribute":"your_attribute_handle"} %} }}
It may look complicated, but it isn't that complicated at all. You only have to change "your_attribute_handle" into the handle you have for a Page Attribute. Available options: