Every Blogger post can be reached through different-looking URLs: the normal post address, a link with tracking parameters, or sometimes a mobile-style ?m=1 version. Search engines need to decide which URL best represents the page.
This tutorial shows how to check a Blogger post's canonical URL and compare the page's declared preference with what Google Search Console reports. You will diagnose a mismatch before considering any code change.
What is a canonical URL?
A canonical URL is the preferred representative among duplicate or very similar page URLs. A page can suggest this preference through a rel="canonical" link element. Google also uses other signals to choose the canonical URL it indexes.
Google's canonicalization documentation makes an important distinction: a declared canonical is a signal, not a guarantee that Google will choose the same URL.
Step 1: Copy the exact Blogger post URL
Open a published article and copy the address from the browser. Use the normal HTTPS permalink without extra sharing parameters if possible. Keep a note of any variations you have seen in Search Console, such as a ?m=1 URL.
Do not change a post's permalink merely because Google reports a parameterized version. Changing an established URL can create unnecessary redirects and broken links.
Step 2: Inspect the page's canonical declaration
On desktop, open the published page, view its HTML source, and search for rel="canonical". A typical element might look like:
<link rel="canonical"
href="https://www.example.com/2026/10/sample-post.html">That address is only an example. Compare the actual href value to the page you intended to publish. Check for errors such as a different post, the wrong domain, or an unexpected query parameter.
If the page has no canonical element or several conflicting ones, record what you found. A custom theme may have changed Blogger's normal output, but do not edit the whole template until you understand the scope.
Step 3: Use Google Search Console URL Inspection
- Open the verified Search Console property for the blog.
- Paste the exact published permalink into URL Inspection.
- Read the page indexing result and the information about the user-declared canonical and Google-selected canonical, when available.
- Compare those addresses with the URL you copied in Step 1.
- If needed, inspect the parameterized version separately to understand how Google handles it.
The inspection result may be based on the last crawl. A live URL test and the indexed page status answer different questions; don't treat an old inspection as proof of current HTML.
Step 4: Decide whether the difference matters
A difference is not automatically an error. For example, Google may choose the clean URL as canonical for a mobile parameter variant, which is often exactly what you want.
Investigate if Google selects a different article, an obsolete domain, or a page with substantially different content. Compare content, internal links, redirects, and template output. Duplicate or near-duplicate articles can produce canonical clustering that cannot be fixed simply by adding a tag.
Common Blogger canonical problems
The canonical points to an old Blogspot address
Check whether your custom domain is properly connected and whether the theme contains a hard-coded canonical URL. Also examine any existing redirects. Avoid global replacements without a theme backup.
The canonical includes ?m=1
Compare the clean and mobile-style URLs in Search Console. The parameter alone is not proof of a penalty. The important question is which version Google selects and whether the page content is accessible.
Two different posts have the same canonical
That can be a serious issue if the pages have distinct content. Check for template-level mistakes, duplicated code, and any manually inserted tag. Do not force both pages to canonicalize to one just because they mention similar keywords.
The declared canonical looks correct, but Google chose another
Google considers multiple signals. Review the content relationship and internal linking instead of assuming Search Console is malfunctioning. See Google's guide to consolidating duplicate URLs for supported approaches.
Check for conflicting canonical signals
A canonical tag is only one signal. Before editing the theme, check whether the clean post URL loads with HTTPS, whether an older Blogspot address redirects correctly, and whether links inside your own articles consistently point to the same preferred URL. Google says redirects and rel="canonical" annotations are strong signals, while sitemap inclusion is weaker. When these signals disagree, fixing the disagreement is usually more useful than adding another tag.
Do not use robots.txt rules or a noindex directive as a shortcut to influence canonical selection. Those controls answer different questions about crawling and indexing. If two posts really cover different topics, improve the distinction between their content instead of pointing both canonical tags at one post.
Record your findings before changing the theme
Make a small note for each affected page: the requested URL, its final address after any redirect, the canonical declared in the HTML, the canonical selected by Google (if reported), and the date of the test. If the mismatch appears on only one post, investigate that page first. If it appears across many posts, a shared template or domain setting is a more plausible cause.
For a broader editorial review, our content refresh checklist covers other changes worth checking when you revisit an older article. Keep a canonical investigation focused on URL identity; don't change titles, content, and redirects simultaneously unless each change has a clear reason.
What not to do
- Don't change every Blogger post canonical because one mobile URL appeared in a report.
- Don't add two canonical tags from competing widgets or scripts.
- Don't canonicalize genuinely different tutorials to the same page to “combine SEO.”
- Don't block a page in robots.txt just to force Google to honor a canonical tag.
- Don't edit an established permalink without a clear migration reason.
Frequently asked questions
Does every Blogger post need a manually added canonical tag?
No. First inspect what your Blogger theme already outputs. Adding another tag may introduce a conflict.
Is a ?m=1 URL a duplicate content penalty?
Not by itself. It may be a mobile URL variant. Look at the selected canonical and whether the clean post URL is correctly accessible.
Why does Search Console show a different canonical?
Google chooses from several signals and may disagree with the page's declaration. Investigate the URLs and content before changing settings.
Can I fix canonical issues with a redirect?
Only when a redirect is truly appropriate. A redirect changes where visitors go; a canonical signal indicates a preferred representative for duplicate content. They are not interchangeable.
Final verification checklist
Check the live post URL, inspect the canonical element, compare it with Google's selected canonical, and look for genuine content or redirect conflicts. Make changes only when the evidence identifies a real problem.