Larry -

In Pinterest, the little heart button is just like the Facebook "Like" icon.  (But they had to be different, so it's a heart, meaning you love it.  But not in the till-death-do-us-part way.)

Here's a link on how you can like other people's pins:

https://en.help.pinterest.com/entries/22980372-Pins-and-likes#like

From Pinterest:

What's a like?  (The Heart Shaped Thing)

Liking a pin adds the pin to your profile’s likes section rather than a specific board.

To like a pin, hover over the pin and click on the heart icon in the top right corner.

What's a pin?

A pin is an image or video you add to Pinterest that leads back to the site where it was found. You can pin anything you find on Pinterest or around the web.

Having lots and lots of people pin a product on your website, or an image or video on your page adds to it's social media profile, and should help with both consumer engagement and possibly rankings.

Hope this helps!

-- Jeff

Wow... that's not so ideal.  My guess is that all of those sites are sharing the same IP address, and the server's settings are such that if you hit the IP address with a forward slash (i.e.  http://00.00.00.00/domainname/) it's showing content.

My $0.02 is to find a new hosting company.... and one that gives each site it's own IP address instead of doing shared-level hosting with the same IP address in a name-based space.

Saijo-

Ideally, a sitemap has a list of all of the pages on a site in a flattened out structure, so that a search engine is able to view all of the pages quickly and easily.

Typically an eCommerce site will have a structure like this:

• Home Page
• About Page
• Other content pages
• Main Category Page (with pagination), lists sub-categories
     - Sub Category Page (with pagination), lists products (or perhaps another sub-category).
• Individual Product Pages

Best practice seems to be:

• Make sure that all of the content and individual pages on the site are on the sitemap.
• For any page with pagination, link to the "View All" version of the category page (or any page with pagination), where instead of listing 9, 25 or 50 items, it lists all of the information on the page.  That way you don't have to list the paginated pages in the sitemap.
  (Note: if you have thousands of items on one of these "view all" pages, this might not be a viable option because the page load time might be too long and/or contain too many links).

Hope this helps...

• Jeff

Neenor-

Google does quite a bit of work to keep pages that show "explicit" content from appearing, unless the end user is searching for adult content.  Lingerie images walk a fine line between safe content and one that won't show up during a normal search.  Based on what you've written, sounds like their site is more on the risque side of things...

The best way to see if your clients' site is affected is to turn Safe Search ON, and then see if their site will appear in search results.

Safe Search, according to Wikipedia (http://en.wikipedia.org/wiki/SafeSearch), is a feature that acts as an automated filter of pornography and potentially offensive content.

In a statement given to The Verge, a Google spokesperson said:

"We are not censoring any adult content, and want to show users exactly what they are looking for -- but we aim not to show sexually-explicit results unless a user is specifically searching for them. We use algorithms to select the most relevant results for a given query. If you're looking for adult content, you can find it without having to change the default setting -- you just may need to be more explicit in your query if your search terms are potentially ambiguous. The image search settings now work the same way as in web search."

David -

It looks like there are two main options for you:

Keep the same URL structure (option 1), and create category pages that are state-based / area-based, that then have a short description of each location in that geographic area, with a link to their location page.

This is typically how it might be done with an eCommerce site, where you'd have a parent category (i.e. shoes) and then a sub-category (i.e. running shoes).

The downside to this is that you risk having duplicate content on these category pages.

Option #2 would be my recommendation, because you are including the area / state information into the URL.

One company that does not do this well is Noodles & Company.  Their location URL looks like this:

http://www.noodles.com/locations/150/

... where "150" is a store ID in a database.  Easy to pull out of a database table.  Less helpful to the end user who doesn't know that store ID 150 = the one closest to them.

It would be much better to have it listed like:
http://www.noodles.com/locations/Colorado/Boulder/2602-Baseline/

You don't want to go much beyond 4 layers, but it's a better way of indicating to Google and other search engines the location tree.

Also, I'd highly recommend using a rich-data format for displaying the location information.

For example, on the Customer Paradigm site, we use the RDFa system for tagging the location properly:

Customer Paradigm

5353 Manhattan Circle

Suite 103

Boulder CO, 80303

303.473.4400

... and then Google doesn't have to guess what the location's address and phone number actually are.

Vadim -

There was a thread yesterday about Wistia vs. You Tube here: http://moz.com/community/q/wbf-videos-and-transcripts

… and they linked to this page about how video with Wistia vs. YouTube affects SEO: http://wistia.com/learning/advanced-seo-with-distilled

That said, you're correct that there's nothing stopping someone from using a video capture system to grab the images.

Perhaps a watermark on the video could help prevent this temptation?

I'm not a huge Vimeo expert, but I know that Wistia is what Moz uses...