301 redirect for SEO on WP - my question straddles so many forums I decided to ask here. Thanks.

[SEO Lady]

Hello guys n gals good evening.

I have an interesting scenario that is a first to me.

Rather than verifying 2 websites in GWT, 301'ing all pages to the new URLs then submitting a 'change of address' I have a potential client that asked me a question that I don't know the answer to. You guys who know me, know I have no shame in learning something new and asking questions in a public forum.

Mr bluewidget.com decided to change his domain to bluewidgetkeyword.co.uk 18 months ago
They swapped platform over to WP
Bombed in Google
Alert Alert something must be wrong with WP let's ask Nina

I discovered that all internal bluewidget.com pages (and posts) are indeed correctly 301'ing over to bluewidgetkeyword.co.uk - however - the homepage still resides at bluewidget.com

So, in GWT I can see bluewidgetkeyword.co.uk is verified however there's no bluewidget.com

Yay! I say Simples! Verify bluewidget.com under the same GWT, and complete a Change Of Address, plus the 301 from bluewidget.com to bluewidgetkeyword.co.uk so there's no dupe content issue that's currently in place.

Mr Widget tells me that old website bluewidget.com was also transferred over to WP but he doesn't have a bluewidget.com/wp-admin login as it redirects to bluewidgetkeyword.co.uk
"I cannot verify it because there is no actual site to paste the code into""

......A-are you with me so far?

So, can we verify bluewidget.com by FTP and dropping the GWT verification code in the Index.php file via his host?
Then we can 301 the homepage of bluewidget.com to bluewidgetkeyword.co.uk via the host - then instructing the Change Of Address with GWT and winning the weekend?

This is my theory. Is it a working theory or a working 'jump into the pond of wrongness'?

Many thanks.
Nina

 

[StartUpC]

Hello Nina,
perhaps would be a good idea to use file based verification from G: this case you put a Google generated file into the domain root directory (usually a html file).

301 is a server side action (.htaccess if the site runs on Linux/Apache) so the original site content "can not be seen" by any visitor - including Goggle since the request is immediately redirected to another site/page. Whatever you put in php/html content files they will not be processed (theoretically).

Using .htacess the original site's content can be redirected to another domain or even certain pages of other sites. 301 inherits pagerank and trust of pages - this is useful.

When you redirect a site the old content (site) should not be seen any more.

Best,
Chill

 

[SEO Lady]

Hello Nina,
perhaps would be a good idea to use file based verification from G: this case you put a Google generated file into the domain root directory (usually a html file).

301 is a server side action (.htaccess if the site runs on Linux/Apache) so the original site content "can not be seen" by any visitor - including Google since the request is immediately redirected to another site/page. Whatever you put in php/html content files they will not be processed (theoretically).

Using .htacess the original site's content can be redirected to another domain or even certain pages of other sites. 301 inherits pagerank and trust of pages - this is useful.

When you redirect a site the old content (site) should not be seen any more.

Best,
Chill

I did wonder how we were going to get round this - thank you!

The only other thing I could think of was to un-301 bluewidget.com so we can login to WP, verify in GWT, then re-301 the site and complete the change of address.

- Would this have been a valid workaround or not?

Where are you in the UK and can I buy you a pint as I owe you a one

 

[webgeek]

For these, I find the DNS verify method works well. Sign in to their DNS provider, add a record and click verify. With DNSMadeEasy, they add/propagate faster than I can alt-tab and click the verify button/link. Obviously not everyone has external DNS, but they should still have a way of adding a basic record to their domain DNS config.

 

[altonroot]

I think, StartUpC is right. Do verification through html file and then point change of address in Google webmaster tools. As far as your this comment concern

The only other thing I could think of was to un-301 bluewidget.com so we can login to WP, verify in GWT, then re-301 the site and complete the change of address.

- Would this have been a valid workaround or not?

The whole drama has played 18 months ago so now un-redirect and then change of address and then redirect doesn't make sense to me. Just do above two simple steps. Let Google know you have changed address and leave it.

 

[lynxus]

Id go with webgeeks idea too. This is how I do most of mine..
Just create a TXT record with your verification code.. No need to play with the server, redirects or anything else. Just a simple DNS change.

 

[OldWelshGuy]

How exactly is the 301 being handled? is it a straight catchall 301? if so then that will explain a large portion of why it bombed. I think there is more to this than appears and would want to look at the HTACCESS with regard the redirection. I am assuming it is a page by page 301 as the homepage still exists under the old name you say?

 

[SEO Lady]

Thanks for the replies - a few things have changed since last week

OK so the original domain does not actually have a site loaded up, and is now directly 301's over to the new domain.

The thing is, the domain was registered back in 1998 and has some nice links and age and I'd like a 'Change Of Address' with Google to pass on the authority.

The owner can't do the Change Of Address as it's not verified in GWT and he can't verify in GWT as it's just the domain without a website.

In light of this new information what advice so you guys have as this is the first time I've come across this.

Many thanks
- Nina

 

[altonroot]

You have to verify the domain in webmaster to use change of address feature. Just map the dns and host the website on new server. Tell the server provider people they will do it. Then you have FTP server details. Using that upload a simple html file and verify the domain and then do change of address. Keep that website for few months then after you can remove it and sell the domain also.

 

[SEO Lady]

So what you are saying is what I said earlier in the thread:

1. On the old domain stop the 301 redirect to the new domain
2. Upload a version of the new website even though it's duplicate content
3. Whilst it's live upload the HTML verification file so it's in GWT
4. Do the change of address
5. After a while implement the 301 back

The client does not want to sell the domain.

 

[altonroot]

No! you don't need to stop the redirect. Even you don't need to put whole website. Just upload verification html file in root folder through FTP server. Just you need to host the website.
If you do stop the redirect it will add more confusion. Just put a PM with your contact detail if you want me to help.

 

[steved45]

Must place the 301 redirect to avoid duplicate content, and work on the new domain. Eventually, people will just go to the new domain.