Guides3 March 2026·8 min read

Why Your Careers Page Is Invisible to AI — And What to Do About It

You spent months getting your careers page right. The photography is warm, the copy hits the right notes, the job listings are current. It looks brilliant on a laptop screen.

There's just one problem: AI can't see any of it.

When a candidate asks ChatGPT "What's it like to work at [Your Company]?", your careers page might as well not exist. AI skips right past it — and builds its answer from Glassdoor reviews, LinkedIn snippets, and whatever scraps of content it can find elsewhere.

This isn't a niche technical issue. It's a top-of-funnel crisis hiding in plain sight. And the culprit, more often than not, is your ATS.

The ATS Visibility Problem

Most UK mid-market employers host their careers pages on applicant tracking systems: Greenhouse, Lever, Workable, Ashby, Teamtailor. These platforms are excellent at managing applications. They're terrible at making your employer brand visible to AI.

Here's why.

1. Template Content, Zero Differentiation

ATS-hosted careers pages follow the same structure across thousands of employers. A header image, a "Life at [Company]" section with three bullet points, a list of open roles, and a "Values" section that reads like every other "Values" section.

AI models process millions of these pages. They all look identical. When content is indistinguishable from thousands of other pages, AI treats it as low-signal noise — not worth citing.

What AI sees: Another templated careers page with generic claims about "innovation" and "collaboration."

What AI needs: Specific, structured, unique content that answers the questions candidates actually ask.

2. JavaScript-Rendered Content

Many ATS platforms render careers pages using JavaScript. The job listings, the team photos, the perks section — they load dynamically after the page itself loads.

This matters because AI training pipelines and web crawlers often capture the initial HTML before JavaScript executes. If your content loads via JavaScript, there's a reasonable chance it was never captured in the first place.

Test it yourself: Right-click your careers page, select "View Page Source." If the actual content isn't in that raw HTML — if it's just empty divs and script tags — AI probably can't see it.

3. Subdomain and Iframe Isolation

Your careers page might live at jobs.yourcompany.com (a Greenhouse subdomain) or be embedded as an iframe on yourcompany.com/careers. Both create problems.

Subdomains are treated as separate entities by AI models. Content on jobs.yourcompany.com may not be associated with your main domain, diluting its authority.

Iframes are worse. Content inside an iframe is often invisible to crawlers entirely. Your beautifully designed careers page, embedded in an iframe from your ATS, might be completely un-indexable.

4. No Structured Data

ATS platforms rarely include structured data (Schema.org markup) on careers pages. Without structured data, AI has to guess what each piece of content means — and it frequently guesses wrong.

A human can tell the difference between a perk description and a job requirement. AI needs markup to make that distinction reliably. Without it, your 4-day work week and your £2,000 learning budget blend into an undifferentiated blob of text.

5. Thin Content Per Page

A typical ATS job listing contains:

Job title
200-word description
A bullet list of requirements
A bullet list of "nice to haves"
A generic "About us" paragraph copied across every listing

That's roughly 400 words of content, most of it generic. AI needs depth, specificity, and context to form useful answers about your employer brand. A thin job listing provides none of that.

What an AI-Visible Careers Page Looks Like

We've audited hundreds of UK employers through OpenRole, and the pattern is clear. Companies with high AI visibility share specific characteristics on their careers pages — regardless of which ATS they use.

Rich, Specific Content (Not Marketing Fluff)

Invisible version:

"We offer a competitive salary and excellent benefits in a collaborative, fast-paced environment."

Visible version:

"We pay in the top quartile for our sector — senior engineers earn £85,000-£105,000 depending on experience. Every employee gets private health insurance (family included), a £2,000 annual learning budget, and 6 months fully-paid parental leave regardless of gender."

The second version answers three candidate questions in one paragraph. AI can extract salary ranges, specific benefits, and parental leave policy directly. The first version tells AI nothing useful.

Interview Process Documentation

Only 9% of the companies we've audited have any AI-discoverable information about their interview process. The ones that do see dramatically higher AI visibility scores.

What to publish:

How many stages your interview process has
What each stage involves (technical test, culture chat, case study)
How long the entire process typically takes
What candidates should prepare
Who they'll meet at each stage

This doesn't need to be a glossy microsite. A well-structured blog post titled "How We Hire at [Company]" is enough. Monzo, Octopus Energy, and Starling Bank all do this — and AI cites them constantly.

First-Party Culture Content

AI can't read your office vibes. It can only read what you've published. And "We have a great culture" tells it nothing.

What works:

Employee stories with names and specific details
Descriptions of actual rituals ("Every Friday at 4pm we do a company-wide show-and-tell")
Concrete policies ("Everyone finishes by 5:30pm — no exceptions, no guilt")
Real numbers ("Our average tenure is 3.4 years, and 40% of our senior hires were internal promotions")

Structured Data Markup

If you're technical (or have a developer handy), adding Schema.org JobPosting markup to your listings makes a significant difference. It tells AI exactly what each field represents — salary, location, employment type, benefits.

Google already uses this markup for its job search feature. AI models increasingly leverage it too.

Content on Your Own Domain

This is the single most important point. Your employer brand content needs to live on your primary domain — not on a subdomain managed by your ATS, and not only on third-party platforms like Glassdoor or LinkedIn.

AI gives more weight to first-party content. A blog post on yourcompany.com/blog/how-we-hire carries more authority than the same information scattered across review sites.

A Practical Fix: 5 Steps This Week

You don't need to rebuild your careers page from scratch. You need to supplement it with content AI can actually find and use.

Step 1: Audit What AI Currently Says (15 minutes)

Before you fix anything, understand the baseline. Ask ChatGPT, Claude, and Perplexity:

"What's it like to work at [Your Company]?"
"What does [Your Company] pay for [role you're hiring]?"
"What's the interview process at [Your Company]?"

Document what comes back. Is it accurate? Generic? Empty?

Run a free AI audit at openrole.co.uk →

Step 2: Publish a "How We Hire" Blog Post (2-3 hours)

This is the highest-ROI action for most employers. Write a 1,000-word blog post on your own domain covering:

Your hiring philosophy (2-3 sentences on what you value in candidates)
The stages (list each stage with a one-paragraph description)
Timeline ("Our process typically takes 2-3 weeks from first call to offer")
What to prepare (specific tips for each stage)
FAQs (answer the 5 most common candidate questions)

Use clear headings. Use bullet points. Be specific. Publish it on your main company blog, not buried in your ATS.

Step 3: Create a "Working at [Company]" Page on Your Domain (2-4 hours)

Separate from your ATS job listings, create a standalone page on your primary domain that covers:

Compensation approach (ranges, philosophy, how you benchmark)
Benefits (every perk, listed explicitly — not "competitive package")
Working patterns (remote, hybrid, office — be specific about expectations)
Growth (how promotions work, learning budgets, internal mobility)
Culture (specific examples, not generic values)

This page becomes the canonical source AI references when candidates ask about your employer brand.

Step 4: Add Structured Data to Job Listings (1-2 hours, needs a developer)

If your ATS supports custom code injection (most do), add JobPosting Schema.org markup to each listing. At minimum, include:

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior Software Engineer",
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "GBP",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 85000,
      "maxValue": 105000,
      "unitText": "YEAR"
    }
  },
  "employmentType": "FULL_TIME",
  "jobLocationType": "TELECOMMUTE",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Your Company"
  }
}

If structured data feels too technical, even adding salary ranges as plain text in your job descriptions helps enormously. Most UK employers still don't include salary ranges in listings — which means AI either guesses (usually wrong) or says nothing.

Step 5: Refresh Content Quarterly (Ongoing)

AI prioritises recent content. A brilliant careers page published two years ago carries less weight than a mediocre blog post published last month.

Set a quarterly reminder to:

Update salary ranges
Refresh employee stories
Add new benefits or policy changes
Publish at least one new blog post about working at your company

Consistency beats perfection. A steady cadence of useful, specific content will compound your AI visibility over time.

The Employers Getting This Right

A handful of UK companies have figured this out. Their careers content is AI-visible, accurate, and regularly cited.

Monzo publishes detailed "How we hire" guides for every department. When candidates ask AI about Monzo's interview process, AI gives a specific, accurate answer — because Monzo made it easy.

Octopus Energy documents its culture with specifics, not slogans. Their blog includes real stories from employees, concrete policies, and honest descriptions of what the work is actually like.

GoCardless publishes salary bands openly and explains their compensation philosophy in detail. AI can cite their pay ranges accurately because GoCardless published them in a structured, accessible format.

The common thread: These companies treat their employer brand content as a product — something that needs to be maintained, updated, and optimised for how people (and AI) actually consume it.

The Cost of Doing Nothing

Every week you don't fix this, candidates are asking AI about you and getting one of three responses:

Nothing — AI doesn't know you exist, and suggests competitors instead
Generic fluff — "They offer a collaborative environment" (indistinguishable from every other employer)
Outdated or wrong information — Salary data from 2022, culture descriptions from before your transformation

Each of these costs you candidates. Not hypothetically — right now, every day.

The fix isn't expensive. It's a few hours of focused content work, published on your own domain, structured for AI to find and use.

The employers who do this now will own their AI narrative for years. The employers who wait will find it increasingly difficult to displace the companies already dominating AI responses.

Your careers page might look great to humans. But if AI can't see it, an increasing number of candidates won't see it either.

Want to know exactly what AI tells candidates about your company?

Run a free AI visibility audit — we'll show you what ChatGPT, Claude, and Perplexity say about your employer brand, and where the gaps are.

Related reading: