Impact of Errors 404 and Referring to Site Migration: Google Tips

One day, Reddit user shared his client's website migration experience, which led to a loss of positions in the ratings. He said that it took a few steps to solve problems, including correction of technical problems on the site, forwarding pages with errors 404 to the relevant URL, and submitting these changes to verify at Google Search Console. However, despite the fact that all the forwarding and bugs of 404 were working correctly, he could not confirm the changes to Search Console. It caused him disappointment, and he sought the advice of what to do next. This prompted John Muller to answer and explain how Google processes these changes.

"Mark as Corrected" only tracking as things re -processed. It does not speed up the re -processing process. If pages have to return an error 404, then there is nothing to do. Error 404 for pages that do not exist is normal. It's technically correct to return 404. - John Muller

🚀 For example, if you have a page that should no longer exist and you deliberately return a 404 error, this is the right approach. This means that you do nothing wrong, even if Search Console denotes these 404 errors. Therefore, it is important to understand that 404 mistakes are not always bad.

• 📌 You need to correctly adjust the forwarding and make sure that new content returns 200 (OK).
• 📌 Update internal links so that they display new URLs.
• 📌 Update the site cards with new dates to signal Google to change.