This is something I have faced before. the page URL is blocked via the google search console removal tool, but it is not actually removed by google. I will be receiving 404/410 error on this page nd I will block all internal links to it.The problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.
I have experienced such an issue on one of my websites. the solution of taking out that URL from the google search console will not solve the issue for long. the best practice would be to give the URL a 404 or 410 status nd to find any links pointing towards that URL on your website.The problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.
nevertheless, this removal tool will only make the URL invisible temporarily. this is not an actual removal from the index. I would also see to it that there are no internal links, sitemap links, and old backlinks linking to the same URL since google could still find it via other sources. If google always displays 410, then just leave it for some time.The problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.
It just hides the URL for around 6 months because the site has not been deindexed. After 6 months, the URL appears in search engine results.The problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.
You need to make sure they return a proper 404 or 410 status code and remove any internal links pointing to them.The problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.
this could be true of CDN caches as well, especially when you have got different HTTP code for the same URL from both the CDN edge nd origin server. there have been instances where the old HTTP code gets cached and keeps coming even when you remove the URL or make change on the server-side. I want to check my cache status to purge the URLs and see if there is any difference that way. do you test your responses via cloudflare or do the same from the origin as well?The problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.
I think the most important thing would be to ensure that the Google bot can have regular access to the 404 or 410 status code temporary removals only conceal URLs for a certain period of time so this cannot be used as an alternative to deindexation i would also check the internal linking and sitemapThe problem is, after the temporary removal period ends, the URL sometimes pops right back into the search results, even though the page is a completely dead 404 or 410 now. It feels like Google’s cache takes ages to actually drop the dead link permanently.