Schema markup has been around for more than a decade now. Schema markup as we know is a systematic way of providing the relevant/extra information about the website, webpage, and the content of the webpage to the search engines which enables the crawlers to quickly understand the context of the page and increase the probability of the getting the page listed in the Search Engine Results Page or SERPs when a relevant search is made by the user.

The purpose of this blog is to understand the concept of graph schema and it’s benefits over the separate schemas that we write for the website. Before understanding the graph schema, it is important to explore, if you are new to the digital marketing about what Schema Markup is and what are the various types of schema markups. We have covered this topic in a blog series:

Any digital marketing consultant would be aware about the power of schema markup and what advantages they add to the website. For this blog, we will look into one particular schema type i.e. Graph Schema. Though technically not a schema itself, it is a method in which other schemas are written.

What is Graph Schema?

In context of schema markup and structured data, graph schema is a method of consolidating all the schema types on a web page in to one single block rather then adding each in a separate tag block. Graph schema is a systematic web or network of multiple schemas on a single web page with a goal to show relationship between other entities such as organization, service, website, webpage, and other. It helps search engines understand how different things on your site are related.

In a typical schema markup, you might have multiple schema types (such as Organization, LocalBusiness, Person, Product, etc.) written separately. When using a graph schema, these schemas are all placed into a single structure, allowing you to explicitly connect them using identifiers (@id) and properties (like parentOrganization, sameAs, etc.).

Example of a Graph Schema

Let’s say an organization i.e. Nimblechapps has a page of web app development company. Considering that I want to add Organization schema, Breadcrumb Schema, and Service schema on this page, with the separate schema approach, I would need to write all the three schema in separate tags and to establish a relation would be difficult but, with Graph Schema, it's much simpler to consolidate all the schema types into a single block of code and effectively establish a relation.

The relation we want to convey to Google is this:

Nimblechapps Pvt. Ltd. is a company which is owner by Keval Padia. It is located in Ahmedabad, Gujarat, India. It provides the service of web app development across the globe.


  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@graph": [
      {
        "@type": "Organization",
        "@id": "https://www.nimblechapps.com/#organization",
        "name": "Nimblechapps Pvt. Ltd.",
        "url": "https://www.nimblechapps.com",
        "logo": "https://www.nimblechapps.com/logo.png",
        "description": "Nimblechapps Pvt. Ltd. provides web app development services globally.",
        "address": {
          "@type": "PostalAddress",
          "streetAddress": "Ahmedabad",
          "addressLocality": "Ahmedabad",
          "addressRegion": "Gujarat",
          "addressCountry": "IN"
        },
        "founder": "Keval Padia",
        "contactPoint": {
          "@type": "ContactPoint",
          "contactType": "Customer Service",
          "telephone": "+91-1234567890",
          "email": "info@nimblechapps.com"
        },
        "sameAs": [
          "https://www.facebook.com/nimblechapps",
          "https://www.linkedin.com/company/nimblechapps"
        ]
      },
      {
        "@type": "Service",
        "@id": "https://www.nimblechapps.com/#webappdevelopment",
        "serviceType": "Web App Development",
        "provider": {
          "@id": "https://www.nimblechapps.com/#organization"
        },
        "areaServed": {
          "@type": "Place",
          "name": "Global"
        }
      },
      {
        "@type": "BreadcrumbList",
        "@id": "https://www.nimblechapps.com/#breadcrumb",
        "itemListElement": [
          {
            "@type": "ListItem",
            "position": 1,
            "name": "Home",
            "item": "https://www.nimblechapps.com"
          },
          {
            "@type": "ListItem",
            "position": 2,
            "name": "Service",
            "item": "https://www.nimblechapps.com/services"
          },
          {
            "@type": "ListItem",
            "position": 3,
            "name": "Web App Development Company",
            "item": "https://www.nimblechapps.com/web-app-development"
          }
        ]
      }
    ]
  }
  </script>

Explanation:

  • Organization: Represents Nimblechapps Pvt. Ltd., including the name, description, address, contact information, and the social media links.

  • Service: Specifies the Web App Development service, showing that it is provided by Nimblechapps Pvt. Ltd. and available globally.

  • BreadcrumbList: Defines the navigation path Home -> Service -> Web App Development Company

** Optimize your website with Schema Markup today. Get ranked on Google Search. **Contact us

Benefits of using Graph Schema in structured data

Graph schema offers a variety of benefits as compared to the separate schema blocks. Let’s look into some of the benefits which gives us an idea on a theoretical level.

  • Improved Clarity:** By including entities under a single graph schema, the search engines better understand about your business, products, and other elements and how they are related. This leads to more accurate and detailed search results. Example: You can link a LocalBusiness schema to a Person schema, showing that a specific person is the owner of the business.

  • More Efficient Crawling: Search engines can process the structured data more efficiently since everything is grouped together in one structure instead of scattered across multiple separate blocks. Example: You can combine Product, Offer, and Review schemas into one graph instead of writing them separately, reducing complexity.

  • Better SEO Opportunities: When search engines clearly understand the relationships between entities (like a local branch and the parent company), it increases the chances of enhanced rich results. Example: If you add a LocalBusiness with graph schema, you might get a more detailed business listing on the SERP, including opening hours, reviews, location, and even social media links.

  • Voice Search Compatibility: Graph schemas are especially useful for voice search and AI-based systems. These systems rely on structured data to fetch accurate answers, and clear relationships help provide the right information. Example: If someone asks, "Who is the CEO of X company?" or "What are the business hours of Y store?" structured data in graph form can provide the most accurate, relevant response.

  • Ideal for multi-location businesses: Graph schema is well-suited for complex entities and relationships that go beyond simple data types. It is ideal for businesses with multiple branches, events, services, and organizations that need to be connected in a meaningful way. Example: A parent company and its subsidiaries, or an event with multiple performers, venues, and dates, can be neatly organized within a graph schema.

  • Simple maintenance and scalability: With all the entities in a single structure, it’s easy to make changes to existing entities or add new schema types. As your business or content grows, you can scale your structured data without needing to add multiple separate schema blocks. Example: If you add new branches to your local business, you can quickly update the graph schema instead of creating individual schema blocks for each branch.

Important points to consider while adding a Graph Schema

When adding a graph schema to your website, there are several key points to consider to ensure it is implemented correctly and provides maximum SEO benefits.

  • If combining multiple schema types in one graph, choose types that logically relate to each other.

  • Avoid leaving essential fields empty. Incomplete data may cause search engines to ignore your structured data or display incorrect information.

  • Your graph schema should adhere to the guidelines from Schema.org. Check that the properties and data types used are valid and correspond to the chosen schema types.

  • The @id property is critical when linking different schema types in the graph. It uniquely identifies each entity within the schema, allowing connections between them.

  • Test graph schema using Google’s Rich Results Test and Schema Markup Validator. You can also use ClassySchema visualization tool to check the relationship visually with node and connector diagram.

  • Make sure to provide the full URL to the entity’s page when using the @id property.

  • Even though graph schema allows for complex relationships, try to keep it simple and avoid unnecessary complexity.

Comparing graph schema to separate schema for each type

We got to know graph schema and it’s intricacies better from the aforementioned points. Let’s now look into a comparison between a graph schema and the separate schema modules.

Parameter
Graph Schema
Separate Schema Module


**Definition**
A single structure using @graph that connects multiple schemas and entities together.
Individual schema types added separately without internal linking.


**Structure**
Multiple schema types bundled into one graph. Connections between entities are established via @id.
Each schema type is defined independently without internal connections.


**Data Redundancy**
Reduces redundancy by connecting related entities (e.g., linking services to an organization).
Can result in duplicate data entries across schemas as they are independent.



**Relationships**
Explicit relationships between entities (e.g., organization, person, service) are defined within the graph.
Relationships are not inherently established; each schema stands alone.

SEO Offers better performance as search engines can quickly interpret relationships between entities. Slightly slower in terms of performance as search engines need to piece together separate schemas.

Processing by Search Engines Preferred by search engines for understanding relationships between entities, leading to better structured data interpretation. Search engines must independently analyze each schema module and infer relationships.

Complexity in Implementation Higher complexity in initial setup due to linked entities and unique identifiers (@id). Easier to implement as each schema type is self-contained and independent.

Error Handling If there’s an error in the graph, it could impact multiple linked entities, making it harder to debug. Errors are isolated to individual schema types, making it easier to troubleshoot.

Rich Results Potential Higher chance of rich results, as relationships between services, organization, and products are better understood. May result in rich results but not as efficiently as graph schemas, since relationships aren't explicitly defined.

Google Search Understanding Google can quickly grasp the structure and connections, leading to faster and more accurate indexing. Google needs to analyze separate modules independently, which might take more time for comprehensive indexing.

Conclusion

Consolidating all the schema types within a single graph schema enables you to provide accurate and the right relationship information between the schema types. This can lead to enhanced rich results, improved crawling efficiency, and better indexing, ultimately increasing the chances of being featured in prominent positions on SERPs. Adding schema markup of any kind require an expert website development service. Leveraging graph schema not only enhances their SEO strategy but also ensures that their services, organizational structure, and other key information are presented more accurately and comprehensively to both search engines and users.