Want to remove m=1 from Blogger blog URL? Don’t Spoil SEO, 2021 update

You’re facing duplicate content issues due to m=1 in the Blogger blog. And want to remove that m=1, but it is not possible. You can temporarily hide that but can’t remove it. Let’s understand how to remove Blogger m=1 duplicate content issue and enhance the SEO of the Blogger 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. In this article, we’ll explain how to fix the Blogger m=1 issue for the Blogger blog.

  • Desktop Version:
  • Mobile Version:
Fix Blogger m=1 issue

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 for us to remove the m=1 from the Blogger URLs, as we do not have access to the root of the Blogger. But what happens if I say 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 as well as in 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

As we already discussed, if you want to remove m=1 from the Blogger blog URL, then this article is not for you.

You can solve the SEO problem of indexing the URL, Duplicate, submitted URL not selected as canonical. This problem occurs due to 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.

We can use the Google search console parameter tool to perform this action. The Google search engine recommends these settings under the crawling of parameterized duplicate content. And completely SEO and search engine friendly.

So we keep the m=1 for Blogger but notify Google that treats both URLs as the same. You can refer to the link provided above.

Change URL Parameters to solve this issue.

Open Google Search Console dashboard, and click on Legacy tools and report > URL Parameters.

Google Search Console dashboard to resolve m=1
Google Search Console dashboard to resolve m=1

Now you’ll redirect to a new tab for URL Parameters of Google Search Console.

Blogger m=1 for old blogs
Blogger m=1 for old blogs

If you’ve been using Blogger Blogspot blog for a long time, you may see a similar interface as displayed above. Now, check the “m” parameter, is it listed or not? If listed, it’s left on google that let Googlebot Decide, but we’ve to change this. Click on Edit, and you’ll see a pop-up window to define that parameter setting:

Parameter m doesn't make any changes
Parameter m doesn’t make any changes.
  1. Select: No, it doesn’t affect pages content
  2. Save the settings.

For new Blogger users, you’ve to add the “m” parameter as

Add Parameter m=1
enter parameter value for blogger blog
enter parameter value for Blogger blog
  1. Please enter the value here; that will be “m” in our case.
  2. The page is not affecting the content, then choose no doesn’t affect it.

Now save these settings, and wait for a few days; all errors of “Duplicate, submitted URL not selected as canonical” will be removed due to the Blogger m=1 issue.

If you’re using Adsense Ads for monetization, follow this method to boost Adsense revenue by 150 to 200%. You can read how to improve the SEO score of Blogger, best practices available on the internet.

Don’t add any javascript to remove m=1 from the Blogger blog URLs. You can check the header response after adding the script. 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 m=1 URL generated by Google, but we can notify Google to treat both URLs as the same. If you think that implementing a script can remove m=1, it will be completely wrong.

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

Ashok Kumar

Ashok Kumar working in the Search Engine Optimization field since 2015. And worked on many successful projects since then. He shares the real-life experience of best SEO practices with his followers on You also can learn Advance level SEO for WordPress, Blogger, or any other blogging platform. Stay tuned.

Related Articles


    1. “NO” as m=0 is not visible anywhere and that is also canonical URL, we’re declaring url rel=alternative mean relation of article with original url i.e. alternative.

    1. Your m=1 will remove from Google index pages, it only display for mobile users, That means same content error resolve. I checked your blog, correctly implemented. So now work on your content and back-links

    1. This article already mention that the m=1 will not remove. This will help Google to understand the actual structure of website. And the results in long run. Instant results can’t be possible in SEO.

  1. Hey Ashok, thanks for this blog!
    Actually, I was auditing my blogspot through LightHouse and saw that the redirects were still being made. I had implemented that JavaScript code that just visually removes ‘?m=1’ parameter. Just got to know through this article that it hurts SEO. So, will remove it.
    About that, Changing URL Parameters, you must’ve URL-Prefix Property instead of Domain Property. I had Domain Property of my Blogspot, so just created URL-Prefix property of it, but it doesn’t show any parameters, should I add ‘m’ manually or wait for some time?

  2. Thanks friend for the information, you solved me some recorded problems that I had on my website. My site fell out of positions because of the M parameter, and now it is gradually being resolved.

    1. Hi, I just figured it out myself. So thought to update you too.
      What I did was, I had submitted my blog on the google search console as a domain.
      We have to submit it as a URL.

      So, I removed the property from Google search console and added it back by selecting the Add URL and not Add domain. Now I can access it.

  3. Hello Ashok, That’s a brilliant piece of information. Thanks for it.
    However, one thing stands in my way to solve my issue.
    When I click on URL parameters in the GSC, it says, “Legacy tools and reports are not available for domain properties’.
    What should I do?
    Hope to hear from you soon. Thanks

    1. It is because you added and verified your property as domain property. You’ve to add it as a URL prefix property.
      Please remove the property and add it again with the appropriate method.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button