Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Multiple Local Schemas Per Page
-
I am working on a mid size restaurant groups site. The new site (in development) has a drop down of each of the locations. When you hover over a location in the drop down it shows the businesses info (NAP). Each of the location in the Nav list are using schema.org markup.
I think this would be confusing for search robots. Every page has 15 address schemas and individual restaurants pages NAP is at the below all the locations' schema/NAP in the DOM.
Have any of you dealt with multiple schemas per page or similar structure?
-
I help run a directory site and we have City pages with multiple listings. We don't mark up that page but we have a landing page for each location. The landing page for a location is what we markup that way.
If you look on sites like Yelp they do the same thing.
On the Dallas page there is no schema markup but
http://www.yelp.com/biz/eddie-vs-prime-seafood-dallas
If you visit a local restaurant then the schema markup shows up.
I was looking through the schema.org documentation
http://schema.org/docs/gs.html
Using the url property. Some web pages are about a specific item. For example, you may have a web page about a single person, which you could mark up using the Person item type. Other pages have a collection of items described on them. For example, your company site could have a page listing employees, with a link to a profile page for each person. For pages like this with a collection of items, you should mark up each item separately (in this case as a series of Persons) and add the url property to the link to the corresponding page for each item, like this:
_[itemprop="url">Alice Jones](alice.html) [itemprop="url">Bob Smith](bob.html)_So in the example on Schema, you can tag the location with the type and then use the URL parameter to point to the actual page that has the information.
I then looked at CitySearch I did see an example of this
http://dallas.citysearch.com/find/section/dallas/restaurants.html
and
http://dallas.citysearch.com/profile/34327220/lewisville_tx/mama_s_daughters_diner.html
If you look at the code on the Dallas Restaurant pages they use Item List markup
itemscopeitemtype="http://schema.org/ItemList">
That is a list of Breakfast Restaurants in Dallas and then for each place on that page they will mark up
itemtype="http://schema.org/LocalBusiness" itemprop="itemListElement">
and
itemscope itemtype="http://schema.org/AggregateRating" itemprop="aggregateRating">
and then they reference the URL to the location page (as suggested above in the schema.org documentation)
[Check with your developer, but it looks like if you define the list of locations first, the spiders can see that all of the locations are a part of that list (vs the page being dedicated to a single location) then when you have the link to the landing page for the location you can do the full markup.
Good luck!](http://dallas.citysearch.com/profile/41040743/dallas_tx/breadwinners_cafe_bakery.html)
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Explore more categories
-
Chat with the community about the Moz tools.
-
Discuss the SEO process with fellow marketers
-
Discuss industry events, jobs, and news!
-
Chat about tactics outside of SEO
-
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
-