Guidance for setting up new 301s after having just done so (
-
Hi
I've recently set up a load of 301 redirects for a clients new site design/structure relaunch
One of the things we have done is take the kw out of the sub-category landing page url's since they now feature in the top level category page urls and don't want to risk over-optimisation by having kw repeats across the full urls. So the urls have changed and the original pages 301'd to the new current pages.
However If rankings start to drop & i decide to change urls again to include kw in final part of url too for the sub category landing pages, whats best way to manage the new redirects ?
-
Do i redirect the current urls (which have only been live for a week and have the original/old urls 301'd to them) to the new url's ? (worried this would create a chain of 301's which ive heard is not ideal)
-
Or just redirect the original urls to the new ones, and can forget about the current pages/url's since only been live for a week ?
(I presume best not since GWT sitemaps area says most new urls indexed now so I presume sees those as the original pages replacement now) -
Or should they all be 301'd (original urls and current urls to the new) ?
-
Or best to just run with current set up and avoid making too many changes again, and setting up even more 301's after having just done so ?
Many Thanks
Dan
-
-
Hi Aleyda
Sorry 1 more question:
Ive noticed that the new pages have started to rank well already.
In this case is it still advisable to 'fetch as google' in GWT the old redirected urls or, since the new pages have been found and ranking well, best to not fetch the old urls ?
Best Rgds
Dan
-
ok great many thanks Aleyda !!
-
You shouldn't remove them. If you implement the 301-redirects and do everything what's described before, although it might take some time, they should be eliminated from the index while referring their value with the redirects.
-
Great thanks Aleyda
I have already done most of those things except for fetching as googlebot in gwt, which ill do next.
Please confirm then that theres no need to remove the old urls in GWT at any point and they should just 'fade away' ?
many thanks
dan
-
Hi Dan,
Despite it's not a domain migration there are a lot of aspects that apply in this situation too! For example:
- You should monitor is that up update your internal (menu, content from your own site) and external links (at least the most important) towards the old URLs and target to the new ones.
- Make sure that the 301-redirects have been correctly implemented (in a URL to URL basis) to the relevant pages and make sure the new ones are still relevant and optimized for the same keywords than the previous ones.
- Generate a new XML sitemap with your new URLs and resubmit them in GWT.
- Resubmit your Old URLs with the fetch as Googlebot option in GWT to make sure Google knows about the update and identifies the 301-redirects.
- Monitor the (organic search and general) traffic and visibility (with GA and GWT) that the old URLs still receive vs. the new ones. If everything has been correctly implemented then there should be a trend that goes down with your old URLs and one that goes up with your new ones. If not, check which ones are still receiving a high amount of traffic and why: if they're still linked from an external source and hasn't been correctly redirected, etc.
Follow the previous recommendations and you should be able to minimize the effects of the changes.
Thanks,
Aleyda
-
Many Thanks Aleyda for your detailed reply
In this case though its not a site migration just a redesign but thanks for your great info ill use for future reference when tackling any migrations
In the case of a redesign where the urls have been changed (and hence why set up the 301's) would you recommend after aproximately 2 weeks that you should 'fetch as google' in GWT the old page urls and then few days after that remove the old urls ? (or should they just disapear eventually ?)
Many Thanks
Dan
-
Hi again Dan,
I would recommend that you first follow this checklist so you make sure your whole migration is SEO friendly and that you're not forgetting anything in the migration process and that you validate everything well.
The best process is the one the most straightforward one: do the migration as simple as possible (from one domain to the other with 301 redirects) and avoid changing many things at the same time. Please keep in mind that redirects will help but is not the only thing you should do, take a look at the checklist and you'll see.
It's actually natural that in the following days after the migration your rankings drop, search engines need time to crawl and index again the URLs in the new site, identify that you have moved your content from the old domain to the new one and with the help of the 301-redirects.
Among the additional things you should do to have an SEO friendly migration that you'll see in the checklist are that you should notify Google that you've moving your domain through Google Webmaster Tools (there's an option for this), create a new profile and generate a sitemap for the new domain, verify that the 301-redirects are all well implemented, that the content relevance is also kept in those pages for the keywords they were ranking with, that external and internal links going to the old urls are updated and now go to the new ones, prioritizing those landing pages that had the most highly relevant traffic, trying to change the minimum from the structure -keep one change at a time to be able to identify any issue-, check and follow-up on crawling errors). If you do everything what is recommended on the checklist little by little you should see how you start regaining your rankings again, but you need to give time (usually at least a couple of months if everything goes right).
So, there are a lot of other factors and I will make sure to follow the recommendations to minimize the negative impact, although is impossible of not having it. What is definitely not recommended is that you are updating many times your URLs or that you redirect many times, this is why this process should be effectively planned and designed validating all the aspects from the beginning and making sure that the more relevance signals you can keep (like the keywords in the appropriate elements of the pages) the best it is and making one change at a time makes things much more simple (first migrate, then one the effects of the migration have gone you can start optimizing and changing the new domain architecture) otherwise it can get really messy and this is what you're already experiencing I'm afraid.
I hope this helps! Aleyda
-
301 chains aren't ideal but, as long as they result in a real page, it's OK. The danger is you get a bad 301 in there which results in an infinite loop (A points to B points to C points to A).
I would avoid changing URLs on a frequent basis. A 301 is chaos for pages and results. Sometimes a page will inherit all of its predecessor's rank in a timely fashion but I've also seen where it takes time. You should expect some rankings drop after a URL structure change. It should recover in time but, again, there's no telling how fast that happens. As long as you can afford a short term drop, I say let it ride.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
HTTPS & 301s
Hi We have like most set up a redirect from HTTP to HTTPS. We also changed our website and set up redirects from .ASP pages to PHP pages We are now seeing 2 redirects in place for the whole of the website.
Technical SEO | | Direct_Ram
http.www.domain.com > https.www.domain.com (1) >> oldwebpage.asp >> new webpage.php (2) The question is: Is there anyway of making the redirect 1 and not 2? thanks
Enver0 -
Page authority old and new website
Dear all, I tried to find this question using the search option but cannot find the exact same problem. This is the thing: I launched a new website in January, replacing our old website that did pretty good in the SERPs. The old website is still running on a subdomain old.website.com and the new website is on www.website.com (www.denhollandsche.nl) Both sites are indexed by google right now, but I'm not sure if that's a good thing. For our main keyword, the page on the new website has an authority of "23" and the exact same page (some minor differences) on the old website still has an authority of "30". Both currently are on the second page of google while some time ago, they where still on position 2/3/4. My question is: if I would take down the old website and make a 301 redirect for the old page with P/A 30, to point to the new page with a P/A 23, will the p/a of this new page take over the P/A of the old page? What effects can I expect? The reason the old website is still running is that google images still shows images from old.domain.com in stead of images from the new website... Thanks for your help guys!
Technical SEO | | stepsstones0 -
Are my Canonical Links set up correctly?
I have Enable Canonical Links (recommended) on my web site. However, I also have THIS checked: Enable full URL for Home Page Canonical Link (include /default.asp) Is it hurting me??? Keep getting dinged on our report card. We are using the Volusion shopping cart software/platform.
Technical SEO | | GreenFarmParts0 -
Accidentally checked privacy setting in WP to "not to index" and dropped rank...how can I fix this?
I recently rebuilt a static website to a wordpress site...In the privacy settings ....the -"Ask search engines not to index this site" was checked and I didn't notice. I had a top ranking website now its completely gone off google and every where else. I have unchecked it, resubmitted a sitemap to google.....does anyone know if this is permanent damage or if there is something else I can do to help fix this......I'm freaking out
Technical SEO | | eversseo0 -
Yoast settings help
I could use some real help here in my Yoast settings. I had some great settings before but we switched servers and it looks like we lost all our settings. I've taken some screenshots and I'm hoping someone can help! http://d.pr/i/chNQ http://d.pr/i/51TY http://d.pr/i/io7S http://d.pr/i/nak http://d.pr/i/acon The site is run by a couple guys. Please help!
Technical SEO | | ttb0 -
Base HREF set without HTTP. Will this cause search issues?
The base href has been set in the following format: <base href="//www.example.com/"> I am working on a project where many of the programming team don't believe that SEO has an impact on a website. So, we often see some strange things. Recently, they have rolled out an update to the website template that includes the base href I listed above. I found out about it when some of our tools such as Xenu link checker - suddenly stopped working. Google appears to be indexing the the pages fine and following the links without any issue - but I wonder if there is any long term SEO considerations to building the internal links in this manner? Thanks!
Technical SEO | | Nebraska0 -
Any way around buying hosting for an old domain to 301 redirect to a new domain?
Howdy. I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway! Basically DomainA.com is being retired, and DomainB.com is going to be launched. We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately. Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com? Thanks!
Technical SEO | | SamTurri0 -
How to Redirect only specific pages to new domain
My HTACCESS FILE IS AS FOLLOWS: rewriteengine on
Technical SEO | | askthetrainer
rewritecond %{HTTP_HOST} ^mydomain.com$
rewriterule ^mydomain/(.*)$ "http://www.mydomain.com/$1" [R=301,L] #4d864805b49b5 I want to move ONLY specific pages from this domain to a new domain How do I edit my HTACCESS (which redirects http:// to www.) to move specific pages from old domain (which I have to delete) to new domain.... I.e. http://mydomaon.com/move.html needs to move to http://mynewdomain.com/move.html Where i can delete the original domains0