Welcome to the Q&A Forum

Thank you both, that's great info to have. Patience is always a virtue when it comes to Google, right?

We have a Google+ business page @ <cite>https://plus.google.com/105699067779457680386</cite> (therefore the managers of that page log in with their personal Google accounts to use Google+ as the business page). We had/have a Google Places listing tied to our company Google account, and that does show up in Google+ Local.

I simply would like to marry the two so they can live together in perfect harmony. But that does not seem straightforward at all.

If I'm logged in with our company Google account, I am asked to "join" Google+, but I don't want our company to be a "person" on Google Plus (just a Business Page).

If I'm logged in with my personal Google account, and switch to using Google+ as our business page, and then click to claim/edit our Google+ Local listing, that doesn't work because I'm not logged in under our corporate Google account.

It's an Internet mystery. Mozzers, assemble!

Howdy.

So I'm working on "example.com", which has thousands of URLs. The site is going to be redesigned, with some changes to the information architecture.

I'm trying to think of a good way to organize and account for similarities and differences between the original information architecture and the new one. This should help with building 301s.

I've downloaded a list of URLs from example.com from Open Site Explorer. What I would love to do is generate a visual "tree" of the site based on the output from Open Site Explorer. It would basically look like a pyramid with all of the subfolders branching out.

Does anybody know of a tool out there that will do this for me? Or am I going to have a long day in Excel?

Any other thoughts on working through this process are welcome.

Thank you!

Thank you Alan. Are you suggesting that via DNS records I have DomainA.com "live" in the same place as DomainB.com, and then host the .htaccess on DomainB.com's hosting space?

So somebody requests DomainA.com, the DNS points to the hosting for DomainB.com, and then the .htaccess for DomainB.com can process the original DomainA.com request?

Thanks, but does this help with 301s for inner pages?

Thank you. I'm actually not understanding. How do I Park A on B. What is "explicit .htaccess"?

Howdy.

I have just read this QA thread, so I think I have my answer. But I'm going to ask anyway!

Basically DomainA.com is being retired, and DomainB.com is going to be launched.

We're going to have to redirect numerous URLs from DomainA.com to DomainB.com. I think the way to go about this is to continue paying for hosting for DomainA.com, serving a .htaccess from that hosting account, and then hosting DomainB.com separately.

Anybody know of a way to avoid paying for hosting a .htaccess file on DomainA.com?

Thanks!