I thought this would be a normal feature, considering it's essential to run your domains 100% through GHL. Actually quite disappointed to find that it's just half and incomplete feature, very inconvenient as some hosting platforms don't allow the redirect feature. So used to having domain flexibility before AI studio, would not have used it if I knew it was so restrictive. Will advise my clients againt it going forward, as setup is also frustrating and extremely counter intuitive, you first have to disconnect an existing domain and delete from domains completely in order for AI studio to read it, then reconnect. Even if there are no A records, you will still get an A record error reading, until it's been deleted and re added. Such a schlepp

any news on this? I actually assumed this was already available until trying to select the domain on the redirect screen major major flaw? surely this should be a critical update?

Definitely need this asap. major flaw with AI studio. If your dns records are managed by cloudflare, you should in theory, be able to set up a 301 there, but other dns managers such as wix it will not work. I tried it with wix, but since the site is in AI studio, the traffic will never hit wix servers. this may be the case with other registrars as well.

Is there any work arounds for this? i heard u can connect domain to a blank funnel step first, use the 301 redirect tool quickly, then point domain back to ai studio and itll save the redirects in the backend? but idk i dont want to try with my client.

It is URGENTLY required that they solve this at the SEO level, it is essential that this exists. The published AI Studio environment tested and ignored the public/_redirects and vercel.json redirection rules. The old URLs were still showing HTTP 200 and loading the React application instead of returning a 301 response with a location header.

Please solve this situation as soon as possible, otherwise this does not allow working with clients or migrating to the platform

It's a meaningful gap for anyone doing a migration onto the platform. I have a live site serving traffic and didn't realize it would not have this feature included. My bad for not checking first! But it is critical this is available.

Have just completed a new website with AI studio and there is no way to create or control a 301 redirect inside GHL

Yes, this is highly necessary. I have clients who's websites I want to migrate to GHL and build their site using AI Studio. I can't do this because I can't set up 301 redirects from their old site. This is losing me clients every week.

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.