In the footer of all pages we have listed his address, he has 2 offices which we added in schema format. But Im not sure if this will confuse Google having both on all pages and whether I have added it right for multiple addresses?

Member

thanks for your reply, on contact page we didnt use schema markup, so you think keep contact page as it is, remove schema from the footer on all pages, and just add schema on an actual individual location page?

Member

Hi RFK. I would assume that one of those locations would be considered their "main" location, so the other location could be considered one of their branches. If that's the case, you could always use the "branchOf" property to specify the difference between the two locations.

Member

Member

Hi RFK. I would assume that one of those locations would be considered their "main" location, so the other location could be considered one of their branches. If that's the case, you could always use the "branchOf" property to specify the difference between the two locations.

Member

Well, I've never been a big proponent of marking up the address on every single page of a website, simply because it seems like overkill. The exception to that would be if you were marking up different pages that highlight a different product or service that the business offers. In that case, you would also want to mark up who is offering the service and where they are located. It won't hurt to have the addresses marked up in the footer, but it won't necessarily help much either.

But since that's how everything is currently formatted, you can just leave it as it is. So I would recommend that you mark up the main office location with either schema.org/Organization or schema.org/LocalBusiness and the sales office with the "branchOf" property. But because of the way that schema.org has things set up, you will have to essentially mark them up inversely, like this:

Schema also has a "hasPOS" (has points-of-sales) property, which is also an option here, but I think that the branchOf property with the LocalBusiness schema type would be more appropriate in this case.

Member

Looks better. But I did notice that the phone number is not nested within either location schema, so that's something important that you really should fix. And you can use the LocalBusiness schema type for both locations. You don't have to use the Organization type for one, because LocalBusiness is actually an extension of Organization.

Member

Hi Callmenicholi. Well, since you have two locations, one really should to be the parent and the other should be the subOrganization. And when you mark them up, you do need to include all of the information about both locations including the name, address, etc.

So in your case since there are only two locations, you would only need one block of markup, specifying which is the parent and then nesting the info about the subOrganization.

Member

Looks pretty good Nicholas, from what I could see after taking a quick peek. Although one thing I should mention is that "price range" is usually displayed as $, $$, $$$, and $$$$. This guide might help you to decide which value to use: The New York Times Restaurant Key: Ratings