Global Schema Basics
Overview
Global schemas allow you to tag a piece of schema data as “global,” meaning once it’s saved, you can reuse it across any URL on your website. This is especially useful for elements like contact details, which remain consistent across multiple pages. By centralizing such schema information, you save time and help maintain consistency, which ultimately contributes to improved search engine visibility and data management.
This guide walks you through everything—from adding a global schema on a contact page, to reusing it in another context, to managing or removing global schemas later on.
Step 1: Adding a Global Schema
Background:
Global schemas are particularly useful when you have information that remains the same across various pages (for example, contact or address information). This ensures consistency and simplifies future updates.
How to Add a Global Schema:
Access the Schema Editor – Navigate to the ‘Tag Schema’ dashboard and the page that contains the schema you want to use as global. For this example, we’ll use the ‘Contact Page’ schema.
Edit the Schema – Click on “Edit Schema” on the page displaying the ‘Contact Page’ schema.
Add Specific Schema – Locate and add the ‘Postal Address’ schema. Fill in all required properties, such as Description, Locality, Region, etc.
Mark as Global – Once all required fields are complete, click “Set as Global”.
Step 2: Configuring Global Schema Attributes
Why This Step?
Global schemas must have a unique identifier so that they can be reliably referenced on other pages. Two critical attributes are required: a unique @id and a meaningful Name. If not, you're going to see this message.
How to Configure:
Adding @id:
Click “Add Property”. Select @id from the dropdown.
Enter the URL appended with a unique fragment (e.g., https://yourwebsite.com#postaladdress).
Important: Ensure the @id value is unique and not used by any other schema.
Adding Name:
Click “Add Property” once more.
Select Name and enter a descriptive name, e.g., “Milestone Postal Address”.
Finalizing Global Status:
After these fields are added, click “Set as Global” again.
You’ll see a global icon appear along with a notification prompting you to save the changes to officially declare the schema as global.
Step 3: Saving and Verifying Global Schema
Background:
It’s important to save your changes so that the global schema is stored and accessible for future use.
Steps:
Once the global schema is set, click “Save”.
Return to the Tag Schema page to verify that your URL now displays the global schema indicator.
This confirmation lets you know that the schema has been saved as global and is ready for reuse anywhere on your website.
Step 4: Reusing a Global Schema
Overview:
Once a global schema is created, you can easily insert it into other pages. This avoids duplicate work and ensures consistency across your website.
How to Reuse:
Editing a New Page:
Click “Edit” on another URL where you want to incorporate the global schema.
Selecting Global Schema Reference:
Choose the schema type for the page (for instance, Organization).
When configuring the Contact Point property, select the @id type.
A list of available global schemas will appear. Select the “Milestone Postal Address” schema you created earlier.
Complete the Schema:
Add any additional properties required for this page.
Click “Save and Generate” to apply the changes.
Verification:
In the Generated Schema preview, you will notice that the global schema (Milestone Postal Address) is included along with your other tags.
The global schema will also show under the schema column on the page once published.
Step 5: Using Filters to Manage Global Schemas
Why Filtering?
As global schemas proliferate, quickly locating pages that declare or reference them becomes essential.
Steps:
On the Tag Schema page, use the ‘Filter’ option.
Declaring Global Schemas:
Selecting this filter displays pages that have one or more global schemas saved.
Containing Global Schemas:
This filter shows pages that reference one or more global schemas.
This tool helps you keep track of where global schemas are used, facilitating easier updates and troubleshooting.
Step 6: Removing Global Schemas
Understanding the Process:
There might be times when you need to update or remove a global schema. The process is designed to prevent accidental data loss and ensure that no pages are still referencing the schema.
Steps to Remove:
Removing Global Declaration:
On the schema editor, click on “Remove as Global” on the schema you wish to modify using the 3 dots.
You will be prompted to save your changes; upon saving, the schema will no longer be available as global.
Handling References:
If the global schema has been referenced on one or more URLs, you must first remove those references.
Click on “Show me the referencing URLs” to view all pages using the global schema.
Remove each reference individually.
Final Removal:
After all references are removed, you can remove the global schema definitively by clicking “Remove Referred Schema” and then saving/publishing the changes.
Glossary
Global Schema: A schema that, once set as global, can be reused across multiple pages on your website. It centralizes information like contact details for consistency and efficiency.
@id: A unique identifier for a schema. The @id property must be unique and is used to reference a global schema on various pages.
Name: A descriptive label for a schema property, used to identify the global schema in dropdown selections.
Schema Markup: Structured data added to web pages that helps search engines understand the content, enhancing search visibility (e.g., rich snippets).
Tagging: The process of linking or mapping on-page content to structured data fields as defined by schema.org.
Repeating Fields: Schema fields that can appear multiple times on a single page (e.g., multiple reviews or FAQ items).
Validation: The process by which the system checks schema tagging for completeness and correctness before it can be published.
Tips for Success
Consistency is Key: Always use global schemas for data that remains constant across pages.
Double-Check Uniqueness: Ensure that the @id property is unique to prevent reference errors.
Regular Reviews: Periodically review global schemas and their references to ensure data accuracy and consistency.
Utilize Filters: Use filtering options to quickly identify where global schemas are declared or referenced for easier maintenance.