LocalBusiness Schema for Multiple Location Subpages

[ceeze]

Hi, if I have LocalBusiness schema for one location - let's say xyz.com/los-angeles - should its subpages (ex. xyz.com/los-angeles/car-accident-lawyer) use the same local business schema that point to that main location page's URL and ID?

 

[fisicx]

Each page needs it's own schema.

 

[keyserholiday]

Hi, if I have LocalBusiness schema for one location - let's say xyz.com/los-angeles - should its subpages (ex. xyz.com/los-angeles/car-accident-lawyer) use the same local business schema that point to that main location page's URL and ID?

Yes, each page can use the same local schema.

 

[GMBapi.com]

Yes, if those subpages (like /los-angeles/car-accident-lawyer) are part of the same physical business location, then it's totally valid—and recommended—to reuse the same LocalBusiness schema across them.
Here’s how to approach it:

• You can include the same @id (e.g. "@id": "https://xyz.com/los-angeles#localbusiness") to point back to your main location entity.
• This helps Google understand that all those service-specific pages belong to the same local business at that specific location.
• Just don’t repeat the full schema on every page if it’s not relevant—keep it lean, but consistent.

So yes, your /car-accident-lawyer page can absolutely reference the main location schema, as long as the content is tied to that physical office. That’s a good way to reinforce local relevance and build a clear entity structure.

 

[fisicx]

A bit of a conflict there!

Yes they all can have the same schema but they should be written for each topic. Google likes schema so the more detail you can provide the better.

For example:

xyz.com/los-angeles would have a schema for the location

https://schema.org/location

xyz.com/los-angeles/car-accident-lawyer would have a schema for the service in that location.

https://schema.org/Service

 

[Shihab]

Hi ceeze,
It should contain the service schema markup not the local business schema markup.

Thanks

 

[ceeze]

Thank you everyone for your replies. So, if I'm following GMBapi.com's advice correctly - I would have the LocalBusiness schema on the location main page and reference it on the location subpages through an id, but it shouldn't be an exact copy of the main location's schema?

My thought was that it could be the same LocalBusiness markup for the subpages as long as I used the correct id - which would correspond to the main location's URL since those subpages all correspond to the same local business and are not separate entities (would not self-reference the subpage URLs).

Fisicx and Shihab you're saying I should only have LocalBusiness schema on the location main page but not on the location subpages? and subpages should have service schema?

 

[fisicx]

It all depends on the content and purpose of the page. The schema should be tailored for each page.

The details are all listed in the schema specifications.

As another example, there is a schema specification for an about us page:

https://schema.org/AboutPage