web-metadata

name

web-metadata

description

Expert guidance on implementing state-of-the-art (SOTA) metadata for websites, including Schema.org (JSON-LD), Open Graph, Twitter Cards, Dublin Core, COinS, and Geo-JSON. Use when you need to optimize a website for search engines (SEO), social media sharing, or academic/bibliographic interoperability. Use also when generating structured data for articles, products, local businesses, or geographic features.

Web Metadata

This skill enables the implementation of comprehensive, project-agnostic metadata to ensure maximum visibility, rich search results, and interoperability for web documents.

Workflow: Implementation Strategy

1. Identify Content Type: Determine if the page is an Article, Product, Organization, FAQ, or other specific entity.
2. Prioritize Schema.org (JSON-LD): Always implement JSON-LD as the primary structured data format for Google and other search engines.
   • See schema-json-ld.md for patterns.
   • Use available templates in assets/templates/.
3. Configure Social Presence: Implement Open Graph and Twitter Cards for predictable social sharing.
   • See social-metadata.md.
4. Identify Niche Requirements:
   • Academic/Library? → Implement Dublin Core and COinS. See legacy-academic-metadata.md.
   • Location-based? → Implement Geo-JSON or Geo Meta Tags. See geo-metadata.md.
5. Validate: Use standard validation tools to ensure zero errors in production.

Core Capabilities

1. Schema.org & JSON-LD

Generate valid JSON-LD for rich snippets.

• Tools: Refer to the Schema.org validator and Google Rich Results test.
• Reference: schema-json-ld.md.

2. Social Optimization

Ensure high-quality sharing experiences on Facebook, Twitter, LinkedIn, and Slack.

• Reference: social-metadata.md.

3. Specialty Metadata

Implementation of legacy or academic standards where required for specific industries.

• Dublin Core: For official and library systems.
• COinS: For bibliographic tools like Zotero.
• Geo-JSON: For geographic data.

Best Practices

• Prefer JSON-LD: Avoid Microdata or RDFa unless specific legacy constraints exist.
• Consistency: Ensure values (like titles and images) are consistent across Schema.org and Social Meta tags.
• Canonicalization: Always include a <link rel="canonical" href="..." /> tag to avoid duplicate content issues.
• No Placeholders: Never leave placeholder values in production metadata.