Structured Data & Semantic Web

인물 구조화 데이터

Person is an entity description that can be nested inside an article’s author property, whereas ProfilePage describes the page focused on that person. For coauthored work, list authors as an array so each contributor is identified transparently. As automated content production expands, accurately identifying the people who wrote or reviewed material remains valuable context. Markup should reflect genuine contributions and does not independently establish expertise.

Business applications and impact#

Helps systems reconcile author identity and stated credentials and may contribute to accurate entity understanding.

Implementation guidance and considerations#

Use sameAs links that genuinely identify the person and keep jobTitle and worksFor consistent with their actual current role.

Code example#

{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "김전문",
  "jobTitle": "테크니컬 SEO 리드",
  "worksFor": { "@type": "Organization", "name": "MKTGLab" },
  "sameAs": ["https://www.linkedin.com/in/kimjeonmun"]
}

Knowledge Panel

지식 패널

A search-results information panel summarizing an entity such as a person, organization or place.

FAQPage Schema

FAQ 구조화 데이터

Markup that describes a set of frequently asked questions and answers, eligible in supported cases for expanded search presentations.

Google Discover

Google Discover

Google's personalized content feed, which recommends material based on interests and activity without requiring a search query.

JSON-LD

JSON-LD 구조화 데이터

A structured-data format that expresses linked data as JSON in a script element, commonly used in an HTML head.

QAPage Schema

Q&A 구조화 데이터

Structured data for a page containing one question with multiple answers contributed by users.