Job Title Schema Markup: Which Property You Actually Need

The Short Answer

For a job opening, put the plain role title in title and nothing else. Google's documentation states it directly: the title of the job, not the title of the posting, with "Software Engineer" and "Barista" given as examples.

Everything people habitually cram in alongside it already has a home. The employer goes in hiringOrganization, the city in jobLocation, the pay in baseSalary, the requisition code in identifier. Google specifically advises against putting job codes, addresses, dates, salaries, or company names in the title.

Which Property Do You Need?

If you landed here for the second row, skip to Person.jobTitle further down. Everything between here and there is about job openings.

What Google Expects in JobPosting.title

The rule is narrower than most people assume, and it is easiest to hold as a single question: would a candidate type this into a search box? "Registered Nurse" yes. "Join our award-winning care family" no. That is essentially the whole standard.

Google's stated guidance adds three things to avoid. Do not include job codes, addresses, dates, salaries, or company names. Do not use clickbait or promotional phrasing, where the documentation gives "Apply now for IT job -FRENCH speaker in Bucharest" as a not-recommended example against the suggested "Market Specialist, French speaker". And do not use excessive special characters such as exclamation marks and asterisks, which can read as spam.

{
  "@context": "https://schema.org",
  "@type": "JobPosting",
  "title": "Senior Software Engineer",
  "hiringOrganization": {
    "@type": "Organization",
    "name": "Acme Corp"
  },
  "jobLocation": {
    "@type": "Place",
    "address": {
      "@type": "PostalAddress",
      "addressLocality": "Austin",
      "addressRegion": "TX",
      "addressCountry": "US"
    }
  },
  "identifier": {
    "@type": "PropertyValue",
    "name": "Acme Corp",
    "value": "REQ-4471"
  }
}

Note where the requisition code went in that example. identifier takes a PropertyValue, so you keep the reference without it ever touching the field Google matches searches against.

Before and After

These are the patterns that show up over and over in imported feeds and hand-written listings.

On a job board the fix is almost never per-listing. These titles arrive from employers or feeds already malformed, so the durable answer is a normalization step at import: strip trailing employer names, pull bracketed codes into identifier, and flag titles carrying currency symbols or runs of punctuation for review.

Why This Affects Matching, Not Validation

This is the part that makes bad titles persist for years. A validator only checks that title exists and is a string. "Join Our Rockstar Team!" passes the Rich Results Test exactly as cleanly as "Senior Software Engineer", so nothing in your tooling ever complains.

The cost lands somewhere no report shows you. Google for Jobs matches candidate queries against the role, and candidates search job titles. A posting whose title contains no job title has nothing to match against, so it competes for almost nothing and quietly underperforms while looking perfectly healthy in Search Console. If you are chasing errors in that report, see what each Google for Jobs schema message means, but understand that this particular problem will never appear there.

The Other One: Person.jobTitle

Different property, different purpose, and much simpler. jobTitle is a plain text property on a Person, used to say what role a named individual holds. It appears on about pages, team pages, and author bylines, and it helps search engines connect a person to an organization and a field of expertise.

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Simon Gingras",
  "jobTitle": "Founder, Kardow",
  "url": "https://kardow.com/author/simon-gingras"
}

That example is not hypothetical. This article's own byline emits exactly that markup, so you can view source on this page and find the Person object with its jobTitle in the Article structured data.

One thing to keep straight: Person.jobTitle has no role in Google for Jobs. It will not make a job appear, and adding it to a job posting page does nothing for job search. If you are trying to get listings into Google for Jobs, JobPosting.title is the property you want.

Getting It Right by Default

Our job posting schema generator gives the title its own field, separate from employer, location, and salary, so there is nowhere to cram the extras even if you wanted to. Worth being clear about the limit though: it does not rewrite what you type. If you paste marketing copy into the title box, marketing copy is what comes out. The structure nudges you toward the right shape and the required properties, and the judgement stays yours.

For the wider picture, including how the title interacts with everything else Google needs before a listing becomes eligible, see the full JobPosting schema guide. If you are earlier than that and just need the concept, structured data for job postings explained from scratch is the starting point.

Frequently Asked Questions