title

Redirect error: Search Console report - Blogger Community

format-detection

email=no

robots

follow,index

X-UA-Compatible

IE=edge,chrome=1

description

<div>A very common question raised in the Blogger Help Community is related to the Page Indexing report, specifically for <i>Redirect error</i>, where URLs without the <code>?m=1</code> get flagged and <i>how it can be fixed</i>.</div> <div>&nbsp;</div> <div>The short answer is: <u>there is nothing to fix</u>.</div> <div>&nbsp;</div> <div>In order to offer a detailed answer, I will use the information given by the Search Console Product Expert <a href="https://support.google.com/profile/2040358" target="_blank" rel="noopener"><b>dwsmart</b></a> in his Google Search Central Community Guide: <a href="https://support.google.com/webmasters/community-guide/254759331" target="_blank" rel="noopener">Have a Blogger Site and Seeing Page Redirect Errors in Search Console?</a></div> <div>&nbsp;</div> <div>&nbsp;</div> <div><b>How Blogger works?</b></div> <div>Blogger uses the separate URLs method to ensure mobile-friendly pages for mobile users: <a href="https://developers.google.com/search/docs/crawling-indexing/mobile/mobile-sites-mobile-first-indexing" target="_blank" rel="noopener">Mobile site and mobile-first indexing best practices</a></div> <div>&nbsp;</div> <div>When Blogger detects a mobile user, it automatically 302 redirects them to the URL with <code>?m=1</code> added to the end. If the user wants to access the desktop version on their mobile or tablet device, the URL will contain <code>?</code><code>m=0</code>. This happens for both <i>*.blogspot.com</i> and custom domain sites.&nbsp;</div> <div>&nbsp;</div> <div>Blogger ensures that the correct canonical tags are included in its themes, using <code>&lt;b:include data=&#39;blog&#39; name=&#39;all-head-content&#39;/&gt;</code>, to point to the URL without the <code>?m=1</code>&nbsp; and the matching vary headers and alternative markup.</div> <div>&nbsp;</div> <div>If using a custom theme or one provided by a 3rd-party, it is important to verify that at least it contains this line of code:&nbsp; <code>&lt;link expr:href=&#39;data:view.url.canonical&#39; rel=&#39;canonical&#39;/&gt;</code></div> <div>&nbsp;</div> <div>&nbsp;</div> <div><b>Why are appearing these errors?</b></div> <div>Google mostly crawls as a mobile user, so it too sees the redirects. <b>Search Console just reports on what it finds</b>, and for other sites, things like this might be a misconfiguration.</div> <div>&nbsp;</div> <div>For Blogger sites, redirections are part of the platform&#39;s configuration and are supposed to be happening, then it&#39;s safe to ignore the report.</div> <div>&nbsp;</div> <div>&nbsp;</div> <div><b>What steps should be taken?</b></div> <div>Short answer: <i>maybe 1</i>.</div> <div>&nbsp;</div> <div>Given time, when Google crawls as a desktop, the URLs without the <code>?m=1</code> usually end up as the canonical, indexed version, and in the meantime, it&#39;s not an issue if the content is indexed with <code>?m=1</code>.</div> <div>&nbsp;</div> <div>But it is worth checking if the theme contains <code>rel=&#39;canonical&#39;</code>. If not, be sure to fix this.</div> <div>&nbsp;</div> <div>&nbsp;</div> <div><b>What actions should NOT be taken?</b></div> <div>Sometimes it&#39;s tempting to panic and block the <code>?m=1</code> URLs with <i>robots.txt</i>, or try and add a <i>noindex</i>.</div> <div>&nbsp;</div> <div>These are things that can stop the whole mobile / desktop relationship from working, and can ultimately harm the site.</div> <div>&nbsp;</div> <div>&nbsp;</div> <div><b>What about Alternate page with proper canonical tag?</b></div> <div>If the reported URLs are ending with <code>?m=1</code>, it&#39;s the same basic cause, Googlebot accesses the <code>?m=1</code> version, but the canonical is the desktop URL.</div> <div>&nbsp;</div> <div>So this is a sign that Google has processed the relationship and is now treating the desktop URL as the canonical one. This is not an error or something to worry about.</div> <div>&nbsp;</div> <div>&nbsp;</div> <div><b>What if the Redirects aren&#39;t to <code>?m=1</code>&nbsp; or <code>?m=0</code></b></div> <div>Then it might be an actual issue, the best approach is to open a thread in the Google Search Central Help Community <a href="https://support.google.com/webmasters/thread/new?hl=en" target="_blank" rel="noopener">https://support.google.com/webmasters/thread/new?hl=en</a> and make sure to give some example URLs.</div> <div>&nbsp;</div> <div>&nbsp;</div> <div>&nbsp;</div> <div><code><b>@brigitte</b></code></div> <div>&nbsp;</div> <div>-------------</div> <div>&nbsp;</div> <div>Please remember, in Blogger Help Community and other communities, we as <i>Product Experts</i> are volunteers offering our experience and knowledge to guide other users, just as we also are.</div> <div>&nbsp;</div> <div>If you consider that Blogger and Search Console integration is not handled in the best way, you can send feedback to Google. That is one-way communication. You will not receive a reply, but the Google Team definitely receives your message.</div> <div>&nbsp;</div> <div>-------------</div> <div>&nbsp;</div> <div><b>The sole purpose to publish this guide when there is already one in the same language created by a Google Search Console expert is to make it accessible on the Blogger Community homepage.</b></div> <div>&nbsp;</div> <div>&nbsp;</div> <div>&nbsp;</div> <div>&nbsp;</div>

canonical

https://support.google.com/blogger/community-guide/325142055/redirect-error-search-console-report?hl=en

preload

https://fonts.googleapis.com/css2?family=Google+Sans+Text:wght@400;500;700&display=swap

preload

https://fonts.googleapis.com/css2?family=Noto+Color+Emoji&display=swap