Welcome to the Q&A Forum

Hi! Thanks! I completely understand. We would never want to prevent URLs on the client's domain from being crawled. That could clearly put our client's online presence at risk. However, we're more concerned with Google noticing the shopping cart's domain is pointing to every page of the client's website which could appear unnatural & potentially, put the client's site at risk. What we're hoping to achieve is preventing from Google crawling the third party URL on every page to avoid any penalization.

Sorry, I meant to respond to this days ago.  Started, but didn't finish and then it left my mind. It sounds to me like you want to place a Google map on your site to show the location of the business?  If this is correct, I wouldn't use KML nor KMZ.  I would just use a javascript point market that represents the one location using the Google Maps API.  You can see what I mean as I have several points on one site I'm finishing up at http://www.snoshield.com/contest/christmas2012 You can also show service area like this: http://www.kcdirt.com/contact Both of those maps use strictly JavaScript, there is no KML or KMZ on them.

It all depends - if you were to create 100 external links, each with a back-link that said "click here" and they all were linking to the same page, it takes on an unnatural feel and at that point, Google might cast an eye over what you are doing. Remember, Google looks for diversity in link pages and anchor text. They also look for links to (ideally) form a natural feel as part of content. Keep it realistic and you will be fine. Andy

I'm glad... Well, sort of anyway.  The reason I started digging around more was that I was thinking that would be a great product to put together if no-one was doing it.  Happy you have the solution you were looking for, but slightly disappointed that you didn't lead me to a great business opportunity!  

Hi Katie, I think you're referring to the "More +" button on the bottom left of the site? I think that's an OK implementation, but it would be a lot better if it was more obvious. Aside from the fact that the site takes forever to load (which is a much bigger issue), having to figure out to click that little button to get that big section of content isn't ideal - from a user experience standpoint I'd much prefer to see that content displayed normally and just require guests to scroll down to see it. But, the client wants what the client wants I suppose. Companies have been penalized for hiding content on a page - though the examples are malicious and obviously link-driven, unlike the content on the site you linked. SInce none of the content that is hidden is especially spammy, and they're not trying to squeeze in a bunch of keyword-rich links, I don't think it'd be an SEO issue. The text of that section is about 700 lines deep in the source code, however, which isn't ideal. If you can find a way to move that higher in the code I would do so. Take a look at this company's portfolio: http://www.whitestonemarketing.com/design.html They do a good job of integrating large photography for hospitality sites without making the site visitor have to click 'more' buttons. I much prefer the user experience on a site like http://www.victorianfarmhouse.com/ than on the one you linked.

Hi Bill, I wouldn't set a hard and fast rule to look solely at PageAuthority because it doesn't provide the big picture.  Instead, I would use it in conjunction with DomainAuthority so you can understand the authority/trust behind the referring domain and get some context for the link. That way you aren't ruling out "good" links because they have a low PA.  For example, I would rather have a PA=13,DA=100 link from Stanford.edu than a PA=56,DA=5 link from some random article directory. Does that make sense?