Files

Andrew Yim 7c5efea817 Restructure skill numbering: SEO 11-30, GTM 60-69, reserve 19-28 for future skills

Renumber 12 existing skills to new ranges:
- SEO: 11→13, 12→18, 13→16, 14→17, 15→14, 16→15, 17→29, 18→30, 19→12
- GTM: 20→60, 21→61, 22→62

Update cross-references in gateway architect/builder skills, GTM guardian
README, CLAUDE.md (skill tables + directory layout), and AGENTS.md
(domain routing ranges).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-13 02:37:39 +09:00

3.2 KiB

Raw Blame History

name, description

name	description
seo-schema-generator	JSON-LD structured data generator from templates for various content types. Triggers: generate schema, create JSON-LD, schema markup, structured data generator.

SEO Schema Generator

Purpose

Generate JSON-LD structured data markup for various content types using templates.

Core Capabilities

Organization - Company/brand information
LocalBusiness - Physical location businesses
Article - Blog posts and news articles
Product - E-commerce products
FAQPage - FAQ sections
BreadcrumbList - Navigation breadcrumbs
WebSite - Site-level with search action

Workflow

Identify content type
Gather required information
Generate JSON-LD from template
Validate output
Provide implementation instructions

Schema Templates

Organization

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "[Company Name]",
  "url": "[Website URL]",
  "logo": "[Logo URL]",
  "sameAs": [
    "[Social Media URLs]"
  ]
}

LocalBusiness

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "[Business Name]",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "[Street]",
    "addressLocality": "[City]",
    "addressRegion": "[State]",
    "postalCode": "[ZIP]",
    "addressCountry": "[Country]"
  },
  "telephone": "[Phone]",
  "openingHours": ["Mo-Fr 09:00-17:00"]
}

Article

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Title]",
  "author": {
    "@type": "Person",
    "name": "[Author Name]"
  },
  "datePublished": "[YYYY-MM-DD]",
  "dateModified": "[YYYY-MM-DD]",
  "image": "[Image URL]",
  "publisher": {
    "@type": "Organization",
    "name": "[Publisher]",
    "logo": "[Logo URL]"
  }
}

FAQPage

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "[Question]",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "[Answer]"
      }
    }
  ]
}

Product

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "[Product Name]",
  "image": "[Image URL]",
  "description": "[Description]",
  "offers": {
    "@type": "Offer",
    "price": "[Price]",
    "priceCurrency": "[Currency]",
    "availability": "https://schema.org/InStock"
  }
}

Implementation

Place generated JSON-LD in <head> section:

<head>
  <script type="application/ld+json">
  [Generated Schema Here]
  </script>
</head>

Validation

After generating:

Use schema validator skill (13) to verify
Test with Google Rich Results Test
Monitor in Search Console

Limitations

Templates cover common types only
Complex nested schemas may need manual adjustment
Some Rich Results require additional properties

Notion Output (Required)

All audit reports MUST be saved to OurDigital SEO Audit Log:

Database ID: 2c8581e5-8a1e-8035-880b-e38cefc2f3ef
Properties: Issue (title), Site (url), Category, Priority, Found Date, Audit ID
Language: Korean with English technical terms
Audit ID Format: [TYPE]-YYYYMMDD-NNN

3.2 KiB Raw Blame History