What Is numberOfEmployees Schema?

numberOfEmployees is the Schema.org property for describing an organization’s employee count with a QuantitativeValue.

It can represent an exact point value or a supported range when the organization publicly reports only an approximate size. The property is used on Organization and BusinessAudience. For company and local business markup, the value should be a QuantitativeValue rather than a bare number or marketing phrase. The hardest part is not JSON-LD syntax; it is defining which organization, date, worker population, and source the count actually represents.

• Place numberOfEmployees on Organization or BusinessAudience.
• Use QuantitativeValue as the value.
• Publish only a scoped, dated, evidence-backed count.

1. Frame the decision raised by What Is numberOfEmployees Schema.
2. Confirm its value type and the object it describes.
3. Compare the markup with visible page information.
4. Correct the source data or template without inventing values.
5. Validate the rendered result and monitor future changes.

numberOfEmployees is useful only when the QuantitativeValue has a clear organization scope and trustworthy source.

numberOfEmployees can be used on Organization and BusinessAudience, with QuantitativeValue as the expected value.

Organization includes companies, nonprofits, schools, stores, hospitals, agencies, and LocalBusiness subtypes. The property should not be attached directly to Person, Place, PostalAddress, JobPosting, Department text, or WebSite. A location-specific count belongs on a distinct branch or LocalBusiness Organization entity when that entity is truly modeled. A hiring page that lists openings does not establish the number of current employees.

1. Identify the exact Organization entity.
2. Confirm whether the number is global, subsidiary, branch, or audience scope.
3. Create a QuantitativeValue.
4. Connect the value to the correct organization node.

• Evidence for Where Can numberOfEmployees Be Used: the live structured-data entity and property relationship
• The expected value type and any nested object
• Visible page information that supports the structured value
• Related offer or catalog fields needed for interpretation
• A fresh validation result after the page changes

Place the count on the entity whose workforce the number actually describes.

Use QuantitativeValue.value for an exact employee count that is current, publicly supported, and measured for the stated organization scope.

An exact value should mean the organization knows and intentionally reports that count, not that a third-party directory generated a precise-looking estimate. Use a Number value and avoid commas or text suffixes such as “employees.” A count of zero can be valid for a new or inactive organization only when the page supports it. Because headcount changes, the visible page should provide context or a reporting date even though numberOfEmployees itself has no dedicated date property.

• Use QuantitativeValue with value.
• Store the count as Number, not formatted Text.
• Expose the same figure visibly with scope and date.
• Refresh or remove the value when it becomes stale.

1. Frame the decision raised by How Do You Mark an Exact Employee Count.
2. Confirm its value type and the object it describes.
3. Compare the markup with visible page information.
4. Correct the source data or template without inventing values.
5. Validate the rendered result and monitor future changes.

Exact syntax should be reserved for an exact, current count rather than a rounded estimate dressed as precision.

Use QuantitativeValue.minValue and maxValue when the source supports a bounded employee range rather than one exact count.

A public company profile may state 51–200 employees or approximately 500–1,000. The endpoints should be Numbers and should reflect the same workforce definition and reporting period. Do not invent a range around an uncertain estimate. If only a minimum or maximum is genuinely known, use the appropriate bound carefully and explain the visible meaning. Avoid using value and contradictory range fields together.

1. Confirm the source publishes or supports a range.
2. Set minValue and maxValue as Numbers.
3. Keep both endpoints within one scope and date.
4. Show the range visibly on the page.
5. Avoid false precision or arbitrary bands.

• Evidence for How Do You Mark an Employee Range: the live structured-data entity and property relationship
• The expected value type and any nested object
• Visible page information that supports the structured value
• Related offer or catalog fields needed for interpretation
• A fresh validation result after the page changes

A range should come from the source’s actual uncertainty or classification, not from a template’s default band.

The count must match the exact Organization node: global group, parent company, subsidiary, department, brand operator, franchisee, or individual location.

A corporation can have thousands of employees while one store has twenty. Publishing the global count on every LocalBusiness location creates false local facts. A brand may not directly employ workers if a parent, franchisee, or operating subsidiary does. Map the organization hierarchy and legal or operating responsibility before attaching a number. If the page cannot explain the scope, omission is safer than borrowing a group-wide total.

• Map parent, subsidiary, brand, franchise, and branch entities.
• Match the count to the employing organization.
• Avoid copying global numbers to local locations.
• Keep department counts separate from company totals.
• Document consolidated versus standalone reporting.

1. Frame the decision raised by What Organization Scope Should the Count Use.
2. Confirm its value type and the object it describes.
3. Compare the markup with visible page information.
4. Correct the source data or template without inventing values.
5. Validate the rendered result and monitor future changes.

Headcount becomes meaningful only after the organization boundary is defined correctly.

The published workforce definition should distinguish employees from contractors, agency staff, franchise workers, volunteers, members, sellers, creators, and other connected people.

Different reports use full-time equivalents, payroll headcount, total employees, average annual employees, or combined employees and contractors. Structured data should not silently merge those definitions. Use the organization’s current first-party definition and expose it visibly where ambiguity matters. Do not calculate headcount from public employee profile pages; those pages are curated and incomplete. Do not treat marketplace sellers or loyalty members as staff.

1. Identify the workforce definition in the source.
2. Separate payroll employees from contractors where reported.
3. Distinguish headcount from full-time equivalent.
4. Exclude members, customers, sellers, and volunteers unless the source defines otherwise.
5. Keep the definition consistent across updates.

• Evidence for Who Counts as an Employee: the live structured-data entity and property relationship
• The expected value type and any nested object
• Visible page information that supports the structured value
• Related offer or catalog fields needed for interpretation
• A fresh validation result after the page changes

A reliable count uses one disclosed workforce definition instead of adding every person connected to the organization.

Manage numberOfEmployees as a dated business fact with a named first-party source, review owner, refresh cadence, and expiration rule.

Headcount changes through hiring, layoffs, seasonality, mergers, acquisitions, divestitures, and restructuring. Schema.org does not provide a date directly inside numberOfEmployees, so the page should visibly state “as of” context or connect the figure to a dated report. Keep source and review metadata in the CMS even when those internal fields are not published. Do not quote third-party estimates as the organization’s own fact.

• Record the first-party source and reporting date.
• Assign a content owner.
• Set a review or expiration date.
• Update after material workforce events.
• Remove the structured value when evidence is stale.

1. Frame the decision raised by How Should Date and Source Be Managed.
2. Confirm its value type and the object it describes.
3. Compare the markup with visible page information.
4. Correct the source data or template without inventing values.
5. Validate the rendered result and monitor future changes.

Treat headcount as time-sensitive data, not a timeless Organization attribute.

Common mistakes include using a bare Number, attaching the count to the wrong entity, copying third-party estimates, mixing contractors, omitting date context, and publishing contradictory exact and range values.

Teams may also use the number of public team profiles as headcount, copy a global workforce total to every branch, or leave figures unchanged after an acquisition. A formatted string such as “1,000+” does not satisfy the expected QuantitativeValue shape. Validation catches structural errors but cannot prove workforce definition, organization scope, or currency.

• Bare number or Text used instead of QuantitativeValue.
• Global count applied to a local branch.
• Third-party estimate presented as first-party fact.
• Employees and contractors mixed silently.
• Exact value conflicts with minValue or maxValue.
• No visible source date or update owner.
• Count remains after major workforce change.

1. Frame the decision raised by What numberOfEmployees Mistakes Are Common.
2. Confirm its value type and the object it describes.
3. Compare the markup with visible page information.
4. Correct the source data or template without inventing values.
5. Validate the rendered result and monitor future changes.

Valid markup still fails quality when scope, population, source, or date is wrong.