🔍 Overview of Known Wix Integration Defects
Search Atlas integrates with Wix to help you publish and manage on-page SEO content directly from the platform. However, a small number of users have reported recurring defects when using this integration. This article explains the four known issue categories, what causes them, and the steps you should take to document and escalate them effectively.
The four defect categories currently under investigation are:
- Metadata not saving correctly — Meta descriptions or titles written in Search Atlas do not persist on the live Wix page after publication.
- Title mutations — Page titles are altered unexpectedly during or after a publish action, resulting in unintended wording or formatting changes.
- Alt text rewrites — Image alt text is overwritten with incorrect values, or reverts to a previous state after publishing.
- Cold-load discrepancies — Changes appear saved inside the platform but do not reflect on a fresh browser load of the published Wix page.
⚠️ Why These Issues Happen
Wix uses a proprietary API layer that controls how external tools write and read page content. Conflicts can occur when:
- Wix's internal editor cache does not sync immediately with changes pushed via the API.
- Wix applies its own formatting rules that override externally set title or alt text values.
- A publish action triggers a Wix-side re-render that resets certain metadata fields to their previous state.
These are integration-level defects that require engineering investigation on both the Search Atlas and Wix API sides. They cannot be resolved by changing settings within your account.
📋 How to Document Your Issue Before Escalating
Strong documentation speeds up engineering investigations significantly. Before contacting support, please gather the following:
- Affected page URLs — List every Wix page URL where the defect has occurred.
- Screenshots or screen recordings — Capture the value as set inside Search Atlas, then the value shown on a fresh (incognito) browser load of the live page.
- Timestamps — Note the exact date and time you published the change.
- Steps to reproduce — Write out exactly what you did: which field you edited, what value you entered, and what you expected versus what appeared.
- Previous ticket or case references — If you have earlier ticket numbers (for example, from a previous support conversation), include these so our team can retrieve prior evidence and link everything to a single active case.
🚀 How to Escalate to Engineering
Once you have your documentation ready, use the following process to get your case escalated with a tracked reference:
- 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.
- Tell the teammate you are reporting a Wix integration defect and provide your documentation.
- Ask the teammate to create or reopen an escalation ticket and confirm the active reference number with you in chat.
- Request that the ticket be linked to any prior case references you have on file so evidence is consolidated.
- Ask for a named owner and current status to be assigned to your case so you have a clear point of contact.
Our support team will log the defect with engineering and set up the required cold-load and controlled publication tests to confirm whether the fix is working before the case is closed.
✅ What Happens After Escalation
Once your case is active with engineering, the following process applies:
- Engineering will review all linked evidence from previous and current tickets.
- A cold-load test will be performed — this means loading the affected page on a fresh browser session with no cached data to verify whether published changes are visible.
- A controlled publication test will be run — this involves making a defined change, publishing it, and independently verifying the result on the live Wix page.
- The case will remain open until both tests confirm resolution. It will not be closed based solely on an internal fix being deployed.
- You will receive a status update via the platform chat each time there is a meaningful change to your case.
🛡️ Temporary Workarounds While Awaiting a Fix
These steps will not permanently resolve the defects, but they may reduce the impact while engineering works on a fix:
- Verify changes immediately after publishing — Open the page in a private or incognito browser window right after publishing to check whether the correct values appear.
- Re-publish if a revert is detected — If metadata or alt text has reverted, make the change again inside Search Atlas and publish a second time. Some users find the second publish attempt sticks.
- Avoid bulk publishing — Publishing one page at a time appears to reduce the frequency of title mutations compared to publishing multiple pages simultaneously.
- Keep a local record of intended values — Maintain a simple document with your intended titles, meta descriptions, and alt text so you can quickly re-enter them if a revert occurs.
💬 Need Help With Your Case?
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.