# Landing-page custom domain not working?

> Diagnose a landing-page domain problem by checking the exact hostname, DNS record, routing status, certificate, and redirects before changing the page.

- Canonical: https://pageree.com/guides/landing-page-domain-troubleshooting/
- Published: 2026-09-15. Updated: 2026-09-15.
- Collection: Guides (https://pageree.com/guides.md)
- Site index for agents: https://pageree.com/llms.txt

**The short answer.** Open the hosted page and the exact custom hostname separately. If only the custom address fails, compare its DNS record with Pageree's returned instructions and inspect domain status. Use the actual error to choose the next check instead of guessing a DNS target.

## Separate the page from the address

If a landing page works on its hosted subdomain but fails on your business domain, begin with the domain connection. Rebuilding the page will not fix a missing DNS record. If both addresses fail, check publication and the page itself before changing DNS.

This guide is a diagnostic recipe based on Pageree's domain workflow and Cloudflare's documentation. The symptoms below are examples to help you investigate; they are not a collection of reproduced customer incidents. Record the actual error and status returned for your hostname before choosing a fix.

## Start with the exact hostname

`example.com`, `www.example.com`, and `launch.example.com` are different hostnames. Connecting one does not automatically connect all three. Open the exact HTTPS address you supplied to Pageree and compare it with the hostname returned by the domain-status tool.

The page must already be published. Ask the assistant to read its current information, then run the domain-status check. Keep the returned status, errors, and DNS instruction together. Cloudflare distinguishes hostname routing status from certificate status; its [custom-hostname API guidance](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/common-api-calls/) explains why correct DNS and an active certificate both matter.

## Use the symptom to choose the next check

| What you observe | What to inspect | Useful next action |
| --- | --- | --- |
| Hosted URL works; business hostname does not resolve | Exact DNS name and target | Compare the public DNS record with Pageree's returned instruction |
| `www` works but the bare domain fails | Which hostname is connected | Connect the intended hostname or configure an intentional redirect with your provider |
| Domain is pending | Returned errors and DNS changes | Correct the reported mismatch, then check status again |
| Certificate warning | Certificate status and hostname spelling | Wait for confirmed issuance or investigate the reported validation error |
| Old site appears | Existing DNS, proxying, redirects, or caching | Inspect the exact route instead of repeatedly republishing |
| Cloudflare 1016 error | Hostname validation and routing | Share the error and status with support if your DNS matches instructions |

Cloudflare documents several reasons for a 1016 custom-hostname error, so the number alone is not a diagnosis. Use its [SaaS troubleshooting reference](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting/) alongside the specific status response.

## Check DNS without disrupting other services

Use the CNAME target returned by Pageree. Do not substitute a guessed IP address or copy a target from an unrelated tutorial. DNS providers differ in whether the name field expects `launch` or the full hostname; inspect the resulting record to avoid accidentally creating `launch.example.com.example.com`.

For this Pageree connection, a record in your own Cloudflare account should be set to DNS only. Apex domains need a provider that supports appropriate CNAME flattening or ALIAS behavior. If yours does not, a dedicated subdomain is a simpler route. Preserve records for email and unrelated services; changing nameservers or deleting an entire zone is not a routine fix for one landing-page hostname.

If certificate validation explicitly reports a CAA restriction, follow your DNS provider and Cloudflare's current [certificate troubleshooting instructions](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/troubleshooting/). Do not remove security-related DNS settings just because a generic checklist mentions them.

## Copy this diagnostic prompt

```text
Diagnose my Pageree domain connection without changing DNS.
Page URL or ID: [known page].
Exact hostname I own: [hostname].
Observed HTTPS error: [message].
Hosted-subdomain result: [works / error].
Time of last DNS change: [time and timezone].

Read page information and custom-domain status. Compare the
returned DNS record with the record I provide. Separate hostname,
routing, certificate, and redirect issues. Explain the smallest
next check. Do not invent a DNS target or remove a connection.
If evidence is incomplete, say what is still unknown.
```

After the status is active, open the HTTPS address, follow important links, and test the live form. Check the preferred canonical URL using the [SEO checklist](https://pageree.com/guides/landing-page-seo-checklist/). For a first-time connection, follow the [custom-domain guide](https://pageree.com/guides/ai-landing-page-custom-domain/). If the page opens but messages do not arrive, move to [form troubleshooting](https://pageree.com/guides/ai-contact-form-not-working/) rather than changing DNS again.

## Related
- [Connect a domain to your AI-built landing page](https://pageree.com/guides/ai-landing-page-custom-domain.md): Use your own hostname for a published Pageree page. Understand the returned DNS record, certificate checks, apex-domain limits, and verification steps.
- [Custom domain or hosted subdomain for your landing page?](https://pageree.com/guides/landing-page-domain-options.md): Compare hosted and owned landing-page addresses by setup, brand, continuity, and maintenance. Plan canonical URLs and migration without assuming SEO gains.
- [SEO checklist for an AI-built landing page](https://pageree.com/guides/landing-page-seo-checklist.md): Check search intent, titles, crawlability, canonical URLs, mobile experience, and useful content. A practical SEO checklist for a single landing page.

## Build it with your agent

Pageree is an MCP server. Add https://mcp.pageree.com/ to an MCP client that supports Streamable HTTP and OAuth, sign in, and the agent can build, publish and measure the page. Setup for every supported client: https://pageree.com/docs.md. Sign up: https://console.pageree.com/signup.