Alternate page with proper canonical tag error

#708586
Viewing 6 replies - 1 through 6 (of 6 total)
  • Hello,

    We apologize for the inconvenience you’re facing with the “Alternate page with proper canonical tag” error in Google Search Console. We appreciate you bringing this to our attention.

    To redirect the ?nonamp=1 pages to normal URLs using Rank Math, you can easily set up redirections in the Redirection Manager. Here’s how you can do it:

    1. Navigate to the Redirections section in Rank Math from your WordPress Dashboard → Rank Math SEO.
      Navigate to redirections in Rank Math

    2. Click on “Add New” to add a new redirection.
      Add new redirection in Rank Math

    Once you’ve added the redirection, Google should re-index the page with the new canonical URL.

    If you have a lot of URLs that need to be redirected, you can also add them in bulk. You can learn more about bulk 301 redirects in WordPress here.

    We hope this helps! If you have any further questions or need additional assistance, please feel free to reach out to our support team directly from here, and we’re always here to help.

    Best regards.

    Sources:
    Alternate Page with Proper Canonical Tag Status in Google Search Console » Rank Math
    Redirect all AMP pages to non-AMP pages » Rank Math
    How to Fix “Duplicate, Google Chose Different Canonical than User” » Rank Math

    Hello,

    Since the AMP no longer exists on the site, the URLs with ?nonamp=1 will have the canonical URL of the correct page, and Google will report the errors if they have found those URLs. However, the error will not cause any issues with the indexing of the correct URLs. If you redirect them, then Google will report the Page with Redirect error.

    If you don’t want Google to crawl the nonamp URLs, then you should use the following rule in your robots.txt file:

    Disallow: *?nonamp=1*
    

    Here is how to edit your site’s robots.txt file using Rank Math: https://rankmath.com/kb/how-to-edit-robots-txt-with-rank-math/

    Hope that helps and please do not hesitate to let us know if you need our assistance with anything else.

    Great. Thank you so much for the support. 🙂

    Hello,

    We are glad to know that this issue has been resolved. Thank you for letting us know.

    We’re just following up with you to see if you still need our assistance or if we can go ahead to mark this ticket as closed.

    We appreciate your patience and cooperation throughout this process.

    Thank you for choosing Rank Math.

    Suresh V
    Rank Math free

    Hello support team,

    I added Disallow: *?nonamp=1* to the robot.txt file as you recommended.

    Today I received an error from GSC saying that “Search Console has identified that some pages on your site are not being indexed due to the following new reason: Blocked by robots.txt”.

    When I opened the report, I could see a couple of URLs with ?nonamp=1 extension blocked by robots.txt.

    Can I ignore this error? Please assist me.

    Thank you.

    Hello,

    The “Blocked by robots.txt” error means that your website’s robots.txt file is blocking Googlebot from crawling the pages. In other words, Google is trying to access those pages but is being prevented by the robots.txt file.

    Since AMP no longer exists on your site you can safely ignore this notice from Google. It can be taken as purely informational. Even without the disallow rule Google would not have indexed those pages as they correctly have the main pages as canonical, but will lead to wastage of your crawl budget.
    https://monosnap.com/image/E3LylbittHKmSnCKaMGD9mQliEFABf

    We hope this helps. Please let us know if you have further questions or concerns.

    Thank you.

    Hello,

    Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.

    If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)

The ticket ‘Alternate page with proper canonical tag error’ is closed to new replies.