Hi Guys, I posted a question recently about "Can I have multiple areaServed mark up on one domain?" and the responses I got was no. My client work predominantly in the South East of England in specific towns, so I wanted to be able to list all the areas they service. However, after being told no, I went ahead anyway and put in multiple areaServed markup on the page to see if this generates any errors and it isn't when I run it through the Structured Data Testing Tool. I don't get any errors by doing this, so hurray! But... What I want to understand (which I can't find the answer anywhere), is if this is okay, and how will Google read my markup? Will Google see that we are in multiple areas across the SE of England and push my content up before other sites, or is this just going to confused Google? By putting in all these areas into the website as multiple locations, will Google identify that person X in area Y fits the areaServed mark up I've added and push my content to them? Overall... has anyone else used multiple areaServed markup and can validate that this works? hHpEyQf

Hello, I work exclusively with Dentists and we have been putting our json schema in the footer for a while now. Just recently they made 'image' a requirement for the Dentist category. We already use the logo in our schema and that is an image. Since the schema is in the footer, it is on every page, and the only image on every page is the logo. Does the image we add to our schema need to be on the actual web page or could it be anything related to the business, like an image of the practice or the dentist? Would it hurt to have the logo listed twice in the schema - once as the logo and once as the image? Trying to figure out what the best thing to do is for the required 'image' field for a dentist. Thanks! Angela

Google has this page on location pages. It's very useful but it doesn't say anything about handling the duplicate content a location page might have. Seeing as the loctions may have very similar services. Lets say they have example.com/location/boston, example.com/location/chicago, or maybe boston.example.com or chicago.example.com etc. They are landing pages for each location, housing that locations contact information as well as serving as a landing page for that location. Showing the same services/products as every other location. This information may also live on the main domains homepage or services page as well. My initial reaction agrees with this article: http://moz.com/blog/local-landing-pages-guide - but I'm really asking what does Google expect? Does this location pages guide from Google tell us we don't really have to make sure each of those location pages are unique? Sometimes creating "unique" location pages feels like you're creating **doorway pages - **"Multiple pages on your site with similar content designed to rank for specific queries like city or state names". In a nutshell, Google's Guidelines seem to have a conflict on this topic: Location Pages: "Have each location's or branch's information accessible on separate webpages"
Doorway Pages: "Multiple pages on your site with similar content designed to rank for specific queries like city or state names"
Duplicate Content: "If you have many pages that are similar, consider expanding each page or consolidating the pages into one." Now you could avoid making it a doorway page or a duplicate content page if you just put the location information on a page. Each page would then have a unique address, phone number, email, contact name, etc. But then the page would technically be in violation of this page: Thin Pages: "One of the most important steps in improving your site's ranking in Google search results is to ensure that it contains plenty of rich information that includes relevant keywords, used appropriately, that indicate the subject matter of your content." ...starting to feel like I'm in a Google Guidelines Paradox! Do you think this guide from Google means that duplicate content on these pages is acceptable as long as you use that markup? Or do you have another opinion?

I'm starting to use schema on a site currently working on the business address in the footer.  What is the correct way to use data that has more than one line? So for example the address is something like "Unit 1, Some Farm, Some Street..." Unit 1, Some Farm Some Street or Unit 1, Some Farm
Some Street

I would like to get some opinions on the best way to handle duplicate / similar content that is on our company website and local facility level sites.  Our company website is our flagship website that contains all of our service offerings, and we use this site to complete nationally for our SEO efforts.  We then have around 100 localized facility level sites for the different locations we operate that we use to rank for local SEO.  There is enough of a difference between these locations that it was decided (long ago before me) that there would be a separate website for each.  There is however, much duplicate content across all these sites due to the service offerings being roughly the same.  Every website has it's own unique domain name, but I believe they are all on the same C-block.  I'm thinking of going with 1 of 2 options and wanted to get some opinions on which would be best. 1 - Keep the services content identical across the company website and all facility sites, and use the rel=canonical tag on all the facility sites to reference the company website.  My only concern here is if this would drastically hurt local SEO for the facility sites. 2 - Create two unique sets of services content.  Use one set on the company website.  And use the second set on the facility sites, and either live with the duplicate content or try and sprinkle in enough local geographic content to create some differential between the facility sites. Or if there are other suggestions on a better way to handle this, I would love to hear any other thoughts as well. Thanks!