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.
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
-
Should I wrap schema in the footer or within the body of the text?
-
Thanks Wesley.
-
Schema.org is a quite extensive vocabulary for implementing structured date. The data highlighter tool only offers limited options for implementing structured data information about your content to the search engines.
So, yes i would recommend schema.org because it is more specific.
If you think my original response was helpful could you mark it as the correct answer to close this question?
-
Awesome. Thank you! So, just to clarify, in your opinion, it is better to use schema for Google than the data highlighter tool because it is more specific?
Thanks so much again
-
Hello Denis,
To your first question: Schema.org is indeed much more specific than Google's data highlighter tool.
To your second questions: If the client has a footer with their contact details and address location than this would be a good place to use the schema markup and then it would be included on every page.You're talking about 'manually marking up every page'. If the contact information is in the footer this would only have to be marked up once? Don't really understand that part of the question.
**Conclusion: **It's not necessary to mark up local business information on every page, but if the client has the local business information on every page because it's useful for their users than this is a perfect opportunity to mark it up with schema information.
Hope i was of assistance and if you have any other questions please let me know
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
-
SEO Best Practice for Managing a Businesses NAP with Multiple Addresses
I have a client with multiple business addresses - 3 across 3 states, from an SEO perspective what would be the best approach for displaying a NAP on the website? So far I've read that its best: to get 3 GMB account to point to 3 location pages & use a local phone number as opposed to a 1300 number. Display all 3 locations in the footer, run of site
Local Website Optimization | | jasongmcmahon1 -
Local Business Schema Image requirement
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
Local Website Optimization | | tntdental0 -
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 -
301 or 302 Redirects with locale URLs?
Hi Mozers, I have a bit of a tricky question I need some help answering. My agency are building a brand new website for a client of ours which means changing the domain name (yay...). So! I have my 301's all ready to go for the UK locale, however, the issue I have is that the site will also eventually have French, German and Spanish locales - but these won't be ready to go until later this year. We will be launching in just English for September. The current site already has the French and German locales on it as well. Just to make sure I'm being clear, the site will be www.example.com for launch, but by lets say November, we will also have a www.example.com/fr/ and www.example.com/de/ site launched too. So what do I do with the locale URLs? As I said above, the exisitng site already has the French and German locales on it, so I don't particularly want to redirect the /fr/ and /de/ URLs to the English homepage, as I will want to redirect them to the new URLs in November, and redirecting more than once is bad for SEO right? Any ideas? Would 302s maybe be the best suggestion? Thanks! Virginia
Local Website Optimization | | Virginia-Girtz1 -
Local Service pages guide?
There are a lots of Local landing pages guide on the internet. Is there any guide for Local service pages? How to create them, what to include?
Local Website Optimization | | Michael.Leonard0 -
Call Tracking, DNI Script & Local SEO
Hi Moz! I've been reading about this a lot more lately - and it doesn't seem like there's exactly a method that Google (or other search engines) would consider to be "best practices". The closest I've come to getting some clarity are these Blumenthals articles - http://blumenthals.com/blog/2013/05/14/a-guide-to-call-tracking-and-local/ & the follow-up piece from CallRail - http://blumenthals.com/blog/2014/11/25/guide-to-using-call-tracking-for-local-search/. Assuming a similar goal of using an existing phone number with a solid foundation in the local search ecosystem, and to create the ability to track how many calls are coming organically (not PPC or other paid platform) to the business directly from the website for an average SMB. For now, let's also assume we're also not interested in screening the calls, or evaluating customer interaction with the staff - I would love to hear from anyone who has implemented the DNI call tracking info for a website. Were there negative effects on Local SEO? Did the value of the information (# of calls/month) outweigh any local search conflicts? If I was deploying this today, it seems like the blueprint for including DNI script, while mitigating risk for losing local search visibility might go something like this: Hire reputable call-tracking service, ensure DNI will match geographic area-code & be "clean" numbers Insert DNI script on key pages on site Maintain original phone number (non-DNI) on footer, within Schema & on Contact page of the site ?? Profit Ok, those last 2 bullet points aren't as important, but I would be curious where other marketers land on this issue, as I think there's not a general consensus at this point. Thanks everyone!
Local Website Optimization | | Etna1 -
Is it worth it having different cities in your footer, each with a separate page?
I have been looking at the website of local web design companies and every single one in my area has a footer with links to a separate page for that local city. This seems like a bad idea to me, but everyone in the local pack has it. Does it work?
Local Website Optimization | | EcommerceSite0 -
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