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
-
Should the canonical tag for the redirected pages be changed
Hi! Does anyone know if the canonical tag of the old redirected page should be changed, and include the URL of the new destination? Thanks in advance.
Technical SEO | | AnahitG0 -
Rel=canonical and redirect on same page
Hi Guys, Am I going slightly mad but why would you want to have a redirect and a canonical redirecting back to the same page. For Instance https://handletrade.co.uk/pull-handles/pull-handles-zcs-range/d'-pull-handle-19mm-dia.-19-x-150mm-ss/?tag=Dia.&page=2 and in the source code:- <link href="<a class="attribute-value">https://handletrade.co.uk/d'-pull-handle-19mm-dia.-19-x-150mm-ss/</a>" rel="<a class="attribute-value">canonical</a>" /> Perfect! exactly what it is intended to do. But then this page is 301 redirected tohttps://handletrade.co.uk/pull-handles/pull-handles-zcs-range/d'-pull-handle-19mm-dia.-19-x-150mm-ss/ The site is built in open cart and I think it's the SEO plugin that needs tweaking. Could this cause poor SERP visibility? This is happening across the whole site. Surely the canonical should just point to the proper page and then there is no need for an additional bounce.
Technical SEO | | nezona1 -
301 redirects for all urls - legal dispute
The website in question is a very high traffic website with substantial credibility in it's subject matter (sorry, can't share more details) that delivers an overwhelming majority of traffic from SEO, much of which is new visitors. A legal dispute has resulted in both parties agreeing to forward a percentage of the total URLs to alternative websites (only 1 website for each party). All URLs for the domain will be forwarded elsewhere. It does not make sense to me that the "sum of the parts" will be as strong once the redirects are implemented but I am looking for feedback. It is fair to say that the alternative domains of each party are no where near as strong as the domain being "parted out." Will the SEO juice be distributed to each domain in full? Will both parties lose out substantially? Feel free to ask for clarifications and I'll do the best I can given the legal parameters. Thanks.
Technical SEO | | ReachMaineAgency0 -
Redirecting a blog
We've acquired another company and want to redirect their soon-to-be-obsolete website to ours. It includes a blog with many blog posts. Should we: only 301 redirect the top level blog URL
Technical SEO | | Caro-O
try redirect individual blogs to blogs of a similar topic on our site (least practical I'm sure)
redirect all their individual posts to our main blog URL Thanks, Caro1 -
Redirect Question
We have a client that just did a redesign and development and the new design didn't really match their current structure. They said they didn't want to worry about matching site structure and never put any effort into SEO. Here is the situation: They had a blog located on a subdomain such as blog.domain.com - now there blog is located like domain.com/blog They want to create redirects for all the old the blog urls that used to be on the subdomain and not point to the domain.com/blog/post-name What is the best way of doing that - Through .htaccess?
Technical SEO | | Beardo0 -
Use 302 redirect when site crashes
My company has switched to a new ecommerce platform that we are not totally familiar with yet. As we've worked with it, we've had a couple situations where both the front and back ends of our site crashed simultaneously (always after installing a third party module). The platform's built-in backup solution hasn't been an option in those situations so we've been coming up with alternatives. We now have a duplicate of the site on our server for such emergencies. The plan is to have pages on the broken site point to the backup site using 302 redirects until the broken site is fixed. Is this correct usage of the 302 redirect? I often see people recommend to never use 302 redirects, but I thought this might be the kind of situation where they'd be appropriate. If so, are there other SEO considerations we should keep in mind? For example, I'm wondering if we should put canonical tags on the temporary site that point to the broken site so the broken site stays in the SE indexes.
Technical SEO | | Kyle_M1 -
.htaccess redirects
I've done some research but can't find a good answer to this question. Here's my situation: Site redirects from example.com to www.example.com just fine. However, it doesn't work so well for internal pages. My site incorrectly redirects (non-www) example.com/page2 to www.example.com when it should instead go to www.example.com/page2 So I need a method to redirect non-www internal pages to www versions. Currently I have this in my .htaccess - do I need to modify the rules? RewriteEngine on
Technical SEO | | 3plains
RewriteCond %{HTTP_HOST} !^www.example.com
RewriteRule (.*) http://www.example.com/$1 [R=301,L] Thanks0 -
301 Redirect for homepage with language code
In my multilingual Magento store, I want to redirect the hompage URL with an added language code to the base URL. For example, I want to redirect http://www.mysite.com/tw/ to http://www.mysite.com/ which has the exact same content. Using a canonical URL will help with search engines, but I would just rather nip the problem in the butt by not showing http://www.mysite.com/tw/ to visitors in the first place. Problem is that I don't want (can't have) all /tw/ removed from URLs due to Magento limitations, so I just want to know how to redirect this single URL. Since rewrites are on, adding Redirect 301 /tw http://www.88kbbq.com would redirect all URLs with the /tw/ language code to ones without. Not an option. Hope folks can lend a hand here.
Technical SEO | | kwoolf0