So I'm moving my website from one domain to another. In this process I'm using the "change address" function in Google Webmaster Tools on my old-domain. In Step 2 of this process, Google Webmaster Tools will check whether redirect is setup properly on old-domain. And it fails I've setup the redirect on my old-domain. The only possibility is that if Google is requesting the www subdomain? In this case, Google would not see the redirect since you are specifically checking for the bare domain.
Since your old-domain is a separate hosting account then your directives can be simplified ie. Make sure when you are adding a domain in Google Webmaster Tools, use the domain as www. This will also cause error when you revamp or migrate the site. If you have already added example. After you validate the step 2, I warn you, step 3 may fail depending on the validation method you had for webmasters tools.
To resolve this, you will have to re-validate your old domain by using a configuration option in your DNS acseso to your service ISP provider's option. Webmasters tools will give you a code when you choose that option, and will ask you to create a TXT record in your DNS settings.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
I am assuming the reason for this is that Google picked up the new links naturally via the site and just has not yet gone to the old links and discovered the Since there is no way to get to these old links, as they redirect, I assume I just have to wait it out until it does a full re-index and sees that the old links are in fact and then dump them and give the PR to the new links.
So far we have not seen a shuffle much of the pages but I wanted to ask this question in case there is something else we have missed. As our site is approximately 30, pages where a large number are now, this is just a matter of time and I shouldn't panic. I hope this all makes sense Thanks, Kris tedster Msg pm on Apr 3, gmt 0 Senior Member joined:May 26, posts votes: 0. You'll even sometimes find that some of the URLs end up in the ' pages' list for a short time some months later.
That's what I was kind of thinking.. Just a matter of time. We only just uploaded this on April 1st and Google visited within minutes of the upload. At the moment, the old links are still the ones showing in the SERPs.
They have not been replaced by the new. Again, I am assuming that is just a matter of time as well. We didn't expect Google to visit so quickly after upload. I do see the old and new in the "site:" check but my thinking is that since it is only April 3rd and it started indexing on April 1st, that the old just hasn't been flushed yet.
My fingers are crossed. Thanks again, Kris berrysharpie Msg pm on Apr 3, gmt 0 Junior Member joined:Mar 11, posts votes: 0. I am glad I did The other kick in the head is that we had a some "permissions" problems when we uploaded.
I was not joking when I said Google visited within a matter of minutes. About 10 minutes after upload we noticed some pages that were "Forbidden" so we frantically went to fix them. During that time Googlebot had already gone through a bunch of these pages while we were trying to fix the incorrect permissions!
So much preparation and sometimes you just can't win. If you're unlucky, you'll see a code returned instead of the that you actually need. We are now seeing pages removing from the index and a lot of the old pages dropping lower in the index. So far it is really hanging on to these old links which is frustrating. But we do have an example now of one page where it is removed completely. Do you think it would be wise to add a list of the old links on like an "Old Sitemap" page so that the bot can come see these old links and redirect to the new ones a little more quickly rather than wait for this to figure itself out?
We are getting extremely nervous that it removed that one page I mentioned above because it had the old link in the index and naturally found the new one and has considered it duplicate and removed it. Not really sure how else you would introduce new links. We were thinking they would happily switch but of course the bot is going to find the new ones naturally through the site and still have the old ones. We have to wait for it to go through the old ones from other resources and that could be very very slow.
So now we are thinking and old sitemap to help it along a little smoother. Any advice is greatly appreciated here. If you think we should just be expecting a disruption in traffic and we shouldn't worry about the negative movement and just sit tight, that would be good to know as well.
Thanks tedster Msg pm on Apr 5, gmt 0 Senior Member joined:May 26, posts votes: 0. Yes, it takes patience - especially if you've changed many urls, as I assume you have by moving to all lowercase from mixed case. Just "stress test" all your urls as you've been doing, looking for anything you can improve, such as redirect chains or incorrect error handling or old urls still published in your source code. Ok, so we will hold off on adding an "old urls" sitemap.
We don't want to cause any further issues. A huge chunk of these pages are now So you are probably right, we just need to be patient. I will continue to stress test the urls regularly. I just don't like seeing that sort of error when I know both pages don't exist. Most of the old content will be redirected, including RSS feeds and email lists. A bit of history. Google first launched this solution as Google Sitemaps. Google launched the webmaster help center, and the Sitemaps group became a subcategory of a larger Google Group that included categories for lots of other site owner issues.
In May, , Google changed the name of Webmaster Tools to Search Console , which was the first sign — yes, five years ago — of Google broadening the scope. Redirecting URLs is the practice of resolving an existing URL to a different one, effectively telling your visitors and Google Search that a page has a new location. Redirects are particularly useful in the following circumstances:.
While your users generally won't be able to tell the difference between the different types of redirects, Google Search uses redirects as a strong or weak signal that the redirect target should be canonical.
Choosing a redirect depends on how long you expect the redirect will be in place and what page you want Google Search to show in search results:. The following table explains the various ways you can use to set up permanent and temporary redirects, ordered by how likely Google is able to interpret correctly for example, a server side redirect has the highest chance of being interpreted correctly by Google.
Choose the redirect type that works for your situation and site:. Googlebot follows the redirect, and the indexing pipeline uses the redirect as a strong signal that the redirect target should be canonical. Set up meta refresh redirects. Crypto redirect Learn more about crypto redirects.
Googlebot follows the redirect, and the indexing pipeline uses the redirect as a weak signal that the redirect target should be canonical. Setting up server side redirects requires access to the server configuration files for example, the.
You can create both permanent and temporary redirects on the server side. If you need to change the URL of a page as it is shown in search engine results, we recommend that you use a permanent server side redirect whenever possible. This is the best way to ensure that Google Search and people are directed to the correct page. The and status codes mean that a page has permanently moved to a new location. If you just want to send users to a different page temporarily, use a temporary redirect.
This will also ensure that Google keeps the old URL in its results for a longer time. For example, if a service your site offers is temporarily unavailable, you can set up a temporary redirect to send users to a page that explains what's happening, without compromising the original URL in search results. The implementation of server side redirects depends on your hosting and server environment, or the scripting language of your site's backend.
To set up a permanent redirect with PHP, use the header function. You must set the headers before sending anything to the screen:. If you have access to your web server configuration files, you may be able to write the redirect rules yourself.
0コメント