ServicesAI Audit
← Back to Blog

How to Use EducationalOccupationalCredential Schema for AI Trust

Schema MarkupAI VisibilityJSON-LDLLM SEOEducationalOccupationalCredentialStructured DataAI Trust
Software developer analyzing code on a tablet in a modern office workspace.

Why AI Search Engines Care About Credentials

When ChatGPT, Perplexity, or Gemini recommends a professional, a course provider, or a qualified practitioner, it is not just pattern-matching keywords. These systems are actively looking for signals of authority and trustworthiness. One of those signals is structured data that explicitly states what qualifications someone holds, who granted them, and what they relate to.

This is exactly what EducationalOccupationalCredential schema does. It gives AI systems a machine-readable record of credentials, certifications, degrees, and professional qualifications. Without it, that information might exist on your page in plain text, but an AI model has to infer it. With it, the information is unambiguous.

If your business involves qualified professionals, certified trainers, licensed practitioners, or accredited services, this schema type is one of the more underused tools available to you. Most sites skip it entirely, which means implementing it correctly is a meaningful differentiator right now.

What EducationalOccupationalCredential Actually Describes

The EducationalOccupationalCredential type sits within the Schema.org vocabulary and describes a credential gained through education or occupational experience. That covers a wide range of real-world scenarios:

  • University degrees (BSc, MBA, PhD)
  • Professional certifications (ACCA, CFA, PRINCE2, Google certifications)
  • Trade licences (electrical, gas safe, legal practising certificates)
  • Continuing professional development (CPD) awards
  • Vocational qualifications (NVQs, BTECs, apprenticeship completions)
  • Course completion certificates

The schema type is most commonly used as a property of Person schema, attached to the hasCredential property. It can also appear within EducationalOccupationalProgram to describe what credential a course awards upon completion.

The key properties you will use most often are:

  • name: The name of the credential (e.g. "Chartered Financial Analyst")
  • credentialCategory: The type (degree, certificate, licence, etc.)
  • recognizedBy: The organisation that recognises or awards it
  • educationalLevel: The level of education (undergraduate, postgraduate, etc.)
  • validFor: How long the credential is valid
  • url: A link to the awarding body or verification page

A Practical JSON-LD Example for a Professional Profile

Let's say you run a financial planning firm and want AI search engines to understand that your lead adviser holds a Chartered Financial Planner qualification from the Chartered Insurance Institute. Here is how you would mark that up:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Sarah Whitfield",
  "jobTitle": "Senior Financial Planner",
  "url": "https://example.com/team/sarah-whitfield",
  "hasCredential": [
    {
      "@type": "EducationalOccupationalCredential",
      "name": "Chartered Financial Planner",
      "credentialCategory": "Professional Certification",
      "recognizedBy": {
        "@type": "Organization",
        "name": "Chartered Insurance Institute",
        "url": "https://www.cii.co.uk"
      },
      "url": "https://www.cii.co.uk/chartered-financial-planner"
    },
    {
      "@type": "EducationalOccupationalCredential",
      "name": "BSc (Hons) Financial Services",
      "credentialCategory": "degree",
      "educationalLevel": "undergraduate",
      "recognizedBy": {
        "@type": "Organization",
        "name": "University of Manchester"
      }
    }
  ]
}

Place this inside a <script type="application/ld+json"> tag in the <head> of the relevant page, or in the <body> before the closing tag. Either works. The <head> is often cleaner from a maintenance perspective.

Notice the use of an array for hasCredential. A person can hold multiple credentials, and listing them all gives AI systems a richer picture of that individual's qualifications.

Using EducationalOccupationalCredential Within Course Schema

If you offer training or education, this schema type becomes even more powerful when nested inside EducationalOccupationalProgram or Course schema. You can tell AI models exactly what credential a learner earns upon completing your programme.

{
  "@context": "https://schema.org",
  "@type": "Course",
  "name": "Advanced Google Ads Certification Programme",
  "description": "A 12-week intensive course covering advanced PPC strategy and Google Ads campaign management.",
  "provider": {
    "@type": "Organization",
    "name": "Digital Skills Academy",
    "url": "https://example.com"
  },
  "educationalCredentialAwarded": {
    "@type": "EducationalOccupationalCredential",
    "name": "Advanced Google Ads Practitioner Certificate",
    "credentialCategory": "certificate",
    "recognizedBy": {
      "@type": "Organization",
      "name": "Digital Skills Academy"
    },
    "validFor": "P2Y"
  }
}

The validFor property uses ISO 8601 duration format. P2Y means two years. P1Y6M would mean one year and six months. If the credential does not expire, you can omit this property entirely.

When a user asks Perplexity or Gemini something like "what courses give you a Google Ads certification", your structured data makes it significantly easier for the AI to identify your programme as a direct, confident answer. That is the practical value here.

How AI Systems Use This Data to Build Trust

AI language models are trained on vast amounts of text, but when they are augmenting their responses with live web data (as Perplexity, Bing Copilot, and Gemini do), they prioritise sources that are easy to interpret. Structured data removes ambiguity.

Consider two scenarios. In the first, a physiotherapy practice has a bio page for one of their practitioners. It says in plain text: "James qualified from King's College London and holds a HCPC registration." In the second, the same information is expressed in EducationalOccupationalCredential schema with recognizedBy pointing to the Health and Care Professions Council.

When an AI system is evaluating whether to cite this practitioner as a qualified source, the structured data in scenario two removes any need for inference. The AI does not have to parse a paragraph and decide whether "HCPC registration" constitutes a professional licence. The schema says it explicitly.

This matters most in regulated industries. Healthcare, finance, law, education, construction, and food safety are all areas where AI systems are cautious about recommending practitioners without clear evidence of qualification. Schema markup is one of the clearest signals you can provide.

At FlinnSchema, we see this pattern regularly when auditing client sites. Professionals with strong real-world credentials are being ignored by AI systems, not because the credentials are not on the site, but because they are buried in unstructured text. Adding the right schema changes that quickly.

Common Implementation Mistakes to Avoid

A few errors come up consistently when businesses first implement this schema type.

Omitting the recognizedBy property

A credential without a recognising body is much weaker. AI systems assign more weight to credentials that are tied to a named, verifiable organisation. Even if the credential is awarded by your own company (for internal training, for example), name the organisation explicitly. If it is an external body, link to their website using the url property within the nested Organization node.

Using vague credentialCategory values

Schema.org suggests using values from the ISCED framework for credentialCategory, but in practice, using clear plain-English values like "degree", "certificate", "licence", or "diploma" works well and is what AI systems tend to interpret most reliably. Avoid vague strings like "qualification" or "achievement".

Placing schema only on the homepage

If you have individual team member profile pages, the schema should live on those pages, not just the homepage. AI systems crawl individual URLs. A credential schema buried in a JSON-LD block on the homepage, referencing a person whose profile page has no structured data, is weaker than having the schema on the profile page itself.

Forgetting to validate

Always run your implementation through Google's Rich Results Test and Schema.org's validator. Syntax errors in JSON-LD are silent failures. The page looks fine, but the schema is not being read. A missing comma or an unclosed bracket will break the entire block.

If you are not sure where your schema implementation stands right now, a free AI visibility audit is a good starting point before you start adding new markup.

Who Should Prioritise This Schema Type

Not every e-commerce brand needs EducationalOccupationalCredential schema. But it is genuinely important for a specific set of businesses.

Professional services firms

Solicitors, accountants, financial advisers, architects, and chartered surveyors all operate in regulated environments where credentials matter. If your firm's credibility depends on the qualifications of your team, this schema should be on every team member's profile page.

Training and education providers

If you sell courses that lead to a qualification, expressing what that qualification is in structured data helps AI systems recommend your courses when someone asks about getting certified in your subject area. Combined with Course schema, this creates a strong signal about your offering.

Healthcare and wellness practitioners

GPs, physiotherapists, nutritionists, therapists, and other practitioners are increasingly being surfaced by AI systems in response to health queries. Structured data confirming their regulatory body registrations is a direct trust signal.

Freelancers and consultants with personal brand sites

Consultants who rely on their expertise being recognised should combine EducationalOccupationalCredential with ProfilePage schema. The two work well together to build a machine-readable picture of who you are and why you are qualified to do what you do.

A Note on Staying Current

Credentials sometimes expire. Practitioners gain new qualifications. If your schema references a certification with a validFor date that has passed, that could undermine trust rather than build it. Make a habit of reviewing credential schema alongside your regular content audits. Quarterly checks are usually sufficient for most practices, but any time a team member gains or loses a qualification, the markup should be updated promptly.

This is part of the broader question of schema maintenance. If you want to think through how frequently your structured data needs attention, this guide on schema update frequency walks through a sensible framework for different schema types.

Frequently Asked Questions

Does EducationalOccupationalCredential schema directly affect Google rankings?

Not directly in terms of traditional Google rankings. It is not a schema type that triggers a rich result in Google Search the way FAQ or Product schema does. Its primary value is in helping AI search engines and language models understand and trust the qualifications of a person or the credential awarded by a programme. Think of it as an AI trust signal rather than a Google ranking factor.

Can I use this schema if my team's qualifications are not from well-known bodies?

Yes. The schema still adds value even if the recognizedBy organisation is not a household name. What matters is that the information is accurate, complete, and linked to a real, verifiable organisation with its own URL. AI systems can follow those links and assess the credibility of the awarding body independently.

How is EducationalOccupationalCredential different from just mentioning qualifications in plain text?

Plain text requires an AI to infer meaning. Structured data states it explicitly. When an AI model is processing your page to decide whether to cite your team as qualified practitioners, a clear JSON-LD credential block is interpreted with much higher confidence than a paragraph that mentions the same information in passing. It removes ambiguity from the equation.

Should I include credentials for every member of staff, or just senior people?

Focus on people whose credentials are relevant to the services you are promoting and likely to be asked about in AI queries. For most businesses, this means client-facing professionals, named experts, or anyone whose qualifications directly support your claims of authority. Back-office staff with credentials that are not relevant to your core offering probably do not need this treatment unless you have a specific reason to surface their expertise.

Want to check your AI visibility?

Run a free audit on your website and see how visible you are to ChatGPT, Perplexity, and other AI search engines.

Run Free Audit