Back to blog

Google Chose a Different Canonical for Your SaaS Post

Compare the two URLs, decide whether to consolidate or preserve both articles, and verify your changes without assuming Google will follow them.

Two SaaS article URLs compared before choosing a canonical page

A different Google-selected canonical is not automatically a problem. If both URLs give readers essentially the same answer and Google chose a useful version, you can accept that choice. If you prefer the other URL, consolidate the duplicate pages around it. If the articles answer genuinely different questions, keep both and investigate why Google grouped them. Start by comparing the actual pages—not by changing a canonical tag to make a report look right.

Compare the URL you published with the one Google selected

In Search Console, inspect the full public URL of the post in the appropriate property. In its indexed result, open Page indexing and record the user-declared canonical, if shown, and the Google-selected canonical. Then inspect the selected URL too if you have access to its property. Google's URL Inspection guidance says the selected canonical comes from indexed data; Test Live URL cannot predict which URL Google will ultimately select.

Open both public URLs and compare the question each page answers, its instructions, and where it sends the reader next. Note whether either URL redirects. Check the current pages separately from the inspection report: Google's indexed result describes its most recently indexed version, so a correction already visible on your site might not appear there yet. If the selected URL is on a property you do not own, you may not be able to inspect its indexed result; you can still compare the public pages and your own site's signals.

Decide whether readers need one URL or two answers

Google recommends considering whether its chosen page better serves people arriving from Search, even when you explicitly declared another canonical. Content differences matter too: pages clustered as duplicates need sufficiently distinct answers if you want them treated separately. Use the comparison below to choose the outcome before editing technical signals.

Hypothetical example: https://example.com/blog/import-guide and https://example.com/blog/import-guide-new contain almost identical import instructions. Suppose Google selects the newer URL. If that page is accurate and existing links can sensibly lead there, keep it as the destination and retire the other URL. If the original URL is the better permanent home, retain that one instead and align the site around it. The slug Google picked is evidence to examine, not a reason by itself to discard a useful URL.

Now consider two different hypothetical posts: https://example.com/blog/import-csv explains how to map CSV columns, while https://example.com/blog/import-api explains API authentication and request errors. If inspection shows Google selecting one for the other, do not redirect the CSV guide to the API guide just to resolve the report. Keep both, make each question and its answer unmistakable on the page, and check for a misplaced canonical or redirect.

Choose the outcome from the pages readers actually see
What you findDecisionWebsite action
Near-identical answers; Google's choice works for readersAccept the selected URLMake it the consistent destination for the duplicate content
Near-identical answers; your other URL is the better homeConsolidate on your preferred URLRetire the duplicate and align its signals with the retained page
Different questions with useful, distinct answersPreserve bothClarify the answers and correct signals pointing one page at the other

Correct signals that disagree with your decision

Check what each live URL does: its redirect destination, any HTML or HTTP rel="canonical" annotation, the URLs in your sitemap, and internal links to the articles. Google's canonical guidance treats redirects and canonical annotations as strong signals and sitemap inclusion as a weaker one; none forces Google's choice. It also advises against specifying different canonical destinations through different methods. Point your site's signals at the URL you decided to retain rather than asking Google to reconcile contradictory preferences.

When retiring a near-identical page, make sure the retained page satisfies visitors following the old URL, then use a permanent redirect from the retired URL to the retained one. Update relevant internal links to point directly to the retained URL. Google recommends a permanent redirect for a deprecated duplicate, not as a fix for two pages that still serve different purposes. When keeping two distinct articles, let each remain accessible and remove an erroneous canonical or redirect that points one at the other.

If a canonical annotation unexpectedly points off-site or a URL redirects somewhere you did not configure, investigate the site's publishing and server setup before treating Google's choice as an editorial judgment. Google's troubleshooting guidance identifies incorrect canonical elements and server configuration as possible causes of unexpected selection.

Verify the release, then recheck Google's decision

Before release, prepare the intended redirect, canonical annotations, sitemap entry, and internal-link changes together. If the release is not atomic, make the retained destination available before publishing links or a redirect to it. After deployment, open both public URLs and confirm the destination, page content, and live signals match the decision. This verifies your website—not Google's subsequent canonical choice.

Reinspect the affected URLs in Search Console after Google has processed the changes and compare the indexed Google-selected canonical with your recorded starting point. A live test can help check the current URL, but Google's URL Inspection documentation says it cannot predict canonical selection; an indexing request does not guarantee indexing. If the URL has a broader discovery, crawl, or indexing problem, use the separate SaaS post indexing guide rather than treating every missing URL as a canonical dispute.

Ranks' connected Search Console overview can help you spot the article alongside clicks, impressions, average position, and top queries. Use Search Console itself for URL Inspection and detailed page or query filtering. Performance may help you prioritize which post to examine, but it does not explain why Google selected a particular canonical.

Sources

  1. URL Inspection tool — Search Console Helpsupport.google.com
  2. Fix canonicalization issues — Google Search Centraldevelopers.google.com
  3. How to specify a canonical URL — Google Search Centraldevelopers.google.com
  4. Ranks public product referenceranks.so
  5. Why Your SaaS Blog Post Is Not Indexed Yetranks.so

Grow your SaaS traffic on autopilot

One vetted backlink submission and one targeted blog article per day, on autopilot. Track your growth, all in one dashboard.

Try Ranks