Changelog

Update Page Metadata no longer returns an error when the slug field can’t be applied. The request now returns 200 OK with the slug field silently ignored — all other fields in the update apply as expected.

What changed

• Home pages, collection template (detail) pages, and utility pages (e.g. 404, password, search) previously returned 400 Bad Request ("Slug of index pages can't be updated", "Collection Template page slugs cannot be updated", or "Utility page slugs cannot be updated") when a slug was included. They now return 200 OK with the slug ignored.
• Secondary locales on sites without the Advanced or Enterprise Localization add-on previously returned 403 Forbidden when a slug was included. They now return 200 OK with the slug ignored.

Migration notes

If your integration relied on the previous 400 or 403 responses to detect page-type or plan restrictions, switch to comparing the returned page’s slug against the value you sent — they’ll differ when the slug was ignored.