Last verified: October 2, 2026 against Google’s Job posting structured data (docs last updated September 8, 2026) and AIOSEO’s 4.9.9 announcement.
Direct answer: JobPosting schema is structured data that labels a single open role — title, employer, work location, description, posted date — so Google can treat the page as a vacancy instead of a brochure. Done correctly, the listing becomes eligible for Google for Jobs. Eligibility is not placement. Google still decides. The markup must match what a candidate can read on the page.
Trigger for this desk: All in One SEO emailed Tygart Media on September 25, 2026 that Job Posting schema (and Event schema) now ships on every paid AIOSEO plan starting with Basic, as of AIOSEO 4.9.9. That is a product-access change, not a ranking promise. tygartmedia.com runs Rank Math. The schema type is the same either way. The plugin is a generator. Google’s Job posting structured data spec (docs last updated September 8, 2026) is the rulebook.
Why a restoration shop should care
Related: Schema Markup for AI Search: The New Meta Description · Your Google Profile Is Your New Front Door
Most restoration companies hire the way they market: on someone else’s board. Indeed, Facebook, a text to a former tech. That works until storm season, and then the shop needs a water tech in Everett, a project manager in Lynnwood, or an estimator who already knows Snohomish County adjusters. If the only public copy of the role lives on a job board, Google indexes the board. Your domain does not own the vacancy.
A careers page on your site is the durable object. JobPosting schema is the label on that object. Answer engines and Google for Jobs both prefer a page that states the role in plain sentences and then repeats the same facts in JSON-LD. That is AEO and GEO in one hang: the page answers “who is hiring water mitigation technicians in Everett, WA,” and the markup gives the city, employer, and dates without forcing the model to guess.
What Google requires
Google’s required JobPosting properties, from Search Central:
- title — the job title only. “Water Mitigation Technician,” not “Water Mitigation Technician — $28/hr — Everett — Apply Now!!!”
- description — the full description in HTML. Duties, qualifications, hours, education, experience. A teaser fails.
- hiringOrganization — the company, not the branch nickname. Name plus a sameAs URL to the official site.
- jobLocation — where the person reports. PostalAddress with addressCountry. For a 100% remote role, use jobLocationType TELECOMMUTE plus applicantLocationRequirements instead.
- datePosted — original post date in ISO 8601. Do not refresh it to fake newness.
Recommended properties that matter for a restoration hire: validThrough (when the listing dies), employmentType (FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, PER_DIEM), baseSalary as a MonetaryAmount with currency and unit (HOUR / YEAR), and identifier so you do not duplicate the same role across reprints.
AIOSEO’s walkthrough (updated August 21, 2026) maps those fields into a Schema Generator: title, description, employment type, location, hiring organization, salary, requirements, publish date, expiration date. Rank Math exposes the same JobPosting type. Fill the fields from the visible page. Do not invent a salary in schema that is missing on the page.
GEO: mark the city the truck leaves from
Local service hiring is geographic. A candidate searching “water damage technician jobs Everett WA” or “IICRC tech hiring Lynnwood” is not looking at a national career hub. Put the reporting city in the visible copy and in jobLocation.addressLocality / addressRegion / postalCode / addressCountry.
Worked example for a shop that stages out of Everett and runs the Lynnwood–Mukilteo–Mill Creek pack:
- Title on the page and in schema: Water Mitigation Technician
- hiringOrganization.name: the legal company name, not “Everett Crew”
- jobLocation: Everett, WA, United States, with the real street if that is where they report
- description: names the pack — Everett, Lynnwood, Mukilteo, Mill Creek — as service area, not as four fake job locations
- employmentType: FULL_TIME or PER_DIEM, whichever is true
- validThrough: a real close date, then take the page down or set the date in the past when the seat is filled
Do not stamp four JobPosting graphs on one page for four cities unless there are four distinct open seats. Google wants one job per leaf URL. A list page of “all openings” is the wrong surface.
AEO: write the vacancy so an engine can quote it
Schema does not rescue thin copy. Open the careers page with the answer a model can lift:
We are hiring a full-time water mitigation technician based in Everett, Washington. The role reports to our Everett shop and runs losses across Snohomish County. Pay is listed on this page. Apply on this page.
Then the body: first-day duties, IICRC or in-house training, on-call expectations, what “storm mode” means, whether the truck is assigned. That paragraph is the description field. If ChatGPT or Gemini is asked “who is hiring restoration technicians near Everett,” the engine needs a quotable sentence plus an organization it can attach to a maps entity. JobPosting is the attachment point. The sentence still has to exist in public HTML.
How to hang it in WordPress
- Create one WordPress post or page per open seat. Slug like
/careers/water-mitigation-technician-everett/. - Write the full vacancy on the page first. Salary, city, dates, how to apply.
- In Rank Math (this site) or AIOSEO Schema Generator (if that is the client stack), add schema type JobPosting. Map every field to visible text.
- Validate with Google’s Rich Results Test. Fix errors before you call it done.
- When the seat fills: set validThrough to a past date, or 404/410 the URL. Do not leave a live JobPosting on a closed role.
AIOSEO 4.9.9 made that generator available on Basic instead of reserving it for higher tiers. If a client already pays for AIOSEO, they do not need an upgrade to mark up jobs. If they are on Rank Math, they already had the type. Do not switch plugins to chase a newsletter.
What gets a listing dropped
- Markup on a jobs index that lists many roles
- Title or salary in schema that the page does not show
- Expired jobs still marked active
- No way to apply on the page
- jobLocation missing addressCountry, or a “remote” job that is not actually remote
- Keyword stuffing in the title (“#1 BEST WATER TECH JOBS SEATTLE EVERETT TACOMA”)
Google can issue a manual action for job spam. Fake seats used as lead magnets are not a grey area. If you are not hiring, do not hang JobPosting.
The line to remember
A careers page without JobPosting is a flyer. JobPosting without a real, dated, city-true vacancy is spam. Host the seat on your domain, mark the five required fields, expire it when the truck is staffed, and let Google decide whether it belongs in the job experience.
FAQ
Q: Does JobPosting schema guarantee a listing in Google for Jobs?
A: No. It makes a qualifying page eligible. Google still applies content and spam policies. The official spec is explicit on that point.
Q: We only hire on Indeed. Should we still put jobs on our site?
A: If you want the vacancy attached to your entity — maps profile, site, AI answers — yes. The board can stay as an apply path. The leaf page on your domain is what you can mark up.
Q: Can one page cover Everett, Tacoma, and Belfair?
A: One page can describe a service area. Schema jobLocation should be the report-to city. Separate open seats in separate cities need separate URLs.
Q: Is this an AIOSEO-only feature?
A: No. AIOSEO expanded plan access in 4.9.9 (announced July 13, 2026). Rank Math and hand-written JSON-LD can emit the same type. Use the generator you already pay for.
Q: What if we do not publish pay?
A: baseSalary is recommended, not required. Do not invent a number in JSON-LD. Leave it out until the page states pay.
