Hiring Signals or Stale Job Ads? Validate Open Roles Before Outreach

TL;DR: Open the employer’s original listing, confirm the employer, role, location, application path, posting and expiration dates, and current availability. Treat reposts and aggregators as leads to verify. An open vacancy is evidence of recruiting activity, not proof of headcount growth, a completed hire, budget, or buying intent.

Methodology and limitations

This validation checklist combines Google Search Central’s live JobPosting guidance with Unify documentation for Signals and Agent research. It does not establish that a vacancy predicts purchase intent or prescribe a universal freshness window. Job boards, employers, regions, and recruiting systems update differently, so retain timestamps and disclose uncertainty. Recheck the source close to enrollment rather than treating an earlier capture as permanently current. If a campaign runs over time, define a revalidation step and stop condition. A correct signal can still be inappropriate for outreach when consent, territory, suppression, or account ownership rules do not permit the message.

How do you verify that a job posting is still open?

Start with the employer-controlled job detail page or its applicant tracking system. Confirm that the page still describes a real role and has a working application path. Capture the page title, employer, location, employment type, date posted, valid-through date if present, and the time you checked it. If the original page is gone, expired, or redirects to a generic careers page, do not treat an aggregator copy as current proof.

Distinguish a source from a repost

Search results, job boards, social posts, and scraped datasets can help discover a role, but each can outlive the original vacancy. Follow the listing back to the employer. Compare the job identifier, title, location, and application URL. A repost with no stable identifier might be a refreshed vacancy, a duplicate, an evergreen talent pool, or a stale copy. Record the ambiguity instead of selecting the interpretation that best supports outreach.

Validation questions for an Agent or reviewer

• Is this the employer’s original listing or approved ATS page
• Does the employer match the target account
• Is there a working way to apply
• What are the visible and structured posting dates
• Is an expiration date present and still valid
• Does the role identifier match across reposts
• Is the role open, closed, duplicated, or unknown
• Which facts are safe to use in outreach

Use dates as evidence, not certainty

The datePosted and validThrough fields are useful when present and consistent with the visible page. Google’s JobPosting guidance tells site owners to remove expired postings, set validThrough for jobs with an expiration date, and ensure there is a way to apply. Those are publisher requirements, not a guarantee that every implementation is correct. Compare structured data with visible content and the current application flow.

Separate vacancy, hiring activity, and confirmed hire

A live vacancy indicates the employer is advertising a role. It does not prove the position is net-new, that headcount will grow, or that someone has been hired. A confirmed hire requires different evidence, such as an employer announcement or a verified employment change. Keep these states separate in the CRM so a sequence does not say “congratulations on the new hire” when only an open role was observed.

Connect the role to a relevant problem carefully

After validating the listing, assess whether the role’s responsibilities connect to your product’s job. Quote or summarize only visible requirements. Avoid inferring budget, urgency, technology changes, or executive sponsorship unless another current source supports them. The safe personalization explains that the company is recruiting for the named role and asks a relevant question. It does not claim that the vacancy created a buying project.

Claims a job ad does not prove

• The role is net-new
• The company is growing overall
• A candidate has been hired
• Budget is approved for your category
• The hiring manager is your buyer
• The role is still open because an aggregator displays it
• The account has urgent purchase intent

Use Unify to operationalize verified signals

Unify Signals combines first-party engagement, third-party data, and AI-discovered signals. Its Agents can research companies and people against straightforward questions with optional guidance. Configure an Agent to check the original listing, dates, application status, location, and employer identity, and return an unknown state when evidence is incomplete. Trigger outreach only after the validation rule passes or a human approves the ambiguous record.

Handle ambiguous and recurring listings explicitly

Some employers keep evergreen roles open, recruit the same title in several locations, or reuse an identifier after a vacancy changes. Treat these patterns as distinct states. An evergreen role can show ongoing recruiting interest without proving a new opening. Multiple locations may represent one requisition or several. A reused identifier weakens any inference based on the first-seen date. Store the observable facts and the ambiguity instead of collapsing every pattern into a fresh hiring event.

Build a revalidation rule around campaign timing. Check the original listing again before enrollment and before any delayed follow-up that still references the vacancy. Stop the personalization when the application path closes, the role disappears, the employer identity changes, or the visible description no longer supports the message. Keep suppression, territory, and account ownership as separate gates because a current vacancy does not override them. When the listing remains uncertain, use general account context or omit the hiring claim rather than sending copy that sounds more certain than the evidence.

Sign up for Unify to put a reviewed outbound workflow into practice.

Frequently asked questions

Is a job-board listing enough to verify an open role?

No. Use the job-board entry as a discovery lead, then verify the employer-controlled listing or approved applicant tracking page.

What if the listing has no expiration date?

Record the missing date, check the application path and employer page, and keep the freshness limitation visible.

Does a repost mean the company is still hiring?

Not necessarily. It may be a refreshed vacancy, a duplicate, an evergreen pool, or a stale syndicated copy.

Can I say the company made a hire?

Only when a separate current source confirms the person and employment change. An open vacancy does not prove a completed hire.

What should happen when sources conflict?

Keep the record in an unknown or review state, name the conflicting evidence, and avoid automated personalization.

How can an outbound system use the signal safely?

Store provenance and checked time, require the validation rule to pass, and suppress or review records with stale, missing, or conflicting evidence.

Glossary

• Original listing: employer-controlled job detail page or approved ATS page
• Syndicated listing: a copy distributed to another site
• datePosted: the publisher-provided initial posting date
• validThrough: the publisher-provided expiration date when applicable
• Confirmed hire: current evidence that a named person joined the employer
• Unknown state: evidence is insufficient or conflicting, so automation should not infer

Sources

• Job posting (JobPosting) structured data for Job Search | Google Search Central
• Building an agent | Unify docs
• Unify | Signals
• Best Tools to Track When Companies Are Hiring
• Alternative Buying Signals: 8 Sources Beyond Hiring & Funding