citec-seo-routing

Implements route metadata, JSON-LD, sitemap, RSS, and manifest SEO for the CITEC Astro frontend.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/TOBIASpuchito/Citec --skill citec-seo-routing-tobiaspuchito
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: citec-seo-routing
Source: https://github.com/TOBIASpuchito/Citec/tree/main/citec-frontend/.codex/skills/citec-seo-routing
Command: npx skills add https://github.com/TOBIASpuchito/Citec --skill citec-seo-routing-tobiaspuchito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping SEO metadata consistent across an Astro site is error-prone: canonical URLs, Open Graph tags, JSON-LD, sitemaps, and feeds often get duplicated, hardcoded, or forgotten on individual routes. This Skill enforces a single SEO architecture for the CITEC frontend so every route ships correct, specific metadata. ## Core Features & Use Cases - Centralized Metadata via BaseLayout: Keeps canonical URLs, Open Graph, Twitter metadata, JSON-LD, header, and footer in BaseLayout.astro instead of duplicating them per page. - Structured Data Helpers: Uses helpers from src/utils/seo.ts such as breadcrumbJsonLd, itemListJsonLd, pulseArticleJsonLd, eventJsonLd, and faqPageJsonLd for route-specific structured data. - Generated Route Endpoints: Maintains robots.txt, rss.xml, and site.webmanifest endpoints and validates changes with bun run build. - Use Case: When adding a new article detail route, the Skill ensures the page passes ogType="article", ISO-compatible publishedTime and modifiedTime, and article JSON-LD describing only visible content. ## Quick Start Use the citec-seo-routing skill to review and implement the SEO metadata, JSON-LD, and canonical URL for the new events route in the CITEC frontend.

Frequently Asked Questions about citec-seo-routing

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

FAQPage Schema
How do I add SEO metadata to an Astro page route?▼

Declare a specific title and description through the shared BaseLayout component for every route. Keep canonical URLs, Open Graph, and Twitter metadata centralized in BaseLayout rather than duplicating them in individual page components.

How do I add JSON-LD structured data in Astro?▼

Use helper functions like breadcrumbJsonLd, itemListJsonLd, eventJsonLd, and faqPageJsonLd from a central seo utility module. Only add route-specific JSON-LD that describes content actually visible on the page.

How do I generate robots.txt and RSS feeds in Astro?▼

Create endpoint files such as src/pages/robots.txt.ts and src/pages/rss.xml.ts that generate the output dynamically. Keep global values like the site URL in a central data module instead of hardcoding them in endpoints.

Should article pages use different Open Graph metadata?▼

Yes, article and dynamic detail routes should pass ogType="article" along with ISO-compatible publishedTime, modifiedTime, and section values. This gives social platforms and crawlers accurate content typing and freshness signals.

Why should canonical URLs not be hardcoded in page components?▼

Hardcoding the site URL, locale, or OG image in pages causes inconsistencies when the domain or branding changes. Centralizing these values in a site data module and BaseLayout ensures every route stays consistent automatically.