Why redirected URLs show as not indexed, and which ones actually need attention

What the error means

The URL redirects to another URL, so Google indexes the destination instead. Search Console lists the redirecting URL as not indexed. That is the expected result of any working redirect.

Why Google rejects it

Google indexes final destinations, not the addresses that forward to them. Old URLs after a migration, http and non-www versions, and renamed products all land here. The report only matters when a redirecting URL is one you still link to or list in your sitemap.

How to fix it

1. Export the list and sort it into expected redirects (old URLs, http, www) and unexpected ones (pages you meant to be live).
2. For unexpected ones, find why the page redirects: an app, a redirect rule, a changed handle or a language/market redirect.
3. Update internal links and the sitemap to point directly at the final URL, so Google stops rediscovering the redirecting one.
4. Collapse chains: a redirect that goes A to B to C should go straight from A to C.

Common causes

URL was intentionally moved

A 301 or 308 redirect tells visitors and crawlers that the page has moved. Search Console excludes the source URL because the destination is the address that may be indexed. If the destination is the intended equivalent and works, this is often expected rather than a defect.

Product handle changed

A platform may redirect an old product slug after a rename. The old URL remains known to Google, but shoppers should land on the new product URL. Check that the redirect points to the same item and that the feed and internal links now use the destination directly.

Redirect points to a generic or unrelated page

Sending a deleted product to a homepage or broad category can confuse visitors and may cause the destination to be treated as irrelevant. Review the redirect target; keep a redirect only when there is a close replacement.

Redirect chain remains after migration

Several successive redirects may still work for a browser but slow and complicate crawling. Search Console's page-with-redirect status itself is not the same as a redirect error, but long chains and loops need correction. Test every hop and destination.

Fix it on your platform

On Shopify

1. Open Online Store > Navigation > URL redirects (or the current redirects area in admin) and check that the old product or page path maps to the final equivalent URL.
2. After a handle change, update product feeds, menus, collection links, and campaign links to use the new URL instead of relying on the redirect indefinitely.
3. Avoid redirecting removed products to the homepage. Use a close replacement or allow a true 404/410 when there is no equivalent.
4. Test old and new URLs while logged out and check that the destination returns the expected product, not a generic page.

On WooCommerce

1. Check redirect plugin or server rules for the old URL and confirm the destination represents the same item. Remove duplicate rules that create multiple hops.
2. When changing product permalinks, update internal links and feed URLs. WooCommerce documentation notes that prior URLs can 404 without redirects after a permalink change.
3. Do not redirect every deleted product to the shop root. Choose a relevant replacement or return a not-found response.
4. Test redirects with a crawler or HTTP tool and check the final status and Location header.

On other platforms

1. Use the platform's URL redirect manager when a page has moved permanently and select the closest relevant destination.
2. Update navigation, sitemaps, product feeds, and links to point straight to the destination URL.
3. Remove redirect rules that lead to unrelated pages or form a chain, and keep redirects for old URLs with real traffic or links.
4. If a page was removed with no replacement, let it return 404 or 410 rather than creating a misleading redirect.

How to confirm it is fixed

1. Fetch the old URL and record each redirect hop, then inspect the final destination for a 200 response and equivalent content.
2. Check that internal links and sitemap entries use the destination URL, not the redirecting source.
3. Use the bulk status check to inspect URL status and redirect chains across affected pages.
4. Inspect the destination in Search Console. The live test follows redirects, so check the source report and destination index status separately.

A worked example

Hypothetical case: a WooCommerce shop changes a product permalink from /product/linen-cover to /shop/linen-duvet-cover during a catalog cleanup. Search Console lists the old URL as Page with redirect. The redirect resolves directly to the same duvet cover, but the sitemap and two category links still use the old path. The owner updates the sitemap source and internal links to the new URL, retains the old redirect for visitors with saved bookmarks, and checks the destination in URL Inspection. The old address remains excluded by design; the important check is that the final product URL is accessible and eligible for indexing.

Other errors like this