One of the most important points to keep the quality of a website is to avoid duplicate content on it. Google does not like blogs that have different pages with the same content.
Not only Google but also other search engines demand unique content from a blog.
They do not like a website/blog that offers the same content through more than one URL.
I am doing my best to maintain each page on CoreNetworkZ unique, but recently I noticed duplicate content issues.
This duplicate page issue is not from my side but is from Blogger's side. Blogger automatically generates different post URLs for mobile users.
The intention of the Blogger team is good, but the problem is the landing web page URL of mobile visitors. Blogger adds an affix ?m=1 to each URL.
So, the visitors can access the same content through two different links.
It attracts duplicate content issues. To solve this ?m=1 landing page redirection issues, we have to disable the Blogger mobile view.
I am using a responsive theme for CoreNetworkZ.com, and there is no need for generating separate post links for mobile users.
Blogspot redirects mobile users to the mobile version, and those page URLs end with ?m=1. That is why you can see page links end with ?m=1 on Google Analytics.
Here are the screenshots of my Google Analytics report, which shows how much impact this ?m=1 redirection.
You can see at least half of our visitors are landing on URLs end with ?m=1. Those are visiting CoreNetworkZ on mobile phones.
Since they are on mobile phones, Blogspot automatically redirected them to the mobile version of the site.
You can see from the list, Blogspot allows visitors to access the same content from two different URLs.
Look at the URLs given below. Both links point to the same page. The first URL is the landing page for desktop and tab users. The second URL is the landing page for mobile visitors.
Those who are visiting my blogger post on a mobile phone will reach the ?m=1 page. Both pages show the same content.
It violates Google's Search quality guidelines of not allowing users to access the same information by different links.
To remove Blogspot links with ?m=1, follow the instructions given below.
From now on, Blogspot will not redirect mobile visitors to the pages with links that end with ?m=1. So, you are finally free from the risk of displaying the same content on two different pages.
Though you have successfully resolved possible duplicate content issues due to ?m=1 Blogspot links, there is another potential issue you need to consider.
If your Blogger theme is not responsive, your mobile readers will land the desktop version. It will affect the readability.
Two risks are associated with non-responsive Blogger templates after disabling the mobile theme version.
In some Blogger themes, this trick is not working. Even if you have disabled the mobile view, Blogger redirects mobile users to the ?m=1 pages.
What can we do in such a situation? We can fix this problem with the help of a canonical tag. To read more about it, visit the link below.
How to Set Canonical Tag to Avoid Multiple Post Links Issue? Here is another method that removes ?m=1 from Blogger URLs that worked on my test blogs.
I tested this code with another Blogspot blog. However, I have not implemented it on CoreNetworkZ yet due to possible code conflicts with other customizations.
Not only Google but also other search engines demand unique content from a blog.
They do not like a website/blog that offers the same content through more than one URL.
I am doing my best to maintain each page on CoreNetworkZ unique, but recently I noticed duplicate content issues.
This duplicate page issue is not from my side but is from Blogger's side. Blogger automatically generates different post URLs for mobile users.
The intention of the Blogger team is good, but the problem is the landing web page URL of mobile visitors. Blogger adds an affix ?m=1 to each URL.
So, the visitors can access the same content through two different links.
?m=1 mobile pages no longer creates duplicate issues. Blogger adds Canonical tag automatically on its updated Blogger themes.
I am using a responsive theme for CoreNetworkZ.com, and there is no need for generating separate post links for mobile users.
Effect of Blogger ?m=1 Pages On Search Results
Here are the screenshots of my Google Analytics report, which shows how much impact this ?m=1 redirection.
You can see at least half of our visitors are landing on URLs end with ?m=1. Those are visiting CoreNetworkZ on mobile phones.
Even though the different links for Blogspot mobile users do not create a duplicate content problem, I recommend you to use the same URL for both mobile and desktop users for the ease of the natural link development process.
Since they are on mobile phones, Blogspot automatically redirected them to the mobile version of the site.
You can see from the list, Blogspot allows visitors to access the same content from two different URLs.
How to Disable Blogger Mobile Redirect ?m=1
- https://www.corenetworkz.com/2009/08/how-to-set-up-custom-domain-name-in-my.html
- https://www.corenetworkz.com/2009/08/how-to-set-up-custom-domain-name-in-my.html?m=1
Those who are visiting my blogger post on a mobile phone will reach the ?m=1 page. Both pages show the same content.
Blogger adds the rel='canonical' tag in its latest themes to avoid content duplicate problems.
To remove Blogspot links with ?m=1, follow the instructions given below.
- Log in to your Blogger account and once you are on the dashboard of the specific blog, click Theme on the left-hand side menu.
- Click on the Settings icon below the mobile theme view
- You need to choose the radio button near the "No. Show the desktop theme on mobile devices" and click the Save button. If you wish to see the mobile version of your site, you may click on the preview button.
From now on, Blogspot will not redirect mobile visitors to the pages with links that end with ?m=1. So, you are finally free from the risk of displaying the same content on two different pages.
- Web Traffic Required to Earn $100 Per Day
- How to Delete Photos Shared On Hangouts
- How to Find Email Address of Hangouts Friend
Though you have successfully resolved possible duplicate content issues due to ?m=1 Blogspot links, there is another potential issue you need to consider.
If your Blogger theme is not responsive, your mobile readers will land the desktop version. It will affect the readability.
- Turn on HTTPS Encryption On Blogspot Blogs With Custom Domain Names
- Show AdSense Ads Inside Blogger Post Content
- How to Manually Place AdSense Unit Below the Blogspot Post Title?
Two risks are associated with non-responsive Blogger templates after disabling the mobile theme version.
- The first one is the possible bounce back by mobile readers due to less readability.
- Second is the possible punishment by Google by identifying your blog not suitable for mobile readers and placed in lower positions in Google search results for mobile readers.
What If This Trick Does Not Work?
New Blogspot themes have an inbuilt canonical tag. So, you do not need to add any extra tags.
How to Set Canonical Tag to Avoid Multiple Post Links Issue? Here is another method that removes ?m=1 from Blogger URLs that worked on my test blogs.
- Go to Blogger theme
- Click the Customize button and select Edit HTML
- Paste the below JavaScript code before the closing of the HTML body tag.
<script type="text/javascript">
//<![CDATA[
var uri = window.location.toString();
if (uri.indexOf("%3D","%3D") > 0) {
var clean_uri = uri.substring(0, uri.indexOf("%3D"));
window.history.replaceState({}, document.title, clean_uri);
}
var uri = window.location.toString();
if (uri.indexOf("%3D%3D","%3D%3D") > 0) {
var clean_uri = uri.substring(0, uri.indexOf("%3D%3D"));
window.history.replaceState({}, document.title, clean_uri);
}
var uri = window.location.toString();
if (uri.indexOf("&m=1","&m=1") > 0) {
var clean_uri = uri.substring(0, uri.indexOf("&m=1"));
window.history.replaceState({}, document.title, clean_uri);
}
var uri = window.location.toString();
if (uri.indexOf("?m=1","?m=1") > 0) {
var clean_uri = uri.substring(0, uri.indexOf("?m=1"));
window.history.replaceState({}, document.title, clean_uri);
}
//]]>
</script>
- Save the changes
I tested this code with another Blogspot blog. However, I have not implemented it on CoreNetworkZ yet due to possible code conflicts with other customizations.
