3천건 · 관련도순
Add or repair structured data, labels that help search engines understand page content. The skill selects suitable schema types, prepares JSON-LD code, and provides validation checks while distinguishing supported Google search features from retired ones.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create output schemas, definitions of result fields and display settings, for an Apify Actor by inspecting its source code. Generate dataset and output files, add key-value storage definitions when needed, and update actor.json to reference them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or fix structured data, code that describes page content to search engines. The skill selects suitable schema.org types, prepares JSON-LD markup, and provides placement instructions and validation checks for products, articles, FAQs, and other pages.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit, create, and fix structured data, the labels that help search systems understand web pages. Get JSON-LD code for articles, products, and other page types, plus validation findings and guidance on where to place it.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema Markup Validator," "Google Rich Results Test," "FAQ schema," "Article schema," "Organization schema," "JobPosting," "HowTo," "Event," "SoftwareApplication," "BreadcrumbList," "WebSite," "Recipe," "Product," or "Dataset." For SERP feature types and zero-click patterns, use serp-features. For AI search visibility strategy (not markup), use generative-engine-optimization. For HowTo step sections (placement, copy, vs FAQ), use howto-section-generator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Schema.org structured data (JSON-LD) for any page type. Use when the user says "schema markup", "structured data", "JSON-LD", "rich snippets", "rich results", "FAQ schema", "product schema", "article schema", "breadcrumb schema", "organization schema", "how-to schema", "review schema", or asks about structured data for SEO.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a data schema specification document. Use when the user says "schema spec", "document this schema", "schema design doc", "data model spec", "table spec", "field definitions", "schema contract", "data dictionary", "define these fields", or needs to formally document a database schema, event schema, or API payload schema - even if they don't explicitly say "schema spec".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design serialization schemas using JSON Schema, Protocol Buffer definitions, or Apache Avro. Covers schema versioning, backwards compatibility, validation rules, and evolution strategies for long-lived data formats. Use when defining a new API contract or data interchange format, adding fields to an existing schema without breaking consumers, migrating between schema versions, choosing between schema systems, or documenting data validation rules for automated enforcement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a 360-degree or peer feedback process and create empty response templates from confirmed requirements. Produces consistent CSV, SQL, JSON Schema, or Notion property mappings while keeping visibility choices and scoring configuration separate.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Write, review, and upgrade Effect v4 code for Composio CLI and its related packages. It guides service definitions, typed errors, command APIs, and version alignment, checking unfamiliar APIs against source files and installed type definitions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Detect and check structured data, machine-readable descriptions of page content, and generate suitable Schema.org JSON-LD snippets. Get a report of missing fields, syntax errors, and markup issues, plus code prepared for implementation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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," or "breadcrumb schema." For broader SEO issues, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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," or "breadcrumb schema." For broader SEO issues, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author and own ONE content type's typed schema (the CONTENT-TYPE.md) at .unikit/gamedesign/content-types/CT-<slug>.md — the content / catalog layer of the GDD (cards, items, weapons, enemies, levels, quests, loot). Use whenever the user wants to ADD a new kind of content or UPDATE its schema, e.g. "add a new content type", "design the loot content", "define the card schema", "add an enemies content type", "add a rarity field to items", "switch this catalog to curated". Create the skeleton, fill its typed field schema (CT.fields), scale, relationships, and validation, AND revise the schema under the delta discipline (a schema change bumps the version + changelog). Selects the scale (bulk | curated) and self-registers content_types/content. This owns the content SCHEMA, not the catalog of values — adding individual entries/units is data handled in the editor, not a schema edit. To add or detail a system use /unikit-gd-system; to add a flow use /unikit-gd-flow; to apply a multi-zone edit use /unikit-gd-apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quando o usuário quer adicionar, corrigir ou otimizar schema markup e dados estruturados no seu site. Use também quando o usuário menciona "schema markup", "dados estruturados", "JSON-LD", "rich snippets", "schema.org", "FAQ schema", "product schema", "review schema" ou "breadcrumb schema". Para problemas de SEO mais amplos, consulte seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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," or "breadcrumb schema." For broader SEO issues, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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," or "breadcrumb schema." For broader SEO issues, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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," or "breadcrumb schema." For broader SEO issues, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recommend where new gbrain pages belong using the active schema pack, a configuration defining page types and storage paths. It also checks existing pages for missing or undeclared types and highlights cases requiring a classification decision.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.