Yoast SEO 28.3 — docs(schema-aggregator): Document new schemamap.xml site-root URL

[claude]

RC docs sync — 28.3-RC2

Product: wordpress-seo
Area: schema-aggregator
Source evidence:

• src/schema-aggregator/user-interface/schemamap-xml-rewrite-integration.php (new file): registers a WordPress rewrite rule that serves schemamap.xml at the site root via Yoast_Dynamic_Rewrites, using Front_End_Conditional (public, non-admin)
• src/schema-aggregator/application/schema_map/schema-map-xml-provider.php (new file): provider that builds and caches the XML, shared by both the REST route and the new rewrite-based URL
• Changelog (28.3): "Adds a schemamap.xml file at the site root that exposes the aggregated schema map."

Changes in this PR

• docs/features/schema/schema-aggregator/api-reference.md: adds a new "Get XML Schemamap — site-root URL (since 28.3)" section above the existing REST endpoint section, including response format, headers, and a note that both URLs share the same cache
• docs/features/schema/schema-aggregator/overview.md: updates the "Schemamap" subsection to list both the site-root URL and the REST endpoint, with the example XML updated to show the urlset format both endpoints return

Verification

• yarn build passes locally in this workflow.
• yarn lint clean for files touched by this PR.

Reviewer notes

• The rewrite integration class lives under src/schema-aggregator/user-interface/, which would normally trigger the "path contains /user-interface/" heuristic for internal surface. However, the class uses Front_End_Conditional (not admin), has no @internal annotation, and no permission callback — it is unambiguously public. The /user-interface/ layer in this codebase is the DDD presentation layer for serving HTTP responses, not an admin-only signal.
• The robots.txt integration was not changed in this RC; robots.txt still references the REST endpoint. If that changes in a future RC the robots-txt area docs will need a separate update.
• The schemamap.xml URL and the REST endpoint share the same cached XML via the new Schema_Map_Xml_Provider application service. No doc change was needed to reflect this cache-sharing in the existing filters docs (the behavior of filters like wpseo_schema_aggregator_cache_ttl is unchanged).

Sibling PRs from this RC

• Yoast SEO 28.3 — docs(sitemaps): Document new wpseo_disable_xml_sitemap_cache_priming filter #421 docs(sitemaps): Document new wpseo_disable_xml_sitemap_cache_priming filter
• Yoast SEO 28.3 — docs(indexables): Document new wpseo_indexable_indexing_failed action #422 docs(indexables): Document new wpseo_indexable_indexing_failed action

---

Authored by the RC docs-sync agent. Not auto-merged — requires human review. Run: https://github.com/Yoast/developer/actions/runs/30983367949

[cloudflare-workers-and-pages]

Deploying yoast-developer with    Cloudflare Pages

Latest commit:	9017638
Status:	✅  Deploy successful!
Preview URL:	https://dd9f5dcf.yoast-developer.pages.dev
Branch Preview URL:	https://rc-sync-wordpress-seo-28-3-r.yoast-developer.pages.dev

View logs