1
Verify the exact domain
Check whether you connected example.com or www.example.com; they are separate hostnames. Open the Domain area of the correct PageLinker project and use the record instructions for that exact hostname.
Troubleshoot domain verification, wrong DNS targets, pending HTTPS and a custom hostname that does not open your site.
Check whether you connected example.com or www.example.com; they are separate hostnames. Open the Domain area of the correct PageLinker project and use the record instructions for that exact hostname.
At your registrar, look for conflicting A, AAAA or CNAME records on the same hostname. Copy the type, name and target PageLinker currently displays rather than using a record from an old tutorial.
A domain can resolve before a TLS certificate is ready. Use Check connection in your project if available, then wait for successful verification and a secure HTTPS connection before sending paid traffic.
Use your PageLinker-provided live link while the custom domain is pending. If verification remains unsuccessful, send support the hostname and screenshots of non-sensitive DNS records—never share registrar logins.
Tell us what you tried, what happened instead, and the relevant page link. Include a screenshot or error message if useful. Please hide passwords, OTPs, payment details and visitor information.
Contact PageLinker support →