Sitemap Support

Generate a dynamic /sitemap.xml endpoint with lastmod values for Orquestra pages.

21|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/berkayoztunc/orquestra --skill sitemap-support
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Sitemap Support
Source: https://github.com/berkayoztunc/orquestra/tree/main/packages/frontend/assets/.well-known/agent-skills/sitemap
Command: npx skills add https://github.com/berkayoztunc/orquestra --skill sitemap-support

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

You need reliable search discoverability for Orquestra’s public pages, especially as new programs are published and update frequently.

Core Features & Use Cases

  • Dynamic sitemap at /sitemap.xml that reflects the current public registry without requiring a frontend rebuild.
  • Canonical indexing support for Orquestra’s main site pages on https://orquestra.dev.
  • Fresh program discovery including per-program lastmod values so search engines can prioritize updates.

Quick Start

Ask your AI agent or frontend tooling to verify that robots.txt points to /sitemap.xml and then confirm that newly added public program pages appear with up-to-date lastmod timestamps.

Frequently Asked Questions about Sitemap Support

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

FAQPage Schema
How do I generate a dynamic sitemap.xml without rebuilding the frontend?

A dynamic sitemap.xml endpoint generates at request time, reflecting current public registry pages and their accurate lastmod timestamps without requiring a frontend rebuild.

Why does my robots.txt need to point to a sitemap for search engine discovery?

Robots.txt must include sitemap discovery linkage so search engines can find and index canonical site pages alongside registry-derived public program pages for accurate search discovery.

How do I ensure search engines index newly published public program pages with accurate lastmod dates?

Request-time sitemap generation includes per-program lastmod values so search engines can prioritize indexing newly published public program pages and their recent updates accurately.

Can I apply canonical indexing support to public registry pages that update frequently?

Yes, canonical indexing support applies to registry-derived public program pages that update frequently, ensuring accurate last modification dates for search engine prioritization.

What is the best way to make new program pages discoverable instantly without frontend deployment?

Publishing a dynamic /sitemap.xml endpoint makes new program pages discoverable instantly by generating the sitemap at request time, reflecting the current public registry without frontend deployment.

When should I not use a static sitemap for SEO indexing?

Static sitemaps are unsuitable when public program pages update frequently, as they require frontend rebuilds and cannot provide accurate lastmod timestamps for fresh program discovery.