Welcome to the Q&A Forum

Even with one location, checking every important review site for new reviews on a regular basis is time consuming. With multiple clients and multiple offices it's nearly impossible to keep on top of them. What is the best tool or option for alerting us to new reviews on sites like Google Places, Yelp, Yahoo Local, etc.

is it maybe that the new site is more 'vertical' than the old site? the old site, if you look at it, is horribly designed and architected but it does have many, many more Level 1 categories and less subcategory organization than our new site

thanks for reply!

answers:

1. Did you reuse the product descriptions, etc. from the old site on the new site.  In other words do you have a duplicate content problem between the domains?
   • the old site is not live, it is blocked by robots.txt file so there is no dup content issue
2. Have you done any promotion of the new site that will produce links, likes, tweets, etc?  If not, then that might be your problem.
   • no but we did 301 redirect over 12,000 old urls to new urls and made sure all the old urls with external links pointing to them were redirected as well. the site has alot of links to it, mainly to product pages so i feel we have all that link juice captured properly
3. Why have you not doe a 301 redirect of the old site to the new site?  If you do this correctly a lot of the rankings of the old site will be transferred to the new site.
   • yeah, we did this, huge project to do over 13,000 url redirects!

thanks sha!

Ryan; thanks so much for your help! i really really really appreciate it!

iis 6.0

the developer provided this as their solution, any ideas?

Here’s a basic overview:Using the Ionics Isapi Rewrite Filter available here:http://iirf.codeplex.com/The code should already be installed on the server, but needs to be set up for each site that is using it.In IIS right-click and select Properties and select the ISAPI Filters tab. Click the Add… button. Click the Browse… button and select the .dll (Default location is C:\Program Files\Ionic Shade\IIRF 2.1\IIRF.dll.) Enter a filter name (“ISAPI Filter” is fine) and click OK.Add an IIRF.ini file to the root of the website. The text file will contain something similar to this:§  remove index pages from URLs RedirectRule (.)/default.htm$ $1/ [I,R=301] RedirectRule (.)/default.aspx$ $1/ [I,R=301] RedirectRule (.)/index.aspx$ $1/ [I,R=301] RedirectRule (.)/index.htm$ $1/ [I,R=301] RedirectRule (.)/index.html$ $1/ [I,R=301] RedirectRule (.)/[Old URL]$ $1/[New URL] [I,R=301]§  force proper www. prefix on all requests RewriteCond %{HTTP_HOST} domain.com [I] RewriteRule /(.*) http://www.domain.com/$1 [R=301]§  RewriteLog c:\temp\iirfThe first block ensures that the default page will never have a page name at the end. It will just use the root or folder name ending with a slash. It also can be used to write Old URL to new URL.The second block forces www. to be added to the domain if it does not exist in the url.If you remove the ”#” from the beginning of the last line the filter will write out debug information to the provided location.And that in essence is how we set it up.

I have seen generally good reviews for http://www.textbroker.com. Does anyone here have personal experience with it?

We are considering using it for content creation for guest blogging for clients. As far as we have found, this is all within Google's acceptable webmaster guidelines.

In general, how much editing is required from an article provided by Text Broker?

Thanks!

We have an ecommerce client transitioning to a new platform. Due to the nature of the platform, all the pages will have different URLs. There are between 7000-8000 total pages on the website.

We wrote 301 redirects for all URLs which are showing inbound links. Unfortunately, automating this process is pretty difficult and hand writing URLs for 8000 links is unfeasible. Is it worth investing the time to 301 redirect all 8000 URLs, or are we safe with only doing those with inbound links?

One other option would be to implement a generic redirect for all the rest of the old URLs that sends them to the homepage. Would this be a good compromise?

Hey thanks. is there some tool or feature in google webmaster account that shows us info about the caching frequency?

also, we only set up 301's for 400 of the 8,000 urls. only those 400 hand external links to them. it would be a massive project to redirect all those other 7,600 urls. do we need to do that?

We are preparing for a major platform migration with an ecommerce client. The website is in the range of 7000 pages. During this migration, all URLs will change due to differences in the platform and improvements to the site structure. Unfortunately, they run on a Microsoft server, so doing 301 redirects also tends to be a painful process.

What can we do to minimize the initial dent this puts in the website traffic?

We are

• prepared to submit XML sitemaps to Google and Bing as soon as the new site is live.
• writing 301 redirects for all pages which have inbound links (this is tough to automate due to the URL structures).

In the long run, we expect the new platform, URL structure, and site architecture to be a huge improvement for our organic rankings. The client and we are worried about the transition period though!

Any tips or advice to help us through it?

Thanks!