I encountered this exact issue while migrating a live blog from an AI Studio website to a new blog subdomain. The new blog was successfully published, but the old AI Studio URLs could not be given true server-level 301 redirects.

Both public/_redirects and vercel.json redirect rules were tested and ignored by the published AI Studio environment. The old URLs continued to return HTTP 200 and load the React application instead of returning a 301 response with a Location header.

This creates a serious SEO and migration risk. AI Studio needs native redirect management for exact paths, wildcard paths, cross-domain destinations, query-string preservation, bulk imports, and proper HTTP 301 responses before the application loads.

This should be treated as a core production requirement, not a minor enhancement.

Yes! Please, please, please. Somehow figure this out.

we need this ASAP, migrating websites to AI studio without loosing SEO is essential.