directApply

directApply · Recommended

Appears in

JobPosting

What is it?

A boolean that indicates whether candidates can apply directly through the job posting URL. Set to true when the posting page includes an application form or "Apply" button. Set to false when the page describes the role but directs applicants elsewhere to apply.

Why this matters for AEO

AI assistants evaluating job listings assess the application friction. When a user asks "Find me jobs I can apply to right now," listings with directApply: true rank higher in that context. The field signals to AI engines whether the link they surface will lead to an immediate application experience or a dead end requiring additional navigation.

What the specs say

Schema.org:Boolean. Indicates whether a URL that is associated with a JobPosting enables direct application for the job, via the posting website. schema.org/directApply

Google: Recommended. "Indicates whether the URL that's associated with this job posting enables direct application for the job." Google Search Central

Note: directApply is currently in schema.org's Pending section. It was proposed by Google (Dan Brickley) via GitHub issue #2907 on the schemaorg repository, based on Google's experience building job search with JobPosting data.

How to find your value

• Your job page has an "Apply Now" form or button that starts the application — true
• Your page collects resumes or redirects to an ATS with one click — true
• Your page describes the job but applications go through a separate portal — false
• You are a job aggregator linking to the employer's site — false

Format and code

Type: Boolean

{
  "@type": "JobPosting",
  "title": "Frontend Developer",
  "directApply": true
}

{
  "@type": "JobPosting",
  "title": "Senior UX Designer",
  "directApply": false
}

The value must be a JSON boolean (true or false), not a string ("true" or "false").

Invalid:

"directApply": "true"

"directApply": "yes"

Strings are not valid boolean values in JSON-LD.

Webflow implementation

Static pages

Add the boolean directly in your JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Product Manager",
  "directApply": true
}
</script>

CMS template pages

Webflow does not have a native boolean CMS field type. Use a switch field and conditionally output the value:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "directApply": {{wf {&quot;path&quot;:&quot;direct-apply&quot;,&quot;type&quot;:&quot;PlainText&quot;} }}
}
</script>

Create a Switch field named "Direct Apply" in your CMS collection. Webflow switch fields output true or false as plain text, which maps directly to JSON boolean values.

In Schema HQ

The directApply field detects whether your job posting pages include application forms and sets directApply accordingly. For CMS driven job boards, it reads the switch field value and outputs the correct boolean in the JSON-LD.

Real examples

Schemantra (schemantra.com):

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Frontend Developer",
  "directApply": true,
  "datePosted": "2025-06-01",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "TechStartup Inc."
  }
}

Highrise Digital (highrise.digital):

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior UX Designer",
  "directApply": false,
  "datePosted": "2025-03-15",
  "employmentType": "FULL_TIME"
}

Related fields

• title: the position candidates can apply to directly
• hiringOrganization: the company receiving the application
• datePosted: when the application became available
• validThrough: deadline for the application

FAQ

Does directApply affect ranking in Google job search?

Google has not confirmed that directApply directly impacts ranking. However, it influences how the listing is presented to users. Listings marked true signal lower friction, which may lead to higher click through rates and user preference signals.

Is directApply required for JobPosting rich results?

No. It is listed as Recommended, not Required. JobPosting rich results will still appear without it. Including the field provides additional context that helps both search engines and AI assistants evaluate the quality of the application experience.