Skip to main content

​
SEO-only updates: PUT /seo

Declare the seo capability and Castro’s “Update Metadata” action pushes just the SEO block, title tag, meta description, keywords, without touching the entity’s content:

​
Resolving the target

The entity is identified by whichever of id, url or slug is present, often all three. Resolve them in that order of confidence: your stored id first, then the URL, then the slug against your page table. Respond 200 with { "id": "..." }, or 404 + { "error": "..." } if nothing matches.
Merge the SEO object, don’t replace it. A push carrying only a description must not wipe the title you stored earlier. This is the same partial-update rule that governs blog posts, and it’s just as easy to get wrong here.

​
Where to store it

That depends on your stack: a meta table, frontmatter fields, or your SEO plugin’s storage. What matters is that the page’s rendered <title> and <meta name="description"> actually reflect the values. The quickest way to confirm the whole path works: push an SEO update from Castro, then load the page and look at the browser tab. If the title didn’t change, the value isn’t reaching your template.

Page sync

GET /pages lets Castro map its crawl of your site onto your entity ids, which is what makes bulk SEO updates possible in the first place.

Test it

The conformance script checks PUT /seo and the SEO merge rule.