M
Mark
Our site gets searched by robots all the time. This is great. However,
many of our pages that we want to be cataloged are data driven, so we end up
with pages like:
www.ourdomain.com/products.aspx?productid=356
Let's assume that we stop selling productid 356. This means that the url
above is invalid. If a general user has bookmarked this page or pastes in a
url into a browser that isn't quite right, we want them to get a 'pretty'
error message. However, using this approach means that a search engine like
google will interpret this page as still being "OK" and will continue to
catalog it.
Off the top of my head, I see two solutions:
1. Redirect to a bogus page that doesn't exist, so a 404 message displays.
Search engines would remove the link in their catalog(hopefully????), but
users would not have a "pleasing" experience.
2. Throw an unhandled exception. A ugly ASP.NET error message page is
displayed. This ticks off the user, but hopefully the search engine
realizes that the page does not actually exist? Probably not.
Suggestions on how to handle this?
Thanks in advance.
Mark
many of our pages that we want to be cataloged are data driven, so we end up
with pages like:
www.ourdomain.com/products.aspx?productid=356
Let's assume that we stop selling productid 356. This means that the url
above is invalid. If a general user has bookmarked this page or pastes in a
url into a browser that isn't quite right, we want them to get a 'pretty'
error message. However, using this approach means that a search engine like
google will interpret this page as still being "OK" and will continue to
catalog it.
Off the top of my head, I see two solutions:
1. Redirect to a bogus page that doesn't exist, so a 404 message displays.
Search engines would remove the link in their catalog(hopefully????), but
users would not have a "pleasing" experience.
2. Throw an unhandled exception. A ugly ASP.NET error message page is
displayed. This ticks off the user, but hopefully the search engine
realizes that the page does not actually exist? Probably not.
Suggestions on how to handle this?
Thanks in advance.
Mark