Session 10.5: Schema Maintenance and Evolution

Course → Module 10: Measurement and Maintenance

Session 5 of 10

Structured data is not a one-time implementation. It is a living layer of your website that requires ongoing attention. Schema.org releases new versions. Google changes which types and properties it supports. Your business evolves, adding services, changing locations, hiring new people. Every one of these changes means your structured data needs updating.

The businesses that treat schema as "set and forget" are the ones who discover, six months later, that their markup contains errors, references a discontinued product, or uses deprecated properties that Google no longer processes. By then, the damage is done: months of degraded entity signals that silently eroded their search presence.

The Quarterly Schema Audit

Schema maintenance follows a quarterly cycle. Each quarter, you review your markup against three standards: technical validity, content accuracy, and Schema.org currency.

graph TD A["Quarterly Schema Audit"] --> B["Technical Validation"] A --> C["Content Accuracy"] A --> D["Schema.org Currency"] B --> B1["Rich Results Test"] B --> B2["Schema Markup Validator"] B --> B3["GSC Enhancement Reports"] C --> C1["Compare markup to
actual page content"] C --> C2["Check all URLs,
dates, names"] C --> C3["Verify nested
relationships"] D --> D1["Check Schema.org
release notes"] D --> D2["Review Google
documentation changes"] D --> D3["Identify new types
or properties to adopt"] style A fill:#222221,stroke:#c8a882,color:#ede9e3 style B fill:#222221,stroke:#6b8f71,color:#ede9e3 style C fill:#222221,stroke:#6b8f71,color:#ede9e3 style D fill:#222221,stroke:#6b8f71,color:#ede9e3 style B1 fill:#222221,stroke:#8a8478,color:#ede9e3 style B2 fill:#222221,stroke:#8a8478,color:#ede9e3 style B3 fill:#222221,stroke:#8a8478,color:#ede9e3 style C1 fill:#222221,stroke:#8a8478,color:#ede9e3 style C2 fill:#222221,stroke:#8a8478,color:#ede9e3 style C3 fill:#222221,stroke:#8a8478,color:#ede9e3 style D1 fill:#222221,stroke:#8a8478,color:#ede9e3 style D2 fill:#222221,stroke:#8a8478,color:#ede9e3 style D3 fill:#222221,stroke:#8a8478,color:#ede9e3

The Maintenance Checklist

Use this checklist each quarter. Work through it page by page for every page that contains structured data. For most baseline entities, that means your homepage, about page, contact page, and any service or product pages.

#	Check Item	Tool / Method	Pass Criteria
1	Run Rich Results Test on each page	Google Rich Results Test	Zero errors, zero warnings
2	Run Schema Markup Validator on each page	validator.schema.org	No validation errors
3	Check GSC Enhancement reports	Google Search Console	All items show "Valid"
4	Verify Organization name matches legal name	Manual comparison	Exact match
5	Verify address in schema matches current address	Manual comparison	Exact match with GBP
6	Verify phone number is current	Manual comparison	Matches live phone line
7	Verify all URLs in sameAs are live and correct	Click each URL	All return 200, correct profiles
8	Verify logo URL returns correct image	Open URL in browser	Current logo, correct dimensions
9	Check for deprecated properties	Schema.org release notes	No deprecated properties in use
10	Verify @id values are consistent across pages	Manual review	Same @id for same entity everywhere
11	Check for new Google-supported types relevant to your entity	Google structured data docs	Adoption plan for any new relevant types
12	Verify dates (foundingDate, datePublished) are accurate	Manual comparison	All dates correct
13	Check that service/product schema reflects current offerings	Manual comparison to service pages	No discontinued items, no missing new items
14	Verify Person schema for key people is current	Manual comparison	Job titles, affiliations up to date

Schema.org Versioning

Schema.org is not frozen. It releases updates regularly, adding new types, new properties, and occasionally deprecating old ones. As of early 2026, Schema.org is on version 28.x. Each release is documented at schema.org/docs/releases.html.

You do not need to track every release in detail. Most updates involve specialized types (medical, automotive, financial) that may not affect your entity. What you do need is a quarterly habit of scanning the release notes for changes that touch the types you use: Organization, Person, LocalBusiness, Product, Service, Article, and FAQPage.

Google's Documentation Changes

Google independently decides which Schema.org types and properties it supports for rich results and entity understanding. Just because Schema.org adds a new property does not mean Google uses it. And just because Google supported a property last year does not mean it still does.

Google's structured data documentation at developers.google.com is the authoritative source. Bookmark it. When you do your quarterly audit, check for any documentation updates, especially for types you have implemented.

In 2025 and 2026, Google made several changes to its structured data support, including dropping Search Console reporting for some types and adjusting requirements for others. These changes were announced on the Google Search Central blog but were easy to miss if you were not watching.

When to Expand Your Markup

Your baseline schema covers the essentials: Organization or Person, LocalBusiness if applicable, and basic sameAs linking. But as your entity matures, your schema should grow with it.

Consider adding new types when:

You launch a new service or product line (add Product or Service schema)
You publish articles or blog posts (add Article schema with author linking)
You receive awards or certifications (add the relevant properties to your Organization)
You speak at events (add Event schema with performer linking)
You hire key people whose names have entity potential (add Person schema)

Each expansion strengthens your entity graph by adding more nodes and relationships that Google can map. But only expand when you have accurate, verifiable information to include. Schema with placeholder data or inaccurate claims does more harm than having no schema at all.

Structured data maintenance is not busywork. It is the practice of keeping your machine-readable identity synchronized with your real-world identity. When the two drift apart, Google notices.

Assignment

Perform a quarterly schema audit on your website (or a practice site).

List every page on your site that contains JSON-LD structured data.
Run the Rich Results Test on each page. Record whether the result is valid, has warnings, or has errors.
For each page, compare the structured data values against the visible page content. Note any mismatches (outdated phone numbers, wrong addresses, discontinued services).
Visit schema.org/docs/releases.html and scan the last two releases. Note any changes to types you use.
Create a prioritized list of fixes (errors first, then warnings, then content mismatches) and a timeline for completing them.

Schema Maintenance and Evolution