JobPosting Schema vs Indeed for Private-Pay Caregiver Recruiting: What Each Channel Actually Does

Private-pay home care agencies can use JobPosting structured data to make individual caregiver vacancies eligible for Google’s job-search experience, but eligibility does not guarantee display, ranking, applications, or hires. This article explains how owned caregiver job pages should be crawlable, current, candidate-visible, and aligned with their JSON-LD markup and application destination. It also separates Google Jobs from Indeed: Google Jobs can lead candidates to an agency-controlled careers page or ATS flow, while Indeed is a separate marketplace that may offer free listings and optional paid sponsorship. Finally, it shows how agencies should verify Indeed billing terms, use capped campaigns for urgent coverage, and evaluate both channels by qualified applicants, interviews, hires, retention, cost, and time to fill.

What's in this guide

• How JobPosting Schema Appears in Google Jobs
• Indeed Caregiver Job Posting Cost: What Agencies Actually Pay For
• Google Jobs vs. Indeed for Caregiver Recruiting
• JobPosting Schema Requirements and Google Guidelines
• How to Add JobPosting Schema to a Home Care Job Page
• Maintaining Caregiver Job Listings in Google Jobs
• Why Caregiver Jobs Do Not Appear in Google Jobs
• JobPosting Schema vs. Indeed Recruiting Decision: Build a Measurable Channel Mix

The numbers at a glance

How JobPosting Schema Appears in Google Jobs

JobPosting structured data can make an individual caregiver vacancy eligible for Google’s job-search experience, but it does not guarantee that Google will display, rank, or send applicants to that vacancy. For a private-pay home care agency, schema is an owned-site eligibility signal—not a replacement for an ATS, prompt recruiter follow-up, or paid distribution such as Indeed.

JobPosting schema is machine-readable job-vacancy markup placed on a specific job page so search engines can identify details such as the role, employer, location, employment type, date posted, and application destination.

A caregiver opening can appear in three materially different places: a conventional organic result linking to an agency’s website, a Google Jobs panel that aggregates job listings within Search, or an Indeed listing hosted in Indeed’s marketplace. A Google Jobs result should not be reported as an Indeed result merely because the candidate searched Google first; the destination URL and application flow determine which channel produced the visit.

The supplied research set includes an overview of the Google Jobs search-result feature from Semrush, but it does not include Google Search Central’s JobPosting documentation, a Schema.org specification URL, a live caregiver URL, Search Console data, or screenshots. Therefore, no agency should claim a documented Google Jobs inclusion, ranking position, crawl result, or applicant-volume outcome from this evidence set alone.

Does JobPosting schema guarantee Google Jobs visibility?

No. Valid JobPosting markup is an eligibility input for a job-search feature, not a contractual promise that a caregiver role will appear in Google Jobs, appear above competing agencies, generate applications, or produce a hire.

The operational distinction matters when an owner says, “Our schema is installed, but our caregiver jobs are not showing.” A developer may have added JSON-LD correctly while Google has not crawled the page, has selected another version of the page, has found conflicting visible job details, or has decided not to show the listing for that query.

Google Search does not publish a fixed formula that guarantees job-panel ranking or a number of applicants per indexed listing. An agency should consequently reject vendor promises such as “page-one Google Jobs placement” or “20 caregiver applicants per month from schema” unless the vendor identifies a separate paid media commitment and measurable source attribution.

How does Google index caregiver job pages?

Google must first discover a caregiver job URL, crawl its accessible content, evaluate the page and its markup, and then decide whether and where to show it in Search. A job page that is blocked, duplicated, expired, redirected incorrectly, or missing visible vacancy details can fail before markup quality becomes relevant.

For a private-pay agency, the practical unit is one durable URL for one real opening: for example, a “Caregiver—Houston, Texas—Full Time” page with the title, city, employment type, duties, qualifications, employer identity, and application link visible to a human visitor. The JSON-LD should describe that same opening rather than inventing pay, availability, or a location that the page does not display.

A technician auditing a careers site typically finds one of four failures:

• The sitemap contains only the general /careers/ page, not individual caregiver vacancy URLs.
• The job page loads vacancy text only after a script or ATS widget runs, leaving inconsistent crawlable content.
• The agency reuses one generic caregiver page while changing the visible city, schedule, and pay without maintaining a distinct, current vacancy record.
• Filled roles remain public, creating stale listings and candidate complaints about applying to jobs that no longer exist.

A documented verification sequence should preserve evidence rather than rely on a verbal assurance: submit or confirm the XML sitemap in Google Search Console; inspect the exact caregiver URL; record whether Google reports the URL as indexed; test the rendered page and structured data; then search a relevant caregiver query and capture the job panel, job card, and final application destination. No such live-URL, Search Console, or screenshot record was supplied for this section, so it should be created before reporting Google Jobs performance.

What JobPosting JSON-LD is needed for Google job search eligibility?

JobPosting JSON-LD should describe a current, individual caregiver opening and align with the vacancy information a candidate can read on the page. The markup should not turn a permanent “join our team” form, a staffing-pool page, or an already-filled shift into a falsely active job listing.

For a home care agency, the implementation should capture the employer, job title, description, date posted, valid-through date where used, employment type, hiring location, and application route. The visible page and structured data should agree on practical details that drive candidate trust: whether the role is full-time or part-time, whether it is in a specific city or home-visit territory, and whether the agency is hiring caregivers rather than advertising client services.

The supplied sources do not provide Google’s supported-property documentation or Schema.org’s JobPosting property specification. Before publishing production markup, the implementer should validate property requirements against the current first-party documentation rather than treating a copied code sample, WordPress plugin output, or ATS template as authoritative.

How should Google Jobs link to an agency careers page?

Google Jobs should usually send the candidate to an agency-owned careers page or a clearly branded ATS application flow that applies to the exact caregiver opening. The destination should let the agency attribute the application, preserve the job details the candidate saw, and avoid forcing the candidate to search again for the role.

The cleanest candidate journey is:

1. The applicant searches for a local caregiver role.
2. Google may show a job card in its job-search panel.
3. The applicant selects the agency’s job card.
4. The click opens the matching agency page or ATS requisition.
5. The applicant applies through the agency-controlled workflow.

The recruiter’s real-world test is simple: open the job card on a phone, follow the application button, and confirm that the title, location, and employer name still match. If the click instead lands on a generic careers homepage, an expired requisition, a broken ATS session, or an unrelated office location, the agency has lost the attribution and conversion benefit of owned job visibility.

Indeed remains a separate channel with its own marketplace experience and reporting. Its hiring-market publications, including Indeed Hiring Lab’s 2026 U.S. jobs and hiring trends report, should not be used as evidence that an agency’s own Google Jobs listing is indexed or attracting applicants.

Frequently Asked Questions

Does JobPosting schema guarantee Google Jobs visibility for caregiver roles?

No. Valid JobPosting markup is an eligibility input for Google’s job-search feature, not a contractual promise that a caregiver role will appear in Google Jobs, rank above competitors, generate applications, or produce a hire.

What should a caregiver job page include for Google Jobs eligibility work?

A caregiver job page should present one current, individual opening with a visible title, city or hiring territory, employment type, duties, qualifications, employer identity, and application link, while its JSON-LD describes those same details.

How can an agency verify whether Google has indexed a caregiver job page?

The agency should submit or confirm its XML sitemap in Google Search Console, inspect the exact caregiver URL, record whether Google reports the URL as indexed, test the rendered page and structured data, and capture the relevant job panel, card, and application destination.

Are Indeed caregiver job posts free?

An agency may be able to publish a caregiver job without paying for promotion, while sponsored placement is a paid option intended to increase visibility; the role’s eligibility, billing model, budget controls, and available features must be verified in the agency’s own employer account.

Why is cost per application not enough for an Indeed campaign?

Cost per application measures form submissions, while cost per qualified applicant and cost per hire measure whether candidates meet the agency’s requirements and ultimately accept the role. A high-volume campaign can still fail to produce someone available for the location, pay rate, schedule, or required start date.

When should a private-pay agency use Google Jobs, Indeed sponsorship, or both?

An agency should prioritize owned Google Jobs visibility for recurring caregiver demand, use Indeed sponsorship for a time-bound coverage gap needing added reach, and combine both when it needs immediate applicants without abandoning its long-term careers asset.

Sources

• Semrush: SERP Features—Jobs
• Indeed Hiring Lab: Indeed’s 2026 U.S. Jobs & Hiring Trends Report

Key takeaways

• JobPosting JSON-LD can support Google Jobs eligibility, but it cannot guarantee display, ranking, applications, or caregiver hires.
• Each active caregiver vacancy needs a crawlable, candidate-visible job page that matches its structured data.
• An XML sitemap and Search Console URL Inspection record are evidence of discovery and indexing work, not proof of Google Jobs placement.
• A Google Jobs click should normally lead to the matching agency careers page or ATS requisition, not a generic careers homepage.
• Indeed reporting and Google Jobs visibility are separate measurements and should be attributed as separate recruiting channels.

Indeed Caregiver Job Posting Cost: What Agencies Actually Pay For

Indeed caregiver recruiting can begin with a free job post, but agencies pay when they choose sponsored visibility; the actual billing method, budget controls, and available features must be confirmed inside the agency’s country-specific Indeed employer account before funds are committed. A sponsored-post budget should be judged by qualified caregivers interviewed, hired, and scheduled—not by application volume alone.

An Indeed caregiver-posting program is the agency’s combination of free job listings, optional paid sponsored distribution, applicant screening, and follow-up workflow used to recruit for specific care shifts.

Which parts of an Indeed caregiver-posting program may be free, and which require paid sponsorship?

An agency may be able to publish a caregiver job without paying for promotion, while sponsored placement is a paid option intended to increase a job’s visibility to relevant job seekers. Free posting does not mean a listing will receive enough visibility or applications to cover an urgent private-pay client schedule.

The practical split is usually:

Indeed’s available employer products and payment options can differ by market and account configuration. The source of truth is the pricing, campaign, and billing screens presented to the agency’s own employer account—not a generic caregiver cost-per-click or cost-per-application benchmark.

How should an agency verify Indeed sponsored-job pricing before approving budget?

Verify the campaign’s billing language, budget cap, duration, and pause controls in writing or within the live Indeed account before publishing the sponsored caregiver role. Do not approve a recruiting budget based on an assumed cost per click, application, or hire.

This verification matters because Indeed ended its pay-per-application pricing model, according to SHRM’s report on the policy change. A home-care agency should therefore avoid using an old “pay only per application” assumption when forecasting spend.

Before launch, the recruiting owner should record:

• The exact job title, service area, pay range, shift hours, and employment type shown to applicants.
• The selected total budget or daily budget and the campaign’s intended stop date.
• The billing event described in the account interface and the payment method attached to the account.
• Whether the job can be paused immediately after a qualified caregiver accepts the shift or role.
• The contact person responsible for replying to applicants during the scheduled coverage window.

This is particularly important for agencies comparing rented Indeed reach with the owned careers-page visibility discussed in the preceding section. A valid agency job page can remain a recruiting asset, while paid sponsorship should have a documented stop condition.

Why is cost per application not the same as cost per qualified caregiver applicant or hire?

Cost per application measures form submissions; cost per qualified applicant measures candidates who meet the agency’s defined minimum requirements; cost per hire measures the spend required to produce an accepted caregiver. These are different calculations because a high-volume campaign can still yield no candidate available for the client’s location, pay rate, schedule, or required start date.

A recruiting coordinator sees this failure mode directly: applications arrive, but candidates may be unable to work the overnight, live outside the service radius, decline the offered pay, lack required experience, or fail to answer the phone. Those applicants can make an Indeed dashboard look productive while the client shift remains uncovered.

Here is an illustrative internal planning example, using disclosed assumptions rather than a universal Indeed benchmark:

The agency should define “qualified” before the campaign runs. For a private-pay caregiver position, that definition might require availability for the advertised shift, ability to travel to the client’s service area, acceptance of the disclosed pay range, and completion of the agency’s first-call screening. The exact qualifications must match the agency’s own hiring and client-care requirements.

How should an agency set a seven-day Indeed budget for an urgent weekend or overnight shift?

Set a capped, seven-day sponsored budget only after comparing it with the agency’s documented internal cost of leaving the client shift unfilled, then stop the campaign when the role is covered or the cap is reached. The purpose is to fill a defined coverage gap within a defined window—not to buy the largest possible applicant count.

For example, an agency could authorize an illustrative $350 seven-day cap for an overnight caregiver opening. If the agency’s internal estimate of an uncovered shift—including coordinator escalation, overtime exposure, service recovery, and client-retention risk—is higher than that cap, the campaign may be commercially reasonable; if it is lower, leadership may choose a narrower test, employee referral outreach, or an internal scheduling solution instead.

The campaign should include a decision rule:

1. Launch only with a specific start date, shift hours, service area, pay range, and minimum qualification screen.
2. Review applicants at fixed intervals during the seven-day window.
3. Pause sponsorship when a candidate is accepted for the applicable role or shift.
4. End the campaign at the total cap if no qualified pipeline emerges.
5. Record why candidates were rejected: geography, availability, pay mismatch, unreachable contact information, experience, or another defined reason.

What improves paid Indeed campaign efficiency for caregiver roles?

Fast response, sufficient screening capacity, precise geography, disclosed pay, and exact shift details improve the chance that sponsored visibility turns into workable caregiver interviews. Paid distribution cannot compensate for a recruiter who replies too late or for a job description that hides the information candidates need to self-select.

For urgent home-care recruiting, the job should state whether the work is weekend-only, overnight, short-notice, recurring, live-in, or a standard daytime schedule. “Caregiver needed” is not enough operational detail for a candidate deciding whether they can cover a client in a particular neighborhood.

Pay transparency also reduces avoidable screening calls when the stated compensation does not fit the candidate’s expectations. Agencies should use the pay information they can actually honor for that role, rather than attracting applicants with a broad range that a scheduler cannot apply to the shift.

Geography needs the same discipline. A metropolitan-area label can generate applications from caregivers whose commuting distance makes a two-hour evening visit or overnight start impractical. Use the service area and any travel expectation that the agency can accurately communicate without disclosing client-identifying information.

Sources

• SHRM: “Indeed’s Pay-per-Application Pricing to End Dec. 18”
• Indeed Hiring Lab: 2026 US Jobs & Hiring Trends Report

Key takeaways

• Indeed job posting may be free, but sponsored caregiver visibility requires a budget whose billing terms must be verified in the agency’s own account.
• A caregiver campaign’s useful metrics are cost per qualified applicant, interview, hire, and filled shift—not cost per application alone.
• A seven-day urgent-shift budget needs a hard cap, a screening owner, and a stop rule when coverage is secured.
• Exact pay, geography, shift hours, and response speed determine whether sponsored applicant volume becomes usable caregiver capacity.

Google Jobs vs. Indeed for Caregiver Recruiting

Google Jobs and Indeed are different caregiver-acquisition paths: Google Jobs can surface an agency’s own eligible job page in Google’s job-search experience, while Indeed provides a job-board listing and optional paid visibility. Neither channel is inherently “higher quality” until the agency measures qualified applicants, interview attendance, offers, retention, cost per qualified applicant, and time to fill by source.

Google Jobs is Google’s job-search experience that may display an eligible employer or ATS job page in search results; Indeed is a job marketplace where employers can publish listings and may pay to promote their visibility. Google Jobs is therefore a discovery layer that can lead directly to an agency-controlled application destination, whereas an Indeed listing begins inside a third-party marketplace.

The earlier section explains why JobPosting structured data is an eligibility input—not a promise of Google Jobs inclusion, ranking, applicants, or hires. The next section addresses the page-content, markup, update, and expiration work needed to keep an owned caregiver job page eligible and accurate.

How do Google Jobs and Indeed affect caregiver applicant quality?

Google Jobs and Indeed should be judged by downstream caregiver outcomes, not by application volume or a blanket claim that one source produces better candidates. A private-pay agency should score each source against the same qualification, attendance, offer, retention, cost, and fill-time definitions.

Use a source-quality scorecard for every caregiver requisition:

• Qualified applicant rate: applicants meeting the agency’s stated service-area, availability, credential, experience, transportation, and wage requirements ÷ applicants from that source.
• Interview-show rate: candidates who attend the scheduled interview ÷ candidates scheduled.
• Offer rate: offers issued ÷ interviewed candidates, with a separate offer-acceptance measure of accepted offers ÷ offers issued.
• 30-, 60-, and 90-day retention: caregivers still actively employed at each interval ÷ hires from that source, where the agency can lawfully collect and use the data.
• Cost per qualified applicant: channel spend ÷ qualified applicants, rather than spend ÷ total applications.
• Time to fill: elapsed time from approved requisition to accepted offer or completed onboarding, using one agency-wide definition.

A technician-equivalent recruiting failure is visible in the disposition log: a sponsored listing produces applications, but candidates cannot work the listed overnight hours, live outside the service radius, lack the required credential, decline the wage, or do not attend the interview. That is not proof that Indeed is low quality; it is evidence that the agency needs source-level qualification data and a more specific job description.

The same caution applies to Google Jobs. A candidate who searches for “caregiver jobs near me” and reaches an owned careers site may be highly intentional, but intent alone does not confirm availability for a split shift, dementia-care competency, weekend rotation, or the ability to travel between private-pay clients. Google job results are a recognized search-results feature, not a hiring-quality label. Semrush

Why should a private-pay agency send candidates to its own careers page instead of relying only on Indeed?

An agency-owned careers page or ATS gives a private-pay home-care agency control over the job facts, screening flow, candidate records, and closed-job removal that a rented job-board listing alone cannot provide. It also creates a durable destination that Google Jobs, organic search, referrals, and paid campaigns can all use.

That control matters when the role is operationally narrow. An agency can state the exact service area, pay range, daytime or overnight pattern, minimum weekly availability, weekend requirement, client-care needs, and required credential before a caregiver applies. It can then ask job-related screening questions in its own ATS and track whether the applicant was qualified, scheduled, interviewed, offered, hired, and retained.

Owned does not mean maintenance-free. The failure modes are stale caregiver listings, a job page saying one wage while the application says another, an open listing after the shift is filled, and an application form that breaks on a mobile phone. Stale or misleading job communications also create trust risk; the Federal Trade Commission warns that scammers impersonate known companies and recruit through job platforms, making accurate employer-controlled communications especially important. Federal Trade Commission

When should a private-pay agency use Indeed sponsored jobs, Google Jobs, or both?

A private-pay agency should prioritize owned Google Jobs visibility for recurring caregiver demand, use Indeed sponsorship for a time-bound coverage gap that needs added reach, and combine both when the agency needs immediate applicants without abandoning its long-term careers asset. Sponsored visibility can accelerate exposure, but it is a promotion tactic rather than a guaranteed hiring outcome.

For recurring daytime hiring—such as continuously adding caregivers for weekday private-pay cases within a defined service area—the agency should build and maintain individual, accurate owned job pages. The listing should distinguish daytime availability from evenings, name the applicable service area, identify credential requirements, and state the wage information the agency intends to offer. This creates a reusable application destination while the agency measures whether Google-origin applicants pass screening and remain employed.

For an immediate overnight, weekend, or high-acuity gap, the decision changes. If a client needs coverage quickly, the recruiter may need a short, controlled Indeed sponsored campaign because the agency cannot wait for owned visibility to develop. The listing should identify the actual shift pattern, location or travel area, care requirements, required credentials, wage, and response expectations; otherwise, the budget can buy inquiries that cannot cover the shift.

A combined approach is appropriate when the agency has a valid owned job page but needs incremental visibility now. Use the sponsored Indeed campaign with a fixed review window, direct applicants into the workflow that preserves source attribution where possible, and stop or revise spend when the scorecard shows low qualification or interview-show rates. Indeed Hiring Lab’s reporting on labor-market conditions can provide broader context, but agency-specific hiring decisions still require local source and requisition data. Indeed Hiring Lab

Sources

• SHRM: Indeed’s Pay-per-Application Pricing to End Dec. 18
• Semrush: SERP Features—Jobs
• Federal Trade Commission: Scammers impersonate well-known companies and recruit for fake jobs
• Indeed Hiring Lab: 2026 US Jobs & Hiring Trends Report

Key takeaways

• Google Jobs supports owned-job-page discovery, while Indeed provides a job-board marketplace and optional paid promotion.
• An agency cannot credibly call either source higher quality without measuring qualification, interview attendance, offers, retention, cost per qualified applicant, and time to fill.
• Owned careers pages give agencies control over job accuracy, screening, ATS records, and the candidate destination across multiple acquisition channels.
• Indeed sponsorship is best treated as time-bound reach for urgent coverage needs, not as a guaranteed applicant or hiring result.
• The final JobPosting Schema vs. Indeed Recruiting Decision section should use the same source-quality scorecard, while the next section should define the technical implementation and maintenance requirements for owned job pages.

JobPosting Schema Requirements and Google Guidelines

Google requires a caregiver job page’s structured data to describe the same real, currently open role that applicants can read and apply for on the page. JobPosting markup can support Google job-search eligibility, but inaccurate pay, location, dates, or application links can cause the listing to be removed from Google’s job experience or trigger a manual action under Google’s job-posting policies.

JobPosting is Schema.org structured data that identifies a specific open position and communicates its title, employer, work location, posting date, compensation, employment type, and expiration details to search systems. Google’s JobPosting documentation distinguishes required properties from recommended enhancements; the agency should treat both as publishing controls, not merely developer fields.

Which JobPosting properties does Google require, recommend, and expect to match the visible caregiver job page?

Google requires title, description, datePosted, hiringOrganization, and jobLocation for non-remote jobs, while validThrough, baseSalary, employmentType, qualifications, and direct-application details are recommended properties that improve completeness when they are accurate. Every material fact in the JSON-LD—including the wage, caregiver duties, employer name, location, and application destination—must be visible or otherwise clearly supported on the corresponding job page.

Google’s job posting content policies require job details to be accurate, prohibit misleading or expired listings, and require a direct path for the applicant to apply. A technician commonly finds the failure in the CMS workflow rather than the JSON syntax: the page says “$18–$22 per hour,” while the markup still sends “$16 per hour,” or an ATS redirect opens a generic careers page rather than the advertised caregiver requisition.

The role description should identify the actual work: personal care, companionship, dementia-care experience, transfer assistance, driver’s-license requirements, weekend availability, or required credentials. Do not add a credential, guaranteed hours, mileage reimbursement, health insurance, or shift differential to markup merely because it appears on another agency page or is available only to a subset of hires.

How should a home-care agency mark up caregiver pay, pay ranges, employment type, and benefits?

A caregiver pay range should be marked up as baseSalary only when the range is genuinely available for the specific job and is shown on the visible job page; use ISO 4217 currency such as USD and an hourly unit such as HOUR. Employment type should reflect the actual hiring arrangement, while benefits should remain in the visible description unless the agency can substantiate the eligibility terms and conditions.

A compliant illustrative hourly-pay structure uses Schema.org’s MonetaryAmount and QuantitativeValue pattern:

"baseSalary": {
  "@type": "MonetaryAmount",
  "currency": "USD",
  "value": {
    "@type": "QuantitativeValue",
    "minValue": 18,
    "maxValue": 22,
    "unitText": "HOUR"
  }
},
"employmentType": ["PART_TIME", "FULL_TIME"]

The $18–$22 range above is an implementation example, not a market-pay claim. The range must also appear plainly on the page, for example: “Caregiver pay: $18–$22 per hour, based on experience, shift requirements, and applicable credentials.” Schema.org defines baseSalary as the base salary for the job and employmentType as the employment-type classification; neither property converts an uncertain wage or conditional benefit into a firm offer.

Benefits language deserves a separate editorial review. “Health insurance available” can be misleading if eligibility depends on scheduled hours, waiting periods, location, or employment classification; state the condition on the job page or omit the claim. Current state and local pay-transparency requirements vary by jurisdiction, so the agency should have counsel or a qualified HR/payroll reviewer validate the current rules applicable to the job location rather than treat schema guidance as legal advice; the U.S. Department of Labor maintains a state-law resource directory but does not replace jurisdiction-specific legal review.

How should caregiver JobPosting schema handle a branch office, client-service territory, multiple locations, and travel between homes?

Use jobLocation for the real place or places where the caregiver performs the job, and describe a client-service territory in visible job copy rather than presenting a service-area claim as a false office address. A branch office belongs in jobLocation when the caregiver genuinely reports there or the job is assigned to that location; it is not automatically the job location simply because it is the agency’s nearest administrative office.

For example, an agency may operate from 100 Main Street, Austin, TX while hiring caregivers who travel to clients across Austin and nearby communities. If the caregiver starts shifts at client homes and does not report to the office, the page should say “Travel to client homes throughout Austin and surrounding communities; reliable transportation required,” while the markup should use the most precise truthful work-location model supported by the role.

For a genuinely multi-location opening, use multiple jobLocation entries only when one requisition is truly open across those specific places. Do not publish one caregiver opening with every branch address merely to expand map exposure; Google’s policies require the marked-up location to represent the job applicants are being offered. Schema.org’s jobLocation property supports a Place, while applicantLocationRequirements identifies where applicants may be located for a remote role—not a mobile caregiver’s service territory.

A role that is fully remote may use Google’s remote-job model with jobLocationType set to TELECOMMUTE and applicantLocationRequirements; that model is generally inappropriate for in-home care because the caregiver’s essential work occurs in a client’s residence. Calling an in-home caregiver position “remote” is a common classification error: the employee may receive schedules electronically, but the service itself is performed on site.

When should an agency set validThrough, update posting dates, or remove a filled caregiver job?

Set validThrough to the date the agency expects to stop accepting applications for that specific caregiver opening, update the listing when its material facts change, and remove JobPosting markup or the page when the role is filled or no longer accepting applicants. Google specifically instructs employers to remove expired jobs and not leave expired roles available to users.

Schema.org defines validThrough as the date after which the job posting is no longer valid. It is not a cosmetic “refresh” field: extending it while the agency has stopped reviewing candidates creates the same applicant experience problem as a ghost posting.

A practical owner workflow is:

• Publish datePosted when the individual requisition becomes publicly available, using ISO 8601 formatting required by Google’s JobPosting guidance.
• Change visible copy and markup together when pay, employment type, branch assignment, shift expectations, or application URL changes.
• Remove the job page, remove its JobPosting markup, or make the page clearly unavailable when the agency fills the opening.
• Test the live URL with Google’s Rich Results Test after a CMS, ATS, or template change.
• Keep a human owner responsible for checking whether a caregiver listing still accepts applications before its validThrough date.

Agency-specific hiring language should be reviewed separately from schema eligibility. Licensing or certification requirements, background-check and drug-screen disclosures, driving-record standards, physical-demand language, accommodation statements, and equal-opportunity wording can be necessary for the agency’s hiring process, but they should be approved by the appropriate HR, compliance, and legal stakeholders—not inserted because a schema validator accepts the page.

Sources: Google Search Central, JobPosting structured data and job posting content guidelines, accessed September 29, 2026; Schema.org, JobPosting, baseSalary, employmentType, jobLocation, applicantLocationRequirements, and validThrough, accessed September 29, 2026; U.S. Department of Labor, state labor-office contacts, accessed September 29, 2026.

Key takeaways

• Google-required caregiver JobPosting facts must match the visible job page and lead applicants to a functioning direct application route.
• Mark up hourly caregiver wages only when the exact range, currency, unit, and conditions are supported by the live listing.
• A home-care service territory is not an office address, and a mobile in-home caregiver role is not automatically a remote job.
• validThrough must reflect the real application window, and filled caregiver listings should be removed or have their JobPosting markup removed promptly.
• Licensing, screening, equal-opportunity, and pay-transparency language requires jurisdiction-specific HR or legal review beyond schema validation.

How to Add JobPosting Schema to a Home Care Job Page

A maintainable caregiver JobPosting schema implementation publishes one current, crawlable job-detail URL for each actively recruitable opening, with JSON-LD generated from the same job record that supplies the visible page copy. The agency must also assign an operational owner to update, expire, validate, and remove listings; valid markup at launch is not the same as an accurate job inventory over time.

JobPosting structured data is JSON-LD markup that identifies a specific live vacancy and communicates its job details to Google in a machine-readable format. As covered in the earlier requirements section, the structured data must represent the visible job page rather than a generic “we are hiring caregivers” message or a stale ATS record.

JobPosting JSON-LD for caregiver job listings

A caregiver JobPosting JSON-LD record should contain the role title, description, posting and expiration dates, employer, location, employment type, pay where displayed, application destination, and a stable internal job identifier. Google recommends JSON-LD for JobPosting markup and requires agencies to keep the structured data aligned with the content job seekers can actually read on the page (Google Search Central).

The page should visibly state the same facts that appear in the markup. For example, if the JSON-LD says “Caregiver — Day Shifts,” “Full-time,” “Houston, Texas,” and “$18.50 per hour,” the heading, job-details panel, and application page should not instead describe a part-time role across an undefined service area.

Below is a non-production example. Its employer name, URL, pay rate, location, dates, and identifier are placeholders that must be replaced with the agency’s actual live job record before publishing.

<!-- Visible page copy -->
<h1>Caregiver — Day Shifts</h1>
<p>Full-time caregiver position serving clients in Houston, Texas.</p>
<p>Pay: $18.50 per hour.</p>
<p>Apply through Example Home Care's online application.</p>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Caregiver — Day Shifts",
  "description": "<p>Full-time caregiver position serving clients in Houston, Texas.</p><p>Pay: $18.50 per hour.</p><p>Apply through Example Home Care's online application.</p>",
  "datePosted": "2026-10-05",
  "validThrough": "2026-11-05T23:59:59-05:00",
  "employmentType": "FULL_TIME",
  "identifier": {
    "@type": "PropertyValue",
    "name": "Example Home Care",
    "value": "caregiver-day-houston"
  },
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Example Home Care",
    "sameAs": "https://www.examplehomecare.com",
    "logo": "https://www.examplehomecare.com/logo.png"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Houston",
      "addressRegion": "TX",
      "addressCountry": "US"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "value": 18.50,
      "unitText": "HOUR"
    }
  },
  "directApply": true
}
</script>

The implementation failure a recruiter usually sees is not malformed braces; it is a technically valid listing that says “Caregiver” while the visible page gives no shift, city, pay, or current application route. That disconnect creates an unreliable applicant experience and can make the listing ineligible for the job-search experience under Google’s job-posting policies (Google Search Central).

Individual job pages for Google Jobs

Each open caregiver requisition needs its own canonical, indexable job-detail page because JobPosting markup describes a particular vacancy, not an agency’s permanent recruiting message. A generic hiring page can remain useful for employer branding, but it should not substitute for separate URLs for “Weekend Caregiver — Katy,” “Overnight Caregiver — Houston,” and “Caregiver — Day Shifts.”

Google’s guidance says a job-posting page must describe a single job and must be available to users and Googlebot (Google Search Central). Put a self-referencing canonical tag on the preferred URL, allow crawling in robots.txt, avoid noindex, and ensure the page returns a successful HTTP response without requiring an applicant login.

A technician should test the page without relying on the browser session used to build it. If opening a job link in a private browser window produces only a loading spinner, redirects to a generic careers hub, or hides the pay and location until a script runs, treat that as a crawlability issue to resolve before launch.

ATS integration for JobPosting schema

A CMS, ATS, careers-site vendor, or custom development team can generate JobPosting JSON-LD by mapping fields from the job record into both the page template and the structured-data template. The maintainable pattern is one source record for title, requisition ID, description, pay, employment type, location, date posted, expiration date, and status—not separately edited website copy and schema code.

Demand written answers to these scope items before approving a low-cost “schema install”:

• A reusable individual caregiver job-page template, not markup pasted onto one generic hiring page.
• Field mapping from the ATS or CMS record to visible page text and JSON-LD.
• A canonical URL rule for every requisition and a rule for duplicate location or shift variants.
• Publicly accessible job-detail URLs that do not require login, cookies, or application-start actions to reveal the description.
• XML sitemap generation or updates for job URLs, following Google’s sitemap guidance (Google Search Central).
• Indexing API handling where the vendor uses it; Google documents the Indexing API specifically for job-posting and livestreaming pages (Google Search Central).
• QA before publication, including rendered-page review and structured-data validation.
• A filled, cancelled, or expired-job workflow that removes the page or removes its JobPosting markup promptly.
• A named agency employee—not only a vendor help desk—responsible for approving job status and escalation.

The operational risk is a feed that creates pages successfully but never receives closure events from the ATS. That is how a caregiver can apply to an already-filled overnight shift weeks after the scheduler closed it. The next maintenance section addresses the recurring review process because publishing valid markup does not keep listings accurate.

Google Rich Results Test for JobPosting schema

Before launch, test the code, the rendered content, and the public URL separately: the Rich Results Test checks Google eligibility, Schema Markup Validator checks broader schema syntax, Search Console reports site-level JobPosting issues, and URL Inspection checks Google’s view of a specific live page. No single test proves all four conditions.

Use this release workflow:

1. Paste the staging-page code or public URL into Google’s Rich Results Test and resolve detected JobPosting errors before release.
2. Run the same markup through the Schema Markup Validator when diagnosing vocabulary, nesting, or JSON syntax issues that may not be rich-result eligibility errors.
3. Compare the rendered page shown to users with the JSON-LD values for title, location, pay, description, dates, and application route.
4. Publish the canonical URL, confirm it is included in the sitemap or submitted through the approved job-update process, and request recrawling when needed through URL Inspection.
5. Review Google Search Console’s Job Posting enhancement reporting after Google discovers the pages, then investigate errors by URL rather than assuming a template fix reached every job record (Google Search Central).

A clean Rich Results Test does not confirm that the page is indexed, that the vacancy is still open, or that an ATS redirect preserves the application path. The final live check is to open the exact canonical job URL on a mobile device, read the visible details, submit a test application only where the agency’s process permits it, and verify that the requisition remains open in the ATS.

Key takeaways

• Each actively recruitable caregiver opening should have one crawlable, canonical job-detail page with visible details that match its JobPosting JSON-LD.
• The safest implementation maps ATS or CMS job fields into both page copy and structured data from one record.
• Rich Results Test, Schema Markup Validator, Search Console, and URL Inspection answer different QA questions and should be used together.
• A vendor scope must include job creation, canonical URLs, sitemap or Indexing API handling, QA, monitoring, and filled-job removal.
• A named agency owner must keep caregiver vacancies current after launch, as valid markup alone does not prevent stale listings.

Sources

• Google Search Central: JobPosting structured data
• Google Search Central: Build and submit a sitemap
• Google Search Central: Indexing API
• Google Rich Results Test
• Schema Markup Validator
• Google Search Console Help: URL Inspection Tool

Maintaining Caregiver Job Listings in Google Jobs

Caregiver jobs shown in Google Jobs must be removed or expired as soon as the agency stops accepting applicants, and every live page must match the current ATS record, visible pay, location, schedule, and qualification requirements. JobPosting schema maintenance is the controlled process of keeping a job page, its structured data, its application destination, and its recruiting status aligned from requisition approval through closure.

Google’s JobPosting documentation instructs employers to remove or expire postings that are no longer accepting applications. For a private-pay home care agency, that means a listing cannot remain live merely because the agency expects similar caregiver demand later; reopen it only when a specific, applicant-ready requisition exists.

How do you remove filled, paused, duplicated, or closed caregiver jobs from Google Jobs?

When a caregiver opening is filled, duplicated, paused, or closed to applicants, the agency should immediately close the ATS requisition, remove or expire the job page’s JobPosting markup, stop paid campaigns, and verify that the public application path no longer accepts applicants. Google says employers should remove the JobPosting markup from jobs that are no longer open or use an expiration date for postings that have expired. Google Search Central

A recruiter should not treat “filled” as an administrative note to be handled at the end of the week. The failure pattern is familiar: a candidate sees a caregiver role in Google Jobs, applies, then receives either no response or a message that the position was filled days earlier. NPR’s reporting on ghost-job concerns describes a broader job-market trust problem; it does not establish that any specific home care agency has posted ghost jobs. NPR

An operational handoff should follow this sequence:

Requisition opened
        ↓
Recruiter confirms applicant-ready details
        ↓
ATS record and job page publish
        ↓
Website/CMS owner validates visible content and JSON-LD
        ↓
Details changed? ── Yes → Update ATS, page, markup, and campaigns → Validate again
        ↓ No
Role paused or filled? ── Yes → Close intake → Remove/expire markup → Stop campaigns → Validate removal
        ↓ No
Continue scheduled audit

How should an agency use the JobPosting validThrough date?

validThrough should be an accuracy control tied to the last date an agency will accept applicants, not a technical field copied forward indefinitely. Google identifies validThrough as the date after which the job posting is no longer valid and directs employers to use it for expired positions. Google Search Central

The field should come from the same requisition status that controls application acceptance. If a branch manager pauses hiring because a client case ends, the recruiter should not leave an old future validThrough value in place while the ATS is closed.

A practical control is to require one of two closure actions:

• Known closing date: retain the page until that date, with the correct validThrough value and an active application path.
• Unexpected pause, fill, duplicate, or withdrawal: remove the markup or expire the posting immediately rather than waiting for a previously entered date.

A forgotten expiration field creates a ghost-job risk because the structured data signals an opening while operations has stopped taking applications. The visible page, ATS form, Google-facing markup, and any Indeed sponsorship should all be governed by the same status decision.

When do caregiver pay, schedule, territory, branch, or credential changes require updates?

Any change a candidate would use to decide whether to apply requires an update to both the visible caregiver job page and its matching JobPosting structured data before the revised listing is promoted. Google requires structured data to represent the job accurately and warns against markup that does not reflect the content available to users. Google Search Central

For example, assume an agency opens Caregiver Job ID CG-184 at its North Branch for $20–$23 per hour. A revised staffing plan moves the role to the South Branch and changes the approved range to $22–$25 per hour.

The required update is not limited to editing a headline:

• Visible page: change the displayed pay range, branch name, service territory, commute expectations, available shifts, and application instructions.
• JSON-LD: change the baseSalary range and the relevant jobLocation or applicant-location information so markup matches the revised page.
• ATS: update requisition CG-184, location, compensation fields, recruiter assignment, screening questions, and branch routing.
• Campaigns: revise Indeed copy, sponsored-job budget targeting, source links, and any branch-specific landing-page references; pause the prior campaign if it points to the obsolete role.
• Validation: test the updated live URL and confirm that an applicant reaches the South Branch application workflow.

If CG-184 is subsequently filled, the agency should close the ATS record, stop the campaign, remove or expire the JobPosting markup, and remove the public application option. Leaving the page indexed with an active-looking wage range after the requisition is closed undermines the candidate’s ability to make an informed application decision.

Who owns caregiver job-status changes across recruiting, operations, marketing, the ATS vendor, and web development?

The recruiter should own the decision that a caregiver requisition is open, changed, paused, or filled, while the branch manager confirms operational facts and the website or ATS owners execute and validate publication changes. No external developer or ATS vendor should be the final owner of job accuracy because neither party knows whether the agency is still accepting applicants.

Use a responsibility assignment matrix that makes one person accountable for each status change:

Activity                                      Recruiter  Branch mgr.  Operations lead  CMS owner  ATS admin  External developer
Approve requisition as applicant-ready        A/R        C            C                I          I          I
Confirm wage, schedule, territory, credential R          A/R          C                I          I          I
Change status to paused or filled             A/R        R            C                I          C          I
Update ATS requisition fields                 C          I            I                I          A/R        C
Update visible careers-page content           C          I            I                A/R        C          C
Update or remove JSON-LD                      I          I            I                A/R        C          R
Stop or revise Indeed and other campaigns     A/R        I            C                C          C          I
Validate live page and structured data        C          I            I                A/R        C          R
Escalate integration or template defect       I          I            I                R          A/R        A/R

A = accountable; R = responsible; C = consulted; I = informed

The agency should also maintain a recurring audit log. A daily review is appropriate when caregiver requisitions change rapidly; a weekly review is a minimum operational check for agencies with lower posting volume. The review should compare ATS status to the public URL rather than checking the website in isolation.

Job ID | URL | ATS status | validThrough | Visible pay/location | Structured-data validation | Last reviewer | Corrective action
CG-184 | /careers/... | Open | [date] | $22–$25; South Branch | Pass / issue noted | [name] | [action and owner]

Sources

• Google Search Central: JobPosting structured data
• NPR: “Ghost jobs” are everywhere — here’s how to avoid falling for them

Key takeaways

• A filled, paused, duplicated, or withdrawn caregiver requisition should trigger ATS closure, campaign updates, and immediate removal or expiration of its JobPosting markup.
• validThrough is a live recruiting control that should reflect the true final application date, not a date left behind after operations closes the role.
• A pay, branch, territory, shift, or credential change requires matching revisions on the visible page, in JSON-LD, in the ATS, and in active campaign copy.
• The recruiter owns job-status decisions, but the CMS owner and ATS administrator must have documented responsibility for publishing and validation.
• A recurring ATS-to-page audit log helps prevent stale caregiver listings from becoming candidate-trust problems.

Why Caregiver Jobs Do Not Appear in Google Jobs

A caregiver job can be live on an agency website yet fail to appear in Google Jobs because Google cannot crawl it, cannot confirm that the visible page and JobPosting markup agree, sees it as expired or duplicated, or determines that the implementation violates structured-data policies. Valid markup is not a publication deadline or a guarantee of inclusion, so agencies should diagnose the live page, technical signals, and Search Console evidence before assuming a Google-side failure.

JobPosting structured data is machine-readable information on an individual job-detail page that describes a currently available role and may make that page eligible for Google job-search experiences. Google requires structured data to represent the page’s visible content accurately and warns that markup must not be misleading, hidden from users, or used for content that is not actually available. Google’s structured-data policies apply alongside the job-posting requirements covered in the earlier requirements and maintenance sections.

When JobPosting schema markup does not match the visible job page

A caregiver listing can be ineligible or unreliable when its JSON-LD says the role is open, paid at a stated range, or located in a stated city while the candidate-facing page says something different—or no longer offers an application path. Google’s policies require structured data to be representative of the visible page and prohibit misleading markup. Google Search Central

The failure is usually operational rather than syntactic. A recruiter fills a “Caregiver—North Houston” requisition in the ATS, but the careers page retains validThrough, the schema retains the old wage range, and the Apply button still opens an application form. A Rich Results Test can show technically valid JobPosting markup even though the listing is materially stale.

For a composite example, consider a private-pay agency whose scheduler marks a weekday caregiver shift filled. The page still says “Now hiring,” accepts applications, and exposes an unchanged future validThrough value in JSON-LD. The remediation sequence is:

1. Close or pause the requisition in the ATS and confirm that the candidate-facing application flow no longer accepts applications for that specific opening.
2. Remove the job-detail page or change it into a clearly closed page without active JobPosting markup, following Google’s job-posting removal guidance.
3. Update the visible title, location, pay, schedule, and application destination before updating the corresponding JSON-LD for any replacement opening.
4. Validate the rendered live URL with Google’s Rich Results Test, then document the change in the listing-maintenance process described earlier in this article.

Do not treat source-code JSON-LD as the only truth. A technician should inspect both View Source and the rendered DOM because an ATS, tag manager, or JavaScript component may insert, overwrite, or suppress job data after the initial HTML response.

Why expired caregiver jobs remain indexed in Google

A closed caregiver requisition can remain indexed or continue appearing temporarily because Google must recrawl, reprocess, and update its understanding of the URL; an agency cannot supportably promise when that will happen. What the agency can control is whether the live page, HTTP response, robots rules, canonical signal, application flow, and structured data accurately communicate that the job is no longer open. Google job-posting documentation

Indexing and job-search eligibility are related but separate observations. A URL may remain in ordinary Google Search after the agency has removed JobPosting markup, while a page with valid markup may not be selected for a job-search result. Google’s documentation describes structured data as an eligibility mechanism and does not guarantee that a rich result will be shown. Google Search Central

A practical troubleshooting decision tree should start with live job status, not with schema:

• Is the caregiver role genuinely accepting applications? Test the candidate path through to the ATS confirmation screen, not merely the presence of an Apply button.
• What HTTP response does the canonical job URL return? Record whether it returns 200, redirects, or returns 404/410.
• Can Google crawl and index it? Check robots.txt, meta robots, X-Robots-Tag, authentication barriers, and the canonical URL.
• Does visible content match the rendered JSON-LD? Compare title, branch or service territory, employment type, wage, posting status, and application destination.
• Does the markup validate? Save the Rich Results Test output, including warnings and detected item details.
• What does Search Console show? Use URL Inspection and the Job Postings report where available; review indexed status, last crawl information, detected structured data, and enhancement issues.
• Is another URL representing the same role? Compare ATS URLs, branch pages, tracking parameters, feed destinations, and aggregator copies before publishing a replacement.

The technical evidence set should include a dated page-source capture, rendered-DOM capture, Rich Results Test result, Search Console URL Inspection export or screenshot, XML sitemap timestamp, redirect-chain result, and screenshots of the applicant journey. That record turns an apparent “Google Jobs delay” into a documented status-control fix rather than a one-time patch.

Google Jobs manual action for job postings

Google can take manual action against structured-data rich results when job-posting markup violates spam policies, including misleading content, markup that does not match the visible page, or practices intended to manipulate search presentation. A manual action can affect a site’s eligibility for rich results and should be addressed through Search Console with a documented correction and reconsideration request where applicable. Google Search Console Manual Actions documentation

For caregiver recruiting, the highest-risk pattern is a page that advertises a specific open role to search engines while directing candidates to a generic talent-pool form, a different location, an expired role, or an unrelated job. Google’s structured-data policies explicitly require that marked-up content be visible to users and not be misleading. Google’s spam and structured-data policies

A technician investigating a suspected action should not delete JSON-LD blindly. First, preserve the evidence, identify every template and ATS feed producing the affected markup, correct the candidate-facing page and structured data together, and verify that expired jobs are removed through the maintenance workflow already defined earlier in this article. Then review the Manual Actions report in Search Console, which is Google’s authoritative place to determine whether a manual action exists. Google Search Console

How duplicate caregiver job listings affect Google Jobs

The same caregiver opening can become duplicated when an ATS, agency careers site, branch-location page, tracking URL, aggregator feed, and job board each publish a separate version of one requisition. Duplicate versions split crawl signals, create conflicting pay or location details, and can leave candidates applying to an opening that another system has already closed.

For example, job ID CG-HOU-WKDY may appear on an ATS-hosted URL, an agency-owned careers page, separate Houston and Katy location variants, an Indeed feed, and tracking-parameter URLs used in recruiting campaigns. Indeed distribution does not make the agency page a Google duplicate by itself, but multiple crawlable agency or ATS URLs that claim to be the same opening create an identity problem that the agency must control.

Use these controls for a single caregiver requisition:

• Assign one stable internal job ID and retain it in the ATS, CMS record, feed record, and audit log.
• Select one canonical candidate-facing URL for each actively recruitable opening and implement a consistent canonical signal, following Google’s duplicate-URL consolidation guidance.
• Ensure that location variants are separate jobs only when the candidate is applying for materially distinct openings with distinct locations, schedules, or requisition identities.
• Redirect or retire tracking URLs where possible; tracking parameters should not create competing indexable job-detail pages.
• Close the ATS, careers-page, feed, and sitemap versions from the same status event rather than relying on separate manual edits.

The useful question is not “When will Google publish this caregiver job?” Google does not provide an agency-controlled publication deadline. The useful question is: “Can we prove that one canonical, crawlable, candidate-accessible URL accurately represents one currently open requisition?”

Key takeaways

• A valid JobPosting object can still be ineligible or unreliable when its visible caregiver-job page, application flow, or status contradicts the markup.
• A filled caregiver role may remain visible temporarily until Google recrawls it, but agencies should immediately correct the live page, markup, sitemap, and application path.
• Search Console Manual Actions is the authoritative place to check whether Google has applied a structured-data-related manual action.
• One requisition should have one controlled job identity and canonical candidate-facing URL across the ATS, careers site, feeds, and location variants.
• A defensible missing-listing diagnosis uses live-status testing, HTTP and robots checks, canonical review, rendered-content comparison, validation output, Search Console evidence, and duplicate analysis.

JobPosting Schema vs. Indeed Recruiting Decision: Build a Measurable Channel Mix

JobPosting schema and Indeed should be managed as a single caregiver-recruiting portfolio: owned Google Jobs visibility builds a measurable applicant path to the agency’s careers site, while Indeed sponsorship buys time-bound reach where qualified-applicant supply is below target. Compare both channels on qualified applicants, interviews, hires, response speed, and filled roles—not applications or media spend alone.

A qualified caregiver applicant is an applicant who meets the requisition’s documented minimum requirements—such as service-area availability, stated credential, work authorization, shift fit, and pay acceptance—and can be contacted for screening. Google says JobPosting structured data can make job pages eligible for job-search experiences, but eligibility is not a promise of display, rank, clicks, applications, or hires; use the implementation and listing-maintenance controls covered in earlier sections to keep the owned channel measurable.

How should an agency measure Google Jobs and Indeed recruiting performance?

Use one ATS source taxonomy, one definition of “qualified,” and the same cohort dates for every channel. A recruiter should not be able to select a vague “online” source after the fact, because that turns a Google Jobs applicant, an Indeed applicant, and a direct careers-page applicant into the same unmeasurable bucket.

Set the ATS required source field to one of these controlled values:

Use UTMs only as supporting evidence, not as a replacement for an ATS source field. A workable naming standard is utm_source=indeed, utm_medium=organic or sponsored, and utm_campaign=[branch]-[requisition]; Google-owned job-page traffic can use a distinct landing-page or referral classification where the analytics and ATS integration support it. The ATS source value should be locked after initial capture, with any correction logged by a named user and reason.

Track these formulas by application cohort date—the date the candidate first applied—not by the date payroll begins:

• Cost per qualified applicant (CPQA) = total source cost ÷ qualified applicants from that source.
• Cost per interview = total source cost ÷ completed interviews from that source.
• Cost per hire = total source cost ÷ hires from that source.
• Time to qualified applicant = timestamp of first qualified applicant − job publication timestamp.
• Time to fill = accepted-offer timestamp or filled-status timestamp − requisition-open timestamp.
• Qualified-applicant rate = qualified applicants ÷ total applications.
• Interview-show rate = completed interviews ÷ scheduled interviews.

A practical failure mode appears when an applicant starts on Indeed, abandons the application, then later applies directly through the careers site. Preserve the first-touch source and record the final application route separately; otherwise the agency will over-credit direct traffic and understate the paid campaign’s contribution.

How do you calculate cost per qualified applicant when Google Jobs has no media charge?

Google Jobs visibility has no media line item, but the owned channel is not cost-free: allocate implementation, careers-site or ATS work, content operations, listing audits, and recruiter handling time to the live requisitions it supports. Indeed costs should include actual sponsored-job charges and the same downstream recruiter labor, so the comparison does not penalize only one channel.

Use this fully loaded owned-channel formula:

Owned-channel cost = allocated implementation cost + maintenance cost + job-page/content cost + ATS or careers-site cost + recruiter screening cost attributable to owned applicants.

For a planning model, amortize one-time implementation across the agency’s selected measurement period and active requisitions. The dollar figures below are illustrative internal planning assumptions prepared for this article on September 29, 2026, not published Indeed pricing; Indeed’s billing model and budget options must be confirmed in the employer account before launch, particularly because reported pricing models can change (SHRM).

This dashboard example is an anonymized calculation template, not a benchmark. Its point is that the channel with more applications does not necessarily produce more qualified caregivers, interviews, or fills.

When is JobPosting schema a justified foundational investment?

JobPosting schema is justified when an agency has recurring caregiver demand, stable individual job-detail pages, an ATS or careers-site workflow that can capture source data, and an owner who can remove or correct filled and changed listings. It is a foundation for durable discoverability, not an emergency substitute for a recruiter who cannot answer applicants promptly or a job post that omits wage, territory, schedule, and minimum requirements.

Technicians and recruiters see the operational version of this problem as duplicate requisitions, a caregiver applying to an already-filled shift, or a phone number that reaches a general office queue. Those defects should be corrected through the listing-maintenance and troubleshooting processes described earlier before interpreting channel performance.

How should agencies allocate Indeed budget while protecting Google Jobs visibility?

Keep owned listings accurate and always available, then use Indeed spend as a variable, capped response to a documented coverage gap. Set a qualified-applicant target per requisition—for example, the number needed to produce the agency’s expected interview and acceptance pipeline—and pause, raise, or redirect spend based on that target rather than raw applicant volume.

For each sponsored campaign, document:

• the requisition ID, branch, service territory, shift pattern, wage disclosure, and campaign start and stop timestamps;
• the maximum authorized spend and the approval owner;
• the qualified-applicant target and maximum acceptable CPQA;
• the recruiter assigned to first contact and the expected response window;
• the reason for sponsorship: urgent coverage, hard-to-staff geography, new-market launch, or a measured owned-channel shortfall.

An executive should review the portfolio monthly with the recruiting operations owner—not simply approve an Indeed invoice. The review should compare live-listing accuracy, application-to-qualified rate, interview completion, hires, time to first qualified applicant, and cost by source; it should also flag ghost-job risk, which can damage candidate trust and invite applicant skepticism (NPR). The same owner should reconcile ATS open requisitions against live Google-facing pages and Indeed listings each month, following the maintenance and missing-listing troubleshooting procedures covered earlier.

Key takeaways

• Google Jobs visibility and Indeed sponsorship are comparable only when both use the same ATS source rules, qualification definition, and cohort dates.
• A no-media-cost Google Jobs applicant still carries allocated web, ATS, maintenance, and recruiter-operating costs.
• JobPosting schema is a foundational investment when job operations, source capture, and listing accuracy are already controlled.
• Indeed budget should be capped and targeted at urgent shifts, hard geographies, branch launches, and documented qualified-applicant gaps.
• A named recruiting operations owner should review source quality and live-listing accuracy monthly before shifting spend.

Gotchas

Schema is not a placement guarantee

Correct JSON-LD does not guarantee that Google will crawl, display, rank, or send applicants to a caregiver vacancy. Google may not have crawled the page, may select another version, may find conflicting visible details, or may not show the listing for a query.

Generic pages create mismatch risk

Reusing one generic caregiver page while changing city, schedule, and pay can leave no distinct, current vacancy record. Markup should describe one real opening rather than a permanent join-our-team form, staffing pool, or filled shift.

Google Jobs and Indeed can be misattributed

A Google Jobs result should not be reported as an Indeed result merely because the candidate searched on Google. The destination URL and application flow determine the channel that produced the visit.

Application volume can mask an uncovered shift

Candidates may be unavailable for the overnight, outside the service radius, unwilling to accept the pay, lacking required experience, or unreachable. A campaign can look productive in a dashboard while producing no workable caregiver.

Stale job details damage conversion and trust

Filled roles left public, mismatched wages between the job page and application, expired requisitions, and broken mobile application forms can lose attribution and candidate trust. Closed roles should be removed promptly and application journeys tested.

Key takeaways

• JobPosting JSON-LD is an eligibility input for Google Jobs, not a promise of visibility, ranking, applications, or caregiver hires.
• Every active caregiver vacancy needs a crawlable, candidate-visible job page whose structured data matches the role, location, employment details, and application route.
• Indeed sponsorship should be evaluated by qualified applicants, interviews, hires, and filled shifts—not application volume alone.
• Google Jobs and Indeed are separate recruiting channels and should be attributed through their destination URLs, application flows, and source data.
• Exact pay, service area, shift details, screening capacity, and response speed determine whether job visibility becomes usable caregiver capacity.

Related reading

• 00-STRATEGY.md
• 01-60-DAY-CALENDAR.md
• 02-VISUAL-PACK.md
• 03-VIDEO-PACK.md
• 04-SOCIAL-PACK.md

Sources

• Indeed’s 2026 UK Jobs & Hiring Trends Report: Caution Persists, but Bright Spots Emerge - Indeed Hiring Lab
• 'Ghost jobs' are everywhere — here's how to avoid falling for them - NPR
• Indeed’s Pay-per-Application Pricing to End Dec. 18 - SHRM
• Scammers impersonate well-known companies, recruit for fake jobs on LinkedIn and other job platforms - Consumer Advice | Federal Trade Commission (.gov)
• SERP Features: Jobs - Semrush
• A Shifting Pipeline: What Indeed's Data Reveals About Immigrants' Role in the US Labor Force - Indeed Hiring Lab
• February 2026 US Labor Market Update: New Year, Same Resolutions - Indeed Hiring Lab
• For New Grads Looking for Work, the Struggle Is Real – But Not for All - Indeed Hiring Lab
• December 2025 Jobs Report: The Job Market Doesn’t Have to Break to Be Broken - Indeed Hiring Lab
• Indeed’s 2026 US Jobs & Hiring Trends Report: How to Find Stability in Uncertainty - Indeed Hiring Lab