🔍 What Is the Post-Render Overwrite Issue?
When Search Atlas publishes SEO changes to a Wix-hosted site, Wix can re-render the page after publishing and overwrite those changes with its own cached or default values. This is known as a post-render overwrite.
The result is that your Search Atlas optimisations appear to save correctly inside the platform but do not persist on the live Wix site. This behaviour has been identified as a recurring defect affecting Wix integrations and is actively tracked by our engineering team.
⚙️ What Specifically Gets Overwritten?
Metadata and content changes made through Search Atlas on Wix-connected sites may not persist after Wix re-processes the page. This can affect page-level SEO fields and content elements that Search Atlas writes via the Wix integration.
📋 Why Does This Happen?
Wix uses a proprietary rendering pipeline that re-processes page content after external publish events. When Search Atlas writes metadata via the Wix API, Wix's renderer can execute a second pass that pulls values directly from its internal CMS database — overwriting the changes made by Search Atlas before the final HTML is served to visitors or cached by Wix's CDN.
This is a known defect caused by a conflict between Search Atlas's publish-sync process and Wix's post-render behaviour. Our engineering team is actively working to address the underlying integration issue, and verification on affected sites is ongoing.
🛠️ What Has Been Fixed So Far?
Our engineering team has shipped updates to improve the reliability of content and metadata publish events on Wix-connected sites. These fixes reduce the frequency of overwrites; however, due to the nature of Wix's rendering pipeline, full verification across all affected pages requires additional monitoring. Our team continues to test and confirm resolution on impacted sites.
✅ Steps to Take Right Now
- Confirm which pages on your Wix site are affected by checking whether your saved changes appear on the live page after publishing.
- Note the exact page URLs and the specific fields that appear to be overwritten (for example, page title, heading, or image metadata).
- Note the approximate time you published the changes, so our team can cross-reference logs.
- Contact our support team with your project name, the affected page URLs, the fields being overwritten, and the timestamps of your publish attempts — this will allow our engineering team to investigate your specific case as efficiently as possible.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.