Page with redirect is a common status in Google Search Console that can make website owners worry about their indexing performance. However, seeing this message doesn’t necessarily mean something is wrong.
Imagine publishing a WordPress article and later changing its URL. You create a redirect from the old address to the new one.
A few days later, Google Search Console reports that the original URL isn’t indexed.
At first, this might look like an SEO problem. In reality, Google may simply be following the redirect as intended.
The important question isn’t whether every redirected URL appears in Google’s index. Instead, you need to determine whether the redirect is correct and whether the destination page can be indexed.
This guide explains what the status means, how to investigate it, and when you should take action.
What Does Page with Redirect Mean?
The Page with redirect status appears when Google identifies a URL that redirects to another address and doesn’t select the original URL for indexing.
For example, consider these two addresses:
Original URL:
Destination URL:
When someone visits the original address, the website automatically sends them to the destination.
Google can follow that redirect and evaluate the destination page.
As a result, the original URL generally doesn’t need a separate place in the search index.
However, this doesn’t guarantee that Google will index the destination.
The destination must still meet Google’s indexing requirements.
Is Page with Redirect an Error?
Not necessarily.
Google Search Console includes this status among reasons a URL isn’t indexed. However, a redirected URL may be excluded for a perfectly legitimate reason.
For example, you might intentionally redirect an outdated product page to its replacement.
In that situation, the redirect can help visitors reach the correct content.
Therefore, you shouldn’t remove redirects simply to reduce the number of non-indexed pages.
Instead, investigate whether each redirect serves its intended purpose.
Why Does Google Search Console Show Page with Redirect?
Several common website configurations can produce this status.
Some are intentional, while others may require correction.
| Cause | Example | Usually a Problem? |
|---|---|---|
| Changed URL slug | Old article redirects to a new slug | No, if intentional |
| HTTP to HTTPS | HTTP address redirects to HTTPS | No |
| WWW normalization | WWW redirects to non-WWW | No |
| Trailing slash normalization | /page redirects to /page/ | No |
| Deleted or replaced content | Old product redirects to a relevant replacement | Depends on relevance |
| Incorrect WordPress redirect | Article redirects to the wrong page | Yes |
| Redirect chain | URL passes through several redirects | Worth simplifying |
| Redirect loop | Two URLs redirect to each other | Yes |
The first step is identifying which situation applies to your website.
How to Check Page with Redirect in Google Search Console
Before changing anything, inspect the affected URLs.
Step 1: Open the Page Indexing Report
Sign in to Google Search Console.
Select the correct website property.
Next, navigate to:
Indexing → Pages
Find the section explaining why pages aren’t indexed.
Then, select:
Page with redirect
Search Console will display examples of URLs associated with this status.
However, the report may not include every affected URL in its example list.
Step 2: Inspect an Affected URL
Choose one of the reported URLs.
Next, open URL Inspection.
Review the indexing information and any available canonical details.
Remember that the indexed inspection report describes the inspected URL.
Meanwhile, a live inspection of a redirected URL can follow the redirect and test the final destination.
Therefore, don’t assume a successful live test means the original URL itself is indexable.
Step 3: Identify the Redirect Destination
Open the affected URL in your browser.
Check where it sends you.
For example:
might redirect to:
However, the browser address bar alone doesn’t reveal every intermediate redirect.
For a more detailed investigation, use a redirect-checking tool or inspect the HTTP response headers.
Step 4: Inspect the Destination URL
Copy the final destination address.
Next, inspect that URL separately in Google Search Console.
Check whether Google has indexed it.
Additionally, review its canonical URL and indexing eligibility.
If the destination is correct and indexed, the original redirect status may require no action.
However, if the destination isn’t indexed, investigate that page independently.
How to Fix Page with Redirect Issues
The correct solution depends on whether the redirect is intentional.
Some situations require no changes.
Others involve correcting WordPress settings, internal links, or server configurations.
Fix 1: Leave Correct Redirects Alone
Not every Search Console exclusion needs fixing.
For example, suppose you change an article slug from:
/inventory-management-tips/
to:
/inventory-tracking-guide/
You then create a permanent redirect from the old address to the new one.
If the redirect works correctly, Google may report the old URL as Page with redirect.
That’s generally expected.
What You Should Do
Confirm that the redirect leads to the intended destination.
Next, inspect the destination page.
If everything works correctly, leave the redirect in place.
However, update internal links so they point directly to the preferred URL.
This avoids unnecessary redirect requests during normal website navigation.
Fix 2: Correct Accidental Redirects
Sometimes, a page redirects even though you want the original URL to remain accessible.
For example, a WordPress plugin might contain an outdated redirect rule.
Alternatively, a server configuration could redirect multiple pages to the wrong destination.
What You Should Do
First, identify where the redirect originates.
Possible locations include your WordPress redirect plugin, hosting configuration, or CDN rules.
Next, determine whether the rule is still necessary.
If the redirect is accidental, remove or correct it.
Afterward, confirm that the intended page returns a successful response and allows indexing.
Finally, inspect the URL again in Search Console.
However, avoid removing redirects that protect important URL migrations.
Fix 3: Update Your XML Sitemap
An XML sitemap should generally contain the canonical URLs you want search engines to index.
However, some websites accidentally include old redirected addresses.
For example, a sitemap might list:
even though that URL redirects to:
What You Should Do
Open your XML sitemap.
Next, check whether important entries redirect elsewhere.
If they do, update the sitemap to include the preferred destination URLs.
For WordPress websites, review the sitemap settings in your SEO plugin.
Afterward, confirm that the sitemap reflects your current website structure.
However, remember that sitemap submission doesn’t guarantee indexing.
Fix 4: Update Internal Links
Internal links help visitors and search engines navigate your website.
However, outdated links may continue sending users through unnecessary redirects.
For example, an article might link to:
/old-pricing-guide/
while the current page is located at:
/ecommerce-pricing-strategy/
Although the redirect may work, the internal link should ideally point directly to the current page.
What You Should Do
Review important navigation links and related articles.
Next, identify links pointing toward redirected URLs.
Update them to the final destination.
Additionally, check menus, category pages, and frequently visited content.
This creates a cleaner navigation structure.
However, you don’t need to remove the original redirect after updating internal links.
External websites may still reference the old address.
Fix 5: Remove Unnecessary Redirect Chains
A redirect chain occurs when one URL redirects through multiple addresses before reaching the final destination.
For example:
URL A → URL B → URL C
Although search engines can follow redirects, unnecessary chains create additional requests.
They can also complicate troubleshooting.
What You Should Do
Identify the original URL and final destination.
Next, review the intermediate redirect rules.
Where practical, configure the original URL to redirect directly to the final destination.
For example:
URL A → URL C
Afterward, test the redirect again.
However, avoid changing complex migration rules without understanding their purpose.
Incorrect modifications can create broken links or redirect loops.
Fix 6: Check for Redirect Loops
A redirect loop occurs when URLs repeatedly redirect between each other.
For example:
URL A → URL B → URL A
In this situation, visitors may see a browser error because the destination never resolves.
Google may also encounter a redirect error.
What You Should Do
Start by identifying the conflicting rules.
Next, check WordPress, hosting, and CDN redirect configurations.
For example, one system might force HTTPS while another incorrectly redirects requests back to HTTP.
Correct the conflicting settings.
Then, verify that the URL resolves to a final accessible page.
Remember that a redirect loop is different from an ordinary Page with redirect status.
Google Search Console may report it separately as a redirect error.
Fix 7: Use the Appropriate Redirect Type
Different redirect types communicate different intentions.
For example, a permanent URL move usually requires a permanent redirect.
Meanwhile, a temporary change may justify a temporary redirect.
| Redirect Type | Meaning | Typical Use |
|---|---|---|
| 301 | Moved Permanently | Permanent URL migration |
| 308 | Permanent Redirect | Permanent URL migration |
| 302 | Found / Temporary Redirect | Temporary relocation |
| 307 | Temporary Redirect | Temporary relocation |
Google uses permanent redirects as strong signals that the destination should become canonical.
Temporary redirects don’t provide the same canonicalization signal.
Therefore, choose the redirect type based on whether the move is permanent.
However, don’t change a correctly configured temporary redirect to a permanent one simply because Search Console reports a redirected URL.
Fix 8: Check Canonical URLs
Canonicalization helps Google identify the preferred version of similar content.
For example, a website might use a permanent redirect to consolidate several URL variations.
However, inconsistent canonical signals can complicate Google’s interpretation.
What You Should Do
Inspect the destination page.
Next, review its canonical URL.
Confirm that internal links, sitemap entries, and redirects consistently reference the intended destination.
For example, if your preferred article URL is:
avoid configuring its canonical tag toward an unrelated page.
Additionally, check whether the destination itself redirects elsewhere.
However, remember that Google makes the final canonical selection.
A canonical tag is a signal, not an absolute instruction.
How to Fix Page with Redirect in WordPress
WordPress websites can generate redirects through several systems.
For example, redirects may originate from permalink changes, SEO plugins, hosting rules, or CDN configurations.
Therefore, identify the source before editing anything.
Check Your Permalink Settings
Open your WordPress dashboard.
Navigate to:
Settings → Permalinks
Review your current URL structure.
However, don’t change the permalink structure merely to remove a Search Console warning.
Changing existing URLs can create additional redirects and broken links.
Review Redirect Plugins
If you use a redirect management plugin, open its redirect settings.
Look for rules involving the affected URL.
Next, confirm the source and destination.
If the rule is correct, leave it unchanged.
However, if the destination is wrong, update it carefully.
Check Hosting and CDN Redirects
Some redirects happen before WordPress processes the request.
For example, hosting services and CDN platforms may enforce HTTPS or normalize domain variations.
Therefore, a redirect may not appear inside your WordPress plugins.
If you cannot locate the rule, inspect your hosting and CDN configurations.
Test the Final Result
After making changes, open the affected URL.
Confirm that it reaches the intended destination.
Next, inspect the final URL in Search Console.
If you restored a page that should be indexed, you can request indexing after confirming its eligibility.
However, Google may need time to update its reports.
Page with Redirect vs. Redirect Error
These two Search Console statuses have different meanings.
| Status | Meaning | Recommended Action |
|---|---|---|
| Page with redirect | URL redirects to another address | Verify whether the redirect is intentional |
| Redirect error | Google encountered a problem following the redirect | Investigate the redirect configuration |
For example, an ordinary 301 redirect may produce the Page with redirect status.
However, a redirect loop or excessively long chain may produce a redirect error.
Therefore, don’t treat both statuses as the same problem.
Should You Click Validate Fix?
Google Search Console provides validation options for certain indexing issues.
However, validation isn’t necessary simply because a correct redirect remains listed as non-indexed.
For example, an old URL that permanently redirects to its replacement may continue appearing under Page with redirect.
That’s expected behavior.
If you correct an unintended redirect, allow Google to recrawl the affected URL.
You can also inspect the current URL and request indexing when appropriate.
However, repeatedly requesting validation won’t force Google to index a URL that intentionally redirects.
Does Page with Redirect Hurt SEO?
A correctly implemented redirect isn’t automatically harmful to SEO.
In fact, redirects are useful when moving content, consolidating duplicate URL variations, or changing domains.
However, poor redirect management can create problems.
For example, redirecting an important article to an unrelated page may confuse visitors and fail to preserve the intended relevance.
Additionally, broken destinations and redirect loops can prevent access to content.
Therefore, focus on redirect quality rather than the number of redirected URLs.
The objective isn’t to make every URL appear as indexed.
Instead, ensure that important canonical pages remain accessible and eligible for indexing.
Page with Redirect Troubleshooting Checklist
Use this checklist when investigating affected URLs.
| Check | Expected Result |
|---|---|
| Redirect intentional? | Yes, or identified for correction |
| Destination correct? | Points to the intended page |
| Redirect type appropriate? | Matches permanent or temporary intent |
| Final URL accessible? | Returns a successful response |
| Redirect chain? | No unnecessary intermediate steps |
| Redirect loop? | None |
| Sitemap entries? | Use preferred canonical URLs |
| Internal links? | Point directly to current URLs |
| Canonical signals? | Consistent with preferred destination |
| Destination indexing? | Reviewed separately in Search Console |
If the redirect is correct and the destination is healthy, you may not need to change anything.
However, if the original page should remain accessible, investigate why it redirects.
Frequently Asked Questions
Why Does Google Say My Page Is Not Indexed Because of a Redirect?
Google identified a URL that redirects elsewhere and didn’t select the original URL for indexing.
This can be normal when the redirect is intentional.
Should I Remove All Page with Redirect URLs?
No.
Removing legitimate redirects can break old links and interfere with website migrations.
Instead, investigate whether each redirect serves a useful purpose.
Can Google Index a Redirected Page?
Google generally processes redirects as signals about which URL should appear in search results.
The final canonical selection depends on multiple signals.
Therefore, a redirect doesn’t guarantee that Google will index the destination.
Should Redirected URLs Be Included in a Sitemap?
Generally, your sitemap should contain the preferred canonical URLs rather than outdated redirected addresses.
How Long Does Google Take to Update Redirect Information?
There is no guaranteed timeline.
Google must recrawl and process the relevant URLs.
Therefore, changes may not appear immediately in Search Console.
What If My Homepage Shows Page with Redirect?
First, check whether the reported URL is an HTTP, HTTPS, WWW, or non-WWW variation.
For example, an HTTP homepage redirecting to its preferred HTTPS version may be completely normal.
However, inspect the final homepage URL to confirm that it is accessible and eligible for indexing.
Final Thoughts
The Page with redirect status in Google Search Console isn’t automatically an SEO error.
In many cases, it simply means Google discovered an old or alternative URL that redirects to another page.
Therefore, the first step is checking whether the redirect is intentional.
Next, inspect the destination URL and confirm that your sitemap, internal links, and canonical signals are consistent.
If the redirect works correctly, no fix may be necessary.
However, accidental redirects, broken destinations, and redirect loops deserve