Nested schema means connected data items. Instead of adding separate bits of structured data for a business, its services, and its locations, we connect those items so their relationships are clear.
That is the whole idea. We are not trying to fit more markup onto a page. We are trying to explain what the page is about and how each supporting detail fits.
For local SEO, this matters because one page can describe several related things. We might have a business, a parent company, a logo, a service, and a service area. The goal is to make those pieces work together, not leave them as separate islands.
What Nested Schema Actually Means
Schema markup is structured data that helps search engines read the meaning of a page. It names the things on that page and describes them using known types and properties.
A type tells us what something is. For example, it might be a WebPage, LocalBusiness, or Service. A property helps describe that thing or link it to something else.
When we talk about nested schema, we mean that those items are linked within a shared structure. Our preferred setup brings them together in one JSON-LD code block, with clear relationships between them.
One block can contain several types. We do not have to choose between describing the webpage and describing the business. We can describe both while showing how they relate.
The connection is what matters. Simply placing several unrelated items inside one block does not explain their roles. We need the properties and references to connect them into a clear schema graph.
Why Disconnected Schema Gets Messy
We often find pages with several separate schema items. There might be one for the organization, another for the local business, another for a service, and another for breadcrumbs.
Sometimes there are even two separate LocalBusiness items on the same page. They may describe the same business in different ways.
That creates an avoidable problem. Instead of giving search engines one clear explanation, we give them several pieces and leave the links between those pieces unclear.
The questions we should ask are simple:
- Which item describes the main subject of this page?
- Which business provides the service?
- Does the organization belong to a parent company?
- Which areas does the business serve?
- Do repeated business items agree with each other?
Disconnected or duplicate markup can make those answers less clear. The issue is not that a page mentions several things. Most pages do. The issue is that we have not explained how those things fit together.
Our approach is to clean up that structure and make the page’s main subject clear.
Got SEO Questions? Get answers every week at 4pm ET at Hump Day Hangouts. Ask questions ahead of time, or live – just go to: https://semanticmastery.com/hdho (bookmark this!) 10+ years of insights given every week!
Get your checklist to help get better results with GBPs, faster.
Need DFY services for you Local SEO projects? Head over to Semantic Links.
Start With the Purpose of the Page
Before we choose schema types, we need to ask what the page is meant to describe.
A homepage, a service page, and a location page have different jobs. Their markup should reflect those jobs rather than repeat the same set of unrelated items everywhere.
We can use a simple planning process:
- Identify the main subject of the page.
- Choose a suitable schema type for that subject.
- List the supporting entities the page describes.
- Connect those entities through the right properties.
This keeps the work focused. We are building a useful description of the page, not collecting schema types just because they are available.
How We Connect Schema on a Business Homepage
Consider a tree service homepage. In our example, the main business uses HomeAndConstructionBusiness, a more specific type within the LocalBusiness family.
That business item connects to other details, including:
- A parent organization described as a Corporation.
- The business logo.
- Business credentials.
- The areas the business serves.
These are not loose pieces with no clear link to the business. They sit within the connected structure and help describe it.
For example, the parentOrganization property explains the link between the local business and its parent company. The logo belongs to the business being described. The service area tells us where that business works.
We can still use several schema types. The difference is that each type has a clear place. We are describing one connected business setup rather than several separate subjects that happen to appear on the same page.
How We Structure Schema for a Service Page
Now consider a tree trimming page. This page has a more specific purpose than the homepage. Its main subject is the tree trimming service.
We can start with WebPage and use its mainEntity property to connect a Service item.
That gives us a clear relationship: this is a webpage, and the main thing it describes is a service.
We do not need a separate, disconnected Service item sitting beside the WebPage item. We connect the service within the page’s structure, then connect the relevant business information.
The distinction is small but important. The WebPage type describes the page itself. The Service type describes what that page is mainly about.
We should also choose relationship properties based on the types involved. Properties such as mainEntity and mainEntityOfPage serve related purposes, but we should not treat them as labels to swap at random.
How Location Pages Fit Into the Graph
A location page needs to explain the link between a place, a business, and the services offered there.
In our location-page example, the connected structure starts with WebPage. It links the page to the website and includes information about the local business, its service catalog, and its service areas.
Properties such as about, mentions, and areaServed help describe those relationships.
A service catalog can identify the services available in that area. The business information explains who offers them. The area information explains where they are available.
Again, the goal is not to place a business item, a service list, and a location item beside one another and stop there. We want the structure to show why those items belong together on this particular page.
How We Check an Existing Schema Setup
The easiest starting point is the Schema Markup Validator. We enter a page URL, run the check, and review the detected items.
We can begin with the homepage, then check a service page and a location page. This gives us a useful look at how the main page types are structured.
During that review, we look for:
- Disconnected items: Are related entities linked?
- Duplicate business markup: Are we describing the same business more than once without a clear reason?
- Conflicting details: Do repeated items describe the business differently?
- A clear main subject: Can we tell what the page is mainly about?
- Useful connections: Do services, business details, and service areas fit together?
We should inspect the relationships, not just count the types. Several types can belong in a clean, connected structure.
Keep the Structure Clear
Nested schema is not about making structured data more complex. It is about making the meaning easier to follow.
We identify the main subject, connect the supporting items, and remove duplicate or conflicting descriptions. Whether we are working on a homepage, a service page, or a location page, the same rule guides us: make the relationships clear.

