Local Schema Mark Up for Multi-Locations Questions

AMBS

Member
Joined
Apr 21, 2016
Messages
1
Hi guys, I wasn't sure where to ask this question. But Organic SEO seemed like the logical place.

I've implemented Local Schema mark up for a couple of clients.
I used Google Tag Manager to do this.
The information I marked up was in their site wide footer.

They have 3 addresses in their footer, but they also have a couple of location specific pages too.

Is it okay to mark up everything in the footer and apply to ALL PAGES in Google Tag Manager?

Or should I only be marking up their specific location pages?

I've read loads of articles on this and keep finding a lot of unclear on contradictory information as soon as there is more than 1 business address.

Please tell me how I should be handling this.
 

Linda Buquet

Moderator
Joined
Jun 28, 2012
Messages
14,436
Hi guys, I wasn't sure where to ask this question. But Organic SEO seemed like the logical place.
Hi AMBS, thanks for asking a great Q.

Often there is more that one place a post fits. Lots know about schema and those Qs should be in organic, you are right. But I think multi-location is the crux of the matter so I moved to that forum and added that word to title, because it requires more specific knowledge from those that have been there/done that. :p

Here in this multi-location forum you'll find some answers. There are a couple posts that directly answer I'll try to dig up after a hand break.

In meantime anyone else want to chime in?
 
Joined
Oct 25, 2013
Messages
770
Hi AMBS,

Linda will definitely be able to pull together more comprehensive stuff than this, but this thread from a month ago might be a good place to start.

Miriam has some great stuff there, both in the original article I linked to at the top of the thread, and in her response down below.

The basic tl;dr... I personally like to keep everything separate for the most part, unless there's really strong usability reasons to have all locations on some (or all) of the pages. Regardless of my own preferences though, I haven't heard anyone comment about running into issues with the current version of the Google local algorithm from having more than one location's NAP on a given page. Sounds like at this point, it's kind of optional.

I don't have any proof that this helps with rankings, but when it comes to individual location landing pages that are only about one of the locations, I'd only use the schema for that one location just to avoid diluting the signal you're giving Google about what that page is actually about. Since you're presumably linking the GMB profile to those individual facility landing pages, having really clear signals on those specific pages is pretty important in my view.
 
Joined
Mar 27, 2015
Messages
35
I use JSON-LD for all my multi locations. Each location should have the below
1. Own Locations Page
2. Own JSON-LD script
3. NAP
4. BIO
5. Map
6. Call to Action
7. Make sure u have call tracking, conversion tracking setup us GA.


<script type="application/ld+json">
{
"@context": "http:\/\/schema.org\/",
"@type": "ContactPage",
"about": "Page Name",
"url": "URL of Page",
"keywords": ["Locations", "Contact Page", "other"],
"sameAs": ["facebook", "Google+", "tiwtter"],
"specialty": "Recruiting",
"publisher": "Business Name ",
"locationCreated": [{
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Kirkland",
"addressRegion": "WA",
"streetAddress": "11111 Carillon Point",
"postalCode": "1111"
},
"name": "Business Name",
"parentOrganization": "Other Name",
"telephone": "111-111-1111"
}, {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Flaurida",
"addressRegion": "FL",
"streetAddress": "6750 N. Andrews Avenue, Suite 2003 Fort Lauderdale",
"postalCode":"1111"
},
"name": "Business Nam",
"telephone": "111-111-1111"
}, {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Fargo",
"addressRegion": "ND",
"streetAddress": "1111 42nd St S.",
"postalCode":"11111"
},
"name": "XTREME FARGO",
"telephone": "111-111-1111"
}, {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Dallas",
"addressRegion": "TX",
"streetAddress": "2222 N. Market Street",
"postalCode":"11111"
},
"name": "Business Name",
"telephone": "111-111-1111"
}, {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Redmond",
"addressRegion": "WA",
"streetAddress": "8888 111th Ave NE",
"postalCode":"1111"
},
"name": "Business Name",
"telephone": "111-111-1111"
}, {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Portland",
"addressRegion": "OR",
"streetAddress": "5555 SW Barnes Rd., Suite 450",
"postalCode": "9999"
},
"name": "Business Name",
"telephone": "111-111-1111"
}, {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Mountain View",
"addressRegion": "CA",
"streetAddress": "000 W El Camino Real, Suite 000",
"postalCode":"99999"
},
"name": "Business Name",
"telephone": "222-222-2222"
},
{
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Phoenix",
"addressRegion": "AZ",
"streetAddress": "3333 E Camelback Rd., #000",
"postalCode": "9999"
},
"name": "Business Name",
"telephone": "222-222-2222"
}
}
</script>
 

Local Search Forum


Weekly Digest
Subscribe/Unsubscribe


Google Product Exert

@LocalSearchLink

Join Our Facebook Group

Top