Skip to content
Settings

Prevent Domain Connection Conflicts in GHL Customer Care

Learn how GHL Customer Care prevents domain connection conflicts across Funnels, Websites, WordPress, Client Portals, and other product types.

2 min read497 words1 explained imageUpdated Sat, 9 May at 7:39 PM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. How Domain Conflict Detection Works
  2. Supported Product Types
  3. Resolving Domain Conflicts
  4. Same Location Conflicts
  5. Cross-Location Conflicts
  6. Important Notes
  7. Frequently Asked Questions
  8. Related Articles

GHL Customer Care now prevents domains from being connected to multiple conflicting product types when doing so would disrupt an existing setup.Before a domain is connected to a new product, the system checks whether the domain is already being used by another supported product type. If a conflict is detected, the connection is blocked and a detailed error message is displayed.This safeguard helps prevent accidental service disruptions involving live Funnels, Websites, WordPress installations, Client Portals, and other connected products.

TABLE OF CONTENTS

How Domain Conflict Detection Works

When connecting a domain to a product, GHL Customer Care now performs a conflict check before validating DNS records.

If the domain is already connected to another supported product type, the system:

  • Blocks the new connection attempt
  • Identifies the product currently using the domain
  • Displays troubleshooting guidance
  • Provides a direct navigation link when applicable

For example, if a domain is already connected to a Funnel, attempting to connect it to a Client Portal may be blocked if the existing setup would break.

How Domain Conflict Detection Works (image 1 of 1) What this shows For example, if a domain is already connected to a Funnel, attempting to connect it to a Client Portal may be blocked if the existing… What this shows Illustrates the "How Domain Conflict Detection Works" section of "Prevent Domain Connection Conflicts in GHL Customer Care". This screenshot appears in the "How Domain Conflict Detection Works" section of "Prevent Domain Connection Conflicts in GHL Customer Care". The text alongside this image reads: For example, if a domain is already connected to a Funnel, attempting to connect it to a Client Portal may be blocked if the existing setup would break. This part of the guide covers 4 fields, listed below. Immediately after, the guide continues: Conflict detection currently applies to the following product types. Image 1 of 1 What this coversFor example, if a domain is already connected to a Funnel, attempting to connect it to a Client Portal may be blocked if the existing setup would break.
Fields in this part of the guide Blocks the new connection attemptIdentifies the product currently using the domainDisplays troubleshooting guidanceProvides a direct navigation link when applicable
Next stepConflict detection currently applies to the following product types:
All 4 steps in this procedure
  1. Blocks the new connection attempt
  2. Identifies the product currently using the domain
  3. Displays troubleshooting guidance
  4. Provides a direct navigation link when applicable

Supported Product Types

Conflict detection currently applies to the following product types:

  • Funnel
  • Website
  • Store
  • Blog
  • Webinar
  • WordPress
  • Client Portal
  • Branded Domain

Email products are excluded from these conflict checks.

Resolving Domain Conflicts

If a conflict is detected, review the error message carefully before proceeding.

Same Location Conflicts

If the conflicting product exists within the same location, the error message may include a direct navigation link to the existing domain connection.

Use the link to:

  • Review the current setup
  • Disconnect the existing product if appropriate
  • Choose a different domain if needed

Cross-Location Conflicts

If the conflict exists in another location within the same agency:

  • The connection will still be blocked
  • A direct link will not appear
  • The error message will identify the issue so you can investigate further

Important Notes

  • Conflict checks occur before DNS validation checks
  • Domain conflicts are detected across all locations within an agency
  • Existing domain connections are not modified automatically
  • Email products do not trigger product-type conflict checks

Frequently Asked Questions

Q: What happens if I try to connect a domain already in use?

The system blocks the connection attempt and displays an error message explaining the conflict.

Q: Can I override the conflict warning?

No. You must resolve the existing conflict before proceeding.

Q: Does this affect existing domain connections?

No. Existing connections remain unchanged unless manually updated.

Q: Why do some errors include a “here” link?

The link appears when the conflicting product exists within the same location, allowing you to navigate directly to the relevant domain settings.

Q: Why is there no link for some conflicts?

If the conflict exists in another location within the agency, the system does not display a direct navigation link.

Q: Are email products included in conflict detection?

No. Email-related products are excluded from these checks.

Was this guide helpful?

Related guides

Agency Company Settings in GHL Customer Care9 min read · 16 imagesBranding System-Generated Links (API Domain)3 min read · 7 imagesHow To Upgrade to GHL Customer Care's Agency Pro Plan ($497 SaaS plan)3 min read · 4 imagesHow to Delete a Subaccount/Location3 min read · 5 images