Builder widgets and reloaded content
Compare a normal post with the affected builder layout. If only there is missing the main content in the HTML, first examine the output of this component.
Compare the public server response to the state after loading all builder scripts. A visible text in the editor or in the preview is not proof that the direct public retrieval already contains it.
Where to check the setting in WordPress
Go to the URL directly logged out and compare page source text and browser DOM. If the missing content is in a builder widget, check its data source and loading condition; a widget that loads content only after a click does not deliver it in the first HTML.
Example of this specific finding
Illustrative control case: The server delivers only one app container; product name, description and links are created only after a JavaScript request. Direct retrieval does not contain the technical content.
follow-up audit in WordPress
Also test as a logged-out visitor. Consent, optimization plugins and delayed JavaScript can change the result compared to a logged-in preview.
Compare initial HTML and rendered view of the same URL. Check that the main content is reachable without prior navigation and that necessary resources can be loaded.
Derogations and scope
Shopping cart status or personalized elements may be reloaded consciously. Little initial HTML alone does not prove that Google cannot render the page.
Related: WordPress with classic or block theme. SEO plugins and page builders are different; there is no universal menu path for all installations.
Classify the general error
Definition, system-independent causes and further correction examples: Distinguish Missing Content from Intentionally Reloaded Functions