How to Audit Whether Your Home Care Jobs Are Eligible for Google's Job Panel

This article explains how home care agencies can audit individual job pages for Google’s job experience. It covers the difference between valid JobPosting markup and actual job-panel visibility; the crawlability, indexing, canonical, freshness, and application-path conditions that can prevent a caregiver role from surfacing; and the job details that make an opening useful, including location, pay, shift, expiration, and direct application information. It also outlines the no-fee Google tools available for testing and monitoring, the division between internal CMS work and developer work, and the distinct roles of Google’s Rich Results Test, Schema Markup Validator, and Search Console in a practical JobPosting audit.

What's in this guide

• How Google Jobs JobPosting Schema Eligibility Works for Home Care Agencies
• What a Google Jobs JobPosting Schema Audit Costs
• Google Rich Results Test vs. Schema Markup Validator for JobPosting
• Google JobPosting Structured Data Required Fields for Home Care Jobs
• How to Audit JobPosting Schema for Home Care Jobs Step by Step
• How to Maintain Google Jobs Listings After Publishing
• Google Jobs JobPosting Schema Errors and Missing Home Care Jobs
• Google Jobs Eligibility Checklist for Home Care Agencies

The numbers at a glance

How Google Jobs JobPosting Schema Eligibility Works for Home Care Agencies

Valid JobPosting structured data makes an individual home care vacancy eligible for Google to process as a job listing feature, but it does not guarantee that the role will be indexed, included in Google’s job panel, or shown prominently to a job seeker. Google explicitly states that structured data does not guarantee a page will appear in Search results or any specific Search feature. Google Search Central

JobPosting is Schema.org structured data that describes one currently open position on a publicly accessible job-detail page, allowing Google to understand employment, employer, location, pay, application, and expiration information. For a home care agency, the useful unit is a distinct caregiver, CNA, HHA, scheduler, or nurse job URL—not a single generic “Careers” page that bundles every opening into one block of text.

Does JobPosting Schema Guarantee Google Jobs Visibility?

No. Passing a schema validator means Google can read eligible markup; it does not mean Google will crawl the page, index it, include it in the jobs feature, or rank it ahead of competing caregiver roles.

Google’s JobPosting documentation distinguishes eligibility from display: markup helps a page become eligible for the job experience, while Google still decides whether and where to show it. Google Search Central A caregiver opening can therefore pass the Rich Results Test but remain absent from the job panel because the URL is blocked, excluded from indexing, duplicated, stale, incomplete, or simply not selected for the visible results.

In an agency audit, a technician commonly finds one of these failures:

• The JSON-LD names a “Caregiver” role, but the visible page says only “Apply Today.”
• The page remains live after the role is filled, while validThrough is missing or expired.
• The listing links to a careers hub rather than a functioning application path for that specific vacancy.
• A WordPress, ATS, or franchise template applies noindex to job-detail pages.
• Several city pages use substantially identical caregiver copy, causing Google to select a different canonical URL.

Google’s job posting policies require employers to remove job postings when they are no longer accepting applications and to ensure the job’s structured data matches the visible page content. Google Search Central job posting policies

How Google Discovers Job Listings From Career Pages

Google can discover an individual caregiver job page when Googlebot can crawl the URL through internal links, XML sitemaps, or other discoverable links—and when indexing controls do not block it. A practical home care setup is a crawlable careers hub that links to each live job-detail page, with those same canonical job URLs included in an XML sitemap.

For example, an agency’s /careers/ page might link to /careers/caregiver-houston-tx/. Googlebot can follow that internal link, request the individual job URL, read its visible job description and JobPosting JSON-LD, and find the same URL in /sitemap.xml.

That path fails if the agency blocks crawling in robots.txt, places a noindex directive on the job page, or points the canonical tag to a general careers page. Google documents that robots.txt controls crawling, while noindex controls whether a crawled page may appear in Google Search; blocking a URL in robots.txt can also prevent Google from seeing the noindex directive. Google Search Central on robots.txt Google Search Central on noindex

Canonicalization matters when an agency has near-duplicate listings such as “Houston Caregiver,” “Caregiver—Houston,” and “Houston TX Home Health Aide” that lead to the same application and substantially the same role. Google may choose a canonical version different from the one the agency intended. Google Search Central on canonical URLs

Google Jobs Ranking Factors for Home Care Jobs

Google does not publish a fixed ranking formula for job-panel placement, but complete, accurate, current job details and a crawlable, indexable application page give a home care listing a materially stronger eligibility and quality foundation than generic or stale job content. For caregiver recruiting, the practical signals are the role title, specific location, employment details, compensation details where applicable, freshness, and a working path to apply.

Consider two illustrative Houston caregiver job pages:

Role A gives both Google and an applicant details that match a real staffing need: where the caregiver will work, what schedule must be covered, and how to apply. Role B creates a common operations problem: applicants may click through, find no suitable shift or closed application, and abandon the process.

Google requires job pages to describe a real job opportunity and warns against misleading content, expired roles, and job pages that do not let users apply. Google Search Central job posting content guidelines For agencies recruiting against urgent coverage gaps, specificity also prevents the wrong applicant from applying to a broad “caregiver” listing when the actual need is a weekend Houston shift.

Google Jobs Eligibility Versus Job Panel Visibility

Technical eligibility, indexing, job-panel inclusion, and prominent visibility are separate stages: a page can succeed at one stage and fail at the next. A home care agency should audit each stage independently instead of treating valid schema as proof that applicants can find the role.

• Technical eligibility: The individual job page contains Google-supported JobPosting markup and meets the feature’s required guidelines. Google Search Central
• Crawlability: Googlebot can access the job URL and its resources without being blocked by robots.txt or an inaccessible application workflow. Google Search Central
• Indexing: Google is permitted to index the page because it does not carry a noindex directive and is not consolidated under another canonical URL. Google Search Central on indexing controls
• Job-panel inclusion: Google elects to use the page in its jobs experience; valid structured data alone does not compel inclusion. Google Search Central
• Prominent visibility: The listing appears for a relevant caregiver search and competes successfully with other current local roles for that query.

The operational distinction is important. A page can be technically valid but unindexed; indexed but not included in the job panel; included but buried below better-matched local openings. The next audit steps should therefore test the actual job URL, its indexability, its visible role details, and whether the application remains open—not merely whether JSON-LD exists.

Frequently Asked Questions

Does JobPosting schema guarantee Google Jobs visibility?

No. Valid JobPosting markup makes a page eligible for Google to process as a job listing feature, but Google still decides whether to crawl, index, include, rank, or display the role in its job panel.

What is the best first tool to test a live caregiver job page?

Google’s Rich Results Test is the best first tool for a live home care job page because it checks whether Google detects JobPosting structured data and reports Google-specific eligibility errors.

Is Google Jobs free for home care agencies?

Yes. Google does not charge a platform fee for eligible job pages to be discoverable through Google Search, and the Rich Results Test and Search Console are no-fee tools; the expense is staff or developer time to build, test, and maintain accurate pages.

What fields are required for a Google JobPosting?

Google’s required JobPosting properties are title, description, datePosted, validThrough, hiringOrganization, and jobLocation, with remote-only jobs using Google’s remote-work fields instead of a conventional worksite location.

Why can an eligible job page still fail to appear?

An eligible job page can remain absent because it is blocked from crawling, carries noindex, is consolidated under another canonical URL, is duplicated, stale, incomplete, lacks a working role-specific application path, or is not selected for visible results.

When should an agency hire a developer for JobPosting work?

A developer is needed when the careers system cannot create separate public job URLs, exposes jobs only inside one page or a JavaScript-only feed, cannot maintain expiration dates, prevents individual public URLs, or duplicates the same role across city pages.

Sources

• Google Search Central: JobPosting structured data
• Google Search Central: Block indexing with noindex
• Google Search Central: Introduction to robots.txt
• Google Search Central: Consolidate duplicate URLs
• Search Engine Land: Google job listings search open to job-search sites and developers

Key takeaways

• Valid JobPosting markup creates eligibility for Google’s job experience, not a guarantee of job-panel display.
• Each active home care opening needs its own crawlable, indexable, role-specific job URL.
• A careers hub link and XML sitemap help Google discover caregiver job-detail pages.
• robots.txt, noindex, incorrect canonicals, stale listings, and broken apply links can stop an otherwise valid job from surfacing.
• Precise Houston location, pay, shift, and application details make a caregiver listing more useful than a generic or expired vacancy.

What a Google Jobs JobPosting Schema Audit Costs

Google does not charge a home care agency to submit its own eligible job pages for Google job discovery or to use Google’s validation tools; the expense is the staff or developer time required to build, test, and maintain accurate job pages. For a small agency, the practical budget ranges from internal staff time for a CMS-based cleanup to contracted web-development and technical-SEO work when the career site cannot produce separate, current job URLs.

JobPosting schema is machine-readable JSON-LD markup on an individual job page that tells Google the role’s title, employer, location, description, employment details, and application information. As covered in the eligibility section, markup is not a paid placement or a guarantee of panel visibility; it is technical work on an agency-owned careers site.

Is Google Jobs Free for Home Care Agencies?

Yes. Google does not charge agencies a platform fee to make eligible jobs discoverable through Google Search, and Google provides the Rich Results Test and Search Console as no-fee tools for testing and monitoring eligible pages.

Google’s JobPosting structured-data documentation directs employers and site owners to mark up job pages and monitor them in Search Console; it does not describe a submission or display charge. An owner can paste a live caregiver-job URL into Google’s Rich Results Test to see whether Google detects JobPosting markup and which required fields are missing.

The no-software-cost audit stack is:

• Google Rich Results Test: checks whether a job URL is eligible for rich-result processing and identifies schema errors.
• Google Search Console: shows indexed-page and enhancement reporting after the site is verified; Google describes Search Console as a free service.
• Schema.org’s validator: provides a second check of the JSON-LD vocabulary, though Google’s own test is the relevant check for Google Search behavior.
• A spreadsheet or applicant-tracking-system export: tracks open date, expiration date, filled date, URL, test result, and owner responsible for removing each posting.

What a technician sees in a failed audit is usually not a mysterious Google problem. It is a generic /careers page with five openings loaded by a script, no crawlable URL per job, or a filled caregiver posting whose validThrough date and visible page were never updated.

Google Rich Results Test Free Schema Validation

Google’s Rich Results Test is free validation, but it is not a full hiring-site audit: it can identify detected JobPosting markup and errors on a tested URL, not confirm that an opening remains real, staffed, or competitively visible.

Test each live caregiver, CNA, HHA, scheduler, and care-coordinator URL individually. Compare the rendered page with the JSON-LD: the title, city or service-area location, pay disclosure, employment type, and application destination should agree. Google’s JobPosting guidelines specifically require employers to remove expired jobs and use validThrough for postings that are no longer valid after a stated date.

A valid test does not repair the operational failure that follows: a caregiver clicks “Apply,” reaches a broken form or a general contact page, and the agency still pays Indeed for the next applicant.

JobPosting Schema Implementation Cost for Small Agencies

For a five-opening home care agency, an implementation should be scoped as a defined build rather than an open-ended “SEO package”: one career-page template, five individual URLs, reusable JSON-LD generation, validation, and staff handoff.

Published marketplace rates are market ranges, not fixed project quotes. Upwork’s web-developer cost guide lists hourly rate bands that vary by experience, while Clutch’s web-development pricing research shows that agency rates and minimum project sizes vary materially by provider and location. Ask for a fixed scope that separates implementation from recurring support.

A CMS template is suitable when the agency’s WordPress, Webflow, Squarespace, or ATS-connected careers system can create a unique public URL for each role and expose fields such as title, location, description, date posted, expiration date, and application URL. An internal marketing coordinator can then enter openings and run the Rich Results Test if the template generates the markup automatically.

A developer is needed when jobs exist only inside one page, the careers feed is JavaScript-only, the application system prevents individual public URLs, the template cannot set expiration dates, or the same role is duplicated across city pages. Those are structural issues, not copywriting tasks.

Cost to Hire a Developer for JobPosting JSON-LD

Hire a developer when the website needs template changes or a data connection—not merely when a Rich Results Test reports a missing field. The developer’s deliverable should be reusable job-page functionality, not five blocks of copied JSON-LD that staff cannot safely update.

Request a proposal that names the CMS, identifies who owns the code, lists the five initial URLs, and states how datePosted and validThrough will be maintained. Require a before-and-after test record for each URL and a repair price for future CMS updates. Google warns that structured data must reflect the visible page content, so a developer should not hard-code pay, location, or expiration data that staff later change only on-page (Google JobPosting guidelines).

Compare this work with paid job-board spend using the agency’s own hiring data. Indeed explains that sponsored jobs use a budget-based advertising model and that employers can set or adjust that budget (Indeed Employer Help); that spend is separate from Google discovery of an agency-owned job page.

For example, use this break-even calculation:

Technical-cleanup cost ÷ one avoided paid-posting expense = paid postings that must be avoided to recover the cleanup cost.

Then qualify the result with applicant quality: multiply applicants by the agency’s documented applicant-to-interview rate, and compare that interview volume with the same measure from sponsored Indeed traffic. A cheaper source is not a hiring win if applicants do not answer calls, lack required availability, or cannot cover the service-area shifts that caused the recruiting need.

Key takeaways

• Google does not charge an agency to make eligible job pages discoverable or to use the Rich Results Test and Search Console.
• A five-opening implementation should include reusable job-page templates, individual URLs, JSON-LD, testing, and staff training—not just copied schema code.
• Internal staff can maintain markup only when the CMS exposes accurate job fields and creates a unique public URL for every opening.
• Developer work is justified when the careers site cannot create, update, expire, or expose individual job pages correctly.
• Compare technical cleanup against the cost of avoided sponsored postings and the agency’s own applicant-to-interview conversion rate.

Google Rich Results Test vs. Schema Markup Validator for JobPosting

For a nontechnical home care owner auditing a live caregiver job page, start with Google’s Rich Results Test using the page URL, then use Google Search Console to find recurring errors across the site. Use Schema Markup Validator as a second diagnostic tool: it can confirm Schema.org vocabulary and JSON-LD structure, but it does not decide whether Google considers the page eligible for a JobPosting rich result.

JobPosting schema is structured data, usually JSON-LD, that identifies an individual open role and supplies job details in the Schema.org JobPosting vocabulary. As covered in the eligibility section, valid markup is not a promise of placement in Google’s job panel; these tools distinguish basic structured-data validity from Google-specific requirements and post-crawl reporting.

What Is the Best Tool to Test JobPosting Schema?

The best first tool for a live home care job page is Google’s Rich Results Test, because it tests whether Google can detect JobPosting structured data and reports eligibility issues for Google-supported rich results. A generic validator is useful after that when the Google report points to malformed JSON-LD, an unexpected property, or a vocabulary-level warning.

Paste the URL of a live “Caregiver,” “CNA,” or “Home Health Aide” job page into the Rich Results Test. The result should identify Job postings as a detected item and separate errors from warnings under Google’s JobPosting requirements, which are documented in Google’s JobPosting structured-data guidance.

A technician commonly finds that the agency’s careers template emits markup on every job page but leaves a field blank on selected postings. For example, a page may visibly show “Weekend Caregiver — Dallas” while the JSON-LD has no jobLocation, or it may retain an expired validThrough date after the role is reposted. Testing the actual page, rather than assuming the template works, catches those page-specific failures.

How to Use the Google Search Console JobPosting Enhancement Report

Google Search Console’s Job Postings enhancement report shows JobPosting errors and warnings found after Google crawls eligible pages, making it the practical tool for detecting sitewide template failures. It also lets the agency monitor affected URLs and request validation after a developer fixes the underlying issue.

Open the Job Postings enhancement report in the verified Search Console property, select an issue, and review the affected-page examples. Google’s documentation for enhancement reports explains that reports group detected structured-data issues and provide a validation workflow after remediation.

This report is especially useful when a CMS update breaks a shared job template. A single missing field in a template can affect every open caregiver role, while the Rich Results Test only reports on the individual URL submitted. After a correction, use Validate Fix in Search Console and keep the jobs open and crawlable until Google processes the validation.

Do not treat a clean Search Console report as proof that every newly published vacancy is correct. It reflects pages Google has crawled, so test a newly posted live URL directly before relying on the sitewide report.

Rich Results Test URL Versus Code Snippet Test

Test a live URL when the agency needs to know what Google can fetch from the published job page; paste a code snippet when diagnosing proposed or corrected JSON-LD before it is deployed. The URL test is the more reliable audit of a live home care vacancy because it evaluates the rendered page Google accesses, not an isolated block copied from a plugin or developer ticket.

Google’s Rich Results Test documentation supports both URL and code testing for supported structured-data types. Use the code option when a developer has revised the JobPosting block and wants to isolate whether the revised syntax and Google-required properties are acceptable before publishing.

Use the URL option when any of these conditions apply:

• The role is already public and accepting applicants.
• A WordPress, Wix, Webflow, or ATS plugin may be changing the JSON-LD after it is saved.
• The visible title, pay, location, or expiration date may not match the structured data.
• The agency uses JavaScript to inject job details after initial page load.
• A page redirects, is blocked, returns an error, or serves different markup than the developer’s local copy.

What does the Rich Results Test check that a general Schema Markup Validator does not? It checks Google’s supported rich-result eligibility rules for JobPosting, including Google’s required and recommended properties, rather than merely whether the markup uses recognizable Schema.org terms.

How to Choose a JobPosting Schema Audit Tool

Choose tools in sequence: inspect the live page, run the Rich Results Test, use Schema Markup Validator for vocabulary-level diagnosis, and use Search Console to monitor Google’s crawled view across the site. This sequence prevents the common mistake of calling a job page “valid” solely because its JSON-LD parses.

What can the Schema Markup Validator reveal that Google’s eligibility report may not emphasize? It can expose Schema.org vocabulary and syntax problems that are not framed as Google JobPosting eligibility failures, such as an incorrectly typed value, an invalid nesting relationship, or a property Google ignores but the agency intended another consumer of Schema.org data to read.

For example, this JSON-LD can be structurally valid Schema.org because it declares a JobPosting with a title:

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Caregiver"
}

Schema Markup Validator may recognize the type and property, but Google’s Rich Results Test can report missing JobPosting fields required by Google, such as job description, posting date, hiring organization, and location where applicable under Google’s JobPosting specification. That difference is not a contradiction: the validator asks whether the markup is legitimate Schema.org; Google asks whether it meets Google’s display requirements.

Key takeaways

• Google’s Rich Results Test is the first tool a home care owner should use for a live JobPosting URL because it checks Google-specific rich-result eligibility.
• Schema Markup Validator can confirm valid Schema.org syntax and vocabulary without confirming Google JobPosting eligibility.
• Test a URL when auditing the published job page; test pasted JSON-LD when checking a proposed fix before deployment.
• Search Console identifies JobPosting errors Google has found across crawled pages and provides a workflow to validate repairs.
• A reliable audit sequence is live-page inspection, Rich Results Test, Schema Markup Validator diagnosis, and Search Console monitoring.

Google JobPosting Structured Data Required Fields for Home Care Jobs

Google requires each eligible home care vacancy to have its own JobPosting markup with a truthful title, description, posting date, expiration date, hiring organization, and job location. Add recommended fields—especially pay, employment type, and direct-application status—when they match what the applicant can see and receive on the live job page.

JobPosting is a Schema.org type for describing a specific employment opportunity, including the employer, work location, compensation, employment type, and application period. Schema.org defines JobPosting as a job listing, while Google’s requirements determine whether that markup can qualify for its job-search experience.

Required JobPosting Schema Fields for Google Jobs

Google’s required JobPosting properties are title, description, datePosted, validThrough, hiringOrganization, and jobLocation; a remote-only job uses Google’s remote-work fields instead of a conventional worksite location. Google also recommends fields that make a caregiver opening more useful and less likely to be filtered as incomplete, including baseSalary, employmentType, identifier, and directApply. Google Search Central’s JobPosting documentation is the controlling property table for this audit.

A technician auditing an agency site commonly finds a generic “Join Our Team” page marked up as one vacancy, even though it lists caregivers, CNAs, nurses, and office staff in several cities. That does not describe one specific job. Google’s content policies require structured data to represent a real job opportunity and prohibit marking up content that is misleading or no longer accepts applications. Google’s JobPosting guidelines should be checked before publishing recurring or evergreen recruitment markup.

How to Mark Up JobPosting Title, Description, DatePosted, and ValidThrough

A home care agency should use a precise title and description that match the visible job page, then publish datePosted and validThrough as ISO 8601 dates or date-times. A misleading title, an old posting date, or an expiration date left in the past can make the listing ineligible or leave applicants clicking into a filled job.

Do not title an opening “Caregiver Needed Immediately—High Pay” if the actual role is a part-time weekend HHA assignment in one service area. Write the role a field applicant will recognize, then state the constraints plainly:

• Caregiver: personal care, companionship, transfers, meal preparation, and required driver or transportation expectations where applicable.
• CNA or HHA: specify whether an active state credential is required and whether duties include hands-on personal care.
• RN: distinguish in-home skilled visits, assessments, supervisory visits, care-plan work, and on-call obligations.
• Scheduler: state whether the role is office-based, hybrid, or remote and whether evening or weekend coverage is part of the schedule.

datePosted is the date the individual opening first went live, not the date the careers-page template was created. validThrough is the real closing deadline; remove the markup or update the page when the role is filled. ISO 8601 permits date values such as 2026-10-07 and date-time values with a time-zone offset, such as 2026-10-07T17:00:00-05:00. ISO 8601 is the reference for that format.

How to Add HiringOrganization and JobLocation Markup

A home care agency should identify itself in hiringOrganization and mark up the actual work arrangement in jobLocation, rather than publishing private client-home addresses. Office-based jobs use the office address; client-home and multi-location roles should use the agency branch or clearly defined service-area location from which the role is managed.

Schema.org’s Organization, Place, and PostalAddress types provide the structure for this information. For a caregiver who travels to client homes across a territory, the branch office can be the job location if that is the employer’s defined location and the page visibly explains that client visits occur across the stated service area.

For a multi-location opening, publish separate job pages only if the agency is genuinely hiring for separate, identifiable locations. A “Caregiver—Dallas and Fort Worth” page should not use one random client neighborhood as the address. For hybrid or remote scheduler roles, follow Google’s remote-job guidance by using jobLocationType: "TELECOMMUTE" and, when applicable, applicantLocationRequirements to identify where the applicant may live. Google’s remote job-location guidance explains the required location treatment.

How to Use BaseSalary, EmploymentType, and DirectApply Schema

Home care agencies should mark up hourly pay as baseSalary, identify the actual employment relationship in employmentType, and use directApply: true only when the application path is genuinely short and direct. The structured data must match the pay, status, shifts, and application process visible to the applicant.

baseSalary uses a MonetaryAmount with a QuantitativeValue. For an hourly caregiver wage, the unit is HOUR; for a real range, use the actual minimum and maximum shown on the page. Do not mark up a top-end rate that depends on credentials, weekend availability, or differential pay unless the page explains those conditions.

The following example shows the structure for a caregiver role. The agency name, compensation, dates, and URL must be replaced with the live vacancy’s verified details before deployment; Google’s salary example uses an hourly QuantitativeValue format. Google’s JobPosting salary guidance governs the implementation.

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Caregiver - Chicago, Illinois",
  "description": "Provide in-home personal care and companionship. Part-time evening and weekend shifts are available. Applicants must be able to travel to client homes in the Chicago service area.",
  "datePosted": "2026-10-07",
  "validThrough": "2026-10-31T17:00:00-05:00",
  "employmentType": "PART_TIME",
  "directApply": true,
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Visiting Angels Chicago",
    "sameAs": "https://www.visitingangels.com/"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Chicago",
      "addressRegion": "IL",
      "addressCountry": "US"
    }
  },
  "baseSalary": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": {
      "@type": "QuantitativeValue",
      "minValue": 18,
      "maxValue": 22,
      "unitText": "HOUR"
    }
  }
}

A full-time caregiver role can use FULL_TIME; a role with a regular reduced schedule can use PART_TIME; and a bona fide independent-contractor engagement can use CONTRACTOR. Do not call an employee a contractor merely because the agency wants schedule flexibility. The visible employment terms, payroll classification, and markup should agree.

When Is DirectApply Appropriate for Home Care Jobs?

directApply: true is appropriate when a job seeker can begin or complete an application directly on the agency’s own application flow with minimal additional steps. It is not appropriate when the click sends applicants to a search-results page, requires them to locate the vacancy again, or routes them through a third-party job board before they can apply.

For a direct-apply caregiver page, the visible “Apply now” control should open the actual form or a role-specific applicant-tracking-system record. A workable flow may ask for contact information, work authorization, credential status, availability, and resume details; it should not make the applicant re-search “Caregiver” and reselect the Chicago branch after clicking the listing.

Treat an evergreen “We are always accepting caregiver applications” page differently from a single open role. A specific vacancy with a real location, current shifts, application deadline, and active requisition can use JobPosting markup. An evergreen talent-pool page should not be presented as a repeatedly renewed vacancy merely by changing datePosted or extending validThrough; verify Google’s current JobPosting content policies before marking up recurring openings.

Sources

• Google Search Central: JobPosting structured data
• Google Search Central: JobPosting content guidelines
• Schema.org: JobPosting
• Schema.org: Organization
• Schema.org: PostalAddress
• Schema.org: Place
• Schema.org: MonetaryAmount
• Schema.org: QuantitativeValue
• ISO: ISO 8601 date and time format

Key takeaways

• Google requires each home care job listing to identify a real role, employer, location, posting date, and application-expiration date.
• A caregiver, CNA, HHA, RN, or scheduler title must describe the actual credentials, work setting, and schedule applicants will encounter.
• Use baseSalary for visible hourly pay, employmentType for the real work classification, and location markup that reflects the office, territory, or remote arrangement.
• Set directApply to true only when the applicant reaches a role-specific application flow without a search or job-board detour.

How to Audit JobPosting Schema for Home Care Jobs Step by Step

A home care owner can audit a live job page without software by running its URL through Google’s Rich Results Test, comparing the detected JobPosting fields with the applicant-facing page, and recording every mismatch for the web vendor. JobPosting is Schema.org structured data that identifies a specific open role and supplies machine-readable details such as title, employer, location, compensation, and posting dates.

This is a page-by-page quality-control process, not a substitute for the required-field review earlier in this guide or the date and closure controls covered in the maintenance section. Google’s JobPosting documentation says structured data must represent the content visible on the page to users, so a technically valid result can still require correction when the page and markup describe different jobs. Google Search Central’s JobPosting guidance is the controlling reference for those requirements.

How to Test a Job Page in Google Rich Results Test

An owner can test a live caregiver or CNA job page by pasting its public URL into Google’s Rich Results Test, selecting Test URL, and reviewing whether the tool detects a JobPosting item. No browser extension, paid platform, or ability to write JSON-LD is required.

Use the public, applicant-facing URL—not the careers-page category URL, an ATS dashboard URL, a staging URL, or a PDF. A reproducible audit record should include:

1. Copy the full live job-page URL from the browser address bar.
2. Paste it into the Rich Results Test URL field and run the test.
3. Confirm whether Job postings appears among detected structured-data types.
4. Open the JobPosting result and record every error and warning shown.
5. Open the test’s rendered HTML view to see the version Google fetched, particularly if the careers platform loads job details after the initial page request.
6. Save a browser screenshot showing the URL, test date, JobPosting detection result, and issue list; also save the test URL or share link where available.

Google describes the Rich Results Test as a tool for checking whether a page is eligible for Google rich results and for viewing detected structured data. Google Search Central distinguishes between errors that prevent eligibility and warnings that identify recommended improvements.

Immediate-action results include no JobPosting item detected, an error on a required property, markup attached to a filled role, or a result showing data for a different position than the visible page. Later-improvement results include warnings on recommended enhancements when the core job is accurate and current; however, a warning involving pay, location, or dates should still be assigned to a named owner because those fields affect applicant expectations.

How to Find JobPosting JSON-LD on a Careers Page

JobPosting JSON-LD is normally found in the page source inside a script block whose type is application/ld+json; an owner can search the source for that phrase or for JobPosting. The markup may appear in the document head, near the end of the HTML body, or be injected by a careers platform, which is why the Rich Results Test’s rendered HTML is useful.

On the live job page, right-click and select View Page Source where the browser provides that option. Then use the browser’s find command and search, one term at a time, for:

• application/ld+json
• JobPosting
• title
• jobLocation
• baseSalary
• datePosted
• validThrough

Finding those terms does not prove the job is eligible; it gives the owner a quick way to locate what the website is declaring. Google’s JobPosting specification identifies these properties and explains the expected structured-data format. Google Search Central’s JobPosting documentation should be used alongside the exact field definitions provided earlier in this article.

If source search returns no JobPosting, record that outcome rather than trying to edit code. A vendor may be placing markup through an ATS template, tag manager, server-side system, or JavaScript rendering process that is easier to diagnose from the Rich Results Test output than from raw source.

Why Visible Content Must Match JobPosting Structured Data

The visible job page and its JobPosting markup must describe the same open position, because Google requires structured data to represent the content users can see on the page. A mismatch can mislead applicants even when the test reports no syntax error.

Consider a home care page whose visible headline says “Caregivers needed” and whose body asks applicants to contact the agency about open shifts. Its markup, however, identifies a specific full-time CNA role, supplies a wage not displayed to applicants, assigns an office address rather than the actual service-area location, and carries a closing date that has passed. That is not a harmless optimization difference: the markup and page are making conflicting promises about title, employment type, compensation, location, and availability.

The correction is not automatically to copy the markup onto the page. The agency should first decide which role is genuinely open, then make both versions match that decision:

• Publish a dedicated page for the specific CNA opening, with the same title, pay presentation, work arrangement, location, duties, and closing status as the markup; or
• Change or remove the markup if the page is a general recruiting page rather than a specific open job.

Google’s general structured-data guidelines require markup to be an accurate representation of page content and caution against marking up content that is not visible to users. Google Search Central’s structured-data guidelines provide the applicable policy.

How to Audit Caregiver Job Title, Location, and Pay Details

A home care JobPosting audit is accurate when every field can be read by an applicant on the same job page and matched to one specific, current opening. Compare the visible copy and markup field by field, rather than approving a page because it merely contains the word “caregiver.”

For each role, verify:

• Title: “Caregiver,” “Home Health Aide,” “CNA,” “Registered Nurse,” and “Care Coordinator” are different roles; the page and title value should use the same role name.
• Location: Confirm whether the applicant reports to an office, works in a named city or service area, serves multiple locations, or works remotely. Compare visible location wording with jobLocation.
• Compensation: Check whether the page states hourly pay, a range, salary, differential, or no pay information; compare that with baseSalary and do not leave a prior campaign’s wage in markup.
• Schedule and employment type: Confirm whether the listing is full-time, part-time, per diem, weekend-only, overnight, employee, or contractor, and ensure the visible schedule supports the structured-data value.
• Duties and qualifications: A caregiver page should visibly describe the actual work—such as personal care, transfers, meal support, companionship, dementia care, or transportation—rather than using generic recruiting language for a different clinical role.
• Dates and closure: Compare datePosted and validThrough with the real posting status, then follow the maintenance section’s controls for expiring, removing, or updating filled jobs.

Use a worksheet that lets a developer correct the exact page and property rather than receiving a vague request to “fix schema.”

Key takeaways

• Google’s Rich Results Test lets an owner test a live job URL and identify whether JobPosting structured data is detected without installing software.
• A detected JobPosting item still needs a manual comparison against the title, location, pay, schedule, duties, and closure status visible to applicants.
• Search page source for application/ld+json, JobPosting, title, jobLocation, baseSalary, datePosted, and validThrough to locate the declared job data.
• Treat missing JobPosting detection, required-field errors, expired roles, and visible-to-markup mismatches as immediate repair items.
• A field-level worksheet gives a web vendor the URL, property, mismatch, owner, correction date, and retest result needed to fix the correct listing.

How to Maintain Google Jobs Listings After Publishing

A home care agency should review every live caregiver job at least weekly and immediately when its pay, location, schedule, hiring status, or application path changes. When a role is filled or no longer accepts applicants, the agency must remove its JobPosting markup or set validThrough to a date in the past so Google does not continue showing a stale opening.

JobPosting maintenance is the process of keeping a job page, its structured data, and its application destination aligned with the role an applicant can actually pursue. This follows the required-field and date-format guidance covered earlier; the later errors section explains how to diagnose stale listings that remain visible after a correction.

How Often Should You Update JobPosting DatePosted and ValidThrough?

Review a caregiver job’s datePosted, validThrough, compensation, location, and application status weekly, plus whenever the recruiting team changes a material hiring fact. Do not reset datePosted merely because an agency edits punctuation, rewrites a benefit bullet, or corrects a non-material wording issue.

Google’s JobPosting documentation says the posting date should be the original date the employer posted the job, while validThrough identifies when the listing is no longer valid (Google Search Central). Resetting datePosted for cosmetic edits can make an old vacancy look newly opened when it is not.

A practical agency process target—not a Google requirement—is:

For example, a scheduler may learn that an “HHA—Weekend Nights, Katy” opening is no longer needed because an existing caregiver accepted additional shifts. Leaving the old hourly range, Katy location, and Apply button live creates an applicant experience that conflicts with the listing Google may have indexed.

How Do You Remove Filled Jobs From Google Jobs?

When a caregiver job is filled, paused, canceled, or no longer accepting applicants, disable the application path and either remove the JobPosting markup or ensure that validThrough is in the past. Changing only the structured-data date while leaving a live “Apply now” page can still mislead applicants and create a mismatch between visible content and markup.

Google specifically instructs publishers to remove expired jobs from their site or remove the JobPosting structured data; alternatively, they can keep the markup only when the expiration date is in the past (Google Search Central JobPosting guidelines). The page’s visible status should make the same outcome clear.

A recruiter workflow can look like this:

1. The care manager approves a new caregiver opening for a defined service area and shift.
2. The agency publishes one job URL with matching visible details and JobPosting markup.
3. During the weekly review, the recruiter confirms the role remains open and that the application form works.
4. After an accepted offer, the recruiter disables the form or removes the apply link.
5. The web owner removes JobPosting markup, or changes validThrough to a past ISO 8601 date as described in the required-fields section.
6. The owner verifies the URL’s response and current index status in Search Console.

How Should You Expire a JobPosting Listing Correctly?

Changing validThrough can be sufficient for an expired job only if the page no longer presents the role as accepting applicants; otherwise, update or remove both the page content and its markup. Use a 404 or 410 for a permanently deleted job URL, a redirect only when there is a genuinely relevant replacement page, and an archived page only when it clearly states that applications are closed and contains no active JobPosting markup.

Google explains that 404 Not Found and 410 Gone responses tell Google content is unavailable and lead to removal from the index over time; a redirect tells Google that the content has moved instead (Google Search Central). Redirecting a filled “Caregiver in Sugar Land” role to a generic careers page can be appropriate if that page helps applicants find current openings, but it should not be used to make the old vacancy appear current.

Use the following decision rule:

• Return 404 or 410: The job page has no continuing applicant value and the vacancy is permanently gone.
• Redirect: A materially relevant current page replaces it, such as a revised live job URL for the same role.
• Retain an archive page: The agency needs the URL for records or historical recruiting links; clearly label the job closed, disable applications, and remove JobPosting markup.
• Remove markup but retain page: The page remains useful as an employer-information or closed-role notice, but it is not an active vacancy.

If an outdated result presents an urgent applicant-harm issue, Search Console’s Removals tool can temporarily hide a URL from Google Search while the agency makes the permanent page, markup, or HTTP-status change. Google states that a temporary removal lasts about six months and does not replace a permanent removal method (Google Search Central).

How Should You Use Search Console Request Indexing for New Job Listings?

Use Search Console’s URL Inspection tool to request indexing after publishing a genuinely new job, making a material correction, or removing stale job markup, but do not treat the request as a promise of immediate crawling, indexing, or Google Jobs inclusion. Google controls crawl timing and may limit requests through quotas, so a request is a signal to recrawl—not a publishing button.

The URL Inspection tool lets a verified site owner inspect the indexed version of a specific URL and request indexing after checking that Google can access the current page (Google Search Console Help). Google says indexing requests are subject to quota limits and that crawling can take days to weeks; requesting indexing does not guarantee that Google will index or display the page (Google Search Central).

For a new caregiver role, first confirm that the live URL returns correctly, the visible job details match the markup, and the application route is functional. Then request indexing once. Repeated requests do not repair an expired validThrough value, a blocked page, an invalid location, or an application form that no longer accepts candidates.

Key takeaways

• A weekly review plus immediate status-change review keeps caregiver job dates, pay, locations, and applications aligned with reality.
• Do not reset datePosted for minor copy edits; reserve it for the original posting of the actual opening.
• A filled or paused job needs an inactive application path and either removed JobPosting markup or a validThrough date in the past.
• Use 404 or 410 for permanently removed vacancies, and redirect only to a genuinely relevant replacement page.
• Search Console indexing requests can prompt recrawling but do not guarantee immediate indexing or appearance in Google’s job panel.

Sources

• Google Search Central: JobPosting structured data
• Google Search Central: How to handle 404 pages
• Google Search Central: Remove information from Google
• Google Search Central: Ask Google to recrawl URLs
• Google Search Console Help: URL Inspection tool

Google Jobs JobPosting Schema Errors and Missing Home Care Jobs

A home care job can fail Google’s rich-result eligibility test because its JobPosting markup is incomplete, invalid, misleading, or inconsistent with the job page an applicant sees. A valid test also does not prove that Google has crawled, indexed, selected, or currently displayed the listing in its job search experience.

JobPosting is Schema.org structured data that identifies one active, applicant-accessible job opening and supplies machine-readable details such as title, employer, location, date, employment type, and compensation. Google requires job markup to follow its JobPosting documentation and structured-data policies; markup is an eligibility signal, not a promise of display.

Why JobPosting Schema Is Not Eligible for Google Rich Results

A job page fails Google’s rich-result eligibility test when Google cannot parse a valid JobPosting item or when required job details are absent, malformed, or conflict with visible page content. Common home care failures are a missing datePosted, expired or absent validThrough, no employer, an unusable location, and compensation markup that does not match the posted wage.

Google’s JobPosting guidance requires each job page to describe a real opening, not a general “Join Our Team” page containing several roles. A careers hub can link to individual caregiver, CNA, HHA, RN, scheduler, or care coordinator pages, but each individual opening needs its own accurate data and application path. Google’s policies also prohibit misleading structured data and content that is not representative of the visible page (Google Search Central).

A technician will usually find one of these practical failures:

• The visible page says “Competitive pay,” while JSON-LD supplies a specific hourly range that applicants cannot see.
• The agency marks a role FULL_TIME even though the page advertises per-diem visits or variable part-time shifts.
• An ATS template retains an old validThrough date after the job is renewed.
• A generic service-area phrase, such as “Serving Greater Houston,” is used where the page does not identify the actual hiring location.
• The page’s Apply button opens a broken ATS link, a login wall, or a different job than the one described.

Why an Expired Google Jobs Listing May Still Show

A corrected or expired job can remain visible temporarily because Google must recrawl the URL, process the changed page, and update its indexed information before search results change. Requesting indexing can prompt a crawl request, but Google states that it does not guarantee immediate inclusion or update (Google Search Central).

For a filled caregiver opening, the owner should confirm more than the validThrough date. The visible job page, JSON-LD, sitemap entry, internal careers links, and ATS application destination must all stop presenting the role as open. Leaving a live 200 OK page with active JobPosting markup is the clearest reason an expired opening can linger.

Google may also retain stale result information after a page changes or disappears while it recrawls and reprocesses the URL. Check the URL Inspection report for Google’s last crawl date and indexed canonical, then compare that evidence with the current live page (Google Search Central).

How Duplicate JobPosting Listings Appear in Google Jobs

Duplicate JobPosting listings usually occur when the same caregiver opening is simultaneously published on an agency careers URL, an ATS-hosted URL, a franchise site, a job board feed, or several location pages with nearly identical content. The agency should retain one preferred job URL and ensure every other version either points to it canonically or represents a genuinely separate vacancy.

A typical home care scenario is:

1. agencyexample.com/careers/caregiver-houston contains JobPosting JSON-LD and an Apply button.
2. agencyexample.atsplatform.com/jobs/12345 contains the same title, pay, and description.
3. The agency page’s Apply button sends applicants to the ATS page.
4. Both URLs remain crawlable and both contain active JobPosting markup.

The owner, developer, and ATS vendor should review the preferred canonical URL, the url and identifier values in each JobPosting item, and the destination reached after clicking Apply. If the agency page is the intended search result, it should identify that opening consistently and direct the applicant to the correct ATS application flow; if the ATS page is the intended result, the agency page should not present a competing, separately marked-up copy. Google explains that canonicalization is its selection of the representative URL among duplicate or very similar pages, and a declared canonical is only a signal (Google Search Central).

Do not create one “Caregiver — Multiple Cities” page and clone it across every branch location unless each page represents a distinct, available opening with its own accurate location and application route. Duplicate titles, copied descriptions, identical identifiers, and a single application destination are clues that the URLs are competing representations of one job rather than separate jobs.

How to Fix Invalid Location, Salary, or Employment Type Errors

Home care agencies should use the actual hiring or work location, show the same pay and job status to applicants that they mark up for Google, and select employment types that reflect the real engagement. A headquarters address, broad service territory, or vague “competitive pay” statement is not a substitute for an accurate job location or visible compensation detail.

For location, distinguish these cases:

• Actual hiring location: A caregiver assigned to clients in Austin should use the applicable Austin work location when that is where the work is performed.
• General service area: “We serve Travis, Williamson, and Hays counties” describes the agency’s market; it does not by itself identify a job location.
• Headquarters: Use the office address only when the role is actually office-based or applicants will work there.
• Remote role: Use Google’s remote-job guidance only when the role is truly remote and any geographic eligibility restriction is stated accurately (Google Search Central).

For salary, show the wage on the page and encode it as a monetary amount with a quantitative value, such as an hourly minimum and maximum, using the applicable currency and unit. “Competitive pay,” “great earning potential,” or an on-page range that differs from the markup creates an avoidable policy and applicant-trust problem. Google’s JobPosting documentation identifies salary information as structured data that must accurately represent the job (Google Search Central).

For employment type, do not label a variable-hours caregiver role as full-time merely because the agency hopes to fill a full-time schedule. Match FULL_TIME, PART_TIME, CONTRACTOR, temporary, seasonal, or other applicable values to the advertised arrangement, and state split shifts, weekends, live-in assignments, or per-diem availability visibly.

Before escalating the issue, collect an evidence packet containing:

• the exact job URL and the preferred canonical URL;
• the Rich Results Test result and named error or warning;
• Search Console URL Inspection status, indexed canonical, and last crawl date;
• a page-source excerpt containing the JobPosting JSON-LD;
• a screenshot of the visible title, location, wage, employment type, expiration status, and Apply button;
• the application-path test result, including the final ATS or franchise URL reached;
• a note stating whether the issue is markup validity, crawlability, indexing, canonical selection, duplication, or job-panel visibility.

Key takeaways

• A passing JobPosting test establishes technical eligibility, not immediate crawling, indexing, canonical selection, or Google Jobs display.
• A filled job can remain visible while Google processes a recrawl, especially when the page or ATS application route still returns an active opening.
• One caregiver vacancy should have one preferred, consistently identified job URL rather than competing agency, ATS, franchise, and location-page copies.
• Home care job markup must match the visible hiring location, hourly wage or range, and actual employment arrangement.

Google Jobs Eligibility Checklist for Home Care Agencies

A home care agency can audit every active caregiver, CNA, HHA, RN, scheduler, and office role with one repeatable checklist: confirm the page can be crawled, the visible job matches its JobPosting markup, applications work, and the role is closed everywhere when hiring stops. Fix eligibility and application failures before spending time on Google Jobs visibility, rankings, Indeed sponsorships, or click volume.

Google Jobs eligibility is the condition in which an individual, live job page provides Google-readable JobPosting data and an accurate applicant experience that Google can crawl, index, and potentially surface in job search results.

This final operating procedure turns the earlier schema audit, maintenance process, and error-diagnosis sections into a role-by-role control sheet. Google’s job-search ecosystem accepts structured job listings from employers and job-search sites, but markup is not a promise of placement or applicant volume (Search Engine Land).

Home Care Agency Google Jobs Audit Checklist

Use the following checklist for each active job, not only for the main careers page. Copy it into a spreadsheet, ATS task, or printable hiring packet; record the page URL, reviewer, review date, and correction owner.

A technician reviewing this sheet typically finds operational failures before markup failures: a caregiver page is valid in testing but routes to a closed ATS requisition, the compensation in the schema was updated but not the page, or a recruiter has no alert when a form is submitted. Those failures should be treated as urgent because they waste the applicant’s intent after the agency has earned the click.

When to Fix JobPosting Schema Versus Use Indeed

Fix page access, accurate visible content, valid JobPosting data, current dates, and the application path before diagnosing Google Jobs visibility or buying applicant traffic. Invest in owned Google-eligible job pages for recurring roles and locations; add Indeed or sponsored recruiting when a documented coverage gap requires applicant volume sooner than owned pages are producing it.

Owned job pages and Indeed do different work. Google job discovery can send a searcher to a page the agency controls, while Indeed can place an agency in an active job-seeker marketplace through employer tools and sponsored campaigns. Google Jobs is a search-result feature rather than a substitute for a recruiting operating system, and job-related SERP features are separate from ordinary blue-link rankings (Semrush).

Do not classify “Google did not show us” as a ranking problem until the earlier error-diagnosis workflow rules out crawlability, indexing, canonical conflicts, stale dates, duplicate listings, and application failure. Structured data can make a page understandable, but it does not override weak job information or an unusable destination; broad claims that schema alone guarantees outcomes are not supported by the wider schema debate (CMSWire).

What to Do After JobPosting Passes Rich Results Test

A passing Rich Results Test means the tested page is eligible for Google’s JobPosting enhancement; it does not confirm indexing, job-panel inclusion, application delivery, or hires. After a pass, publish or verify the live URL, inspect it in Search Console, test the applicant journey, and begin source-to-hire tracking.

Complete these actions in order:

1. Test the live application path on a phone. Submit a controlled test only if the ATS permits it, or at minimum open every step through the confirmation screen. Record where the application is received and who owns the first response.
2. Inspect the URL in Search Console. Check whether Google can index the page and whether the selected canonical is the intended individual job URL.
3. Request indexing only after a material correction or a newly published urgent role. The maintenance process already covered why a request is not a guarantee of immediate crawling or job-panel display.
4. Set a closure owner before applications arrive. The recruiter or hiring manager must notify the web or ATS owner when the role is filled, paused, canceled, or replaced.
5. Create a source label for the role. Use a unique requisition ID or application question that preserves the original source through interview, hire, and first shift.

How to Monitor Google Jobs Applications and Job Page Performance

An agency can identify recruiting sources by combining landing-page data, tagged campaign links, ATS source fields, and an applicant’s self-reported source; no single analytics report can reliably identify every Google Jobs applicant. Monitor speed to contact, interview progression, show rate, hires, first-shift completion, and the coverage gaps each job is intended to solve—not clicks alone.

Use Google Analytics 4 event documentation to define application-start and application-submit events, and use GA4 campaign parameters to distinguish Indeed campaigns, referral links, email, social posts, and other controlled links. Google’s URL-builder guidance explains the use of UTM parameters; use a consistent source and campaign naming convention rather than allowing each recruiter to invent labels.

Search Console’s Performance report documentation can show Google Search clicks and impressions for job-page URLs, but it does not prove that a particular applicant came from the Google Jobs panel. GA4 may also classify Google Jobs traffic as Google organic traffic rather than a distinct “Google Jobs” channel, and applicants can switch devices, return later through a bookmark, call the office, or submit through an ATS that does not pass source information. Treat source attribution as a reconciled record, not a perfect answer.

For each caregiver requisition, track this funnel:

• Source: Google job discovery, Google organic search, Indeed, referral, paid social, walk-in, recruiter outreach, or unknown.
• Application: completed application, not just an Apply-button click.
• Contact: recruiter contact within the agency’s written response-time target.
• Interview: interview scheduled and interview attended.
• Offer: offer made and offer accepted.
• Hire: onboarding completed.
• First-shift completion: caregiver worked the first assigned shift.

Pair that recruiting funnel with a staffing-demand sheet. For every declined client inquiry, record the requested schedule, service area, referral source, and reason the case could not be staffed. If weekend overnight inquiries in one ZIP-code cluster are repeatedly declined, the agency should connect that demand to a specifically promoted caregiver job with the same service area and shift—not boost a generic “Caregiver” listing and hope the applicants fit.

Sources

• Search Engine Land: Google’s job listings search is now open to all job search sites & developers
• Semrush: SERP Features: Jobs
• CMSWire: The Great Schema Myth?
• Google Analytics: Events
• Google Analytics: URL builders and campaign parameters
• Google Search Console: Performance report

Key takeaways

• A caregiver job is not operationally eligible until its individual page, markup, dates, and application path all match and work.
• Fix crawlability, indexing, stale listings, mismatched markup, and broken applications before evaluating Google Jobs visibility or paying for applicants.
• Use owned Google-eligible pages for durable recruiting demand and use Indeed sponsorship for documented, time-sensitive coverage gaps.
• A Rich Results Test pass starts post-publication monitoring; it does not prove indexing, Google Jobs placement, or applicant delivery.
• Measure every recruiting source through application, response speed, interview, offer, hire, and first-shift completion against specific unfilled schedules and service areas.

Gotchas

Valid schema is not visibility

Passing a validator means Google can read eligible markup; it does not mean Google will crawl, index, include, or prominently show the role in the job panel.

Robots blocking can hide noindex

robots.txt controls crawling, while noindex controls whether a crawled page may appear in Search. Blocking a URL in robots.txt can prevent Google from seeing its noindex directive.

A generic careers page is not enough

A single careers page that bundles openings, or a script-loaded careers feed without crawlable URLs per job, can leave the agency without an individual public URL for each vacancy.

Expired roles must be removed

Google requires employers to remove postings when they are no longer accepting applications. A filled role left live with missing or expired validThrough information can fail the audit.

Schema and visible content must agree

A page’s title, location, pay, employment details, expiration date, and application destination should match its JSON-LD. Hard-coded markup becomes a problem when staff update page content but not the structured data.

Key takeaways

• Valid JobPosting markup creates eligibility for Google’s job experience, not a guarantee of indexing, job-panel inclusion, or prominent visibility.
• Each active home care opening needs its own crawlable, indexable, role-specific public job URL.
• A Rich Results Test can detect Google-specific JobPosting eligibility issues, but it cannot confirm that Google will index, rank, or display a role.
• Robots controls, noindex directives, incorrect canonicals, stale listings, duplicate city pages, and broken apply links can stop an otherwise valid job from surfacing.
• Google does not charge agencies to make eligible job pages discoverable or to use the Rich Results Test and Search Console.

Related reading

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

Sources

• SERP Features: Jobs - Semrush
• The Great Schema Myth? New Research Challenges a Decade of SEO Advice - CMSWire
• Google’s job listings search is now open to all job search sites & developers - Search Engine Land