Welcome to the Q&A Forum

We're using the Google snapshot method to index dynamic Ajax content.  Some of this content is from tables using pagination. The pagination is tracked with a var in the hash, something like: #!home/?view_3_page=1 We're seeing all sorts of calls from Google now with huge numbers for these URL variables that we are not generating with our snapshots.  Like this: #!home/?view_3_page=10099089 These aren't trivial since each snapshot represents a server load, so we'd like these vars to only represent what's returned by the snapshots. Is Google generating random numbers going fishing for content?  If so, is this something we can control or minimize?

We have a product that when started was under the domain appnowgo.com.  We've since changed the name and the domain is now knackhq.com.  The latter domain doesn't rank nearly as well as the former for many of the keywords we are targeting.   For example... "online database builder" and "web app builder" are two of those keywords.  Obviously having app in the domain is not a bad thing but it is our old name. The question is, should we 301 the appnowgo.com domain to knackhq.com?   Or should we use that better rank and just link users to knackhq.com from the appnowgo.com site until we can increase our ranking for knackhq.com?  We don't plan to update the content on appnowgo.com anymore and we obviously don't want to drop off rank if at all possible. Thanks! Eric