What Wix gets wrong most often
Wix renders much of the page client-side. A raw fetch can return a thin shell while the browser shows a complete page, which puts content at risk for any crawler that does not run JavaScript.
Social preview text and images are often left empty, so a shared link falls back to a generic card.
Images are served at the size they were uploaded, so a hero can be far heavier than the space it fills, especially on mobile.
robots.txt editing is available in Wix SEO settings, but it is easy to leave a default in place that does not reference the sitemap or that blocks something by accident.
Because the platform owns the server, transport and security headers are set by Wix, so the useful checks are the ones about content and rendering rather than headers.
The checks that matter most on Wix
- JavaScript renderingHow much of the visible content a plain fetch actually receives.
- Title and meta descriptionMissing or defaulted titles and descriptions, and incomplete Open Graph tags.
- ImagesMissing alt text and dimensions on a platform that serves full-size uploads.
- Real-user Core Web VitalsField data that reflects what Wix visitors on phones really experience.
- XML sitemapWhether the generated sitemap is fetchable and its URLs are alive.
- robots.txtWhat the editable robots.txt actually allows and blocks.
What to do about it
- Put the important content, especially the page heading and the main copy, where it is present in the raw HTML rather than injected later.
- Fill in the social share settings so og:title, og:description and og:image are set per page.
- Re-export or replace oversized images at the size they display, and add alt text in the image settings.
- Review the robots.txt that Wix generates and make sure it references the sitemap and blocks nothing you need crawled.
- Check Core Web Vitals on mobile first, since that is where the heavy assets and client-side rendering show up most.
A typical Wix failure, worked through
The setupA Wix page relies on strips and a repeater that populate only after JavaScript runs. The raw HTML returns the layout but almost none of the text.
What the check reportsThe render check reports that a browser sees far more text than a plain fetch. A crawler or assistant that does not render sees a nearly empty page.
The pointOn a platform you cannot change the rendering of, the fix is to make sure the essential text is also present in the initial HTML, for example in the page description and headings.