seeks

seeks · Not mentioned by Google

Appears in

Organization

What is it?

seeks declares what an organization is looking for: products, services, or resources it wants to acquire. It is the inverse of makesOffer. Where makesOffer says "here is what we sell," seeks says "here is what we want to buy." The field points to one or more Demand objects, which describe the desired items.

This is primarily useful for B2B organizations, procurement platforms, marketplaces, and any business that publicly solicits goods or services.

Why this matters for AEO

When a user asks "Who is looking for [product/service]?" or "companies seeking [resource]?", AI engines need structured demand signals. seeks provides exactly that. A procurement-focused query like "organizations looking for sustainable packaging suppliers" can match organizations whose seeks field includes packaging-related demands.

This creates a demand-side discovery channel in structured data, complementing the supply-side signals from makesOffer and product schemas.

What the specs say

Schema.org: Expects Demand. "A pointer to products or services sought by the organization or person (demand)." Source

Google: Not listed in Google's structured data documentation for Organization. Source

How to find your value

• Procurement pages — Open RFPs and solicitations
• "Partners Wanted" pages — Partnership or vendor requirements
• Job board postings — Resource or talent needs
• Supplier portals — Categories of goods/services sought

Format and code

Single demand:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Whole Foods Market",
  "seeks": {
    "@type": "Demand",
    "name": "Local organic produce suppliers",
    "description": "Seeking regional organic farms for direct store supply partnerships"
  }
}

Multiple demands:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "SpaceX",
  "seeks": [
    {
      "@type": "Demand",
      "name": "Aerospace-grade titanium suppliers"
    },
    {
      "@type": "Demand",
      "name": "Heat shield material vendors"
    }
  ]
}

Webflow implementation

Static pages

Add seeks in Page Settings > Custom Code (before </head>):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "seeks": {
    "@type": "Demand",
    "name": "What you're looking for",
    "description": "Details about what you need"
  }
}
</script>

CMS template pages

If running a marketplace or procurement directory, create a CMS collection for demands and reference the fields in a template:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "{{wf {"path":"name","type":"PlainText"} }}",
  "seeks": {
    "@type": "Demand",
    "name": "{{wf {"path":"seeking","type":"PlainText"} }}"
  }
}
</script>

In Schema HQ

seeks supports in the Organization schema editor. Add demand descriptions through the UI, and Schema HQ generates the nested Demand objects.

Real examples

No live implementations of seeks on Organization markup were found during research.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Patagonia",
  "seeks": [
    {
      "@type": "Demand",
      "name": "Recycled polyester suppliers",
      "description": "Certified post-consumer recycled polyester for outerwear manufacturing"
    },
    {
      "@type": "Demand",
      "name": "Fair Trade certified cotton farms"
    }
  ]
}

Related fields

• makesOffer — products or services the organization sells (inverse of seeks)
• hasOfferCatalog — catalog of available products
• areaServed — geographic areas the organization operates in

FAQ

When should I use seeks instead of just describing needs on a web page?

Use seeks when you want AI engines and structured data consumers to programmatically discover your procurement needs. If your organization actively solicits suppliers, vendors, or partners, seeks makes those requirements machine-readable. For internal-only procurement, this field adds no value.

Is seeks commonly used in practice?

No. It is one of the less frequently implemented schema.org properties. However, as AI-powered procurement tools and B2B matchmaking platforms evolve, structured demand data becomes more valuable. Early adopters gain discoverability advantages.

Can I use seeks for job openings?

No. Job openings should use the JobPosting type, which has dedicated fields for requirements, qualifications, and compensation. seeks is for products, services, and resources, not talent acquisition.