Welcome to the Q&A Forum

site address? LOL.

yeah I see the same as you, but what I'm seeing is normal. I've seen it take weeks to update the actual page title in Google's index, etc. Did you get your info as to when it was last crawled from Webmaster Tools?

what search query are you googling when you see the wrong title

need the old and new page titles...

hey Chris - what is the page URL? I can search it on my end and see if its updated to the new title. Sometimes cache (even when cleared) can be pretty stubborn. You many not be seeing what everyone else is seeing.

Also let me know what the old and new page titles are...

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!

Is it better from an SEO perspective to have actual 301's in place for each page, as opposed to one for all?

Hi Jacob -- awesome, thanks so much for sending this. Just to clarify - I'm assuming that this is ONLY USABLE if the new file structure is in fact IDENTICAL, correct?

Hi Dave - each tool that you use to determine inbound links to your site is normally going to show you a different list of links. SEOmoz uses a crawler to index links in it's own index, just like Google does, and Yahoo does as well with their Site Explorer tool. The separate tools will not really ever produce the same list of links. They can be similar, but usually not the same. Usually the most important/heaviest weighted links show up across all tools, but some of the less important ones sometimes get indexed by one tool and not others.

Hi guys - I am getting ready to do a complete domain transfer from one domain to another completely different domain for a client due to a branding/name change. 2 things - first, I wanted to lay out a summary of my process and see if everyone agrees that its a good approach, and second, my client is using IIS, so I wanted to see if anyone out there knows a bulk tool that can be used to implement 301's on the hundreds of pages that the site contains? I have found the process to redirect each individual page, but over hundreds its a daunting task to look at.

The nice thing about the domain transfer is that it is going to be a literal 1:1 transfer, with the only things changing being the logo and the name mentions. Everything else is going to stay exactly the same, for the most part. I will use dummy domain names in the explanation to keep things easy to follow: www.old-domain.com and www.new-domain.com. The client's existing home page has a 5/10 GPR, so of course, transferring Mojo is very important.

The process:

1. Clean up existing site 404's, duplicate tags and titles, etc. (good time to clean house).
2. Create identical domain structure tree, changing all URL's (for instance) from www.old-domain.com/freestuff to www.newdomain.com/freestuff.
3. Push several pages to a dev environment to test (dev.new-domain.com). Also, replace all instances of old brand name (images and text) with new brand name.
4. Set up 301 redirects (here is where my IIS question comes in below). Each page will be set up to redirect to the new permanent destination with a 301. TEST a few.
5. Choose lowest traffic time of week (from analytics data) to make the transfer ALL AT ONCE, including pushing new content live to the server for www.new-domain.com and implementing the 301's. As opposed to moving over parts of the site in chunks, moving the site over in one swoop avoids potential duplicate content issues, since the content on the new domain is essentially exactly the same as the old domain. Of course, all of the steps so far would apply to the existing sub-domains as well, IE video.new-domain.com.
6. Check for errors and problems with resolution issues. Check again. Check again.
7. Write to (as many as possible) link partners and inform them of new domain and ask links to be switched (for existing links) and updated (for future links) to the new domain. Even though 301's will redirect link juice, the actual link to the new domain page without the redirect is preferred.
8. Track rank of targeted keywords, overall domain importance and GPR over time to ensure that you re-establish your Mojo quickly.
9. That's it!

Ok, so everyone, please give me your feedback on that process!!

Secondly, as you can see in the middle of that process, the "implement 301's" section seems easier said than done, especially when you are redirecting each page individually (would take days). So, the question here is, does anyone know of a way to implement bulk 301's for each individual page using IIS? From what I understand, in an Apache environment .htaccess can be used, but I really have not been able to find any info regarding how to do this in bulk using IIS. Any help here would be GREATLY APPRECIATED!!

Thanks EGOL - that's what I figured, but was hoping not to hear. I would have set it up with a custom domain originally myself, but I am taking this one over, so it was already set up with the other name originally.

Hi All - I am currently attempting to move a blog (companyname.blogspot.com) that has a 2/10 GPR to a custom domain name so that I can get my targeted keywords in the domain name. The new domain will just be www.targetedkeyword.com. There are easy instructions for doing this with the A record and CNAME changes in the Blogger help, but I am worried about losing rank and links if I do this. Can you guys help me understand what the ramifications would be, and how I can accomplish this without losing the 2/10 mojo? Thanks!