Schema.org released version 30.0 on March 19, 2026. It adds a general Credential type for hasCredential, a jobDuration property for JobPosting, and lists floorLevel for LocalBusiness and Residence.
If your pages already carry valid schema.org markup, that markup stays valid, so most sites can leave it alone. The release changes the shared vocabulary. It does not switch on a new search feature at Google, Bing or anywhere else.
Update a page only when one of the three facts is visible on it: a fixed or recurring job length, a credential that is not limited to education, or a floor number that helps visitors find the business. If a page of yours shows one of those, add the property and validate it.
What schema.org 30.0 changed
The release notes title version 30.0 this way: "Add equivalence annotations, Add EU DPP (Digital Product Passport) examples, Misc. schema, doc, and infra updates." Inside that release, the schema.org release notes name a new Credential class, a new jobDuration property for JobPosting, and floorLevel for LocalBusiness and Residence. Those three are the changes that touch job pages, business pages and credential descriptions.
The credential work started in GitHub issue #4685, "Expansion of hasCredential to generic Credential," opened on January 13, 2026. It proposed a general Credential supertype and left education-specific properties such as educationLevel on EducationalOccupationalCredential. The release implementation is recorded in PR #4700. The jobDuration change is in PR #4675, and the floorLevel change is in PR #4669.
EducationalOccupationalCredential remains available. The same release also adds Error and errorCode, equivalence annotations, EU Digital Product Passport examples, a change to Quantity and a broader range for priceComponent. None of those changes what an ordinary job or business page writes.
Schema.org defines jobDuration as the duration associated with a job, and hasCredential as the property that connects a Person or Organization to a Credential. Two supporting properties, credentialCategory and recognizedBy, describe the kind of credential, such as a degree, certificate or badge, and the organization that acknowledges it.
Add jobDuration to a JobPosting when the length is fixed
jobDuration holds how long a job lasts, written as an ISO 8601 duration. P6M means six months. It fits a fixed assignment, a seasonal run or a recurring engagement that the posting states in plain words. If the listing never mentions a length, leave the property out, because markup should describe what the page shows.
A recruiter scanning a batch of listings can tell quickly which ones state an assignment length. Those are the pages where the property has a real fact to carry.

The first block shows a fixed-term job described only in visible text. The second adds jobDuration. Replace the company, address and title with your own, and set the duration to match the number in your listing exactly. These are displayed examples with fictional facts on example.com, not code to paste unchanged.
{
"@context": "https://schema.org",
"@type": "JobPosting",
"@id": "https://example.com/jobs/content-editor#jobposting",
"url": "https://example.com/jobs/content-editor",
"title": "Content Editor",
"description": "<p>Example Publishing is hiring a content editor for a fixed six-month assignment.</p>",
"datePosted": "2026-03-19",
"hiringOrganization": {
"@type": "Organization",
"name": "Example Publishing",
"url": "https://example.com/"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Avenue",
"addressLocality": "Example City",
"addressRegion": "IL",
"postalCode": "60000",
"addressCountry": "US"
}
}
}{
"@context": "https://schema.org",
"@type": "JobPosting",
"@id": "https://example.com/jobs/content-editor#jobposting",
"url": "https://example.com/jobs/content-editor",
"title": "Content Editor",
"description": "<p>Example Publishing is hiring a content editor for a fixed six-month assignment.</p>",
"datePosted": "2026-03-19",
"jobDuration": "P6M",
"hiringOrganization": {
"@type": "Organization",
"name": "Example Publishing",
"url": "https://example.com/"
},
"jobLocation": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Avenue",
"addressLocality": "Example City",
"addressRegion": "IL",
"postalCode": "60000",
"addressCountry": "US"
}
}
}Google's JobPosting documentation describes the properties for its job search feature. It lists title, description, datePosted, hiringOrganization and, for on-site jobs, jobLocation as required, and validThrough as required when a posting has an expiration date. It recommends properties such as employmentType, baseSalary, directApply and identifier. For Google, jobDuration is an optional extra beyond those properties. Add validThrough yourself if your posting closes on a date; the sample posting above has no closing date.
Add floorLevel to a LocalBusiness only when it helps visitors find you
A floor number is useful when the business sits above street level in a shared building, such as a studio on the third floor of a plaza. A visitor who arrives at the right address still needs to know which floor. If your business is at street level or in its own building, there is nothing for floorLevel to say.
Schema.org's term page describes floorLevel as the floor level for an accommodation in a multi-storey building, while the 30.0 release lists it for LocalBusiness. Because those two descriptions do not match word for word, treat the property as optional and validate your markup after adding it. Use the numbering the building itself uses, so the value matches the signs and the visible address text.
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"@id": "https://example.com/#business",
"name": "Example Repair Studio",
"url": "https://example.com/",
"address": {
"@type": "PostalAddress",
"streetAddress": "200 Example Plaza",
"addressLocality": "Example City",
"addressRegion": "IL",
"postalCode": "60000",
"addressCountry": "US"
},
"floorLevel": "3",
"telephone": "+1-555-0100"
}Replace the name, address and phone number with your own, and change "3" to your floor as the building labels it. Remove the floorLevel line if the floor does not appear on your page. The local business schema generator builds the surrounding LocalBusiness JSON-LD with the address and contact fields, and you can add this one property to its output when it applies.
Google's Local Business documentation requires name and address for its rich result, and recommends properties such as telephone, url, geo, openingHoursSpecification, priceRange and department. floorLevel is an optional extra for the Google feature, so adding it does not change eligibility there.
Describe a non-educational credential with Credential
Before 30.0, schema.org's credential vocabulary centered on educational and occupational credentials. The new Credential type is the general parent, so a certificate, badge or professional recognition that is not tied to a school can now be described with a type of its own. EducationalOccupationalCredential stays the better fit when you need education-specific fields.
The example below attaches a certificate to a person. The same shape works on an Organization, since schema.org lists hasCredential for both. Replace the person, the credential name and the recognizing body with real ones.
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://example.com/team/example-person#person",
"name": "Example Person",
"url": "https://example.com/team/example-person",
"hasCredential": {
"@type": "Credential",
"name": "Example Accessibility Reviewer Certificate",
"credentialCategory": "certificate",
"recognizedBy": {
"@type": "Organization",
"name": "Example Standards Council",
"url": "https://example.com/standards-council"
}
}
}Only describe a credential as verified, accredited or recognized when that statement is true and shown on the page. These are schema.org vocabulary properties, so none of them is required or recommended for a Google feature.
Make the markup readable for Bing and AI search
Bing's structured data guidance documents Schema.org in JSON-LD, Microdata and RDFa, so the same JSON-LD block serves Bing as well as Google. Microsoft Learn says Copilot web responses can use Bing search to ground answers, so keep the page crawlable with accurate content.

Yandex's semantic markup FAQ documents Schema.org support and a validator, and says not every Schema.org type is supported. To let ChatGPT search reach the page, allow OAI-SearchBot, the crawler OpenAI's documentation describes for ChatGPT search results. Google's AI features documentation, updated December 10, 2025, says AI Overviews and AI Mode need no special schema.org markup and recommends that structured data match the visible text. For the full comparison, see whether AI systems use schema markup.
Who should update and who can wait
Update now if a page matches one of these situations:
- A job page states a fixed duration, a recurring duration or an assignment period that applicants would want to know.
- An organization or person page describes a real credential that is not limited to education.
- A local business page identifies a floor, and that detail helps visitors find the business.
You can wait if your existing markup is valid and none of those facts apply. You can also wait if filling in the new terms would mean inventing, guessing or hiding information, or if the only reason is an expected rich result or AI citation. Neither outcome comes with these terms.
Validate the markup in six steps
Run these checks in order after adding any of the three terms, on the page where the markup lives.
- Compare the visible page text with the JSON-LD, and make sure every fact in the code appears on the page.
- Confirm the type and property names use the
https://schema.orgvocabulary. - Paste the code into the Schema Markup Validator to check syntax and vocabulary.
- For
JobPostingandLocalBusinesspages, run Google's Rich Results Test. - After deployment, watch Search Console for valid and invalid structured data items.
- Confirm the page is crawlable, indexable and open without a login.
A passing test shows that the code is written correctly. It does not guarantee a rich result, a ranking, an AI citation or traffic. For more copyable patterns, the JSON-LD schema examples guide covers the common page types.
Questions people ask
Do I need to update my schema markup for schema.org 30.0?
Most sites do not. Existing valid schema.org markup remains valid, and the release adds optional vocabulary. Add a new term only when its fact appears on the page.
Does Google support jobDuration?
Google's JobPosting documentation lists the required and recommended properties for its job search feature, and jobDuration is an optional extra there. The property is still valid schema.org vocabulary, and it can describe a real fixed-term job for other readers of your markup.
What is the difference between Credential and EducationalOccupationalCredential?
Credential is the new general type for any credential, such as a certificate or badge. EducationalOccupationalCredential remains available for education-specific details, including properties like educationLevel.
What does floorLevel do for a LocalBusiness?
It records which floor of a multi-storey building the business occupies. For Google's Local Business feature it is an optional extra, so use it as a detail that matches the visible address and the building's own numbering.
Does schema markup guarantee a rich result or an AI citation?
No. Google, Bing and Yandex each say correct markup does not guarantee a rich result or snippet, and OpenAI says allowing its search crawler does not guarantee inclusion. Treat markup as an accurate description of the page, not a promise of display.
