Troubleshooting Page Redirect Errors in Google Search Console

The "Page with redirect" error typically occurs when your website contains duplicate URLs for the same article or post. In such cases, Google Search Console will only index the original URL of that page. This issue is commonly found on Blogger websites.

Here's how to resolve the "Page with redirect" error in Google Search Console:

Identify and Choose the Correct URL:

If you are using Blogger, you may notice that your website URL has "/?m=1" at the end, like this:

Identify and Choose the Correct URL
Identify 

  • https://example.com
  • https://example.com/?m=1

Although the domain name is the same, there are two different URL structures. To index the URL correctly in Google Search Console, choose the URL without the "/?m=1" extension. The error occurs because the URL with the "/?m=1" extension redirects users to the other URL, while the second URL does not redirect users further.

Validate the Chosen URL:

If the error persists even after selecting the correct URL, initiate the validation process by following these steps:

Check out: Easy Activation of Lazy Loading Images in Blogger

Validate the Chosen URL
Validate


  1. Go to Google Search Console.
  2. Click on the navigation menu at the top of the GSC dashboard.
  3. Select "Pages" to view the pages with errors.
  4. Identify the pages displaying the "page redirect error."
  5. Start the validation process for these pages.

Please note that it may take up to 5 to 6 days for the validation process to resolve the issue.

Manual URL Inspection:

If the validation process doesn't resolve the problem, consider inspecting each URL manually. This manual inspection may aid in the indexing of your website. Keep in mind that URL inspection allows only 10 URLs to be indexed by Google Search Console bots within a 24-hour period.

Ensure that you perform these steps diligently to fix the "Page with redirect" error in the Google Search Console.

Check Out: How to Fix Crawled - currently not indexed Issues

Post a Comment

0Comments
Post a Comment (0)