How to Stop Old invalid links/bookmarks hitting the new website? - web

I have a heavy traffic website, where i recently upgraded the whole website to new system, where most old urls are now not valid and causing problems in the new system. Most of the old urls are saved in the users browsing history.
How do i make sure these old links/bookmarks are redirected to the main page of the new website
please note i am using nginx and its not possible to redirect by one by one as website is large and not possible to do them manually.
Any ideas ?

I think the simplest solution would be to add the following in your Nginx server block...
error_page 404 /;

Related

Domain name forwarding works only partially

For many years I had a successful website at https://www.lunarium.co.uk built on top of Google App Engine, Java version. Some time ago, GAE deprecated the technology they initially recommended for storage, so I decided to re-create the site on a new, less cumbersome platform. Eventually, I re-created it with Django, hosted on Pythonanywhere.com at the domain name https://www.lunarium.co.
When the new version was ready, I've forwarded the domain name lunarium.co.uk (hosted with GoDaddy) to lunarium.co (301, no masking). I also changed the CNAME www on lunarium.co.uk to point to the naked domain name, lunarium.co.uk. This was done in the beginning of April, but the stats keep showing that many people are still going to the old version of the website. On some days, many more people visit the old website than the new one. This is one part of the problem — why is that happening? (Right now I've also added forwarding from www.lunarium.co.uk to www.lunarium.co but was unable to delete the www CNAME).
Also, I had some pages on the old website that were very popular. For example, this one: https://www.lunarium.co.uk/moonsign/calculator.jsp. I made sure that if someone will come looking for this page on the new website (like https://www.lunarium.co/moonsign/calculator.jsp) they would be redirected to the appropriate new page. However, when trying to navigate to that popular old page, I'm getting a strange error message: Not Found 404.0, and I'm not sure where this message is coming from.
Previously, when navigating to the home page of the old website, I used to be correctly redirected to the home page of the new website. (I just tried to do that, and it didn't work, but maybe that is a temporary glitch). However, specific pages within the website are never properly redirected. Is there a way to make sure that they are redirected?

IIS keep some urls when changing domain

I will be changing a www server to be ww2. Making a new server the www server. The new server has IIS 8.5 running, with https, ASP.Net/MVC. The old server does not have https.
I have some urls that users may have bookmarked to the old www. I would like those urls to still work (doesn't matter if the browser displays ww2). I have made sure those urls are unique and don't conflict with any resource/path on the new server. Some urls are a resource like .html others are any in a path. Do I put all of those urls in as redirects in IIS on my new server? Are redirects the best of accomplishing this?
I think what you're looking for is the URL_REWRITE Extension.
You can download it here: https://www.iis.net/downloads/microsoft/url-rewrite
Then apply the rewrite rules at the server level not the application level. This will allow you to easily control the the flow of any your old URLs to your new location.
Depending on how many you have theirs a few different ways you can do it with URL_Rewrite.
To get you started here's a bunch of tutorials on how to use it: https://www.iis.net/learn/extensions/url-rewrite-module
After you play with it and if have any specific questions, just ask on stackoverflow and tag the question with URL-REWRITE-MODULE

Caching issues - how to identifiy the offending server

Hi
I replacing an existing website. One of the url to a page happens to match one of the url on the old site. I can see old content when I try accessing this url. Is it possible for to debug where this copy of the old site is coming from? I've already identified it's a server between me and our host because I get the same content on web based proxies and my android.
Also how would i get the cache updated?
Our host is Webfusion and our domain is with 123reg

IIS Permanent Redirects

I have seen a few things written about this and remember one where there was an XML file. So, there is an old URL and a new URL. If the user hits the old URL he is redirected to the new one.
The redirects can be from files that don't exist on the server eg new-jobs.php from Apache server has been moved to an IIS Server and the file is now called new-jobs.aspx.
Does anyone know of such a system or have a better solution?
Check out URLRewrite.

Migrating a website to a new domain, and associated google index problem

We currently have a website at "somedomain.net/codefest". We do not own this server (or this domain name).
Due to capacity problems, we are now moving to a new server. Since we do not own the old domain name, we are also moving to a new domain name.
Since we'll need to abandon the old server soon, we'll be redirecting all requests to "somedomain.net/codefest/anything" to "newdomain.net/anything".
My problem is, after a lot of effort, our website's page rank is now fairly significant. I'm sure moving our website to a new domain name will be drastically detrimental to our website's search engine rank.
Is there any way we can tell the search bots that we've moved the website? Perhaps, when I redirect from the old site, if I give a 302 redirect, search spiders will notice it?
Is there any other issue related to moving our website that I should be aware of?
Thanks,
jrh
Google recommend a 301 redirect. (301 indicates permanent change. 302 indicates a temporary change.)
They have other advice on their Moving Your Site FAQ page which should be more widely applicable than just Google.

Resources