Skip to content
Training & Support

GoHighLevel Funnel Not Loading? Fix 404 Errors, SSL & Custom Domain DNS Issues

By Shoaib A. · Updated 16 November 2026 · 23 minute read

funnel-404-ssl-errors

A UK marketing agency launches a Google Ads campaign for a client. The funnel looks perfect inside GoHighLevel, but visitors clicking the advertisement encounter a 404 error or browser security warning. The campaign is running, enquiries are at risk, and nobody knows whether the problem is the domain, the funnel or the platform.

If your GoHighLevel funnel is not loading, the first priority is identifying which part of the connection has failed.

This guide explains how to diagnose 404 errors, incorrect DNS records, SSL problems, Cloudflare configuration, unpublished pages and broken redirects without unnecessarily disrupting your existing website.

Why Is My GoHighLevel Funnel Not Loading?

A GoHighLevel funnel may stop loading because its custom domain points to the wrong server, DNS verification is incomplete, Cloudflare proxy settings interfere with the connection, or an SSL certificate has not been provisioned successfully.

Other common causes include unpublished funnel steps, incorrect URL paths, missing default pages and conflicting redirects.

The correct fix depends on the error. A DNS failure, SSL warning and HTTP 404 response are different technical problems. Changing DNS records will not repair a funnel step that was never published.

First, Identify Your Funnel Loading Problem

Start by reproducing the problem using the exact URL your visitors are opening.

What You SeeLikely CauseFirst Check
404 Not FoundMissing page or incorrect routingFunnel step path and publication
This site can't be reachedDNS or connectivity failurePublic DNS lookup
DNS resolution errorMissing or incorrect DNS recordsAuthoritative nameservers
Your connection is not privateSSL certificate issueDomain verification and HTTPS
SSL certificate errorCertificate or hostname mismatchCertificate details
Domain verification pendingIncorrect DNS or propagationA or CNAME record
Preview works, live URL failsPublishing or domain assignmentPublished version and live URL
Root domain works, www failsDifferent DNS or redirect setupBoth hostnames
One funnel step returns 404Invalid or duplicate pathIndividual step settings
Too many redirectsConflicting redirect rulesRedirect chain
Page appears blankJavaScript or missing assetsBrowser developer tools
Page loads very slowlyHeavy media or scriptsNetwork requests and page speed
A browser displaying an error does not necessarily mean the domain is offline.For example, a genuine HTTP 404 means the server has responded but cannot provide the requested resource. A DNS failure happens earlier: the browser cannot determine where to connect.An HTTP 5xx error, meanwhile, may indicate a server-side or upstream service problem rather than incorrect DNS.

GoHighLevel Funnel Not Loading? Follow This Diagnostic Order

Use the following troubleshooting sequence before changing your configuration.

1. Does the exact hostname resolve?If not, investigate DNS and nameservers.

2. Is the domain connected to HighLevel?If verification is pending, inspect the required DNS record.

3. Does HTTPS load without warnings?If not, investigate SSL provisioning, DNS conflicts and the certificate.

4. Does the requested URL return 404?If yes, inspect its funnel association and page path.

5. Is the correct funnel step published?If not, publish the intended version.

6. Is the default page configured?Check which page should appear when visitors open the domain without a path.

7. Are redirects interfering?Review old campaign URLs, root/www redirects and competing rules.

8. Does the page render and convert correctly?Check scripts, forms, calendars, checkout and CRM activity.

This order prevents a common mistake: changing working DNS records when the actual problem is an unpublished page.

Step 1: Confirm the Exact GoHighLevel Funnel URL

Before diagnosing anything, copy the affected URL directly from the advertisement, email, website button or customer report.

These addresses are not automatically interchangeable:

  • https://example.com/
  • https://www.example.com/
  • https://offers.example.com/
  • https://offers.example.com/book-consultation/

The root domain might load correctly while a specific funnel step returns 404.

Check the hostname, page path, spelling, trailing slash and any redirects.

For active Google Ads or Meta Ads campaigns, inspect the actual destination URL configured in the advertising platform. Do not assume it matches the URL stored in GoHighLevel.

Test the address in a private browser window and record the exact error.

Step 2: Check Whether Your Funnel Is Published

A funnel can work inside the HighLevel editor without being available at its intended public URL.

Open the correct GoHighLevel sub-account and navigate to:

Sites → Funnels → Select the affected funnel

Check that:

You are working inside the correct client sub-account.

The intended funnel and step still exist.

The latest changes have been saved.

The relevant page has been published using the available publishing controls.

The funnel uses the correct domain.

The step path matches the failing URL.

Use the live URL displayed in HighLevel rather than copying an editor or preview address.

Open that URL in a private browser session without being signed into HighLevel.

If the preview works but the public page fails, investigate the publishing, domain association and routing configuration before editing DNS.

Step 3: Verify the GoHighLevel Custom Domain Connection

GoHighLevel needs to recognise the custom domain and associate it with the correct published content.

In the relevant sub-account, open:

Settings → Domains & URL Redirects

Locate the affected domain and select Manage.

Review the Connected Products information.

Confirm that the domain is connected or verified, and that the intended Funnel or Website is associated with the connection.

Look for any Action Required notice concerning default-page configuration.

For a new connection, HighLevel provides an option to connect a domain automatically through Domain Connect or manually through DNS records.

A successfully verified domain does not automatically prove that the correct funnel step has been selected.

Important: Do not disconnect a live domain as your first troubleshooting attempt. This can interfere with existing pages and redirects.

Step 4: Identify the DNS Provider Actually Managing Your Domain

Your domain registrar and DNS hosting provider may be different companies.

Suppose a business purchases its domain through GoDaddy but uses Cloudflare nameservers.

The team updates the domain's A record in the GoDaddy dashboard, expecting the funnel to start working.

Nothing changes because Cloudflare, not GoDaddy, controls the authoritative DNS records.

To avoid this:

Look up the domain's active NS (nameserver) records using a public DNS lookup tool.

Identify the provider associated with those nameservers.

Open that provider's DNS management panel.

Find the record for the exact failing hostname.

Compare it with the DNS instructions displayed by HighLevel.

Tools such as MXToolbox can help you inspect nameservers and published DNS records.

Do not change the domain's nameservers simply because you cannot find a record. Nameserver changes can affect websites, email and other connected services.

Step 5: Check A, CNAME and AAAA DNS Records

DNS records determine where browsers should send requests.

An A record points a hostname to an IPv4 address.

A CNAME record makes one hostname an alias of another hostname.

An AAAA record points a hostname to an IPv6 address.

According to HighLevel's official funnel and website domain setup guidance updated on 16 October 2026, the supported manual configuration includes:

Use CaseRecord TypeHost/NameTarget
Root domainA@162.159.140.166
SubdomainCNAMEofferssites.ludicrous.cloud
Supported subdomain alternativeAoffers162.159.140.166

These are alternative configurations, not records to add together. Always confirm the values in your actual HighLevel connection screen before making changes.

Example: Connect a Funnel Without Replacing Your Main Website

Suppose your existing business website runs at:

https://example.com/

You want a GoHighLevel landing page at:

https://offers.example.com/

You can connect the offers subdomain using the supported CNAME configuration while leaving the root domain pointed at its existing website host.

This is often safer than moving the main business domain.

Avoid Conflicting Records

Check for an existing A, CNAME or unexpected AAAA record pointing the same hostname to another destination.

Do not add an A and CNAME record for the same hostname.

Equally importantly, do not delete every DNS record while troubleshooting.

MX, SPF, DKIM and DMARC records may be essential for business email. They should remain untouched unless a separate, verified email configuration change is required.

Step 6: Fix GoHighLevel Domain Verification Failures

If HighLevel reports that the required A or CNAME record cannot be found, investigate what the public DNS actually shows.

Common reasons include an incorrect host value, the record being created at the wrong provider, an unsupported destination, propagation delays or Cloudflare proxy interference.

Follow this procedure:

Open the active DNS provider identified in Step 4.

Find the affected root domain or subdomain.

Compare the record type, name and target with HighLevel's instructions.

Review conflicting records before changing anything.

Save only the necessary correction.

Check public DNS results for the hostname.

Return to HighLevel and retry domain verification.

For instance, some DNS dashboards expect offers rather than offers.example.com in the Name field.

Entering the full hostname into a panel that automatically appends the domain could create an incorrect record.

How Long Does DNS Propagation Take?

DNS changes may become visible quickly, but cached information can remain in use for longer.

HighLevel advises allowing up to 24 hours for propagation in its domain guidance. This is not a guarantee that every problem will resolve after 24 hours.

If public DNS already shows the expected value but verification continues to fail, investigate the connection configuration and proxy settings instead of repeatedly adding records.

Step 7: Fix GoHighLevel Cloudflare DNS and Proxy Problems

Cloudflare is a frequent source of confusion because it provides both DNS hosting and an optional traffic proxy.

In Cloudflare, an orange cloud means the record is Proxied.

A grey cloud means DNS Only.

With proxying enabled, traffic can pass through Cloudflare rather than directly reaching the destination specified by the original DNS record.

For GoHighLevel Funnel and Website domain connections, HighLevel's official instructions require the relevant A or CNAME record to be set to DNS Only.

How to Check the Cloudflare Setting

Sign in to your Cloudflare account.

Select the domain used by the funnel.

Open DNS → Records.

Find the exact A or CNAME record associated with HighLevel.

Check the Proxy status.

If that specific HighLevel connection record is Proxied, change it to DNS Only as instructed by HighLevel.

Save the setting and retry verification after DNS updates become visible.

Hypothetical Example

A UK agency creates offers.example.com for a Google Ads campaign.

The CNAME target is correct, but the Cloudflare orange cloud is enabled.

HighLevel cannot reliably validate the expected DNS destination.

The agency confirms the record belongs exclusively to the funnel, documents its current settings and switches that record to DNS Only.

It then verifies the public DNS, checks HighLevel's domain status and tests HTTPS.

The important lesson is to change the affected record, not disable Cloudflare globally.

Cloudflare proxying may remain appropriate for unrelated websites and applications that support it.

Step 8: Fix GoHighLevel SSL and HTTPS Errors

SSL certificates allow browsers to establish secure HTTPS connections.

HighLevel automatically provisions SSL after a supported domain connects successfully. You generally do not need to purchase a separate SSL certificate for a standard HighLevel funnel connection.

However, certificate provisioning depends on the domain being configured correctly.

Browser SymptomPossible IssueInvestigation
Connection is not privateInvalid or unavailable certificateDNS and certificate status
Certificate name mismatchWrong hostname or endpointRequested domain versus certificate
SSL pendingDomain connection or provisioning incompleteVerification status
Secure page fails after DNS changeConflicting records or proxyActive DNS and Cloudflare
HTTPS redirects repeatedlyConflicting redirect configurationRedirect chain

How to Troubleshoot SSL Safely

First, confirm that the exact hostname is connected to HighLevel.

Then inspect its DNS records for unexpected destinations and, where relevant, Cloudflare proxy interference.

If the configuration was recently corrected, allow HighLevel time to complete certificate provisioning.

Inspect the certificate presented to the browser and confirm it covers the requested hostname.

If the warning persists despite valid DNS and a confirmed connection, escalate the issue to the appropriate platform or technical support provider.

Never advise visitors to bypass browser security warnings.

Step 9: Fix GoHighLevel Funnel 404 Errors

A 404 error means the requested resource was not found, although a custom error page can sometimes make the visible result misleading.

If your GoHighLevel funnel is showing 404, investigate the URL routing rather than assuming the domain itself is broken.

Check These Causes

Incorrect funnel step path: The URL in your advertisement does not match the published path.

Unpublished or deleted page: The visitor requests a step that is unavailable.

Wrong domain association: The hostname is connected to different content.

Missing default page: The domain opens at its root without an appropriate landing page selection.

Duplicate path: Another HighLevel page or funnel step already uses that path.

Outdated URL: A campaign still points to an old landing page.

Practical 404 Diagnostic Process

Open Sites → Funnels, select the affected funnel and inspect its steps.

Identify the intended page, confirm its path and publish it if necessary.

Check the actual live URL rather than manually reconstructing it.

Then open the domain's Connected Products settings and confirm the correct content association.

Where duplicate page paths exist, assign a unique path and review any existing external links before changing the URL.

HighLevel may add numerical suffixes to URLs when paths conflict. Its official indexing guidance explains how these conflicts can affect funnel URLs.

Verify Whether the Response Is a Genuine 404

A page displaying an error message is not always returning an HTTP 404 status.

Use your browser's Developer Tools, open the Network tab and inspect the main document request.

A genuine 404 response is different from a 200 response showing error-themed content or a redirect to a separate error page.

This distinction matters when diagnosing routing and when evaluating how search engines may interpret the URL.

Step 10: Configure the Correct Default Page

The Default Page determines which eligible page visitors should see when opening the connected domain's default entry point.

For example:

https://offers.example.com/

might need to display your funnel's main landing page.

If the domain is connected but shows an unexpected page, review its Default Page selection.

Navigate to:

Settings → Domains & URL Redirects → Manage

Locate the relevant connection under Connected Products.

Use the Action Required notice if one appears, or open the three-dot menu and choose Edit.

Select the correct eligible page under Default Page and save.

Remember that the Action Required reminder may appear only in the sub-account where the domain was originally connected.

A correctly selected default page does not automatically repair unrelated, invalid funnel step paths.

Step 11: Configure a Custom 404/Error Page

A branded 404 page helps visitors when they open a URL that genuinely does not exist.

It is useful for mistyped paths, deleted content and old links without an appropriate replacement.

Create and publish a suitable Funnel or Website page containing useful navigation, a homepage link and an accessible contact option.

Then open:

Settings → Domains & URL Redirects → Manage → Edit

Select the page under Set default 404/Error Page.

Test it by visiting an intentionally invalid path on the connected domain.

A custom 404 page should improve the visitor's experience, not disguise missing content.

If a page has permanently moved to a known replacement, a 301 redirect is usually more suitable.

Step 12: Fix Root Domain vs www Problems

Your root domain and its www version are different hostnames:

example.com

www.example.com

They may have separate DNS records, SSL behaviour and redirect rules.

That means one version can work while another returns 404 or a certificate warning.

First, test both versions independently.

Identify which hostname should be preferred.

Confirm that the preferred destination is properly configured and that the other hostname is supported by the chosen redirect arrangement.

HighLevel's root-domain connection workflow can provide an option to configure the www version and redirect it to the root domain.

Do not assume that changing one DNS record automatically configures both versions.

Always test the final redirect destination to ensure it does not point back to the original URL.

Step 13: Fix Funnels That Work in Preview but Not Live

An editor preview demonstrates how a page appears within HighLevel. It does not prove that the public domain and its routing are configured correctly.

Check the following separately:

  • The funnel's latest published version.
  • Its connected custom domain.
  • The public step URL.
  • The step's path configuration.
  • The domain's default page.
  • Any redirect applied to that path.

After publishing, test the exact URL from another browser or private session.

If the public page displays older content, investigate publishing and browser caching.

If it returns 404, focus on the domain association and URL path instead.

Private browsing can reduce the effect of browser cookies and cached content, but it cannot replace a genuine DNS, certificate or HTTP response check.

Step 14: Fix Broken 301 Redirects and Redirect Loops

A 301 redirect permanently directs visitors and search engines from an old URL to a new destination.

Consider a UK consultancy that previously used:

https://offers.example.com/book-now/

The team moves its booking page to:

https://offers.example.com/book-consultation/

Existing advertisements and emails may still contain the old URL.

If the page has permanently moved, a 301 redirect can preserve access.

In HighLevel, go to:

Settings → Domains & URL Redirects → URL Redirects

Select Add Redirect, choose the connected source domain and configure a specific path or domain-level redirect as appropriate.

Choose the destination and save the rule.

Avoid Redirect Loops

A loop can occur when URL A redirects to URL B, but URL B redirects back to URL A.

Check whether Cloudflare, your previous hosting provider or another service also manages redirects.

Do not create multiple conflicting rules to solve one URL problem.

A redirect also cannot repair an unpublished destination page.

Test the new target directly before implementing the redirect.

Step 15: Why Your Funnel Loads on One Device but Not Another

A funnel may work on your office desktop but fail on a customer's mobile.

Possible explanations include cached DNS results, browser extensions, outdated cached assets, different network connections and browser-specific scripts.

Test the same exact URL on desktop and mobile, in at least two browsers where practical.

Compare results over separate networks if the issue appears network-specific.

Record the browser warning or HTTP response rather than assuming the issue is caused by cache.

If the page works across most devices but fails in one browser, investigate local scripts, extensions and cached content.

If multiple networks cannot resolve the hostname, return to DNS troubleshooting.

Step 16: Fix Blank or Incomplete Funnel Pages

Sometimes a funnel technically loads, but visitors see a blank screen, missing images or non-functional buttons.

This is different from a domain that cannot resolve.

Open the browser's Developer Tools and inspect the Console and Network panels.

Look for:

  • JavaScript execution errors.
  • Failed image or script requests.
  • Third-party services that cannot load.
  • Incorrect embed code.
  • Blocking or conflicting custom scripts.
  • Large assets delaying page rendering.

HighLevel includes performance features such as image optimisation and JavaScript optimisation, but results depend on the page's actual content and integrations.

If a recently installed script appears responsible, test a controlled change on a duplicate or safe version of the page before modifying production.

Do not blindly remove Google Ads, Meta Pixel, analytics or checkout scripts. Removing them may create separate tracking or payment problems.

Step 17: Test Funnel Conversions After Restoring the Page

A landing page that loads successfully is not necessarily functioning correctly.

Once the technical problem is resolved, complete the visitor journey from start to finish.

Submit a controlled test form using clearly identified test details.

Confirm that the enquiry reaches the correct GoHighLevel contact record and that any required custom fields are mapped correctly.

Test appointment calendar availability, booking confirmations and follow-up notifications.

If the funnel includes checkout, use an appropriate supported test mode rather than creating unnecessary live transactions.

Finally, check whether existing Google Ads or GA4 conversion events still fire as expected.

If the page works but CRM records are missing, investigate the form and integration configuration separately.

GHL Experts UK also provides GoHighLevel integration services for more complex connected-system problems.

GoHighLevel Funnel Troubleshooting Table

Use this quick reference when diagnosing an active issue.

ProblemLikely CauseWhat to CheckRecommended Fix
Funnel not loadingDNS or publishingExact URL and domainIdentify the failed layer
404 errorMissing or incorrect pathFunnel stepsRestore or correct the route
Domain not connectingWrong DNS destinationA or CNAMEMatch current HighLevel instructions
SSL pendingVerification incompleteConnection statusCorrect DNS and allow provisioning
Privacy warningCertificate problemHTTPS certificateValidate hostname and connection
Cloudflare conflictProxied recordProxy statusUse DNS Only for the HighLevel record
Incorrect CNAMEWrong targetCNAME lookupCorrect the specific record
Wrong A recordIncorrect IPA lookupUse the verified supported target
Duplicate DNS recordsConflicting destinationsHostname recordsResolve documented conflicts
Missing default pageNo correct selectionConnected ProductsSelect the intended page
www failsSeparate hostname setupDNS and redirectConfigure the preferred route
Preview works, live failsPublishing or routingLive URLPublish and verify assignment
Old campaign URL failsChanged page pathAdvertisement URLUpdate URL or add suitable 301
Redirect loopConflicting rulesRedirect chainRemove the conflicting rule safely
Blank pageScript or rendering issueBrowser ConsoleIsolate the responsible resource
Unpublished stepDraft contentPublishing controlsPublish the required page
Missing imagesFailed resourcesNetwork requestsRepair affected asset references
Form not submittingForm or CRM faultTest submissionRepair the form-to-CRM journey

Hypothetical UK Agency Scenario: A Broken Google Ads Landing Page

A Manchester marketing agency manages paid advertising for a home improvement company.

The client's main website remains operational, but the agency has launched a separate GoHighLevel funnel at offers.example.com.

After a DNS configuration change, the landing page begins displaying a browser security warning.

The agency should not immediately remove the domain or replace all DNS records.

Instead, its investigation should establish:

Whether the affected subdomain still resolves.

Which provider controls the authoritative DNS.

Whether the expected HighLevel CNAME remains present.

Whether Cloudflare has proxying enabled.

Whether HighLevel verifies the domain and has provisioned SSL.

Whether the funnel is published and assigned correctly.

Once the fault is identified, the team can make the smallest necessary correction, retest the landing page and validate the lead form.

This is a hypothetical diagnostic scenario, not a reported client result or a guarantee that the same fix will work for every agency.

If active paid campaigns point to a broken funnel, treat the problem as an operational priority.

Review the landing page URLs in every affected campaign, advertisement and relevant extension.

If the destination is genuinely unavailable, consider pausing affected traffic or switching to a fully tested alternative while investigating.

Preserve existing tracking parameters where possible, including UTM values and advertising click identifiers.

After the repair, test:

  • The final advertising destination.
  • Any intermediate redirect.
  • The landing page and its main CTA.
  • Form submission and the thank-you page.
  • CRM contact creation.
  • Existing conversion tracking.

Restoring the URL does not automatically recover enquiries already lost during downtime or guarantee that previous campaign performance will return.

Domain Change Safety Checklist

Before modifying production DNS, document the current configuration.

Record who owns the domain, which company manages its nameservers, and which provider hosts the existing website.

Identify all active subdomains, email-related DNS records, live advertising URLs and third-party applications.

Export or document the existing DNS values before making edits.

Prepare a rollback plan and confirm who is authorised to approve changes.

For a business whose main website must remain untouched, a dedicated funnel subdomain may reduce the risk of accidentally replacing an existing service.

Do not alter unrelated MX, SPF, DKIM or DMARC records when the task is only to repair a landing page.

How to Test a Repaired GoHighLevel Funnel

Before declaring the funnel operational, complete a final verification.

Domain and Security

  • Correct sub-account selected
  • Correct domain connected
  • Public DNS points to the intended destination
  • HTTPS works without browser warnings
  • SSL certificate covers the hostname
  • Root and www versions behave as intended

Pages and Navigation

  • Correct default page selected
  • Required funnel steps published
  • Every important step path opens
  • Redirects reach their intended destinations
  • Desktop layout displays correctly
  • Mobile layout displays correctly
  • Critical images and scripts load
  • Page speed is acceptable for the intended audience

Lead Generation and Tracking

  • Forms submit successfully
  • Calendars allow valid bookings
  • Checkout functions where applicable
  • Test contact appears in the CRM
  • Required follow-up workflows execute
  • Conversion tracking works
  • Live advertising destination URLs are verified

Use labelled test information and handle personal data appropriately.

A successful homepage load is only one part of this checklist.

How to Prevent Future GoHighLevel Funnel, DNS and SSL Problems

Prevention starts with keeping domain and funnel configurations understandable.

Maintain a record of domain ownership, active nameservers, DNS destinations and the business purpose of each connected hostname.

Document which funnels use each domain and which paths are referenced by active campaigns.

Before changing a page URL, identify advertisements, email sequences, buttons and external links that may depend on it.

Use controlled publishing procedures and test important pages after structural changes.

For commercially important funnels, periodically check page availability and complete a test enquiry.

It is also useful to monitor critical landing-page URLs so unexpected failures can be investigated promptly.

A dependable funnel is more than a published landing page. Its domain, routing, forms, CRM records and follow-up workflows must continue functioning together.

When Should You Hire a GoHighLevel Funnel Specialist?

Some funnel issues are straightforward. Others require changes that can affect a live business website, advertising campaigns or connected services.

Professional assistance is particularly valuable when:

  • Paid campaigns are directing visitors to broken pages.
  • SSL failures continue despite verified DNS.
  • Domains and redirects are managed across several providers.
  • Multiple client sub-accounts share complex configurations.
  • A previous agency left undocumented domain settings.
  • Repeated fixes have caused new problems.
  • Forms, bookings or payment pages fail after a technical change.

A specialist should establish the actual cause, assess the risk of any proposed changes and validate the complete visitor journey afterwards.

For businesses that need practical investigation and repair, GHL Experts UK provides GoHighLevel technical support for existing accounts, including systems configured by previous agencies.

Where several unidentified issues exist, a structured GoHighLevel account audit can help establish what requires attention first.

If the original funnel is too damaged or unsuitable to repair efficiently, professional GoHighLevel funnel development may be a more appropriate route than repeatedly patching its configuration.

Conclusion: Fix the Cause, Not Just the Error Message

When a GoHighLevel funnel is not loading, the safest approach is to identify the failed component before changing settings.

Start with the exact URL, confirm DNS resolution and domain verification, then check SSL, publishing, page paths and redirects.

Once the page becomes accessible, verify the complete conversion journey, including forms, bookings, CRM records and tracking.

A working funnel should consistently connect the visitor to the intended page and allow the business to receive and process enquiries.

Need help fixing a GoHighLevel funnel?

If your landing page is returning 404 errors, showing SSL warnings or failing to connect to a custom domain, contact GHL Experts UK for GoHighLevel technical support.

Our team can investigate the configuration, identify the likely root cause, assess safe repair options and test the affected funnel before the work is considered complete.

FREQUENTLY ASKED QUESTIONS

Frequently Asked Questions

1. Why is my GoHighLevel funnel not loading?

The cause may involve DNS, an unverified custom domain, SSL provisioning, incorrect routing, an unpublished funnel step or a broken redirect. Identify the exact browser symptom before making configuration changes.

2. How do I fix a 404 error in GoHighLevel?

Check the connected domain, funnel association, published step and exact page path. If an old URL has permanently moved, configure an appropriate 301 redirect to the working replacement.

3. Why isn't my GoHighLevel custom domain connecting?

HighLevel may not detect the required DNS record. Confirm the authoritative DNS provider, record type, hostname, target and Cloudflare proxy settings.

4. What DNS records does GoHighLevel require?

For standard Funnel and Website connections, current HighLevel documentation supports the A record 162.159.140.166 and the CNAME target sites.ludicrous.cloud, depending on hostname type. Confirm the exact connection requirements in HighLevel.

5. How do I fix an SSL error in GoHighLevel?

Verify that the domain is connected, DNS records are correct and conflicting destinations are absent. If using Cloudflare, follow HighLevel's DNS Only instruction. Then allow certificate provisioning and retest HTTPS.

6. Should Cloudflare proxy be enabled for a GoHighLevel funnel?

No. HighLevel's current guidance requires the relevant Funnel or Website connection record to use DNS Only rather than Cloudflare's Proxied setting. Other Cloudflare records should be assessed independently.

7. Why does my funnel work in preview but not live?

Preview mode does not confirm public publishing or domain routing. Check the published page, selected domain, step path and any applicable redirects.

8. Why does www work but the root domain doesn't?

The two hostnames can use different DNS records and routing settings. Check both independently and configure a supported preferred-hostname redirect where appropriate.

9. How long does GoHighLevel DNS propagation take?

Changes may appear quickly, but HighLevel advises allowing up to 24 hours for DNS propagation. Actual timing varies, and persistent failures may have another cause.

10. Does GoHighLevel automatically install SSL?

HighLevel automatically provisions SSL for successfully connected supported domains. An incorrect DNS configuration or verification problem can interfere with provisioning.

11. How do I redirect an old GoHighLevel funnel URL?

Navigate to Settings → Domains & URL Redirects → URL Redirects. Create a redirect from the old path to the published replacement and verify that it does not create a redirect loop.

NOT SURE?

If You Are Not Sure

No obligation • Your information will only be used to respond to your enquiry