How to Fix or Remove ?m=1, URL Google Blogger 2022

how to remove &=1 in blogger

You’re facing duplicate content SEO issues due to m=1 in the Blogger blog. And want to remove m=1 from the Blogger and solve the problem. Let’s understand how to remove the Blogger m=1 duplicate content issue and enhance the SEO of the blog.

Optimization of content for search engines is essential for a website to rank. But what if the same content serves via two different URLs. Yes, we’re talking about Blogger. Blogger CMS serves the same webpage through two URLs – One is for desktop and the other for mobile users.

The Blogger CMS serves canonical URL to desktop and canonical URL with m=1 to mobile users. This article will explain how to fix the Blogger m=1 issue for the Blogger blog.


But if you’re looking only to remove m=1 from the end of the web page URL, this post is not for you as we’re not here to spoil the on-Page SEO website.

You can add some script and remove m=1, but search engines will punish your blog by decreasing your blog’s page rank.

We can provide you with such a script, but no, as we’re here to boost the blog’s Search Engine Optimization and not degrade it. Read this complete article before applying any script etc. Use proper methods to do things.

Is it Possible to Remove m=1 from Blogger?

No, It is practically impossible to remove the m=1 from the Blogger URLs, as we do not have access to the root of the Blogger. But there is no need to remove /?m=1 from the Blogger blog posts.

You can hide m=1 from the URLs served on mobile devices by implementing javascript code to the theme file, but the javascript will only visually hide the m=1, not remove it. You can check that in the HTTP header response and the Google PageSpeed Insight tool. So the javascript injection method will disturb the on-Page SEO. But don’t worry, we found a perfect way to do this.

The Blogger serves different URLs for mobile and desktop devices with and without m=1, respectively. It’s the same case of different URLs for the same post. In such a case, we can declare that Google should treat both canonical URL and URL with m=1 as the same.

Solve the issue of Blogger – Duplicate, submitted URL not selected as canonical

You can solve the SEO problem of indexing the URL, Duplicate, submitted URL not selected as canonical. This problem occurs because the server serves different URLs for mobile and desktop. So we’ll declare to the search console that both URLs must treat as the same.

How to solve Blogger m=1 issue

You can use the google page technique for different URLs for the same page (one for mobile and another for PC). In this method, we inform Google bots that content available at both URLs and is the same.

This tool is no longer available. After the latest updates, Google is able to understand the parameter thing automatically. Now you don’t have to worry about this m=1 thing, Google will take care of it.

Earlier we had to manually report to Google that both with and without m=1 URLs are the same, treat that accordingly. Now you didn’t need to do anything, just ignore this m=1 thing.

If you’re using Adsense Ads for monetization, follow this method to boost Adsense revenue by 150 to 200%. Learn how to improve the Blogger SEO the best practices available.

Don’t add any javascript to remove m=1 from the Blogger blog URLs. But if you did, check the header response of the website for mobile. This means that you made things worst from the SEO point of view. Please keep the above things in mind while making such changes.

Additional Tips: What is more important for any blog is the theme. Google supports HTML5 themes. You can also try our Blogger blog themes that are completely SEO-friendly.

Final Words

We can’t remove the m=1 URL generated by Blogger. But now Google is smart enough to understand and rank content accordingly. You’ve to focus on creating unique content to rank high in the search results.

In case of any doubt, query, or feedback, feel free to comment in the comment section provided below.

Next Post Previous Post
No Comment
Add Comment
comment url