Public Edition and App/Embed Content
Compare the main content with additional app or embedded areas. Check which information is already available during normal retrieval and which only appears after interaction.
Compare editor preview, original retrieval, and published view after apps load. An embedded third-party content does not automatically belong to the directly delivered main text.
Where to check the setting in Wix
Go directly to the published page and examine app and embedded content separately. Check if an important text is loaded only after scrolling or clicking. The preview in the editor is not sufficient control retrieval.
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 Wix
Call up the URL as a logged-out visitor directly and check which content becomes visible without interaction. Do not generalize an app malfunction as a complete failure of the Wix page.
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.
Reference: published Wix/Wix Studio websites. SEO settings differ by static page, dynamic page type and installed app; do not require a freely managed server configuration.
Classify the general error
Definition, system-independent causes and further correction examples: Distinguish Missing Content from Intentionally Reloaded Functions