Person structured data write out and implement

Structured data is a method of presenting information in an organized and uniform manner. In the context of Web sites and SEO, this means using a specific format to provide information about Web pages and their content. This allows search engines to quickly and accurately understand and index the page content, contributing to better visibility and search results.

The importance of structured data cannot be underestimated. It helps search engines such as Google understand what the content of a Web page is, and then use this information to present more relevant and richer search results. This can result in improved click rates, higher visibility and ultimately a better user experience for website visitors.

Different types of structured data (microdata, RDFa, JSON-LD)

There are several formats for structured data, each with its own characteristics and applications:

  1. Microdata: This is a specification to integrate structured data into HTML. It allows developers to insert markups directly into the HTML code of a Web page, making it easier for search engines to recognize the various elements of a page.
  2. RDFa (Resource Description Framework in attributes): RDFa is a way to integrate rich metadata related to Web content. It offers more flexibility than Microdata and is often used in conjunction with HTML5.
  3. JSON-LD (JavaScript Object Notation for Linked Data): This is currently the most recommended format for structured data by Google. It is a method for presenting structured data in JavaScript objects, making it easier to separate from the main content of the page.

Person structured data in a nutshell

No time for a long article? No problem. Watch the video below for a summary of this article.

Person structured data (video).

What is ‘Person’ in structured data

In the context of structured data, “Person” refers to a specific type of entity that represents information about individuals. This can range from general information such as name, occupation and contact information to more specific information such as awards, educational background, or family members. Using the “Person” tag helps search engines understand that the information provided relates to an individual, which is essential for things such as personal branding, displaying author information in search results, or providing detailed information in knowledge maps.

When do I use Person structured data?

Some common scenarios in which “Person”-structured data can be useful include:

  1. Personal websites and portfolios: For professionals who want to highlight their work and expertise. By using structured data, an individual can have his/her information prominently displayed in search results.
  2. Social media profiles: To provide a unified and rich presentation of a person across platforms.
  3. Articles and blog posts: Authors can use structured “Person” data to display their profile information in search results, giving their work more authority.
  4. Company pages: For showcasing key employees or executives on company websites, which can help build trust and credibility.

These applications illustrate how “Person” structured data can not only improve search engine visibility, but also contribute to a richer and more informed user experience.

Basis of Schema.org and ‘Person’ Type

Schema.org is a partnership between major search engines such as Google, Microsoft, Yahoo, and Yandex. The goal is to create a common set of schemas for structured data on the Internet, Web pages and e-mails. Using Schema.org improves the display of Web pages in search results, making them richer and more relevant.

Detailed overview of the ‘Person’ type within Schema.org

Schema.org’s ‘Person’ type is designed to mark information about individuals. It provides a standardized way to display details such as name, contact information, occupation, and much more. This type is particularly useful for improving the visibility of personal profiles, author information and biographical data in search engines.

Important properties and attributes of ‘Person’

Some important properties of the ‘Person’ type include, but are not limited to:

  • additionalName: For additional names or middle names.
  • address: The physical address of the person.
  • Affiliation: An organization with which the person is associated.
  • birthDate: Date of birth.
  • email: Email address.
  • gender: Gender of the person.
  • jobTitle: occupational title.
  • nationality: nationality.
  • telephone: phone number.

These features are only a small part of what Schema.org offers for marking information about individuals. For a complete list and detailed descriptions of all properties available for the ‘Person’ type, visit Schema.org/Person.

Implementation of ‘Person’ Structured Data

  1. Choose the Format: First, decide whether you want to use JSON-LD, Microdata or RDFa. JSON-LD is often recommended because of its easy integration into the head section of HTML pages.
  2. Structure of the Data: Analyze what information about the “Person” you want to display. This may include name, occupation, contact information, etc.
  3. Code Writing: Write the structured data according to the chosen format specifications. Use the Schema.org properties as a guide.
  4. Integration into Web Page: Insert the structured data into the HTML of the web page. For JSON-LD, you usually place this in the <head> section.
  5. Testing: Use Google’s Structured Data Testing Tool to verify that your data is correctly implemented and understood by search engines.

Examples of code in different formats (e.g., JSON-LD, Microdata)

JSON-LD example:

jsonCopy code{ "@context": "http://schema.org", "@type": "Person", "name": "Jane Doe", "jobTitle": "Software Engineer", "telephone": "(555) 555-5555", "email": "janedoe@example.com" }

Microdata example:

htmlCopy code<div itemscope itemtype="http://schema.org/Person"> <span itemprop="name">Jane Doe</span> <span itemprop="jobTitle">Software Engineer</span> <span itemprop="telephone">(555) 555-5555</span> <a href="mailto:janedoe@example.com" itemprop="email">janedoe@example.com</a> </div>

Best practices for implementation

  • Consistency: Make sure the information you provide is consistent with the content on the web page.
  • Completeness: Use as many relevant features as possible to provide a rich and informative structure.
  • Accuracy: Check the accuracy of the information. Incorrect or misleading data can negatively impact SEO.
  • Keep up to date: Update structured data regularly to ensure it remains current.

By following these steps and best practices, you can effectively implement “Person” structured data, which can improve the visibility and relevance of your web page in search engines.

Summary

In this article, we have explored the crucial role of structured data, particularly the “Person” type of Schema.org, in the world of SEO and Web development. We have seen how structured data helps improve search engine visibility and user experience by presenting information in a standardized and machine-readable way. By providing step-by-step tutorials and examples, we demystified the implementation of “Person” structured data. This highlights the value of accurate and detailed information presentation in the digital age, essential for individuals and organizations striving for online visibility and success. For more information and opportunities around Person structured data, see this link.

Senior SEO-specialist

Ralf van Veen

Senior SEO-specialist
Five stars
My clients give me a 5.0 on Google out of 75 reviews

I have been working for 10 years as an independent SEO specialist for companies (in the Netherlands and abroad) that want to rank higher in Google in a sustainable manner. During this period I have consulted A-brands, set up large-scale international SEO campaigns and coached global development teams in the field of search engine optimization.

With this broad experience within SEO, I have developed the SEO course and helped hundreds of companies with improved findability in Google in a sustainable and transparent way. For this you can consult my portfolio, references and collaborations.

This article was originally published on 27 March 2024. The last update of this article was on 27 March 2024. The content of this page was written and approved by Ralf van Veen. Learn more about the creation of my articles in my editorial guidelines.