First confirm that you changed the correct published page, then investigate caching. WordPress preview, a logged-in view and a normal visitor’s view can show different versions. 1
Separate content from styling
Open the exact public URL in a private window. If the new text is missing from the page’s HTML, check publication and page caching. If the text is current but styling is old, inspect the CSS and JavaScript asset versions separately.
Treat caching as layers: browser, WordPress caching, hosting and possibly a CDN. Refreshing your browser does not necessarily invalidate a server-side copy. Response headers such as Age and Cache-Control can provide useful evidence. 2
Change one layer at a time
Where supported, purge only the affected URL and retest while logged out. Record which action changes the result. Clearing every cache at once may hide the symptom without explaining its cause.
Do not permanently disable caching just to make one edit visible. Fix publication-time invalidation or asset versioning instead.
For a store, verify important values across the journey. An updated product price deserves a check in the cart as well as on the product page. Visitors should not encounter contradictory information simply because different parts of the site are serving different revisions.
Related reading
Improving WordPress performance
