What is the best practice for old pages that no longer exist on an Angular site?

Webmasters Asked by umang naik on August 10, 2020

We built our eCommerce web site using Angular as a single page application. We have implemented a spinner that runs until the page is responding with the expected content. We have some category pages which were crawled and indexed by Google but which are no longer available on the site.

What is the best practice for old pages? Should I create "404 Not Found" pages for them instead of saying "loading" forever? Is setting a no index meta tag enough?

One Answer

If the content never existed in the first place, you should return 404. Crawlers will know that there's nothing to see on that page and move on.

If the content used to exist at that URL but no longer does (for example, a product was removed from the website), you should return 410.

404 means there is nothing at this URL. 410 means that there is no longer anything at this URL. While it's a subtle difference, a 410 error code will tell crawlers to stop trying to access that page and will (most likely) drop it from their indexes. This really won't make too much of a difference in your SEO rankings besides letting search engines remove URLs of de-listed products. If implementing this is laborious, you really don't need to- 404 will suffice.


410 GONE: The target resource is no longer available at the origin server and that this condition is likely to be permanent.

If the origin server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 Not Found ought to be used instead.

Answered by Josh Honig on August 10, 2020

Add your own answers!

Related Questions

How do search engines handle ?

3  Asked on October 5, 2020 by tom-marthenal


Can you run a fetish forum anonymously?

0  Asked on July 22, 2020 by anony-inflates


Ask a Question

Get help from others!

© 2022 All rights reserved. Sites we Love: PCI Database, MenuIva, UKBizDB, Menu Kuliner, Sharing RPP