The mobile pages are only for backend and be careful to the cache
-
The mobile pages, e.g. https://your-website.com/example-page-mobile/, are only for backend, and for not logged users they don’t exist.
If you have e.g. https://your-website.com/example-page/, when you are logged in, the related mobile version is https://your-website.com/example-page-mobile/, but visitors have always to see https://your-website.com/example-page/.
The only page that is public is https://your-website.com/example-page/.
This plugin doesn’t redirect the users to the mobile version, it replaces the content of https://your-website.com/example-page/ with the content of https://your-website.com/example-page-mobile/, but https://your-website.com/example-page/ doesn’t exist for people who are not logged-in.
This is to avoid SEO problems related to duplicated content and avoid redirections that would slow down the page loading. This is also the reason the plugin makes it impossible to save the mobile page as public. The mobile page is only for the backend or if you want to have a look when you are logged in.
Having a mobile page for the backend allows Specific Content For Mobile to take advantage of whatever page builder you have, then when the users visit the page, if the user has a mobile device, it replaces the desktop content with the mobile content taking it from the mobile page.
If you are not logged in and you visit https://your-website.com/example-page-mobile/ you will have a 404 page, because that page doesn`t exist for not logged users.
If you have a plugin for server cache, be also careful it distinguishes between desktop and mobile server cache.
The following plugins can create different server cache, for mobile and desktop versions:
– W3 Total Cache
– WP Fastest CacheProbably also other plugins will give you this possibility, just check it.
- The topic ‘The mobile pages are only for backend and be careful to the cache’ is closed to new replies.