Jobsurface: job pages built for Google's job search

A job board can hold thousands of listings and still show none of them in Google's job search. Markup sits on search pages, expired jobs stay live with markup, salaries the employer never gave appear in baseSalary, and sitemaps claim every page changed today. Jobsurface turns a job dataset into one public page per job with valid JobPosting markup, honest sitemaps and a removal flow Google accepts.

What it does

• Markup rights gate: per source, records whether you may host a page, whether the employer publishes the job and whether there is a public apply URL. Live-only feeds get a link out.
• One page per job: app/jobs/[slug]/page.tsx, description visible without login, plus added value such as parsed requirements.
• Exact field mapping: employer title verbatim, original datePosted, the employer as hiringOrganization, baseSalary only when the employer gave it, TELECOMMUTE only for 100% remote with at least one country.
• Safe JSON-LD: native script tag, < escaped, description HTML limited to p, ul, li; one canonical per job.
• Split sitemaps: max 50,000 URLs each, live jobs, real lastModified.
• Clean expiry: one of Google's three removal methods (past validThrough, 404 or 410, or markup removed), dropped from the sitemap, then URL_DELETED.
• Indexing API within quota: 200 publish calls a day by default, for new and deleted jobs.

How it works

1. Gate each source, then build the page with a canonical.
2. Emit JSON-LD typed with schema-dts.
3. Split sitemaps and list them in robots.ts.
4. Run expiry on a schedule with an alert.
5. Notify and validate: Indexing API, Rich Results Test on 5 sample URLs, then Search Console.

Frameworks & tools

Next.js App Router (generateSitemaps, proxy.ts), schema-dts, Google Indexing API, Rich Results Test and Search Console.

Why this beats prompting it yourself

A general prompt adds JobPosting markup everywhere. This skill follows Google's job posting policies: no markup on list pages, no estimated salaries, no rewritten titles, noindex alone is not a removal method, and the Indexing API is used for job pages only.

Use cases

• Job boards and aggregators wanting Google job search traffic.
• Careers sites, where you may set salary and direct apply.
• Fixing rich result errors or expired jobs in search.

Known limitations

Not for feeds that forbid rehosting, search or category pages, sourcing jobs, or page speed and copy. Examples are written for Next.js. The skill checks validity, not ranking.