Welcome to the Q&A Forum

In addition to the responses which have already been posted to your question, there is another way to go about this, frequently used. It's not necessarily "better", but might be a more feasible alternative for you. 1. As long as you still own your old domain, then you could go into your DNS settings of the old domain (with your registrar/nameserver account), and set a simple pattern redirect to point all traffic from old.com/* to new.com/$1. Note that different domain services have different ways for you to specify this, but you are looking for whatever method preserves the file path from the request and appends it to the new domain. 2. So, then if you've done #1 as above, you would then set up your 1:1 redirects for every old page on the new server. This has the disadvantage ofc reating a small "redirect chain", meaning every redirect will have 2 hops instead of just one. Which makes it slightly less optimal than one of the other solutions mentioned which would only have 1 hop. But, at the same time is has a feasibility advantage, and lets you maintain all of your redirects in one place.  But yes, you would want to redirect all of your old pages. You might not need to do all 1:1, if you have some patterns, because you can also use pattern redirects. And if you do, then those ones you might want to put back out in your DNS settings for the old domain, so they wouldn't have 2 hops. 3. Technically, #1 and #2 should take care of #3. However, for the most valuable ones, you might also want to reach out to the sites and request an update. Just because fewer hops is more optimal. But technically a small chain of redirects should work.