I was wondering if there is a way to configurate the snippet preview based on multiple field, where you might use these fields to create the title.
Lets say I have a property for siteName and one for pageTitle .. and of course the default nodeName.
Then I often create a title like this, where it's pageTitle + " | " + siteName. If pageTitle doesn't have a value it would use nodeName: "HomePage | My Company" "Contact | My Company"
It seems that the Snippet preview just display the title of a single property like pageTitle or nodeName.
Is it possible to display it how the actually title is constructed and as the browsers/search engines would see it?
Okay, I found that there already is an option for this:
which gives me this:
However it requires my property with alias title to have a value:
if this field is empty it display this:
so in this case I would like to use the nodeName instead as fallback.
is it possible to have a customize option, where you can use an alternative field if the selected field property is empty? e.g. often I keep the nodenames short, but might want to override the title and therefore have a title property. So I just want the preview to match what I actually displays in the browser title.
Great you already found it. I would have replied with the answer of both of your replies indeed :). There ares some more config tweaks you might like (not related to snippets, but for sitemap etc) described in the manual http://soetemansoftware.nl/seo-checker/downloads
are the plans for rewriting SEO Checker with AngularJS in the backoffice instead of the usercontrols? e.g. have the fixed header, save button in top right to have same look as in the core. etc.?
The UX will be changed a little to have the same buttons as the Umbraco ones but it will not be a complete rewrite yet. SEO Checker is used by many on Umbraco V4 and V6 as well and that would break it. When most customers are on V7 and Higher it could be that pages will be converted to Angular.
Configurate snippet preview
I was wondering if there is a way to configurate the snippet preview based on multiple field, where you might use these fields to create the title.
Lets say I have a property for siteName and one for pageTitle .. and of course the default nodeName.
Then I often create a title like this, where it's pageTitle + " | " + siteName. If pageTitle doesn't have a value it would use nodeName:
"HomePage | My Company"
"Contact | My Company"
It seems that the Snippet preview just display the title of a single property like pageTitle or nodeName.
Is it possible to display it how the actually title is constructed and as the browsers/search engines would see it?
/Bjarne
Okay, I found that there already is an option for this:
which gives me this:
However it requires my property with alias title to have a value:
if this field is empty it display this:
so in this case I would like to use the nodeName instead as fallback.
is it possible to have a customize option, where you can use an alternative field if the selected field property is empty? e.g. often I keep the nodenames short, but might want to override the title and therefore have a title property. So I just want the preview to match what I actually displays in the browser title.
/Bjarne
Okay, I found answer on my question here :)
/Bjarne
Hi Bjarne,
Great you already found it. I would have replied with the answer of both of your replies indeed :). There ares some more config tweaks you might like (not related to snippets, but for sitemap etc) described in the manual http://soetemansoftware.nl/seo-checker/downloads
Best,
Richard
Hi Richard..
yep, will try to take a look at this..
are the plans for rewriting SEO Checker with AngularJS in the backoffice instead of the usercontrols? e.g. have the fixed header, save button in top right to have same look as in the core. etc.?
/Bjarne
Hi Bjarne,
The UX will be changed a little to have the same buttons as the Umbraco ones but it will not be a complete rewrite yet. SEO Checker is used by many on Umbraco V4 and V6 as well and that would break it. When most customers are on V7 and Higher it could be that pages will be converted to Angular.
Hope this answers your question.
Best,
Richard
is working on a reply...