content-seo-standards

Enforce per-page metadata, heading hierarchy, and JSON-LD during planning and QA.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/calebaero/website-factory --skill content-seo-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-seo-standards
Source: https://github.com/calebaero/website-factory/tree/main/skills/content-seo-standards
Command: npx skills add https://github.com/calebaero/website-factory --skill content-seo-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize content structure and SEO hygiene across every site the plugin produces, ensuring consistent page titles, descriptions, headings, image alt text, canonical URLs, sitemap.xml, robots.txt, and JSON-LD data.

Core Features & Use Cases

  • Per-page metadata rules for title, description, canonical URL, robots and social tags (Open Graph/Twitter).
  • Heading hierarchy enforcement to keep exactly one H1 per page and proper H2/H3 structure.
  • URL and asset guidelines: lowercase, kebab-case URLs; proper alt text for images; appropriate image formats and loading behavior.
  • Structured data templates and JSON-LD blocks aligned with home, local business, and content types.
  • Archetype-aware thresholds and QA alignment: different SEO thresholds per archetype and QA pre-flight checks that align with the qa standards.

Quick Start

Apply these standards to every page by validating per-page metadata, structure, and JSON-LD during planning and QA.

Frequently Asked Questions about content-seo-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize SEO metadata like canonical URLs and JSON-LD across multiple sites?

You can standardize SEO metadata by applying per-page rules during planning and QA to enforce canonical URLs, JSON-LD data, and social tags consistently across every site produced.

What's the best way to enforce heading hierarchy and ensure exactly one H1 per page?

The best way to enforce heading hierarchy is to apply structural rules during the QA pre-flight checks, ensuring exactly one H1 per page and proper H2 and H3 nesting across all archetypes.

How do I generate a compliant sitemap.xml and robots.txt for different page archetypes?

Generate a compliant sitemap.xml and robots.txt by applying archetype-aware SEO thresholds that enforce proper URL structures, metadata, and crawler directives during the QA phase.

Can I use different SEO thresholds for local business and home page archetypes?

Yes, you can use different SEO thresholds because the standards are archetype-aware, applying specific metadata, JSON-LD templates, and heading rules tailored to home, local business, and content types.

How do I validate Open Graph and Twitter social tags during content planning?

Validate Open Graph and Twitter social tags by running pre-flight QA checks that align with content standards, ensuring all per-page metadata is compliant before publishing.

Why does my page fail QA checks for image alt text and URL structure?

Pages fail QA checks when they do not meet asset guidelines requiring lowercase, kebab-case URLs and proper alt text for images, which are enforced during the planning and validation phases.