DomainSalesLanderPractical publishing guide
Already prepared your sales page? Connect its exact hostname, preserve your email records, and verify the public HTTPS address.
If these inputs are clear, the rest of the page can stay focused.
This guide starts with a prepared page. If you still need one, use the sales page builder, then return here for the domain connection.
Managed Publish hosts the page directly from the Builder. Export is available if you prefer your own host, and remains available after managed publishing.
Use the built-in route when you want DomainSalesLander to host the page and manage its HTTPS certificate.
Download the editable HTML and upload it to a host you control.
This fictional example connects www.example.com using Editorial and a make-an-offer email. Use your own domain and public sales address; these sample details are not a live listing.
In the Builder, enter www.example.com, choose Editorial and Make an offer, then enter your public sales email. Preview the page and check the spelling of the domain and contact address.
Publish the saved page to www.example.com. This uses one position; example.com is not connected automatically. Keep the displayed DNS instructions open while you visit your DNS provider.
Copy the exact record type, name and value from the publishing screen. In the example below, a provider that appends example.com expects www in the Name field. If it expects a complete hostname, use www.example.com. Check the saved name to avoid adding the domain twice.
Return to the publishing screen and select I added them, check now. DNS and certificate issuance may take time. Add any additional validation record only if the screen requests it, using its exact value.
Once the checks pass, open your exact HTTPS address in a private browser window. Confirm the intended offer loads and the offer button opens a draft addressed to your sales email. Keep an HTML export for migration.
This is the website record for our fictional www.example.com walkthrough. Always use the current values displayed for your own hostname in Managed Publish. Your registrar account and DNS control stay with you.
Keep unchanged: MX mail records, TXT verification records, and unrelated subdomains.
Existing website: if this exact hostname already has an A, AAAA or CNAME record, save its current value before replacing it. This moves that hostname away from its old website. Do not add a conflicting CNAME or change records for other hostnames.
Check first: root domains need CNAME flattening, ALIAS, or ANAME support. Otherwise, use www.
Cloudflare DNS: keep the customer CNAME unproxied while connecting Managed Publish.
The final test is the buyer experience on the exact public hostname.
Troubleshoot an unavailable pageOpen the same apex, www, or subdomain you entered. Do not assume one version redirects to another.
A generated page without a valid certificate is not ready for buyers.
Check the domain name, price or offer method, contact route, and transaction link from the public page.
Update the offer in the Builder and republish the same exact hostname. Managed Publish keeps the saved configuration in your account, while HTML export preserves a portable copy.
Learn what a sales lander should containNo. The file must be uploaded to a hosting account, connected to the intended hostname, and served over HTTPS.
No for Managed Publish. The default route uses the browser and the DNS controls you already have.
It should not if you add only the displayed website record. Do not replace MX or unrelated TXT records.
No. They are separate exact hostnames unless you configure a redirect outside DomainSalesLander.
Create the offer first. Then keep going until the exact hostname works over HTTPS.