Missing field 'text' (in 'mainEntity.suggestedAnswer')

Richie
Sun, 05 Apr 2026 07:44:41 +0000
Bug

Further to this bug last week:

Google search console acceptedAnswer error Bug

Continuing the discussion from Either 'acceptedAnswer' or 'suggestedAnswer' should be specified: I had this issue pop today suddenly after updating to this week’s latest build. Any thoughts as to why it suddenly started? The site has been around for a decade and so has the page that’s affected by it. The topic has only one post (wiki) from the admin (it’s a notice FAQ topic).

And:

github.com/discourse/discourse

FIX: Skip QAPage schema when topic has no visible answers (#38964)

main ← fix/qa-page-schema-no-answers

merged 01:02PM - 02 Apr 26 UTC

ZogStriP

+156 -61

Google Search Console reports acceptedAnswer/suggestedAnswer errors on topics th…at emit QAPage structured data with answerCount:0 and neither field present. This affects single-post topics, topics where the only replies are hidden or small action posts, and topics whose accepted answer has been hidden. The fix introduces two checks: 1. A `has_eligible_answers?` query in SchemaUtils that verifies at least one visible, regular-type reply exists before emitting QAPage schema (both JSON-LD and microdata). Topics without eligible answers fall back to the default DiscussionForumPosting schema. 2. A `has_answers` policy in BuildSchemaMarkup that gates on the materialized accepted_answer/suggested_answers after they've been fetched, catching any edge cases the topic-level check might miss. Additionally, `fetch_accepted_answer` now checks post visibility via `Guardian.new.can_see_post?` (anonymous perspective) so hidden accepted answers are excluded from schema output rather than being advertised to search engines. The `"answered only"` setting also uses this visibility check instead of just testing whether an answer_post_id exists. https://meta.discourse.org/t/399525

I updated this morning to 2026.4.0-latest (97400099a5) but I’m still unable to validate the fixes with Google

My Google search console is showing:

Clicking through to the validation / fix steps:

And when I try to validate any of the fixes:

I get the same “affected pages were found” error for all three types.

Have I missed something?

5 сообщений - 2 участника