Not sure if everyone has had 18.12 land on their community yet however it boasts some SEO enhancements however since 18.12 I'm constantly getting alerts from google search console about errors with my SEO specifically around the Q&A structured data scheme.
This has been raised with support and currently, on a bug backlog, I'm just curious if anyone else has observed this since 18.12 was pushed to live.
>> This is checked-in and should make it to 19.1 unless there is some exception.
>> Can you paste me which page is seeing this error? I tried a Talktalk forum page and there is no error on entity name. Tried with this page
Thanks, I think i'll have to wait for the next alert, i just logged into my search console and whilst there is an entry for that alert there is no URL recorded which is very odd as i have a url for the answer count.
I'll keep checking the console to see if it captures the trouble url, sadly the email alerts dont show the problem page just the domain name.
@Fellsteruk We got the same alert and logged a ticket with Lithium. Indeed a bug and will be fixed in the next release so we just have to wait for it.
Another bug was the text editor in IE Explorer browser (Yes, some of our experts still use that IE version). @mention is not working as well as some text editing capabilities like underline etc,
Also fixed in the next release.
I commented on the release note blog with these issues.
I just got an email from Google Search Console that says:
Top Warnings (5 maximum)
Warnings are suggestions for improvement. Some warnings can enhance your appearance on Search; some warnings can become errors in the future. The following warnings were found on your site:
Is the proposed fix coming soon going to include all these schema designations for better performance in SEO? Or will it just remove some classification to clear the errors?
What version are you on http😕/<your community here>/status/version as of 19.1 this should have been fixed i believe mine stopped happening as of 19.1 but i also got one of these alerts yesterday so I've flagged it with support again, id suggest you do the same.
Either 19.1 didn't fix the issue or google have made changes