numberOfEmployees

numberOfEmployees · Recommended

Appears in

Organization

What is it?

numberOfEmployees reports the headcount of an organization as a structured data field. Unlike a plain text mention of employee count, this field uses the QuantitativeValue type, which makes the number machine-readable and allows for ranges rather than just a single figure.

Google lists numberOfEmployees as a recommended field for Organization markup, meaning it actively uses this data when rendering Knowledge Panel information and answering queries about organization size.

Why this matters for AEO

Organization size is a filtering attribute for many business queries. When a user asks "is this a large company?" or "how many people work at Stripe?", AI answer engines pull from structured data that includes numberOfEmployees. Without it, the AI must estimate from unstructured text, which is less reliable and often wrong.

For B2B contexts specifically, company size shapes purchasing decisions. A procurement team evaluating software vendors wants to know if the vendor is a startup or an enterprise. A journalist researching a story needs workforce figures. numberOfEmployees puts the correct number directly in the Knowledge Graph.

Google's recommendation for this field signals that it flows into search features, not just passive indexing. It is one of the few Organization fields Google explicitly calls out as valuable.

What the specs say

Schema.org:numberOfEmployees expects a QuantitativeValue value. The number of employees in an organization, e.g. business. [Source: https://schema.org/numberOfEmployees]

Google: Recommended. "The number of employees in your Organization." [Source: https://developers.google.com/search/docs/appearance/structured-data/organization]

QuantitativeValue structure

numberOfEmployees does not accept a plain integer. It requires a QuantitativeValue node. The simplest form uses only the value property:

"numberOfEmployees": {
  "@type": "QuantitativeValue",
  "value": 5000
}

For ranges (useful when the exact count is confidential or fluctuates):

"numberOfEmployees": {
  "@type": "QuantitativeValue",
  "minValue": 1000,
  "maxValue": 5000
}

The unitText property can add context, though "employees" is implied:

"numberOfEmployees": {
  "@type": "QuantitativeValue",
  "value": 250,
  "unitText": "employees"
}

How to find your value

• LinkedIn company page — Publicly visible estimate; good for roughly accurate figures
• Annual report / 10-K — Exact figure for public companies
• About page — Use if the company states headcount there
• Press releases — Good for recent announcements with specific numbers

Use the most current authoritative number available. For fast-growing companies, update this field quarterly. For stable organizations, annual updates are sufficient.

Format and code

Single value (exact headcount)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Stripe",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "value": 8000
  }
}

Range (approximate headcount)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Webflow",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "minValue": 500,
    "maxValue": 1000
  }
}

With full Organization context

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Mailchimp",
  "url": "https://mailchimp.com",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "value": 1200
  },
  "foundingDate": "2001",
  "legalName": "The Rocket Science Group, LLC"
}

Webflow implementation

Static pages

Add numberOfEmployees to the Organization JSON-LD block in Page Settings > Custom Code. The QuantitativeValue node requires a nested object. Update the value when headcount changes significantly. Most organizations update this during annual about-page reviews.

CMS template pages

If your site generates organization pages dynamically through Webflow CMS (for example, a directory of companies), create a Number field in your CMS collection for employee count. In the CMS page template, inject this value into the JSON-LD QuantitativeValue node using a custom code embed with dynamic binding.

In Schema HQ

The numberOfEmployees field handles the QuantitativeValue wrapping automatically. Enter the employee count as a number in the Organization editor. Schema HQ generates the correct nested structure in the JSON-LD output. You can enter a single value or a min/max range.

Real examples

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "HubSpot",
  "url": "https://www.hubspot.com",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "value": 7400
  }
}

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Basecamp",
  "url": "https://basecamp.com",
  "numberOfEmployees": {
    "@type": "QuantitativeValue",
    "minValue": 50,
    "maxValue": 100
  }
}

Related fields

• employee
• founder
• foundingDate
• legalName

FAQ

Why does numberOfEmployees need a QuantitativeValue wrapper instead of a plain number?

Schema.org uses QuantitativeValue for numeric quantities that have units or ranges. This structure allows both exact values and min/max ranges in a consistent format. Plain integers are not valid for this field; validators will flag them as incorrect.

Should I include part-time employees and contractors?

Use the number your organization publicly reports. Annual reports and official press releases typically report full-time equivalents. For consistency, match whatever figure appears on your LinkedIn company page or official communications.

How often should numberOfEmployees be updated?

When accuracy matters for trust signals (journalists, investors, enterprise buyers), update it whenever the number changes materially. For most organizations, a twice-yearly review cycle is sufficient. Stale figures that are significantly off from reality reduce the credibility of the overall schema markup.