Confirm support and the DS-record handoff with both DNS providers. Remove a stale DS record before a nameserver move or signed validation can fail for the whole domain.

Source checked 11 August 2026: WordPress.com official documentation.

Yes. A restrictive CAA policy can prevent the platform certificate authority from issuing. Compare the platform’s current CA requirements with your CAA records.

Source checked 11 August 2026: WordPress.com official documentation.

Connect every hostname you intend to serve, choose one primary HTTPS hostname, permanently redirect the alternatives, and make canonicals and sitemaps agree.

Source checked 11 August 2026: WordPress.com official documentation.

Usually yes. Add the full subdomain in WordPress.com and publish the platform-provided CNAME or other record without moving the apex unless the official workflow requires it.

Source checked 11 August 2026: WordPress.com official documentation.

Compare the host’s expected records with authoritative DNS, remove conflicts, check certificate status, test both apex and www, and retain a dated evidence note of every change.

Source checked 11 August 2026: WordPress.com official documentation.

Lower TTL in advance, attach and verify the hostname where possible, reproduce mail and verification records, change the minimum DNS records, monitor both endpoints, then remove the old service only after expiry of caches.

Source checked 11 August 2026: WordPress.com official documentation.

Verify one canonical HTTPS host, 301 redirects, robots.txt, XML sitemaps, structured data, Search Console ownership, analytics continuity and that preview URLs are not being indexed.

Source checked 11 August 2026: WordPress.com official documentation.

Keep the previous DNS values and provider access, avoid deleting the former service during propagation, document the change time, and restore the prior authoritative records if health checks fail.

Source checked 11 August 2026: WordPress.com official documentation.

WordPress.com — Start in https://wordpress.com/support/domains/connect-existing-domain/. Add the domain in WordPress.com, then choose nameserver connection or advanced A/CNAME records.

Source checked 11 August 2026: WordPress.com official documentation.

Monitor DNS answers, HTTP status, redirect chains, TLS expiry, canonical tags and mail authentication separately. Alert on changes at the authoritative nameservers, not only a local resolver.

Source checked 11 August 2026: WordPress.com official documentation.