How should Schema properties be filled in for each data type?

ProcrustesPR

To fill in Schema properties correctly, first identify the markup type that matches the content and the search feature you want to appear. Then check the required and recommended properties, their accepted value types and formats, and whether the values match the actual content. Do not choose properties based solely on their names or treat price, name, or date fields from different types as interchangeable. The following examples from Google’s carousel and job posting documentation show what to check. Each restriction applies only to the context described in the documentation, not to all Schema markup.

ProcrustesPRProcrustesPRWill structured data improve rankings or AI citations?

Choose the content type first, then find the corresponding properties

First ask, “What does this data describe?” Then ask, “Which fields should be filled in?” For example, the carousel documentation recommends Hotel and VacationRental for lists of hotels and vacation rentals, respectively. Although the more general LocalBusiness is also allowed, any type-specific recommended properties must still match the markup type.

  • In that documentation, amenityFeature, which describes accommodation amenities, applies only to LodgingBusiness.
  • servesCuisine, which describes cuisine types, applies only to restaurants.

Accommodation providers and restaurants cannot simply share the same full set of properties just because both are businesses. When consulting a property table, look beyond field names: check which types each property applies to, whether it is required, and where it belongs in the nested structure.

Check the structure of values, not just whether they are present

For product or event offers in that carousel, offers accepts Offer or AggregateOffer. These use different nested fields:

  • When using Offer, the documentation recommends providing price and priceCurrency.
  • When using AggregateOffer, it recommends providing highPrice, lowPrice, and priceCurrency.
  • When price represents a single price, there is no need to provide separate high and low prices. When high and low prices represent a range, do not also include price.

Use three-letter ISO 4217 currency codes. Although the documentation states that USD is the default when no currency is provided, this does not mean every price should be interpreted as US dollars. Always check the actual currency when filling in the fields. Salary ranges in job postings instead use minValue and maxValue within a nested value object; product offer fields cannot simply be reused.

Check rating scales and what dates represent

In the carousel rating specifications, decimals should be written as 4.4, not 4,4. Numeric ratings default to a scale with a minimum of 1 and a maximum of 5. If a different scale is used, specify bestRating and worstRating rather than providing a score without its scale.

The job posting documentation requires datePosted to use ISO 8601 format and give the date the employer originally posted the job. Provide validThrough only if there is an expiration date. If the posting has no expiration date or the date is unknown, do not invent one. Besides checking the format, make sure the date matches what the field is meant to represent.

Finally, check that the fields reflect the actual content

A job posting’s title should be a short, clear job title, not the headline of the entire advertisement. The name property cannot be used in its place. The description property must fully explain the responsibilities, qualifications, skills, working hours, and required education and experience, rather than merely repeating the job title.

The job posting documentation also limits baseSalary to the actual base salary provided by the employer, not an estimated salary, and states that only employers may provide it. Finally, follow the documentation to validate the code with the Rich Results Test, but do not treat testing as a substitute for checking the content. Some issues are unrelated to syntax, and passing the test does not guarantee that the search feature will appear.

ProcrustesPRProcrustesPRHow to choose a CMS for SEO: start with control over features and your team’s needs

Common questions about filling in Schema properties

How should images, names, and URLs be provided for carousel list items?

In the carousel context described by Google, each item must provide image, name, url, and any other required properties for its data type. Images must match the marked-up content and must not be logos; url should point to the item's dedicated detail page. For the best image results, the documentation recommends providing high-resolution images in 16:9, 4:3, and 1:1 aspect ratios, each with at least 50K pixels.

Should a job with no education requirements be marked up the same way as one whose education requirements are unknown?

No. According to the job posting documentation, educationRequirements can be set to no requirements when no education is required. If the requirements are unknown, omit the property. Multiple requirements can be listed in an array. The education-level categories specified in the documentation may not suit every country or region. When using them, choose the closest value and still explain the actual requirements in detail in the description property.

How should a job's experience requirements be expressed in months?

monthsOfExperience represents the minimum number of months of experience required. If either of two experience conditions can be met, the documentation's example uses the lower qualifying number of months. If both must be met, the example uses the higher minimum number of months. When no experience is required, experienceRequirements can be set to no requirements. Even when the property is included, the requirements should also be explained in detail in description.

How should a job be marked up when work experience can substitute for education?

If the job genuinely accepts work experience in place of an education requirement, set experienceInPlaceOfEducation to True and include both experienceRequirements and educationRequirements. This Boolean value expresses that one requirement can substitute for the other. Merely listing both education and experience requirements does not mean they are interchangeable.

Can employment types and job identifiers be entered freely?

No. According to the job posting documentation, employmentType should use the specified case-sensitive values, such as FULL_TIME or CONTRACTOR. Multiple values can be listed when more than one employment type applies. For identifier, use the unique ID the hiring organization assigns to that job posting. The first property describes the employment arrangement; the second identifies the job posting. They are not interchangeable.

ProcrustesPRHow do you choose and use WordPress SEO plugins?

References

  1. 輪轉介面 (Beta 版) 結構化資料 | Google 搜尋中心  |  Documentation  |  Google for Developersdevelopers.google.com — Discusses: How should images, names, and URLs be provided for carousel list items?
  2. 瞭解徵人啟事結構定義標記 | Google 搜尋中心  |  Documentation  |  Google for Developersdevelopers.google.com — Discusses: Should a job with no education requirements be marked up the same way as one whose education requirements are unknown?; How should a job's experience requirements be expressed in months?

Related articles

Will structured data improve rankings or AI citations?How to choose a CMS for SEO: start with control over features and your team’s needsHow do you choose and use WordPress SEO plugins?How can content, links, and structured data help build website credibility?What elements appear on Google search results pages, and why does their appearance vary?How Can Websites Improve E-E-A-T or E-A-T? Start with Content, Authors, and Trust InformationHow Can Understanding Google Search Result Elements Help SEO?How do you plan keywords and create and optimize content for voice search?
ProcrustesPR
ProcrustesPR