XF 2.2 Upgraded to 2.2.15; Google indexing error this morning

Wildcat Media

Well-known member
I don't know if it's a coincidence, but I upgraded to 2.2.15 yesterday, and this morning I get an email with an error. Search console says:

1707063741888.webp

At the bottom of the page (if I view source), I find the section under <script type="application/ld+json"> and there is no "text" field.

I do see "articleBody" but that's all, at least in terms of what it seems to be looking for.

It is a "thread" not an article, if that matters. Also, viewing the source of this page here on XF does show the text field.
 
 
Not quite sure I follow, but even if I check with an unaltered stock XF style, the text field is still missing. But articleBody contains the post text.

It should be obvious but I didn't clarify--this is while viewing a thread, with the first post a traditional thread, not an article/question/poll.
 
Last edited:
They are functionally equivalent, but the rise in errors is for posts which only contain images or embedded media. The thread I linked contains more details but ultimately this is not a major concern and will be addressed in the future.
 
Sort of. Google is saying the posts which contain only photos or media (and no text) will not be eligible for rich results. It has no bearing on regular results or ranking and no bearing on whether the overall thread or other posts are eligible for rich results.
 
That doesn't quite apply to my situation, as the original post has one image. But the rest of the post, and all the replies, are text-based. So, I am thinking that maybe it's the presence of a single image (uploaded as an attachment) that is causing issues with Google? Or are they just blindly looking for a "text" field that doesn't exist, regardless of content?

Is there something we can add or edit to fix this, or should I not worry about it? Google's messages are too cryptic to be of much use, especially since they provide almost no guidance on what they are looking for. (Their one "help" link points to a generic landing page, not a link to the specific error.)

After having been removed from Google's indexing for a robots.txt entry they didn't like and didn't even use (crawl-delay), I'm wary of every message they send to me now.
 
I can't be sure without knowing the URL, but it's almost certainly displaying the error for that one post and parsing the others without issue. It's nothing to worry about, it just means that post (and others like it) are not eligible for rich results.
 
I can't be sure without knowing the URL, but it's almost certainly displaying the error for that one post and parsing the others without issue. It's nothing to worry about, it just means that post (and others like it) are not eligible for rich results.
I'll update this thread if Google starts flagging a lot more of the content in the forum. For now I'm going to consider it a fluke on their end.
 
Top Bottom