Yes, that matches what I’m seeing too:
I don’t appear to have a “TEST LIVE URL” button on mine though? ![]()
A few screen shots if it helps:
Yes, that matches what I’m seeing too:
I don’t appear to have a “TEST LIVE URL” button on mine though? ![]()
A few screen shots if it helps:
@davidb things are looking better this morning too:
Is there scope to address the yellow
items too?
I’ve just re-started validation on the ones that are clearly trending downwards and the flat-lining ones:
But this one won’t even pass the pre-validation:
If it helps, there only seem to be two affected topics.
Not sure if relevant but the first post of this topic only contains hyperlinks: https://greyarro.ws/t/new-gimp-3-0-a-viable-free-alternative-to-photoshop/93092
And this one only has a video in the first post: https://greyarro.ws/t/how-to-film-edit-cinematic-fpv-drone-fly-through-dji-03-air-unit/74515
Is a lack of actual content the issue there perhaps?
Thanks, I will investigate this. I suspect it’s because the OP contains no text at all.
We use the OP text as part of the question in the QAPage schema (for topics enabled for Discourse Solved). If there is no text in the OP then we may need to either skip it or use some placeholder (maybe using the topic title in the text value would work) to prevent Google from showing this error.
We already skip individual posts now if they have no text, but it looks like we can have “questions” in this way without body text so will need to account for that.
I saw a new issue crop up yesterday
Missing field “text” (in “mainEntity”)
These appear to be affecting pages with translations. Here’s an example
https://discussion.mcebuddy2x.com/t/mcebuddy-2-3-and-nas/1763/2?tl=zh_TW
Google search is highlighting this:
</span>
</div>
<div class="post" itemprop="text">
<p>这可能是2.3版本的bug,自那以来已有超过500项新功能和修复。请更新到最新版本,如果仍有问题请反馈。</p>
<p>同时看看这个</p>
<aside class="quote" data-post="1" data-topic="25">
<div class="title">
<div class="quote-controls"></div>
<img alt="" width="24" height="24" src="https://discussion.mcebuddy2x.com/letter_avatar_proxy/v4/letter/m/34f0e0/48.png" class="avatar">
<div class="quote-title__text-content">
<a href="https://discussion.mcebuddy2x.com/t/mcebuddy-solution-to-common-errors-and-issues/25?tl=zh_TW">MCEBuddy FAQ - Common Issues and Errors</a> <a class="badge-category__wrapper " href="/c/installation/documentation/7?tl=zh_TW"><span data-category-id="7" style="--category-badge-color: #3AB54A; --category-badge-text-color: #FFFFFF; --parent-category-badge-color: #12A89D;" data-parent-category-id="5" data-drop-close="true" class="badge-category --style-square --has-parent" title="Documentation about Installing and Uninstalling MCEBuddy including User Guides, Tips n Tricks and Solutions to Common Issues"><span class="badge-category__name">Guides and Solutions</span></span></a>
</div>
</div>
<blockquote>
<img width="20" height="20" src="/images/emoji/apple/play_button.png?v=15" title="play_button" alt="play_button" class="emoji"> Table Of Contents:
</blockquote>
</aside>
</div>
<meta itemprop="upvoteCount" content="0"><meta itemprop="url" content="https://discussion.mcebuddy2x.com/t/mcebuddy-2-3-and-nas/1763/2">
</div>
</div>
It’s mainly there but is still be failing on three URLs.
Both failures are for the same three URLs too:
In case it helps, we had two issues: “Missing field ‘name’ (in ‘mainEntity’)” and “Missing field ‘answerCount’ (in ‘mainEntity’)”. After upgrading to v2026.5.0-latest (commit 601e66da60), and triggering a validation from Google Search Console, both the issues are 100% fixed ![]()
I’m also running 2026.5.0-latest (601e66da60) and still face the issue discussed.
불행히도 Google Search Console가 보여주는 내용을 신뢰할 수 없습니다. 이 도구는 검증이 실행되는 동안(최대 30일까지) 캐시된 인덱스에서 새로운 사례를 기존 이슈에 추가하는 매우 성가신 습성이 있습니다. 그리고 새로 추가된 오래된 인덱스 항목은 실행 중인 검증을 즉시 실패하게 만듭니다.
따라서 수정이 배포되기 전에 마지막으로 크롤링된 페이지의 수에 따라 검증을 여러 번, 심지어 수십 번까지 트리거해야 하거나 몇 달을 기다려야 하는 경우가 흔합니다. 실패를 유발한 항목들이 실제로는 정상적인지 확인하려면 해당 항목의 라이브 인스턴스를 수동으로 검사하고(마지막 크롤링 타임스탬프를 비교하여) 문제가 없으면 검증을 다시 트리거할 수 있는지 확인하면 됩니다(아니면 실패한 항목이 수행되는 빠른 예비 검사에서 실패할 것입니다).
해당 이슈는 Discourse 측에서는 완전히 해결되었습니다. Google 인덱스에 있는 각 페이지가 실제로 업데이트될 때까지 몇 달간의 인내심만 필요합니다.