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.
Listing multiple schema Things (e.g. Organization, LocalBusiness, Telephone, Locations, Place, etc)
-
Greetings All,
My law office features many pages with what are essentially directory listings (names, addresses, and phone numbers of places, agencies, organizations that clients might find helpful).
Am I correct in assuming that using schema for each of these listings might cause confusion for search engines? In other words, are search engines looking for schema on pages or sites to tell them only about the company running that page or site, or do search engines appreciate schema markup to tell them about all the pieces of content on the pages or that site?
-
Everett,
Thank you. Very much appreciate the detail. Will definitely check out JSON-LD.
-
Hello Micromano,
See this thread on Stack Exchange. You can mark up your organization, as well as any organization (or other "entity") that you describe / discuss on your website. Marking up an organization doesn't mean you are necessarily affiliated with them UNLESS you use the "SameAs" tag to connect that data with your own website, wiki page or social profiles...
Also, you may want to look into using JSON-LD instead. You would still base it on the Schema.org hierarchies, but the code is slightly different. The cool thing about JSON is that you don't have to show all of the data you're marking up. It can just be in the source code and not visible on the page, similar to meta descriptions as far as that aspect goes.
Here's what I would do.
1. Put Organization Schema for YOUR business (or your client's) in the HTML header of EVERY page using JSON-LD. Here's a generator I like. Also check out the JSON-LD Playground for testing your code. Don't forget the SameAs tags pointing to other sites/pages that you can verify as "official". This includes Wikipedia pages, Wiki Data pages and social profiles.2. Also surround information about YOUR business (logo, NAP...) with traditional Schema.org Organization markup.
3. Use traditional Schema.org Organization markup for the business listings, and include a SameAs tag around a link to their official websites.
Here's a good Stack Overflow thread to check out: Mixing Together Schemas.
-
Thanks for all the responses! Much appreciated.
-
In general schema.org markup helps search engines understand the content within the context better. So when you makup data it helps SE's understand you pages better. I would go for the schema.org markup in json-ld to be flexible in how the you show the marked-up data in your content. So to answer your question I would go ahead and mark-it-up (but make sure you do it the right way). Good luck.
-
No, it won't create any confusion for SEs if you are using the schema in proper manner like mentioned here, as per my opinion Structured data is a great idea to display your business in SEs, and it is definitely appreciated by SEs. This is also a good article about Schema https://blog.kissmetrics.com/get-started-using-schema/
Hope it helps
-
I've been wondering about this too. I may be wrong, but I feel as if it's contextual. For example, on many event listing websites they use event schema. Which will mark up the event details as well as the organiser details. This uses schema for the organiser and venue's business addresses, phone numbers and website, etc. This is the correct way of marking up events and the rich snippets display correctly on Google. As long as the NAP is under Organization or whatever (which lists the business' name) and you make it clear that it isn't your organisation, I assume it's fine.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Can I use Schema zip code markup that includes multiple zip codes but no actual address?
The company doesn't have physical locations but offers services in multiple cities and states across the US. We want to develop a better hyperlocal SEO strategy and implement schema but the only address information available is zip codes, names of cities and state. Can we omit the actual street address in the formatting but add multiple zipcodes?
Local Website Optimization | | hristina-m0 -
Service Area Location Pages vs. User Experience
I'm familiar with the SAB best practices outlined here. Here's my issue: Doing local landing pages as described here might not be ideal from a user experience point of view. Having a "Cities We Serve" or "Service Areas" link in the main navigation isn't necessarily valuable to the user when the city-specific landing pages are all places within a 15-mile radius of the SAB's headquarters. It would just look like the company did it for SEO. It wouldn't look natural. Seriously, it feels like best practices are totally at odds with user experience here. If I absolutely must create location pages for 10 or so municipalities within my client's service area, I'd rather NOT put the service areas as a primary navigation item. It is not useful to the user. Anyone who sees that the company provides services in the [name of city] metropolitan area will already understand that the company can service their town that is 5 miles away. It is self-evident. For example**, who would wonder whether a plumbing company with a Los Angeles address also services Beverly Hills?** It's just... silly. But the Moz guide says I've got to do those location pages! And that I've got to put them high up in the navigation! This is a problem because we've got to do local SEO, but we also have to provide an ideal experience. Thoughts?
Local Website Optimization | | Greenery1 -
Applying NAP Local Schema Markup to a Virtual Location: spamming or not?
I have a client that has multiple virtual locations to show website visitors where they provide delivery services. These are individual pages that include unique phone numbers, zip codes, city & state. However there is no address (this is just a service area). We wanted to apply schematic markup to these landing pages. Our development team successfully applied schema to the phone, state, city, etc. However for just the address property they said VIRTUAL LOCATION. This checked out fine on the Google structured data testing tool. Our question is this; can just having VIRTUAL LOCATION for the address property be construed as spamming? This landing page is providing pertinent information for the end user. However since there is no brick and mortar address I'm trying to determine if having VIRTUAL LOCATION as the value could be frowned upon by Google. Any insight would be very helpful. Thanks
Local Website Optimization | | RosemaryB1 -
Location Pages and Duplicate Content and Doorway Pages, Oh My!
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"
Local Website Optimization | | eyeflow
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?0 -
Schema - Street Address
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
Local Website Optimization | | MickEdwards
Some Street0 -
Duplicate content question for multiple sites under one brand
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!
Local Website Optimization | | KHCreative0 -
Local Business Schema Markup on every page?
Hello, I have two questions..if someone could shed some light on the topic, I would be so very grateful! 1. I am still making my way through how schema is employed, and as I can tell, it is much more specific (and therefore relevant) in its details than using the data highlighter tool. Is this true? 2. Most of my clients' sites have a footer with the local business info included on every page of their site (address and phone). This said, I have been using the structured data markup helper to add local business schema to home page, and then including the footer markup in the footer file so that every page benefits from the local business markup. Is this incorrect to use it for every page? Also, I noticed that by just using the footer markup for the rest of the pages in the site, I am missing data that was included when I manually went through the index page (i.e. image, url, name of business). Could someone tell me if it is advisable and worth it to manually markup every page for the local business schema or if that should just be used for certain pages such as location, contact us, and/or index? Any tips or help would be greatly appreciated!!! Thanks
Local Website Optimization | | lfrazer0 -
Single Site For Multiple Locations Or Multiple Sites?
Hi, Sorry if this rambles on. There's a few details that kind of convolute this issue so I'll try and be as clear as possible. The site in question has been online for roughly 5 years. It's established with many local citations, does well in local SERPs (working on organic results currently), and represents a business with 2 locations in the same county. The domain is structured as location1brandname.com. The site was recently upgraded from a 6-10 page static HTML site with loads of duplicate content and poor structure to a nice, clean WordPress layout. Again, Google is cool with it, everything was 301'd properly, and our rankings haven't dropped (some have improved). Here's the tricky part: To properly optimize this site for our second location, I am basically building a second website within the original, but customized for our second location. It will be location1brandname.com/secondcity and the menu will be unique to second-city service pages, unique NAP on footer, etc. I will then update our local citations with this new URL and hopefully we'll start appearing higher in local SERPs for the second-city keywords that our main URL isn't currently optimized for. The issue I have is that our root domain has our first city location in the domain and that this might have some negative effect on ranking for the second URL. Conversely, starting on a brand new domain (secondcitybrandname.com) requires building an entire new site and being brand new. My hunch is that we'll be fine making root.com/secondcity that locations homepage and starting a new domain, while cleaner and compeltely separate from our other location, is too much work for not enough benefit. It seems like if they're the same company/brand, they should be on the same sitee. and we can use the root juice to help. Thoughts?
Local Website Optimization | | kirmeliux0