Namecheap setup

Compare a representative public page's returned HTML with the completed browser page before adding rendering. If meaningful content is already present, a rendering connection may not be needed. Start with the setup guide.

Check the domain's active nameservers. Buying the domain from Namecheap does not mean its Advanced DNS zone is authoritative. Use the active DNS provider, and keep the site's existing canonical hostname.

Managed routing needs a stable public HTTPS origin that keeps serving the intended production content after the public hostname is connected. Verify important routes, assets and redirects without signing in.

A temporary or preview address is not automatically suitable. The origin must not redirect back to the public hostname being routed through PB. Follow origin requirements before changing records.

For Namecheap DNS, open Domain List, Manage and Advanced DNS. Copy the connected site's exact records from authenticated PB setup; do not replace them with a universal target.

Namecheap's CNAME instructions explain the Host and Value fields. With BasicDNS or PremiumDNS, the Host field uses the relative label. For www.example.com, that is www; the target is the full hostname supplied by PB.

A www example does not instruct a root-domain website to change its canonical. Use the site's supported apex instructions where applicable.

Copy the current TXT validation value from PB. Where the DNS editor appends the domain, a full name such as _acme-challenge.www.example.com becomes the relative Host _acme-challenge.www.

Check the resulting full record name so the domain is not appended twice. Keep a copy of the zone and replace only confirmed conflicts or obsolete validation values required by the current instructions. Preserve MX, SPF, DKIM, DMARC and unrelated TXT records.

DNS visibility and certificate validation timing varies. A Pending label alone does not establish the cause or justify resetting setup.

Redirect the alternate hostname to the chosen canonical with the path and query string preserved. Use a permanent, unmasked redirect where appropriate.

Namecheap's redirect documentation distinguishes URL forwarding from HTTPS/certificate requirements. An https:// destination does not prove that the source hostname can accept HTTPS.

Test both HTTP and HTTPS source URLs, including a deep path and query string. If the result drops the path, loses the query or fails TLS, use a correctly configured redirect at a request layer you control, or resolve it with the host. Do not switch nameservers simply to work around a failed example.

Run Verify Installation on the intended public URL. Review its final hostname, status, readable content and available delivery evidence. Compare visitor and crawler-style responses; those profiles do not prove crawler identity or indexing.

Use root and www guidance and troubleshooting for disagreements. Health and Monitoring follows important public pages. Rendering is one part of PB's wider workflow, with separate AI Visibility, article and publishing capabilities.