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
-
Redirect Chain Issue
I keep running into a redirect chain issue trying to get a non-https/non-www domain to forward directly to the https/www domain on an Apache server. For background, we are forcing https and forcing www, but it appears the non-https/non-www domain is first redirecting to https/non-www and then redirecting again to the desired final https/www version of the domain. (Hope I am making sense here) I am trying to find code to add to my .htaccess file that will perform the following... 301 Redirect
Technical SEO | | FitzSWC
http://example.com directly to https://www.example.com (without 1st redirecting to https://example.com)
http://www.example.com directly to https://www.example.com Any experts in this with any thoughts? Thanks,
Fitz0 -
How should I set up a domain redirect
A client has 2 domains that he wants to use for the same site. At the moment one domain is just an abbreviation of the main domain (not sure why) as follows: www.mygreatpropertycompany.com
Technical SEO | | davidmaxwell
www.mgpc.com (just redirects to the above) He is complaining that when he searches for 'mpc' there are no results (at all) so I'm wondering what the best approach is.There is currently nothing on the main domain that refers to 'mgpc' in it's abbreviated sense - the only place it's being used is the company's email addresses (info@mgpc.com). The redirect is simply a html file in the root of www.mgpc.com as follows: Is there anything I can do to help him out? (this is one of those 'doing a friend a favour' tasks!) Thanks!0 -
URL redirecting domains
Hi Is there anything wrong/dangerous forwarding a clutch of domains to a sub page (landing page) on a different domain ? Say Brand X buys Brand Z and wants to close down Brand Z site but have Brand Z domain fwd to a landing page (explaining the company acquisition) on Brand X site. In addition Brand Z had a few related but unused domains forwarding to Brand Z doman & now also wants those fwd'd to the new landing page on brand X Since the reasons for doing this forwarding are legitimate company reasons relating to an acquisition i would have thought it should be ok but can anyone think of a reason why could be bad since i remember in the old days peeps used to redirect domains for seo reasons so worried fwd'ing a load of domains could cause some sort of negative flag with big G ? Also do domain redirects transfer the authority/juice from the old site/domain to the new destination page (new landing page on brand x site) similar to how a 301 redirect works ? Many Thanks Dan
Technical SEO | | Dan-Lawrence0 -
301 Redirect with index.asp
I am very new to all of this so forgive the newbie questions I will get better. Ok so after starting a campaign I see that I have many issues including where some pages are being deemed as duplicate content. 1. The report says the http://lucid8.com has duplicate content on 2 other pages 2. When I look at them it shows that http://lucid8.com/index.asp and http://www.lucid8.com are duplicates. 3. Really these are the exactly the same page because the default page that is opened for www.lucid8.com http://www.lucid8.com etc always opens the index.asp page. 4. Now I read that I should do permanent redirects and how to do this via IIS and I tried to do a redirect from index.asp to www.lucid8.com but that does not work because www.lucid8.com is pointing to index.asp and so we end up in a circle. So the question is how do I get rid of these duplicate page references without causing problems. Thanks
Technical SEO | | TroyW0 -
301 redirect
Hi All, I have just completed a 301 redirect on my site http://www.klinehimalaya.com and I was just starting a new campaign on SEOmoz and I got this message: Roger has detected a problem:
Technical SEO | | gorillakid
We have detected that the domain www.klinehimalaya.com and the domain klinehimalaya.com both respond to web requests and do not redirect. Having two "twin" domains that both resolve forces them to battle for SERP positions, making your SEO efforts less effective. We suggest redirecting one, then entering the other here. My only other question, is my .htaccess codeing correct and how long will it take to show it is correct in SEOmoz and online? All ".htaccess" code: AddHandler php-stable .php
**_Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} !^www. [NC]
RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] RewriteRule (.*).html$ /$1.php [R=301,L]_** Lastly, I have recently changed all of my files from .html to .php is this going to hurt my SEO and is the code "RewriteRule (.*).html$ /$1.php [R=301,L]" going to fix the issue by redirecting the .html links to the .php pages? Any suggestions or help appreciated. Paul.0 -
Can I remove 301 redirects after some time?
Hello, We have an very large number of 301 redirects on our site and would like to find a way to remove some of them. Is there a time frame after which Google does not need a 301 any more? For example if A is 301 redirected to B, does Google know after a while not to serve A any more, and replaces any requests for A with B? How about any links that go to A? Or: Is the only option to have all links that pointed to A point to B and then the 301 can be removed after some time? Thank you for you you help!
Technical SEO | | Veva0 -
Redirects
If I redirect page A to page B does page A need to exist before Google sees the redirect. Or can I just put up a redirect and delete page A. If the page doesn't need to exist: You have all your redirects in place for a website. You want this website to redirect to another website. You completely delete the website and put up the htaccess, there should be no problem with this, because the redirects are in place correct? Thanks
Technical SEO | | tylerfraser0 -
301 Single Page Redirects in IIS7?
Hey all -- I am working with a client, getting ready to make a full domain level change to a brand new domain. The existing domain has solid domain importance and trust, and the home page has a 5/10 GPR, so the transfer of all existing link juice is very important. Of course, I will be utilizing 301's to permanently redirect all existing pages to their new permanent homes. It will be a 1-1 structure, which I know is also best when possible. My question comes in specific to IIS. There is a wealth of information out there on the net regarding implementing permanent 301's using Apache and .htaccess, but nada when it comes to doing it in IIS7, which is what the client is using. For instance, today I am seeking to help them redirect 2 single pages to new destinations within the same domain, just diffferent folders. When you open up the IIS7 Control Panel (yes, with full Admin access), you can navigate to the directory, but the individual pages that I am looking to redirect with 301's do not show in IIS7, so you can't just right click on each page and choose "A redirection to a URL," etc. Any help on exactly how to redirect a single page using a permanent 301 in IIS 7 would be huge! Thanks guys!
Technical SEO | | Bandicoot0