Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

I understand these skills can contain unsafe or unintended behavior, and I will review and security-scan before use. No warranty, suitability, or outcome is guaranteed.

MarketingFree Safe

schema-markup

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when the user wants to implement, audit, or validate structured data — schema.org, JSON-LD, rich results, FAQ/Product schema, or Search Console errors — or improve AI search visibility.

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md

---
name: schema-markup
description: Use when the user wants to implement, audit, or validate structured data — schema.org, JSON-LD, rich results, FAQ/Product schema, or Search Console errors — or improve AI search visibility.
category: Marketing
version: 1.0.0
tools: []
---

# Schema Markup Implementation

Implement, audit, and validate JSON-LD schema that earns rich results in Google, improves click-through rates, and makes content legible to AI search systems.

## Before Starting
Search the Knowledge Base for existing brand or product-marketing context before asking questions; use what exists and only ask for what's missing.

Gather: current schema state (existing markup, any rich results already showing, structured-data errors in Search Console), site details (CMS platform, page types needing markup, whether `<head>` tags can be edited directly or need a plugin/GTM), and goals (target rich-result types, AI search visibility, fix errors vs. implement net new).

## How This Skill Works
- **Audit Existing Markup**: determine what schema exists and what's broken. Check the page source and Search Console's Enhancements report, cross-reference against required-field rules per schema type, and deliver an audit report — present/broken/missing, in priority order.
- **Implement New Schema**: identify the right schema type(s) for the page (see selection table below), write complete JSON-LD populated with real page content, and advise on placement (inline `<script>` in `<head>`, CMS plugin, or GTM injection).
- **Validate & Fix**: test with the Google Rich Results Test and the Schema.org Validator, map errors to specific missing or malformed fields, and deliver corrected JSON-LD with an explanation of why each fix works.

## Schema Type Selection
Stack compatible types; never add schema that doesn't match the page content.

| Page Type | Primary Schema | Supporting Schema |
|-----------|---------------|-------------------|
| Homepage | Organization | WebSite (with SearchAction) |
| Blog post / article | Article | BreadcrumbList, Person (author) |
| How-to guide | HowTo | Article, BreadcrumbList |
| FAQ page | FAQPage | — |
| Product page | Product | Offer, AggregateRating, BreadcrumbList |
| Local business | LocalBusiness | OpeningHoursSpecification, GeoCoordinates |
| Video page | VideoObject | Article (if embedded in an article) |
| Category / hub page | CollectionPage | BreadcrumbList |
| Event | Event | Organization, Place |

**Stacking rules:** always add `BreadcrumbList` to any non-homepage with visible breadcrumbs; `Article` + `BreadcrumbList` + `Person` is a common triple for blog content; never add `Product` to a page that doesn't sell a product — Google penalizes misuse.

## Implementation Patterns
Use JSON-LD, not Microdata or RDFa — Google recommends it, it's easiest to maintain, and it doesn't touch existing HTML markup. Place it as a `<script type="application/ld+json">` block inside `<head>`; multiple schema blocks per page are fine as separate script tags or nested in an array.

**Per-page vs. site-wide:** Organization schema belongs in the site template header (site-wide); WebSite schema with SearchAction on the homepage enables a sitelinks search box (site-wide); content-specific schema (Article, Product) and BreadcrumbList matching visible breadcrumbs are per-page.

**CMS shortcuts:** WordPress SEO plugins (Yoast, Rank Math) handle Article/Organization automatically — add HowTo/FAQ via their blocks. Webflow needs custom `<head>` code per page or CMS-driven dynamic JSON-LD. Shopify auto-generates Product schema; add Organization and Article manually. Custom CMS should generate JSON-LD server-side from real field values.

## Common Mistakes
| Mistake | Why It Breaks | Fix |
|---------|--------------|-----|
| Missing `@context` | Schema won't parse | Always include `"@context": "https://schema.org"` |
| Missing required fields | Google won't show a rich result | Check required vs. recommended fields per schema type |
| `name` field empty or generic | Fails validation | Use real, specific values — not "" or "N/A" |
| `image` URL is a relative path | Invalid — must be absolute | Use `https://example.com/image.jpg`, not `/image.jpg` |
| Markup doesn't match visible content | Policy violation | Never add schema for content not on the page |
| Nesting `Product` inside `Article` | Invalid type combination | Keep types flat or use proper nesting rules |
| Deprecated properties | Ignored by validators | Cross-check against current schema.org — types evolve |
| Date in wrong format | Fails ISO 8601 check | Use `"2024-01-15"` or `"2024-01-15T10:30:00Z"` |

## Schema and AI Search
AI search systems (Google AI Overviews, Perplexity, ChatGPT Search, Bing Copilot) use structured data to parse content type faster and more reliably. FAQPage schema increases citation likelihood — AI systems pull structured Q&A directly. Article schema with `author` and `datePublished` helps AI systems assess freshness and authority. Organization schema with `sameAs` links connects the entity across the web, boosting entity recognition. Practical actions: add FAQPage schema to any page with Q&A content (even 3 questions), add `author.sameAs` pointing to real profiles (LinkedIn, Wikipedia, Google Scholar), add `Organization.sameAs` linking social profiles and a Wikidata entry, and keep `datePublished`/`dateModified` accurate.

## Testing & Validation
Always test before publishing:
1. **Google Rich Results Test** (`search.google.com/test/rich-results`) — confirms Google can parse the schema, shows which rich-result types are eligible, and distinguishes errors (no rich result) from warnings (may still work).
2. **Schema.org Validator** (`validator.schema.org`) — broader validation against the full spec; catches errors Google might miss and validates for non-Google parsers.
3. **Google Search Console** (post-deployment) — Enhancements section shows real-world errors at scale and is the only source for rich-results performance data (impressions, clicks); takes 1-2 weeks to update.

## Proactive Triggers
- FAQ-format content with no FAQPage schema — flag and offer to generate it.
- `image` missing from Article schema — required for the article rich-result card.
- Schema injected via GTM — often not indexed since it renders client-side; recommend server-side injection.
- `dateModified` older than `datePublished` — impossible, will fail validation.
- Conflicting `@type` on the same entity (e.g. separate `LocalBusiness` and `Organization` for one company) — combine or extend properly.
- `Product` schema without `offers` — won't earn a product rich result.

## Output Artifacts
Schema audit → priority-ordered findings with completeness score. New schema request → copy-paste-ready JSON-LD with placeholders marked. Error-fix request → corrected JSON-LD with a change log. AI search review → entity-markup gap analysis plus FAQPage/Organization `sameAs` recommendations. Implementation plan → page-by-page schema matrix with CMS-specific instructions.

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

1. Create a dedicated folder for this skill in your local skills library.
2. Place SKILL.md into that folder.
3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

1. Save SKILL.md in your local Syntic Code skills directory.
2. Keep related files in the same skill folder.
3. Run in a safe environment and validate outputs.

Source

https://github.com/alirezarezvani/claude-skills/blob/main/marketing-skill/skills/schema-markup/SKILL.md

Open Source Link

Marketing

Related Skills