A website is having issues showing the correct SEO Title
On (what seems like) random moments, without publishing the page itself, or the page it gets te incorrect title from, the SEO Title on the homepage (and therefor the title in the browser tab) changes.
I've been checking some things and have run out of things to check.
Below is how I get the MetaData element, then I just display the title found in there.
var meta = Model.Value<SEOChecker.Library.Models.MetaData>("seoSettings", Model.GetCulture());
The thing is, the SEO Title of the homepage has been what it is since the beginning and the title it is showing is from a completely different page.
I've made the change (back to) using the Helper. And it does appear fixed for now. But it was that wat when te problem first occurred, so I'll just have to wait and see now.
Republishing the homepage also "fixes" the problem, but of course that's not a real solution.
I'll see if it pops up again, and if so post back here.
Isseu with wrong Seo Title being returned
Using Umbraco 10 and SEO Checker 10.0.3
A website is having issues showing the correct SEO Title
On (what seems like) random moments, without publishing the page itself, or the page it gets te incorrect title from, the SEO Title on the homepage (and therefor the title in the browser tab) changes.
I've been checking some things and have run out of things to check. Below is how I get the MetaData element, then I just display the title found in there.
Am I missing something or have I found a bug?
Think it's getting the raw data from the property editor. What happens if you use the default Tag Helper?
use the default Tag Helper as it may be retrieving raw data from the property editor.
The thing is, the SEO Title of the homepage has been what it is since the beginning and the title it is showing is from a completely different page.
I've made the change (back to) using the Helper. And it does appear fixed for now. But it was that wat when te problem first occurred, so I'll just have to wait and see now.
Republishing the homepage also "fixes" the problem, but of course that's not a real solution. I'll see if it pops up again, and if so post back here.
is working on a reply...