Update for Thursday, April 12, 2012 (9:00 AM EST)
We have been working very hard over the last week to implement 10's of thousands of dollars worth of upgrades to our Keyword Blaze Pro infrastructure. I'm happy to report, that this effort has been completed. I've been working with it this morning, and the performance is better than it has EVER been. We're very pleased with how it has turned out. My only wish is that it had come sooner.
Some things to note:
1. The new improvements have come about with a compete restructuring of our servers. Consequently, there are DNS changes (this is what controls where you go when you type in a web site url into a browser) that need to propagate throughout the whole internet. Normally, this happens pretty quickly (it was fine for me this AM) but there are certainly going to be users where it may take up to 24 hours (this should be very rare). If you are getting the message about performance and try again later, this is the culprit. PLEASE…just wait a little bit before sending in a support ticket. Unfortunately, we simply have NO control over this at all.
2. If you do have any issues, PLEASE PLEASE submit a support ticket. We can't respond to forum posts for technical support. The support desk is at support.blueprintcentral.com
3. Google has changed their "insight" interface , so that data will temporarily be unavailable when looking at keyword detail data. We anticipate that being resolved by end of day.
4. With rank tracker, please note that it counts "google shopping results" as positions. So, what may appear to be position 3 (web site one, 3 entries for shopping, your web site)…that will show up as position 5 in rank tracker.
Once again, I want to thank everyone for their patience. We were knocked down here (really for the first time in our IM careers) but the result is a much more exciting and robust environment for Keyword Blaze Pro…so in the end, it will be worth the pain.
We'll be in touch shortly with other news and a report on how things are going as we'll be monitoring error rates VERY closely.




Reply With Quote



