What goes in your /careers page for AI-search citations

Job applicants searching for "[Company] careers" are doing it through AI search now. Most /careers pages have nothing AI engines can quote. Here are the four signals that earn the citation.

When someone searches "what's it like to work at [Company]" on ChatGPT or Perplexity, the answer comes from your /careers page — if there's anything there to quote.

Most /careers pages have nothing AI engines can use. Just job listings, a generic "join us" header, and a contact form.

Four signals turn /careers into an AI-citable surface.

1. JobPosting JSON-LD on every open role

Each individual role gets a JobPosting schema block: title, description, location, employment type, salary range (yes, even ranges help), how to apply.

This is the highest-leverage signal. AI engines pulling job-search queries cite sites with structured JobPosting data over sites with prose-only listings, even when the prose listing has more detail.

2. A culture statement worth quoting

Two paragraphs, max. Not "we're a fast-paced team that loves coffee." Specific: how the team works, what the work week looks like, what the org structure is, what people get evaluated on.

The test: would an AI engine answering "what's it like to work at [Company]" find a quotable sentence here? If no, it's filler. Cut it.

3. A FAQ section addressing the questions applicants ask

Not "why work at [Company]" — actual questions:

• "Is this role remote, hybrid, or in-office?"
• "What's the interview process?"
• "Do you sponsor visas?"
• "What's the salary range?"
• "What's parental leave?"
• "How are reviews and promotions handled?"

Wrap them in FAQPage schema. AI engines will pull answers directly when applicants search those questions.

4. A "currently hiring for" line that updates

Above the job listings, a one-line summary: "Currently hiring for [N] roles — Senior Engineer, Product Designer, Customer Success Lead."

This catches AI engines that surface results for "is [Company] hiring."

What this looks like at scale

If you have 5+ open roles at a time, manually maintaining all four signals is real work. Most operators don't have a recruiter who maintains structured data on top of writing the actual JD.

Onramp (Merkava's recruiter specialist, managed by OPS) generates the JobPosting schema, FAQPage entities, and the "currently hiring for" line automatically. New role posted → schema updated → /careers page redeployed.

If you're hiring 1-2 roles a year, do it manually. If you're hiring 5+, automate it.