If you have updated your website in the CMS and the changes appear on your desktop but not on your mobile, this is usually caused by caching, publishing status, or mobile-specific settings. Follow the steps below to troubleshoot.
1) Confirm the changes were saved and published
Before checking the mobile device, make sure your updates are live.
Confirm you selected Save after making the edit.
If your site uses a publish workflow, confirm the page or panel is Published (not Draft).
If you edited a panel, confirm the correct panel is assigned to the page you are viewing.
Tip: Open the live page in an incognito/private browser window on desktop. If you cannot see the change there, it is not live yet.
2) Hard refresh on mobile
Mobile browsers often keep an older saved version of a page.
Try these quick steps:
Close the browser app fully (swipe it away), then reopen it and reload the page.
If you are using Safari (iPhone), toggle Airplane Mode on and off, then reload.
If you are using Chrome (Android or iPhone), reload the page, then try again in an incognito tab.
3) Clear your mobile browser cache
If a refresh does not work, clear cached data.
iPhone or iPad (Safari)
Go to Settings
Select Safari
Select Clear History and Website Data
Reopen Safari and load the page again
Android (Chrome)
Open Chrome
Select the three dots menu
Select History > Clear browsing data
Choose Cached images and files
Select Clear data and reload the page
4) Check you are on the same URL and version of the site
It is common to accidentally compare different versions of the website.
On both desktop and mobile, confirm:
You are on the same domain (for example, live site vs staging site)
You are not viewing a bookmarked page with tracking parameters that load a different variation
You are not viewing an old tab that has not refreshed
Tip: Copy the exact page URL from desktop and send it to your phone to test.
5) Check for mobile-specific layout behaviour and settings
Some content will display differently on mobile due to responsive design. For example:
Panels may stack in a different order
Some widgets may collapse into accordions or menus
Columns may appear below one another rather than side by side
Images may resize or crop differently
If you are expecting to see a specific item, scroll further down the page on mobile and check that it has not moved.
Composer 2 template websites (important)
On Composer 2 template websites, most panels include options to control content and layout for desktop and mobile independently. If you have only completed the Desktop tab, this may explain why mobile is not displaying the content you are expecting.
Composer 2 and custom templates: section visibility settings
On Composer 2 and custom templates, you may also have options within a page’s sections to hide content on tablet and mobile.
Check your section settings to confirm the section is not restricted to desktop only:
Open the relevant page in the CMS.
Select the section that contains the content you updated.
Open the section options and go to the General tab.
Look for any visibility settings such as Hide on tablet or Hide on mobile, or a restriction that displays the section on desktop only.
If a restriction is enabled, disable it, then save and publish your changes.
6) Check for device or browser restrictions
Sometimes the page loads differently depending on the device.
Things to check:
Are you on a corporate network or Wi-Fi that uses a proxy or content filter?
Do you have ad blockers or privacy tools enabled that could block scripts or embedded content?
Are you in Low Data Mode or a battery saver mode that restricts background loading?
Try switching from Wi-Fi to mobile data (or the other way around) and reload the page.
7) If your update was an image, script, or embed, it may take longer to refresh
These types of changes are the most likely to be cached heavily on mobile:
Updated banner images
PDFs or downloadable files
Embedded YouTube videos
Embedded Google Maps or third-party widgets
In these cases:
Clear cache (step 3)
Try a different browser on the phone (for example Safari vs Chrome)
Confirm the asset file itself is updated (not just the page)
8) Still not showing? Collect the key details for support
If none of the above resolves it, send the following to support so we can investigate quickly:
The page URL
What change you made (and where in the CMS you made it)
A desktop screenshot showing the correct result
A mobile screenshot showing the issue
Your phone model and browser (for example iPhone 14 Safari, Samsung S22 Chrome)
Comments
0 comments
Please sign in to leave a comment.