Why saved changes are not visible on the live site
First confirm the intended change was saved to the correct page or template. If the editor shows the new version but visitors see the old one, cached output may be involved.
Confirm what changed
Section titled “Confirm what changed”Check the exact domain and page URL, including whether you edited staging instead of the live site. Verify publication status. For a designated posts page, the blog template may control its output.
Compare the page in a logged-out browser window and on another device. This helps distinguish an editor preview from the public page and a local browser issue from cached server output.
Work through relevant caches
Section titled “Work through relevant caches”- Refresh the browser and compare with a fresh window.
- If the site uses a cache plugin, purge the relevant page using that plugin’s documented controls.
- Check hosting cache and, if used, CDN cache. Purge only the layer relevant to this site and change.
- Elementor only: if generated styles remain old, back up the site and follow Elementor’s documented Clear Files & Data procedure. The tool name and location may differ by version.
Do not apply Elementor instructions to a page built with another builder. Clearing cache cannot repair a wrong template assignment, unsaved page, or missing style rule.
Avoid disabling every plugin on the live site or resetting the database as an initial troubleshooting step. If you need a conflict investigation, perform it on staging.
Check the result
Section titled “Check the result”Reopen the same public URL and confirm the specific text or style you changed. Check mobile and a logged-out view, not only the editor preview.
If the symptom persists, record the affected URL, editor/builder, changes made, and cache layers checked. Share those details with the relevant product or hosting support so the next step addresses the cause rather than repeating random purges.