If you’ve ever dropped a perfectly valid Sitecore rendering into a nested <Placeholder> and watched Pages Builder (or your local app) complain that it can’t find the component in component-map.client, you’re not alone — and you’re probably not looking in the wrong place.
This post walks through a real debugging session from an XM Cloud / Sitecore Content SDK Next.js App Router site: adding a Video rendering inside an Interior Media Hero Banner placeholder. The component existed. The GraphQL query existed. The Sitecore rendering componentName was set. And yet the client still couldn’t resolve it.
The root cause wasn’t placeholder naming. It was architecture.
