JobPosting Schema for Indian Employers

One of the few structured data types with a visible, working rich result, and one of the easiest to get a manual action from. The required fields, the expiry problem, and why salary disclosure changes your results.

Job posting markup is unusual among structured data types. It drives a prominent, working search feature, it is available in India, and it can earn you a manual action if you handle it carelessly.

Most Indian employers either do not implement it, or implement it once and then leave expired roles marked up for a year. Both are avoidable.

What it does

Marked-up job postings become eligible for a dedicated job search experience that sits above ordinary results. The listing carries the role, the organisation, the location, how recently it was posted and, where you have provided it, the salary.

For an employer this is a direct channel that bypasses job boards, and for a candidate it aggregates openings regardless of where they were published. The practical consequence is that a company careers page with correct markup competes with aggregators on terms it could not otherwise.

The fields you must get right

A posting needs a small set of properties, and the failures are almost always in how they are filled rather than in which are present.

  • title. The role only. Not the role plus the city plus urgently hiring plus the company name. A title field stuffed with extras is the most common fault on Indian careers pages.
  • description. The complete description, including responsibilities, qualifications, skills and experience, with its formatting preserved. A one-line summary here is not sufficient.
  • datePosted. When it genuinely went live. Not today’s date regenerated on every request, which is a thing some systems do and which makes every role look permanently new.
  • hiringOrganization. The actual employer. For a staffing firm posting on behalf of a client, this is where honesty matters, discussed below.
  • jobLocation. A real address with city, state and postal code. For remote roles, use the remote designation rather than inventing a location.
  • validThrough. When the posting expires. Technically optional and practically essential.
  • employmentType. Full time, part time, contract, internship.
  • baseSalary. Optional and worth discussing separately.

One posting per page. A listings page carrying markup for twelve roles at once is a common and incorrect implementation.

Expiry is where employers get into trouble

This is the specific risk worth understanding before you implement anything.

A posting that is still marked up and still live after the role has been filled is a bad result for a candidate, who applies and hears nothing. Google treats a pattern of expired postings as a quality problem, and employers have received manual actions for exactly this.

The failure is almost never deliberate. A role is filled, HR stops thinking about it, and nothing in the process removes the page.

Three ways to handle it, any of which works as long as one of them is actually wired into your hiring process.

Set validThrough on every posting at creation, with a date you are willing to defend. When it passes, the posting is no longer eligible.

Remove the page when the role closes, returning a 404 or 410. Clean, and it loses any links the page earned.

Keep the page and mark it closed, removing the markup and stating plainly that the role is filled, with a link to current openings. This is usually the best option, because it preserves the URL and gives a visitor somewhere to go. The status code question is covered in our field guide to HTTP status codes.

Whichever you choose, remove closed roles from your sitemap, as discussed in sitemaps that scale.

Salary, and the Indian convention

Most Indian postings omit salary, on the reasoning that it varies by candidate and that publishing it weakens negotiating position.

Two things are worth weighing against that. Salary is among the most used filters in job search, so an omitted figure means exclusion from a filtered search rather than neutrality. And candidates increasingly treat a missing range as a signal, usually an unflattering one.

The workable middle is a range with the basis stated. A band, with a note that the final figure depends on experience and interview outcome, gives the filter something to work with and is honest about variability.

If you genuinely cannot publish a figure, that is a business decision rather than a technical one. Make it knowingly rather than by default, and understand what it costs you in visibility.

Staffing firms and the honesty question

Recruitment consultancies face a specific tension. The client’s identity is often confidential, the same role may be posted by several consultancies, and some firms post speculative listings to collect candidate databases.

That last practice is the reason this category attracts scrutiny, and it affects everyone operating in it.

If you are a staffing firm, the defensible approach is to name yourself as the hiring organisation rather than inventing one, to post only roles that genuinely exist with a live mandate, to remove them when they close, and to avoid posting the same role under several variations to occupy more space.

The visibility benefit of doing this properly is larger than it looks, because so much of the category does not. The wider positioning question for these firms is in SEO and GEO for recruitment and staffing firms.

The page itself still matters

Markup describes a page. If the page is thin, the markup does not rescue it.

A job page that works carries the full description in readable text, the location in words as well as in markup, the employment type, the experience expected, and a clear application route. If the application happens on your own page rather than elsewhere, say so in the markup, because that is a property the feature uses.

The page must be indexable. A careers section behind a filter interface that generates no crawlable URLs per role is the most common structural reason employers see nothing from this, and it is a rendering problem rather than a markup problem.

Generate the markup from the same data that renders the page, so a change in one cannot drift from the other. The method is in automating structured data from your CMS.

What this does for assistants

Beyond the search feature, a job posting expressed as structured data is legible to anything reading your site. A candidate asking an assistant what roles a company has open is a question that can only be answered from data, and an employer whose openings exist as structured, crawlable pages is answerable while one whose roles live inside a filtered application is not.

Be realistic about scale. Large aggregators hold far more listings and will dominate general queries. Where you win is on your own name, which is exactly where a motivated candidate searches. The honest framing of what markup achieves generally is in does schema markup help you get cited.

What is a waste of effort

Marking up a listings page rather than individual role pages.

Keyword stuffing the title. It is a role name, and inflating it makes the listing look like spam to both systems and candidates.

Refreshing datePosted to keep roles looking new. It is inaccurate, candidates notice when a role has been open for months, and it undermines the signal the field exists to carry.

Posting roles you are not hiring for. Beyond the integrity problem, it is the pattern that attracts action against the whole category.

Implementing markup before fixing a careers section that generates no crawlable URLs. Fix the pages first.

A sensible order of work

  1. Confirm every open role has its own crawlable, indexable URL with the full description in text.
  2. Implement markup with one posting per page, generated from the same source as the page.
  3. Set validThrough on every posting at the point of creation.
  4. Wire role closure into your hiring process so a filled role triggers removal or a closed notice.
  5. Decide your salary disclosure position deliberately and apply it consistently.
  6. Validate on deployment so a template change cannot break the whole careers section silently.
  7. Audit quarterly for postings that are still live past their closing date.

If your careers pages produce nothing and you cannot work out whether it is markup, indexing or the page structure, get in touch.