Redirects
-
Hello,
My question is: how important is it to wait for the a redirect to get seen and cached before you take down the old page?
More in depth: my old platform has seriously limited my ability to add sitemaps and make edits to htacces. I just want to change nameservers (which will delete everything on there) and upload the htaccess is that alright?
Another way of saying it: when redirecting a page, is it necessary for google to see the old page before it is deleted?
Thanks
Tyler
-
Hi Tyler.
Both the links you offer are to Dr Pete's profile page. I am presuming this response was shared with you for your private Q&A?
As a follow up to you or Dr Pete I would ask the following questions:
Would you agree the best method of redirect would be at the server level?
If so, would you agree that once a redirect is implemented at the server level there is no reason to keep the old page on the server, and that even if the old page was kept it would never be seen or crawled as long as the server redirect was in place?
If the answer to both of the above questions is yes, then it is in perfect alignment with the information I shared. If the answer is "no", then I would have further questions based on the response.
What method are you using for the redirection?
The first response I shared specifically clarified it was for a server (htaccess) redirect. I use that example since it is the most common form in my experience, but there are other ways to do it.
Thank you for sharing the reply. So far it sounds like it affirms the response I offered.
-
by http://www.seomoz.org/users/profile/22897
It depends a bit on how the redirect is implemented. People sometimes rush to remove an old page from links, XML sitemaps, etc. and then run into a bit of irony - if Google doesn't recrawl the old page, they don't see the redirect and may not process it (or they'll have to find the new page by themselves and kill the old page, which can take a lot longer).
If your redirect is at the server level, like an Apache htaccess directive, you may not need the old page to actually exist. The redirect will happen without it. Typically, though, I'd leave a reference to the old page, like a line in the XML sitemap, at least for a few weeks.
Of course, if the old page is frequently crawled (it has a lot of outside links, etc.), you may be just fine. It's typically deeper pages that dont' get crawled often that run into trouble.
I'm not quite sure what you're saying about changing nameservers (or how that ties to htaccess) though. What method are you using for the redirection?
-
I'm thinking that google may go back to the actual old page in some way.
To the best of my knowledge, that is simply not possible.
Google can choose to ignore the robots.txt. Google can choose to ignore a meta tag. Google can choose to do just about anything it wants with respect to page rankings and SERPs. What Google cannot do is access a page on a web server to which it does not have access.
Google cannot tell the web server "hey, I know you are showing a 301 here but I don't want to be redirected. Show me the original page instead". At least, they can't based on my understanding of how the web works. If I am mistaken, I would love to learn about it so I can improve.
-
interesting. the source was very reliable and actually I am agreeing with what you are saying. I'm thinking that google may (during this discussion in early 2010) go back to the actual old page in some way. Otherwise what would be the point of leaving it up? There may be a caviat in the googel algo that likes it when you seem transparent. This is the old page and this is the new page. Showing that you still have control over the old page. I understand that the googlebot wont even get to the page if it sees a redirect in the htaccess. So this is the reason for the question. I asked a private and question and we'll see what comes back.
-
In a normal web page request, the requested page is provided by the host server with a 200 header code.
In a 301 situation, the new page is returned with a 301 header code. This would happen whether the old page is present or not. Even if the old page was present, the hosting web server would not look at nor offer the old page.
If there is no additional information or context, I would stand by my original statement. My question to the person who is the source of the statement would be, what exactly is Google supposed to see on the page before it is redirected? What has changed from the last time Google saw the page?
-
Ryan,
No I'm not referring to a link.
There's nothing wrong with that statement and it was not taken out of context.
There's no additional information that I am concealing.The 301 can go up immediately. The question is can the old url be deleted before it has been cached as a new url. After it gets cached it will show as the new url in the serps. Then it's safe to be taken down.
-
The fine people at bruce clay said it's important to let the page be seen before deleting it.
Do you have a specific link? Something is wrong with that statement and I feel it must be taken out of context.
Or possibly there is additional details you have not shared? Has the page changed in some way? Let's say your page is crawled by Google every 2 weeks. So it was crawled last week and you decide today you wish to 301 the page. You are suggesting to wait a week to let Google re-crawl the page before 301'ing it. My question is, what has changed on the page since the last crawl? What do you wish Google to see?
-
The fine people at bruce clay said it's important to let the page be seen before deleting it.
-
when redirecting a page, is it necessary for google to see the old page before it is deleted?
If you are performing the redirect via htaccess, then no. A 301 redirect is simply a header code. It lets Google know the page which is being displayed is not the page requested, but a different URL. Google then understands the need to replace the old URL with the new one.
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
-
Removing Multiple 301 Redirects
During my last redesign (and migration to Drupal) some of the updated SEO friendly url's on the new site were misspelled. Rather than updating the 301 redirects to point to the correct page the developer just added an additional 301 redirect. So it was redirected like this website.com/oldpage (301 to) website.com/new-paige (301 to) website.com/new-page Instead of website.com/oldpage (301 to) website.com/new-page I'll be finishing another redesign and updating to https soon, should I remove the redirect to the misspelled domain and just have one 301 from the original page? These multiple redirects have been up for over a year. Thanks for any specific advice!
Technical SEO | | talltrees0 -
Switching forum software - 301 redirects?
Hi everyone I'm working on a successful Wordpress site that also has a forum attached. The forum currently uses YAF forum software, which requires Windows hosting. The site owner wants to switch to Linux hosting. This is not a problem for WP, but it does mean that we'll need to transfer the forum to Xenforo or something similar that runs on Linux. We're OK with the technical side of this, but we're worried about the SEO implications. The URL for every forum post (more than 50,000 of them) is going to change during this transfer. It seems completely impractical to 301 each of those, so should I just 301 the URLs that have inbound links? Also, what is google's algo going to think when we suddenly have ~50,000 404s? Many thanks in advance! J
Technical SEO | | van280 -
Redirect root domain to www
I've been having issues with my keyword rankings with MOZ and this is what David at M0Z asked me to do below. Does anyone have a solution to this? I'm not 100% sure what to do. Does it hurt ranking to have a domain at the root or not? Can I 301 redirect a whole site or do I have to do individual pages. "Your campaign is looking for rankings for the www version of the campaign but the URL resolves as a root domain. This would explain the discrepancy. Since there is no re-direct between the two, you can have brickmarkers.com 301 re-direct to www.site.com which will prevent you from re-creating your campaign to track the root domain. Once the re-direct is in place it will take a while for Google to show the www version in the results in which your campaign rankings will be accurate." Thanks
Technical SEO | | SeaDrive0 -
Redirect a page intended for iframe
we built an interactive calculator that gets iframe embedded in our blog and landing pages. the blog that embeds it is doing well the problem is that the iframe source html page is also indexed by google and is on the second page of results. which we don't want as it doesn't have any context/branding/call to action/etc. if i put a noindex meta tag on the iframe html source page, will that remove the indexing of the pages that consume it in an iframe?
Technical SEO | | icstars0 -
Questions about Redirects
Hi, I am trying to make sure that I can determine if a site has a 301 redirect set up to redirect the site from domain.com to www.domain.com and am hoping that you can confirm the following for me, or let me know if I am off track: is http://www.internetofficer.com/seo-tool/redirect-check/ a reliable way to check if a 301 redirect is set up? is Screaming Frog SEO Spider a good tool to use to see if a redirect is in place? if I search for site:www.domain.com and site:domain.com, I should only get results for the site being indexed, not for the site that has the 301 redirect set up, right? For example, if www.domain.com is set up to redirect to domain.com, then I should get no search results for site:www.domain.com and only show indexed pages for domain.com. If I search for site:www.domain.com and site:domain.com and get results for both, then does this mean that the redirect is not set up? if a redirect is set up from www.domain.com to domain.com, should the crawl report should only show one page crawled on www.domain.com? if a crawl report shows same number of pages for www.domain.com as for domain.com, does that mean that redirect is not set up properly? Thanks in advance for your help! Carolina
Technical SEO | | csmm0 -
301 redirect dropped page rank
Hi, We have a www domain that I have changed to a non www domain. The www domain had been in place for some time and had a good page rank, PR4. After this change the page rank dropped significantly (PR0, and now recently back to PR2) despite it being a 301 redirect which I thought "should" carry over the page rank. Yes, I am aware I should have just left it be. Hind sight 20/20 .. ya ya ya 🙂 My questions Is the 301 the correct method for this? Why did the page rank drop despite the 301? Should we go back to the www domain at this point? Thanks Kris
Technical SEO | | adriot0 -
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 -
301 Redirect vs Domain Alias
We have hundreds of domains which are either alternate spelling of our primary domain or close keyword names we didn't want our competitor to get before us. The primary domain is running on a dedicated Windows server running IIS6 and set to a static IP. Since it is a static IP and not using host headers any domain pointed to the static IP will immediately show the contents of the site, however the domain will be whatever was typed. Which could be the primary domain or an alias. Two concerns. First, is it possible that Google would penalize us for the alias domains or dilute our primary domain "juice"? Second, we need to properly track traffic from the alias domains. We could make unique content for those performing well and sell or let expire those that are sending no traffic. It's not my goal to use the alias domains to artificially pump up our primary domain. We have them for spelling errors and direct traffic. What is the best practice for handling one or both of these issues?
Technical SEO | | briankb0