schema · 스킬 지원 에이전트
사이트의 실제 내용을 바탕으로 구조화 데이터 종류를 선택하고 JSON-LD를 점검합니다.
글, 제품, 이동 경로 같은 페이지 정보를 검색 시스템이 이해하기 쉽게 정리하고 싶을 때 사용합니다. 어떤 유형이 페이지에 맞는지와 필수 정보를 먼저 확인합니다.
화면에 없는 평점이나 후기 정보를 넣지 않도록 실제 내용과 맞춰 작성하세요. 작성한 코드는 검사 도구로 확인하고 페이지에도 적용해야 합니다. 구조화 데이터를 추가했다고 검색 화면의 확장 결과가 반드시 표시되는 것은 아닙니다.
schema로 이 도구 소개 페이지의 Article과 BreadcrumbList JSON-LD를 작성해줘. 제공한 제목·작성자·날짜·경로만 쓰고 없는 평가나 평점은 만들지 마.
받을 수 있는 결과JSON-LD 초안과 검증 항목
2026-10-05 테스트 도메인의 WebSite JSON을 작성하고 파싱을 확인했습니다. Google 리치 결과 검사나 검색 노출 효과는 확인하지 않았습니다.
예제에서 확인한 정보는 사이트 이름, 주소와 목적뿐이었습니다. 리뷰 점수, 상품 가격과 공개 날짜는 제공되지 않았습니다. 검색 화면에 잘 보이게 하려고 없는 항목을 채우지 않는 것이 출발점입니다.
skillbook.invalid는 설명용 테스트 주소입니다. 내 사이트에 적용할 때는 실제 주소로 바꾸고 페이지 내용과 이름이 일치하는지 확인하세요.
{
"@context": "https://schema.org",
"@type": "WebSite",
"name": "스킬북",
"url": "https://skillbook.invalid/",
"description": "상황별 AI 스킬과 도구 모음집"
}JSON이 읽힌다는 검사는 문법 확인입니다. 검색 엔진이 지원하는 유형인지, 노출 요건을 갖췄는지, 실제 결과에 표시되는지는 따로 확인해야 합니다. 구조화 데이터를 추가했다는 이유로 검색 순위나 특수한 결과 표시를 보장할 수 없습니다.
스킬 지원 에이전트가 필요합니다. 사이트 코드 수정과 검색 도구 검증은 별도입니다.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/schema 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 schema 스킬을 인식하는지 확인해줘.
“schema 스킬을 사용해줘. 입력 자료: 실제 페이지 내용·페이지 유형”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘JSON-LD 초안과 검증 항목’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 격리 폴더 설치·샘플 검토 2026-10-05 확인 · 에이전트 자동 호출 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: schema description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo. metadata: version: 2.0.0 --- # Schema Markup You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing schema, understand: 1. **Page Type** - What kind of page? What's the primary content? What rich results are possible? 2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing? 3. **Goals** - Which rich results are you targeting? What's the business value? ------ name: schema description: When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo. metadata: version: 2.0.0 --- # Schema Markup You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing schema, understand: 1. **Page Type** - What kind of page? What's the primary content? What rich results are possible? 2. **Current State** - Any existing schema? Errors in implementation? Which rich results already appearing? 3. **Goals** - Which rich results are you targeting? What's the business value? --- ## Core Principles ### 1. Accuracy First - Schema must accurately represent page content - Don't markup content that doesn't exist - Keep updated when content changes ### 2. Use JSON-LD - Google recommends JSON-LD format - Easier to implement and maintain - Place in `<head>` or end of `<body>` ### 3. Follow Google's Guidelines - Only use markup Google supports - Avoid spam tactics - Review eligibility requirements ### 4. Validate Everything - Test before deploying - Monitor Search Console - Fix errors promptly --- ## Common Schema Types | Type | Use For | Required Properties | |------|---------|-------------------| | Organization | Company homepage/about | name, url | | WebSite | Homepage (search box) | name, url | | Article | Blog posts, news | headline, image, datePublished, author | | Product | Product pages | name, image, offers | | SoftwareApplication | SaaS/app pages | name, offers | | FAQPage | FAQ content | mainEntity (Q&A array) | | HowTo | Tutorials | name, step | | BreadcrumbList | Any page with breadcrumbs | itemListElement | | LocalBusiness | Local business pages | name, address | | Event | Events, webinars | name, startDate, location | **For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md) --- ## Quick Reference ### Organization (Company Page) Required: name, url Recommended: logo, sameAs (social profiles), contactPoint ### Article/BlogPosting Required: headline, image, datePublished, author Recommended: dateModified, publisher, description ### Product Required: name, image, offers (price + availability) Recommended: sku, brand, aggregateRating, review ### FAQPage Required: mainEntity (array of Question/Answer pairs) ### BreadcrumbList Required: itemListElement (array with position, name, item) --- ## Multiple Schema Types You can combine multiple schema types on one page using `@graph`: ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", ... }, { "@type": "WebSite", ... }, { "@type": "BreadcrumbList", ... } ] } ``` --- ## Validation and Testing ### Tools - **Google Rich Results Test**: https://search.google.com/test/rich-results - **Schema.org Validator**: https://validator.schema.org/ - **Search Console**: Enhancements reports ### Common Errors **Missing required properties** - Check Google's documentation for required fields **Invalid values** - Dates must be ISO 8601, URLs fully qualified, enumerations exact **Mismatch with page content** - Schema doesn't match visible content --- ## Implementation ### Static Sites - Add JSON-LD directly in HTML template - Use includes/partials for reusable schema ### Dynamic Sites (React, Next.js) - Component that renders schema - Server-side rendered for SEO - Serialize data to JSON-LD ### CMS / WordPress - Plugins (Yoast, Rank Math, Schema Pro) - Theme modifications - Custom fields to structured data --- ## Output Format ### Schema Implementation ```json // Full JSON-LD code block { "@context": "https://schema.org", "@type": "...", // Complete markup } ``` ### Testing Checklist - [ ] Validates in Rich Results Test - [ ] No errors or warnings - [ ] Matches page content - [ ] All required properties included --- ## Task-Specific Questions 1. What type of page is this? 2. What rich results are you hoping to achieve? 3. What data is available to populate the schema? 4. Is there existing schema on the page? 5. What's your tech stack? --- ## Related Skills - **seo-audit**: For overall SEO including schema review - **ai-seo**: For AI search optimization (schema helps AI understand content) - **programmatic-seo**: For templated schema at scale - **site-architecture**: For breadcrumb structure and navigation schema planning
Original skill: coreyhaines31/marketingskills/skills/schema/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/schema/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.