A field note from shipping Sitecore Content SDK (App Router) on Vercel — where a custom-domain access restriction and an internal editing fetch collided into a cryptic 500.

One of those Sitecore issues that looks simple at first, but turns into a few hours of digging.

We had Sitecore Pages working perfectly against the open *.vercel.app URL, but the moment we switched to our protected custom domain, editing started failing with a rather unhelpful 500. The interesting part was that the problem wasn’t really Pages, Vercel, or the domain restriction on its own — it was how the Content SDK makes an internal request back to the app during editing.

Here’s what we found, and what finally fixed it.

Building an Inline Editable Checkbox Field in Sitecore XM Cloud

SitecoreAI provides content authors with inline editing for text, rich text, date, and link fields, making content management fast and intuitive. However, checkbox fields do not have native inline editing support in Page Builder.

This creates a common pain point: content editors cannot quickly toggle boolean values (like “Closed,” “Featured,” or “Active”) without a clunky workaround. Developers often resort to custom forms, separate pages, or non-intuitive modals — leading to poor UX, slower updates, and more maintenance overhead.

Our solution is to create a custom inline-editable checkbox component that integrates seamlessly with Sitecore Pages Builder and the Content SDK, giving editors the ability to toggle values directly on the page.