Problem/Motivation

The Yoast SEO module for Drupal displays the warning:
Bad SEO score
"No images appear in this page, consider adding some as appropriate". Even when a valid <img> tag is present in the content body (or the field configured for content analysis).
seo

Steps to reproduce

1. Use Drupal 10 or 11
2. Ensure the Yoast SEO module is installed and configured correctly.
3. Edit a content node using a WYSIWYG editor (e.g., CKEditor 5).
4. Insert an image into the body field(field_body) via the editor (ensuring the image renders as a proper <img> tag in HTML).
5. Save the content and observe the Yoast SEO analysis output.

Expected Result

Yoast should detect the image and not show the “No images appear in this page” warning.

Actual Result

Yoast incorrectly reports that no images are found, resulting in a bad SEO score, even though the image appears correctly in the rendered HTML.

Technical Details

  1. The <img> tag does appear in the HTML source of the analyzed field (body, typically).
  2. Verified that the text format allows <img>.
  3. Verified that the image is accessible and publicly viewable.
  4. The issue persists across:
  5. Drupal 10, 11
  6. Different text formats (Full HTML, Basic HTML)
  7. Yoast module versions 2.1.0
CommentFileSizeAuthor
#5 Screenshot 2025-07-12 at 22.47.52.png96.58 KBborisr
Screenshot 2025-05-21 103742.png27.34 KBkarishmaamin

Comments

karishmaamin created an issue. See original summary.

karishmaamin’s picture

karishmaamin commented
Issue summary: View changes
zubair-rana’s picture

zubair-rana commented

Facing the same issue on version 2.1.0

zubair-rana’s picture

zubair-rana commented

The issue was with the widget settings in the form display.
I have to select a view mode that has all the fields, including the image, so it can analyse the contents of the page.
In my case, it was "default", which was empty, and I use "full" view display mode, which fixed the problem.

borisr’s picture

borisr commented
StatusFileSize
new Screenshot 2025-07-12 at 22.47.52.png96.58 KB

I tested this issue with the latest dev version and I'am not able to reproduce the issue.
If this issue is still relevant, can you share an example of your page content? That might help in reproducing the issue.