Publish a job posting with Google for Jobs structured data (JobPosting schema)
domain: recruiting-general · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Add a JSON-LD script block to each job detail page with @context 'https://schema.org' and @type 'JobPosting'
Include all required fields: title (job title only, no embellishments), description (full HTML job description), datePosted (ISO 8601 date of original posting), hiringOrganization (object with @type 'Organization', name, and sameAs URL), and jobLocation (object with @type 'Place' and address including addressCountry)
Add recommended fields: validThrough (expiry date in ISO 8601), employmentType (e.g., 'FULL_TIME'), baseSalary with currency and value, and directApply if using an apply URL
Ensure the structured data content matches what is visible on the page; Google rejects postings where schema data contradicts visible content
Submit the URL to Google Search Console's URL Inspection tool to request indexing and validate the structured data
Known gotchas
The title field must contain only the job title; including location, salary, company name, or special characters in the title field will cause the posting to be rejected by Google's review process
datePosted must reflect the actual original posting date; backdating or using a future date leads to ranking penalties or eligibility removal
Remote jobs must include jobLocationType set to 'TELECOMMUTE' alongside an applicantLocationRequirements field; omitting these causes remote jobs to display with incorrect or missing location context
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?