Outcome
You will choose the right public address, verify it in CREBuilder, and test the resulting Listing Hub and property-page navigation.
Navigation path
Listing Hub > Website & domain
Access
Hosted links and embed controls follow Listing Hub access. Custom-domain management requires company-setting permission and domain control.
On this page
What you will accomplish
Short animated UI capture. No audio.
Goals
- Choose hosted, embedded, or custom-domain delivery
- Configure only the exact DNS records shown
- Verify public navigation while signed out
Public-address choices
Choose one primary experience, then keep the hosted URL as a diagnostic fallback.
CREBuilder Listing Hub
Hosted CREBuilder URL
Embed on existing site
Verified custom domain
- CREBuilder Listing HubHosted CREBuilder URL
- CREBuilder Listing HubEmbed on existing site
- CREBuilder Listing HubVerified custom domain
Before you start
Data, sources, and access to prepare
- At least one listed property for realistic testing
- For embedding, edit access to the host website
- For custom domains, DNS access or a DNS administrator
Prepare these details
- Choose whether the audience should visit CREBuilder directly or an existing company website
- Record the current domain and DNS owner
- Back up or document existing DNS records
- Decide whether the custom-domain root should open the hub or one root listing when offered
Complete the task
- 1
Open Website & domain
Listing Hub
Select Website & domain.
Expected result: The hosted URL, embed, and domain controls allowed for the account appear.
If this does not happen: Ask an Admin if company-level controls are unavailable.
- 2
Test the hosted URL
Website & domain > hosted link
Open the hosted Listing Hub link.
Expected result: The public hub loads in a new viewer context.
If this does not happen: List at least one property before judging an empty public hub.
- 3
Copy the generated embed
Website & domain > embed
Copy the provided embed snippet.
Expected result: The exact current snippet is available on the clipboard.
If this does not happen: Copy again from CREBuilder instead of reconstructing the URL manually.
- 4
Install the embed
Host website editor
Paste the snippet into one supported embed or HTML area.
Expected result: The host page renders the Listing Hub frame.
If this does not happen: Use a responsive container and review host-site content-security restrictions if it is blocked.
- 5
Enter the custom domain
Website & domain > custom domain
Enter the intended domain or subdomain.
Expected result: CREBuilder displays the exact verification or routing records.
If this does not happen: Confirm spelling before modifying DNS.
- 6
Add one required DNS record
DNS provider
Create one record exactly as CREBuilder displays it.
Expected result: The DNS provider accepts the record.
If this does not happen: Do not delete unrelated website or email records to resolve a conflict without administrator review.
- 7
Verify the domain
Website & domain
Select Verify after DNS propagation.
Expected result: CREBuilder reports the domain as verified or provides the remaining mismatch.
If this does not happen: Compare host, type, and value character by character before waiting and retrying.
- 8
Choose the root experience
Website & domain
Select the hub or one root listing when the option is available.
Expected result: The domain root opens the selected experience.
If this does not happen: Return the root to the full hub if a chosen listing is no longer public.
Delivery-option comparison
| Option | Use when | Primary dependency |
|---|---|---|
| Hosted URL | You need the fastest managed public experience | At least one Listed property |
| Embed | An existing company site should display the inventory | Host-site editor and iframe allowance |
| Custom domain | The public experience needs a branded address | DNS authority and successful verification |
Verify before you finish
- The hosted hub works while signed out
- The embedded hub is responsive
- Custom-domain DNS shows verified
- Hub and property links remain on the intended public address
- No unrelated mail or website service was disrupted
Troubleshooting and next steps
Domain verification remains pending.
Likely cause: DNS may not have propagated or the host, record type, or value may differ.
- Compare the exact records shown by CREBuilder.
- Allow the DNS provider’s normal propagation window.
- Verify again without creating duplicates.
The embed is blank or clipped.
Likely cause: The host page may block frames or use a fixed small container.
- Use the generated snippet.
- Allow the CREBuilder frame in the host policy.
- Give the container responsive width and sufficient height.
Final verification
- Website & domain > custom domain: CREBuilder displays the exact verification or routing records.
- DNS provider: The DNS provider accepts the record.
- Website & domain: CREBuilder reports the domain as verified or provides the remaining mismatch.
- Website & domain: The domain root opens the selected experience.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.