What should you do if some pages are not selected as canonical after changing URLs and setting up redirects?

ProcrustesPR

If some new URLs are not selected as canonical after you change URLs and set up redirects, first check the redirect types and destinations, then use Search Console’s URL Inspection results to clarify the issue. Do not simply resubmit the URLs for indexing. If you also changed domains, check both the www and non-www versions of the old domain. The available information supports these troubleshooting steps, but without inspection results for individual pages, it cannot establish the cause or guarantee that resubmitting the sitemap will resolve the issue.

ProcrustesPRProcrustesPRHow should you balance CNAME convenience and performance?

First, check that the redirects suit the URL change

Forum contributor markdeessel recommends rechecking the 301 redirects and their structure, then using Google’s URL Inspection tool to investigate why pages are not indexed. Start by listing the affected old URLs, their corresponding new URLs, and the redirect types. Do not skip this check simply because redirects have already been set up.

A 2023 Semrush article explains that a 302 is a temporary redirect and recommends switching to a 301 if the URL change has become permanent. Citing Google at the time, the article describes a 302 as a weak signal that the redirect destination should become the canonical URL. Other signals may also influence the choice. This explanation comes from a 2023 article; it does not establish that every page using a 302 today will retain its old URL as canonical, nor does it justify blaming a 302 in every case.

Use inspection results to distinguish canonical selection from indexing issues

“The new URL was not selected as canonical” is different from “the page has not been indexed or is not yet ranking.” An October 2026 Search Engine Journal article explains canonical selection as Google choosing a version from multiple domains or URLs to use for indexing and ranking.

  • Following the forum’s advice, use the URL Inspection tool to investigate the affected URLs.
  • Check Search Console for relevant warnings rather than relying solely on whether a page appears in search results.
  • Confirm the actual status before deciding what to do. The forum reply’s suggestion to “wait a little longer” is advice, not a confirmed solution.

If you changed domains, check both www and non-www versions

The Search Engine Journal article mentioned above suggests that external links still pointing to the www or non-www version of the old domain may prompt Google to select URLs on that domain as canonical. For example, if a migration involves both versions of the old domain, check both rather than just one. This is a troubleshooting clue, not a confirmed cause in an individual case. If you only changed paths within the same domain, do not assume this explanation applies.

Check the sitemap, but do not expect a guaranteed fix

Forum contributor KylieSweet recommends resubmitting the sitemap and confirming that it includes the URLs you want indexed. This is a useful additional check, but the original post does not demonstrate that resubmitting it will necessarily change which URLs are selected as canonical. A more cautious approach is to cross-check the sitemap, redirects, and URL Inspection results rather than treating any single step as a guaranteed solution.

ProcrustesPRProcrustesPRShould you use a 302 redirect to a temporary alias for the new server during a DNS update?

Canonical URL selection after URL changes and redirects: perspectives from across the web

Do you need to switch sitemap generators or install Yoast?

Switching tools or installing Yoast should not be treated as a necessary step. A forum reply suggests checking the sitemap generator or SEO plugin and recommends Yoast, but it provides no evidence that switching tools will cause the new URLs to be selected as canonical. If you have concerns about the sitemap’s contents, include the generator or plugin in your checks rather than assuming it is the source of the problem.

ProcrustesPRHow does HSTS protect websites and subdomains?

References

  1. Google de-indexed my URLwww.warriorforum.com — Source used in the article above.
  2. What’s a 302 Redirect? And When Should You (Actually) Use It?www.semrush.com · 2023-07-17T09:16:00Z — Source used in the article above.
  3. Some links not getting indexedwww.warriorforum.com — Source used in the article above.
  4. Google Says Why Site Migrations Can Exceed 4 Monthswww.searchenginejournal.com · 2026-10-13T11:23:58+00:00 — Source used in the article above.
  5. Google de-indexed my URLwww.warriorforum.com — Source used in the article above.
  6. Some links not getting indexedwww.warriorforum.com — Discusses: Do you need to switch sitemap generators or install Yoast?
  7. Some links not getting indexedwww.warriorforum.com — Source used in the article above.

Related articles

How should you balance CNAME convenience and performance?Should you use a 302 redirect to a temporary alias for the new server during a DNS update?How does HSTS protect websites and subdomains?How do SSL certificates protect websites, and why are they needed?Should a Tumblr blog use the platform’s domain or the company’s domain?What types of URLs are there, and what are they used for?When should you use relative or absolute paths in WordPress?What are www subdomains and relative links used for?
ProcrustesPR
ProcrustesPR