GoHighLevel Funnel Redirects & 404 Pages (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 30 September 2026 · 10 min read

Some links below are affiliate links — if you sign up through them, HL Growth Partner may earn a commission at no extra cost to you. It never changes what we recommend. Full disclosure.

GoHighLevel redirects are the layer nobody organises until the traffic is already gone. A funnel gets rebuilt, a step path gets tidied, an old site gets switched off — and three weeks later the enquiries dry up.

The fix is simple, but it lives where most people never look — and nothing in the funnel builder tells you it exists. Here is where the URL Redirects tab sits, which redirect HighLevel actually issues, how to set a HighLevel 404 page worth showing, and how to find your dead URLs first.

Where GoHighLevel redirects actually live

Not in the funnel builder. Not in page settings. HighLevel's guide puts them at Settings > Domains & URL Redirects, then the URL Redirects tab — inside the sub-account, beside the domain list rather than near the pages they affect.

One prerequisite catches people out. HighLevel requires the source domain to already be added to the sub-account, so if you have not finished your domain and DNS setup for GHL funnels, the form has nothing to work with.

Each redirect offers three destination types: Custom URL, Funnel, or Website. The last two let you pick a step or page already connected to that domain, removing the typo risk.

301 vs 302: the choice that decides whether rankings move

Google is blunt. For permanent redirects, "the indexing pipeline uses the redirect as a signal that the redirect target should be canonical." For temporary ones, "Googlebot follows the redirect, but the indexing pipeline doesn't use the redirect as a signal."

Plainly: a 301 moves your rankings to the new URL; a 302 parks them on the old one. Google says permanent redirects show the new target in results, while temporary ones show the source page.

So if you need temporary behaviour, treat it as not documented in HighLevel's redirect tool rather than assuming a hidden setting. Google's crawlers also "follow up to 10 redirect hops", so point old URLs at the final destination, never at a previous migration's target.

Redirecting one page versus a whole path

Single-page redirects are the common case: one old address, one new address. HighLevel supports nested source paths, giving the example of a complete path such as /resources/guides/getting-started.

Whole-path redirects are where expectations outrun the documentation. The nested URL paths feature allows up to 5 levels of depth, refusing deeper saves with "URL path is too deep. Maximum 5 levels allowed", and is still marked Beta.

A path-level pattern — send everything under /blog/ to /articles/ and keep the tail — is not documented, so plan on one row per URL. Settling the website builder versus funnels question before launch avoids most of them existing.

Setting a HighLevel 404 page that does more than apologise

Every connected domain has two dropdowns worth filling in: Default Page and Default 404/Error Page. The first decides what loads at the bare domain; the second decides what loads when a URL no longer exists.

HighLevel added a nudge in May 2025. When a domain is connected to funnels, websites, stores, webinars or blogs but is missing either page, an "Action Required" message appears on the Connected Products screen and opens a modal for both.

Two details are easy to miss: the nudge only appears in the sub-account where the domain was originally connected, and both settings are also reachable from the domain's three-dot Edit menu.

Build it as a page, not an apology: a heading admitting the URL moved, your three highest-intent offers, and the usual header and footer.

What happens to an old funnel URL when you rename a step

HighLevel is direct: "Existing links that use the old path may stop working unless a redirect is created." Its guide recommends a 301 if the old URL is already used in ads, emails, social posts or other shared links.

The nested paths documentation agrees: when you change a live path, set up a 301 from the old address to preserve SEO equity and avoid 404s. The redirect is part of the rename, not a follow-up.

Deleting a funnel outright is less documented. HighLevel does not publish what status code a deleted step returns, or whether the domain's 404 page catches it, so verify it yourself.

A related quirk: HighLevel's guidance on Google Ads rejections describes funnels where "two different URLs load the same page" — root domain and step path — because funnels automatically include a step path. Its fix is a canonical tag, not a redirect. Those duplicates also split your attribution reporting and lead sources.

Not on HighLevel yet? Start with a free 30-day trial here — long enough to build everything in this guide before you pay a cent.

Migrating an old site's URLs into GHL without losing rankings

Do the inventory before you touch DNS. Export your indexed URLs and top organic landing pages while the old site is still live — once the domain points at HighLevel, that list is far harder to rebuild.

Then map, do not guess:

• Direct equivalent exists — 301 to the new page.
• No equivalent but a close parent — 301 to the parent, not the homepage.
• Thin or duplicated page — let it 404 deliberately.
• Still used in ads, emails or print — 301 it regardless.
• Already redirected once — point it straight at the final destination.

Google's site move guidance says to "keep the redirects for as long as possible, generally at least 1 year", and to submit the new sitemap in Search Console, watching indexed counts shift from old URLs to new in the Sitemaps and Index Coverage reports.

Blog content is what most migrations lose, because the old permalink structure rarely matches. Sort your GoHighLevel blog builder SEO setup before importing and you map each URL once.

Wildcards and query strings: what GoHighLevel redirects can and cannot do

The wildcard is real but narrow. HighLevel's changelog describes a single redirect with * as the path and an already connected domain as the target, after which any request to that host and its subpath goes to the same path on the target domain.

Two conditions apply. A * redirect is only allowed if you own the target domain — and once a domain uses a wildcard, its Default Page and 404 page no longer apply, because all traffic is redirected. The two are mutually exclusive on the same host.

Query strings are the clearer limit. HighLevel says to omit ?, %, &, = and # and use only lowercase letters, numbers, hyphens and slashes — so query-string matching is not a documented capability, and nor is whether parameters survive a redirect. Test it with your own tracking parameters.

Do not confuse that with HighLevel's separate URL Parameters feature for page content, which matches case-insensitively and converts hyphens and underscores to spaces.

How to find the broken URLs you already have

You almost certainly have some. Every rebuild, tidied slug and deleted test funnel leaves a dead address behind; the only question is who finds it first.

Fix by traffic, not by count. One dead URL still taking clicks from a live email sequence outranks fifty orphaned test pages, and the ads and email audit is the step no tool does for you.

Check what your 404 page weighs, too — the same rules from fixing slow HighLevel funnel pages apply to it.

For the official references: HighLevel's complete guide to setting up 301 URL redirects covers the tool, and Google's Redirects and Google Search documentation covers how each code is read.

Common mistakes to avoid

• Renaming a step path and creating the redirect only after someone reports a broken link.
• Sending every old URL to the homepage — a canonical signal telling Google those pages were all the same page.
• Leaving the Default 404/Error Page dropdown empty and assuming the domain handles it sensibly.
• Adding a wildcard on a domain you also want a custom 404 page on; HighLevel says both stop applying once all traffic is redirected.
• Chaining migrations so an old URL passes through several hops; Google's crawlers follow up to 10, but each hop is avoidable risk.
• Removing redirects after a month, when Google's guidance is a year.

If you want your GoHighLevel redirects, 404 pages and old-site URL map audited and built properly in one pass, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Or if you just need the software first: grab the 30-day HighLevel trial and book us when you're ready to scale it.

Frequently asked questions

Where do I find URL Redirects in GoHighLevel?

HighLevel's documentation places them at Settings > Domains & URL Redirects, then the URL Redirects tab, inside the sub-account. The source domain must already be added there first. Destinations can be a Custom URL, a Funnel step, or a Website page connected to that domain.

Does GoHighLevel support 302 redirects?

HighLevel's official guide documents 301 permanent redirects and lists no option for another status code, so 302 support is not documented. Verify what your domain actually returns before relying on temporary behaviour. For a permanent move, 301 is correct anyway.

What is the difference between a 301 and a 302 for SEO?

Google states that with a permanent redirect the indexing pipeline treats the target as canonical, and the new URL appears in results. With a temporary redirect Googlebot follows it but does not use it as a canonicalisation signal, so the source page stays in results.

Can I set a custom 404 page for a HighLevel funnel or website?

Yes. Each connected domain has a "Default 404/Error Page" dropdown beside a "Default Page" dropdown, reachable from the domain's Edit menu or the Connected Products nudge HighLevel added in May 2025. Choose a real page rather than leaving it empty.

Do GoHighLevel redirects support wildcards?

Yes, at host level. HighLevel's changelog describes using an asterisk as the path with an already connected domain as the target, so any request to that host and its subpath goes to the same path on the target. It is only permitted if you own the target domain.

What happens to an old funnel URL after I rename the step?

HighLevel states that existing links using the old path may stop working unless a redirect is created, and recommends a 301 if the old URL already appears in ads, emails or social posts. Treat the redirect as part of the rename.

How long should I keep redirects after migrating a site into GoHighLevel?

Google's site move guidance says to keep redirects as long as possible, generally at least one year, so all signals transfer to the new URLs. It also suggests considering them indefinite for users still holding old links.

Related Articles on HL Growth Partner

Tracking and testing your pages

• Running split tests and A/B tests on GHL funnels
• Installing GTM and tags across HighLevel pages

Converting the traffic you keep

• Multi-step forms and conditional logic in HighLevel
• Countdown timers and urgency offers that behave properly

Agency and account foundations

• What GoHighLevel is and who it suits in 2026
• White-labelling your HighLevel agency account
• Managing the Media Library and account storage