How to Buy a Domain Name from Google in 2026: Squarespace Migration, Cloud Domains and Google Registry

Buying a domain from Google is no longer as simple in 2026 as it was three years ago. The consumer registrar service that operated under the "Google Domains" brand was handed over to Squarespace on September 7, 2023, and the entire domain portfolio formally moved to Squarespace on July 10, 2024. When you visit domains.google today, all you see is a transition notice: new registrations go through Squarespace, and the management panel for existing owners now lives in Squarespace Domains accounts. Even so, "buying a domain from Google" isn't a single door — Google's ecosystem still includes Google Cloud Domains, the Google Workspace purchase flow, and TLDs operated directly by Google Registry. This article explains end to end what "buying a domain from Google" actually means in 2026, which path makes sense for which scenario, and the practical points users in Turkey should pay attention to.

Related guides: What is a domain name,.com and WHOIS lookup · Domain lookup tools: WHOIS, RDAP and DNS · DNS settings and how to change them · Free SSL setup with Let's Encrypt · Hosting types and how to choose

Google Domains Is Gone: Brief History and the 2026 Status

Google Domains opened in beta in 2015, became generally available in 2022, and shut down nine years later. The $180 million Asset Purchase Agreement signed between Google and Squarespace on June 15, 2023 transferred roughly 10 million domains. The legal handover finished in September 2023, and the technical migration (DNS, registration agreements, billing) wrapped up in July 2024. If your old Google Domains account is still open today, signing in redirects you straight to domains.squarespace.com. The press tended to summarize this shutdown as "Google left the domain business," but the truth is more nuanced. Google still has four separate domain-related arms: the consumer registrar (Domains — closed), enterprise Cloud Domains (now operating as a proxy on top of Squarespace), Google Registry (TLD operator, still active), and the Workspace purchase flow (via third-party registrars).

What Was Preserved and What Was Lost in the Squarespace Migration

Let's lay out the practical consequences of the migration. Preserved: all DNS record types (A, AAAA, CNAME, MX, TXT, SRV, CAA), custom name server support, domain forwarding, email forwarding (100 destinations per domain), DNSSEC and glue records, free WHOIS privacy, auto-renewal, two-step verification. Lost: the Dynamic DNS API (DDNS), programmatic certificate validation via the ACME DNS-01 API, payment in Indian rupees (INR), Google Domains' CLI/REST APIs, and the low-level integrations used for real-time automation similar to Redis's TTL behavior. Squarespace announced it would honor the old Google Domains renewal pricing for the first 12 months after the migration — meaning numbers like ~$12 USD/year for .com, ~$12 USD/year for .dev, and ~$14 USD/year for .app didn't change during 2024-2025. Price corrections kicked in after 2025, and as of 2026 Squarespace's .com renewal price sits in the ~$14-16 USD/year band (approximate, varies by provider, 2026 figures).

What Does "Buy a Domain from Google" Mean in 2026?

The high-volume search query "buy domain name google" maps to four distinct intents in today's search results. Which path you take depends on your use case.

• 1. Consumer domain purchase (the old Google Domains flow): Through Squarespace Domains. You can sign in with your old Google account; the interface is fairly close to Google Domains and DNS management is nearly identical.
• 2. Enterprise/infrastructure domain purchase: Google Cloud Domains. Tied to your GCP project, billed via Cloud Billing, integrated with Cloud DNS. The registrar behind the scenes is Squarespace, but management runs through the Cloud Console.
• 3. Domain bundled with Google Workspace: The Workspace signup flow lets you instantly buy a domain through a partner registrar (typically Squarespace or GoDaddy). MX records are configured automatically.
• 4. A Google Registry TLD (.dev,.app,.page,.new): Extensions where Google is the direct registry operator. You can buy them from any registrar; this isn't a full closure for Google, the company simply licenses these TLDs in the background.

The line between options three and four often gets blurred: you can register the .dev extension run by Google Registry from any registrar — the domain is still on "a Google-owned TLD." For a detailed comparison see our article on what a domain name is.

Path 1: The "Old Google Domains" Flow via Squarespace

This is the most direct route. Go to domains.squarespace.com and type the name you want into the search box. The behavior is very close to the old Google Domains search: instant availability across 100+ TLDs like .com, .net, .org, .io, .dev, .app, .co, .online. Signing in with your old Google account is still supported — the "Sign in with Google" button lets you continue without creating a separate Squarespace account.

Typical Price Ranges (2026, USD/year, approximate)

• .com — registration: $12-16, renewal: $14-18
• .net — registration: $14-18, renewal: $16-20
• .org — registration: $12-16, renewal: $14-18
• .io — registration: $35-50, renewal: $45-65
• .dev — registration: $12-16 (Google Registry), renewal: $14-18
• .app — registration: $14-18 (Google Registry), renewal: $16-20
• .co — registration: $25-35, renewal: $30-40
• .shop — registration: $0.99-2 first-year promo, renewal: $30-40

Prices fluctuate with promotional launches, exchange rates, and ICANN fee changes. .tr extensions are not sold by Squarespace or anywhere in the Google ecosystem; for.tr you'll need a TRABIS-accredited Turkish registrar. See our domain and.tr article for details.

WHOIS Privacy and ICANN Changes

Squarespace continues the Google Domains tradition of offering free WHOIS privacy (privacy proxy). That means your personal contact details don't appear in public WHOIS/RDAP queries — they sit behind the registrar's proxy. With ICANN's August 2025 update, the Admin and Tech Contact fields became optional for generic TLDs (gTLDs); only Registrant data is required. Country-code TLDs (ccTLDs — for example .us, .de, .tr) still require a full contact set. In Turkey, contact information is mandatory for .tr domains, and commercial domains may require additional documents (chamber of commerce registration, tax certificate).

Path 2: Google Cloud Domains (Enterprise Flow)

For teams running infrastructure on GCP, Google Cloud Domains is still active. From the Cloud Console, head to Network services → Cloud Domains and search. The registrar behind the scenes is Squarespace, but billing flows through your GCP project and the IAM role model ties to Google Cloud. The advantage: your domain and other GCP resources (Cloud Run, GKE, Cloud Storage, Cloud DNS) live in a single control plane. For enterprise users, billing consolidation and granular permissions like roles/domains.admin and roles/domains.viewer are valuable.

Cloud Domains Commands with gcloud

Cloud Domains does not support premium domain registrations (e.g. five-letter .coms or keyword-rich premium TLDs). For premium names, you'll need either Squarespace's consumer side or a specialised broker (DAN, Sedo).

This YAML covers the Registrant fields ICANN requires. The contactPrivacy option takes one of three values: PUBLIC_CONTACT_DATA (full data in WHOIS), PRIVATE_CONTACT_DATA (behind a proxy — the default), REDACTED_CONTACT_DATA (GDPR redaction).

Path 3: Buying a Domain via Google Workspace

When you sign up for Workspace, the "Buy a new domain" option offers an instant domain purchase flow through GoDaddy or Squarespace. The benefit: MX, SPF, DKIM, and DMARC records are written automatically by Workspace; you don't have to wrestle with DNS complexity to get email working. Workspace's domain partner varies by country. For registrations originating in Turkey, the primary partner has been Squarespace since mid-2024; in some regions GoDaddy is active. This path saves time if you only need a domain for Workspace email; if you already own a domain at another registrar, verifying it in Workspace and writing the MX records manually is still possible and a common practice.

Workspace Domain Verification Methods

• TXT record: The most common and most reliable method. Workspace gives you a TXT in the form google-site-verification=...; you add it to DNS and verify.
• MX record: Adding Workspace's MX records verifies automatically. The fastest path for a new domain.
• HTML file: Upload googlexxxx.html to your web root. Useful for static sites.
• HTML meta tag: Add <meta name="google-site-verification" content="..."> to the <head> of your homepage.
• CNAME: Verification via CNAME on a subdomain; more common with Search Console.

If your email DNS isn't configured correctly, providers other than Gmail may flag your messages as spam. Once the chain is in place, measure your spam score with mxtoolbox.com and mail-tester.com.

Path 4: Google Registry TLDs (.dev,.app,.page,.new)

Beyond the shuttered consumer registrar, Google is still the registry operator for 21 different TLDs. That means the ICANN contracts for these extensions belong to Google; Google sells them wholesale to registrars, and registrars sell to end users. Even when you buy these from a third-party registrar, you are technically buying "a Google TLD."

Google Registry TLD List (2026)

• .app — mobile and web applications (HSTS preloaded — HTTPS required)
• .dev — developers, open-source projects (HSTS preloaded)
• .page — personal pages, portfolios (HSTS preloaded)
• .new — action-oriented shortcuts (e.g. doc.new); requires approval to register
• .how — educational and how-to content
• .foo — developer culture
• .dad, .phd, .prof, .esq — profession/family-focused
• .day, .boo, .meme, .rsvp, .soy — culture and events
• .channel — broadcasters
• .zip, .mov — controversially launched in 2023 (file extension collision)
• .nexus, .ing, .みんな — niche use

HSTS preloading is the most important distinction for these TLDs: browsers refuse to connect to any .app, .dev, or .page domain over plain HTTP. As a site owner, you must have a valid TLS certificate from day one. For lab/staging environments, Let's Encrypt's DNS-01 challenge is ideal — you can issue wildcard certificates and skip the bare http:// redirect chain entirely.

Typical Flow for Buying a "Google TLD"

Our DNS configuration guide walks through every record type in detail. NS changes for a new domain typically take 1-24 hours to propagate across the internet.

Google Search Domain Name: Finding the Right Name

The query "google search domain name" is often less about Google selling domains and more about how to find a good domain name. From an SEO and brand perspective, choosing a name is a far more permanent decision than the price you pay — don't trade $14 a year for five years of brand confusion.

• Keep it short: 6-15 characters is ideal. It needs to remain understandable in digital ads, podcasts, and verbal pitches.
• Pronounceable: A Turkish or English speaker should be able to spell it correctly on the first try. Try to avoid letters like x, q, w when possible.
• Few hyphens or numbers: Hyphens make typing harder and send a slightly negative SEO signal. Prefer corporateblog.com over corporate-blog.com.
• Trademark conflict: Always search TÜRKPATENT for Turkey, EUIPO for the EU, and USPTO for the US. If a UDRP case is filed against you, you'll lose the domain.
• TLD fit: A software team should pick .dev; a SaaS, .io; a corporate Turkish service, .com.tr. The right niche TLD signals positioning.
• Protect the main TLD: If .com is taken, consider changing the name rather than falling back to .net. .com remains king for traffic and trust.

A useful tip: cross-check candidate names against the past 5 years of traffic on Google Trends. Phrases that are rising but haven't yet peaked tend to age the best.

To avoid WHOIS rate limits, prefer RDAP — it's standard across all gTLDs, returns JSON, and has more relaxed quotas. Our WHOIS, RDAP and DNS guide covers the protocol differences in depth.

Google Domain and Hosting: Does Bundling Make Sense?

The query "google domain and hosting" maps to two intents. The first: does Google offer hosting? Short answer — "no, there's no traditional shared hosting," but you can host on Google Cloud via Cloud Run, App Engine, GKE, Compute Engine, or Cloud Storage for static sites. The second: is buying domain and hosting from the same provider an advantage? Answer: sometimes yes, often no.

Pros and Cons of Buying Both from One Place

• Pro — Single invoice: Easy from an accounting perspective; everything consolidates onto one bill without VAT or currency mismatches.
• Pro — One control panel: DNS changes and site settings live in the same UI; MX/A/CNAME records get created automatically.
• Pro — One-click SSL: Some providers automatically install a free SSL certificate alongside the domain.
• Con — Vendor lock-in: Even though transferring a domain is relatively easy, some providers refuse to lift the transfer lock for the first 60 days.
• Con — Single point of failure: If your provider account is suspended, both your domain and site go dark. Keeping the domain separate preserves the ability to repoint DNS to another server quickly.
• Con — Hidden price resets: Domains bought for $0.99 in year one can renew at $35-50 in year two.
• Con — DNS speed gap: Independent DNS providers (Cloudflare, NS1, Route 53) typically resolve 30-100ms faster globally than the default DNS bundled with most hosts.

From the markaadi team's field observation: buying the domain from one provider, hosting from another, and DNS from a third (usually Cloudflare) is the healthiest advanced combination. This three-tier split eliminates vendor lock-in and protects the other two layers when any one provider fails.

Google Website Registration: Site Verification and Indexing

The query "google website registration" often blends two distinct intents: registering a site with Google Search Console (so it can be indexed), and registering a domain name. After buying your domain, you need to add the site to Google Search Console. This is the "prove you're the owner" step Google requires before indexing.

• Domain property: Verification via DNS TXT record. Covers all subdomains and protocols at once — the recommended method for modern sites.
• URL prefix property: Via HTML file, meta tag, Google Analytics, or Google Tag Manager. Covers only that protocol+host combination.

After verification, submitting your sitemap to Google (/sitemap.xml) and confirming robots.txt is set up correctly is critical for SEO. The Technical SEO checklist walks through these steps as an ordered checklist.

Domain Transfer: To Squarespace or Elsewhere

Old Google Domains accounts moved to Squarespace; if Squarespace doesn't suit you, transferring out to another registrar is a standard process. ICANN enforces a 60-day new-registration lock across all gTLDs: you cannot transfer a domain to another registrar within 60 days of registering it or changing the contact information.

• 1. Unlock the transfer: Disable "Domain lock" / "clientTransferProhibited" in your current registrar's panel.
• 2. Get the EPP / Auth code: Your current registrar will provide an 8-32 character transfer code.
• 3. Temporarily disable WHOIS privacy: Some new registrars require visible contact information for transfer verification.
• 4. Initiate the transfer at the new registrar: Enter the EPP code and pay (typically including a 1-year renewal).
• 5. Confirmation email: Click the confirmation email sent by your current registrar. If you don't, the transfer auto-approves after 5 days.
• 6. Completion: The transfer takes 5-7 days in total. DNS doesn't change during the process — records continue to serve from the existing configuration.

It's important not to change DNS during the transfer — set the new name servers afterwards. Otherwise, you may see site outages or email drops for 24-48 hours. For a broader migration scenario, see the DNS change guide.

Buy Web Domain: Buying a Domain in General

"Buy web domain" is a broader query — it reflects research intent across any registrar, not just Google. As of 2026, the domain registrar market splits into three typical segments:

• Hyperscale ecosystem: Google Cloud Domains (Squarespace infrastructure), AWS Route 53 Domains, Azure App Service Domains. Integrated with your existing cloud infrastructure.
• Independent registrars: Namecheap, Porkbun, Gandi, Hover, Dynadot. Usually expensive in year one with reasonable renewals; pure domain service.
• Local providers in Turkey: TRABIS-accredited firms like Natro, İsimTescil, Turhost, Atak Domain, Sadecehosting — the only practical route for .tr names.

What to look for when picking a local registrar: TRABIS accreditation, EPP code delivery time (sub-hour is good), 24/7 support, 2FA support, whether they expose a panel API (for automation), and whether DNS is free or sold as an add-on. For detailed selection criteria see our hosting and registrar selection article.

DNSSEC: Hardening Your Domain Against Cache Poisoning

DNSSEC (DNS Security Extensions) is an RFC standard (RFC 4033-4035, 6840) that signs DNS responses and blocks DNS cache poisoning attacks. Squarespace, Cloud Domains, and most modern registrars offer one-click DNSSEC. The majority of local registrars in Turkey now support it as well.

The most common DNSSEC setup mistake: generating signing keys in the zone before submitting the DS record to the registry. Correct order: generate DNSKEY in the zone → submit DS record to the registry → wait 24-48 hours for propagation → test with an external validator. Wrong order can break DNS resolution for hours.

Domain Privacy and GDPR: Two Layers of Privacy

WHOIS privacy works on two layers. The first layer is the registrar's "privacy proxy" service — the registrar's proxy address appears in WHOIS instead of your personal contact info. The second layer is the redaction introduced by ICANN's 2018 GDPR update: for any registration with EU-based personal data, Tech and Admin contacts are already automatically hidden. For registrations originating in Turkey, Squarespace and most international registrars also default to private. An important caveat: privacy proxy does not shield you from legal proceedings — under a UDRP case or a local court order, the registrar must disclose the underlying information.

E-commerce and Brand Domain Strategy

As your brand grows, a defensive domain portfolio strategy becomes essential. On top of your main .com, locking down common typos plus .net, .org, .co, and .com.tr blocks both traffic loss and typo-squatting attacks. Depending on your industry, niche TLDs like .app, .dev, and .shop deserve consideration too.

• Main brand: brand.com
• Country variant: brand.com.tr
• Industry niche: brand.shop (e-commerce), brand.dev (software), brand.app (mobile)
• Typos: baand.com, brand1.com (the 3-5 most common variants)
• Slogan / campaign: A short .new or .page link dedicated to each major campaign
• Marketplace: Channel-specific short redirect domains for marketing

A defensive portfolio can be kept in the ~$150-300 USD/year range; a trademark dispute lawsuit is 1000x that. Our e-commerce SEO article goes deeper into how domain architecture and URL structure tie into SEO.

Automation: Domain Management with Terraform

When you're juggling multiple domains plus their DNS, certificates, and redirects, manage them with Infrastructure-as-Code (IaC), not by hand. Terraform manages Cloud Domains and Cloud DNS declaratively; you check it into Git, run it through peer review, and avoid drift.

The domain registration resource (google_domains_registration) is managed via the Cloud Domains API; however, it is delete-protected — Terraform destroy won't actually delete the domain, only remove it from state. This safeguard is highly justified, because no one wants to accidentally lose a 10-year-old brand domain to a stray terraform destroy. Auto-renewal should be enabled by default on every domain. If your payment card expires and the domain reaches expiry, you go through a 30-day grace period (you still own it; renew at normal price), then a 30-day redemption period (high fee, typically $80-150 to recover), then a 5-day pending delete phase. A domain that isn't renewed within roughly 75 days becomes available to anyone — a critical loss for a branded name.

Squarespace vs Independent Registrar Comparison

Most former Google Domains users moved to Squarespace by default, but it's not mandatory. Transferring to an independent registrar can still make sense — especially for those who only want pure registrar service.

• Squarespace Domains: Modern interface, close to the Google Domains UX, one-click MX/SPF/DKIM presets, free WHOIS privacy, 24/7 support. Native integration with Squarespace's site builder.
• Namecheap: Among the lowest renewal prices, free WHOIS privacy, simple performance-focused interface, broad TLD coverage.
• Porkbun: Developer-friendly, transparent pricing (.com ~$10), free SSL and WHOIS proxy, strong API, competitive pricing on Google Registry TLDs.
• Gandi: European-based, careful about GDPR/privacy, supports.tr and many ccTLDs, email bundled.
• Cloud Domains (GCP): Only for enterprise/infrastructure scenarios. Overkill for individuals or SMBs.
• Local providers in Turkey: The only practical path for.tr; TRABIS-accredited firms are mandatory.

DNS Failure Scenarios During Migration

The most common issues former Google Domains users hit during the Squarespace migration, and how to fix them.

• Issue: Dynamic DNS (DDNS) doesn't work. Squarespace doesn't support a DDNS API. Fix: Move to a DDNS-specific service like Cloudflare DNS (free) or DuckDNS; keep the domain at Squarespace and point name servers to Cloudflare.
• Issue: ACME DNS-01 challenge fails. Squarespace's API isn't complete. Fix: Use a Cloudflare DNS-01 plugin instead of certbot --manual + DNS plugin; or move the NS to Cloudflare and run Let's Encrypt there.
• Issue: Old Google API keys don't work. All Google Domains API credentials are invalidated post-migration. Fix: Move to Squarespace's (limited) API or to the Cloud Domains API.
• Issue: Renewal price increased. After the 12-month price protection ends, Squarespace's standard pricing applies. Fix: Transfer to another registrar after the 60-day rule clears, or lock in the price by renewing for multiple years (3-10).
• Issue: WHOIS info missing or incorrect. Some legacy accounts had stale contact info during migration. Fix: Enter a complete contact set in the Squarespace panel; otherwise the 15-day verification warning will result in ICANN suspending the domain.

Domain Hijacking and Account Security

The physical key to your domain is access to your registrar account. If the account is lost, getting the domain back averages a 6-12 month legal process — during which your site, email, and brand are stranded. The principles in our authentication security article apply equally to your domain account.

• Mandatory 2FA: A hardware key (YubiKey, Titan Key) or at minimum a TOTP app (Aegis, 1Password). SMS 2FA is not safe against SIM-swap.
• Registrar lock: Keep "transferProhibited" on for every domain. Blocks unauthorized transfers.
• Dedicated registration email: Use a 2FA-protected email reserved for this purpose, not your generic business email. Something like domains@company.com.
• Backup email: Define a recovery email in Squarespace and Cloud Domains. Again, a different account.
• Regular WHOIS audit: Verify your domain's owner data through WHOIS / RDAP once a month. An unknown change is an attack signal.
• Persistent WHOIS privacy: Don't expose your contact info in public WHOIS; it shrinks the attacker's phishing surface.

Keeping the DNS Provider Independent of the Domain

We touched on this above, but it deserves its own section as a critical topic: keeping the domain registrar separate from the DNS provider makes sense in many scenarios. Plenty of modern sites buy the name from Squarespace/Namecheap/Porkbun and route DNS through Cloudflare (free). Reasons: performance (Cloudflare's global DNS network is 30-100ms faster than most registrars' default DNS), feature richness (DNS analytics, geo-routing, load balancing, DNS-based DDoS protection), API and automation (works seamlessly with Terraform), stability (a registrar outage doesn't take DNS down with it), and cost (Cloudflare DNS is free).

The SEO Impact of a Domain

The SEO weight of domain choice has shifted over the years. There was a time when an exact-match domain (EMD) — a name that literally matched the search phrase — gave a big edge. After Google's 2012 EMD update, that signal weakened significantly; today, brand value and content quality are far stronger ranking factors.

• Does TLD matter?.com,.net, and.org have historically been neutral for global SEO. Google has confirmed multiple times officially that there is no ranking difference between traditional TLDs and newer ones (.app,.dev).
• ccTLD and geo signal: Country-code TLDs like.tr,.de,.fr signal to Google that you serve that country. For services aimed at the Turkish market,.com.tr or.tr is an advantage.
• Domain age: An older domain doesn't automatically rank higher; long-active domains tend to carry more backlinks and content history.
• Domains penalized by previous owners: If you're buying an expired domain, check its history with the Wayback Machine, Ahrefs, and Majestic. A spammy or manipulative past can leave the domain under Google penalty.
• Subdomain vs subdirectory: Affects brand architecture; from a technical SEO standpoint, a subdirectory (brand.com/blog) is generally preferred over a subdomain (blog.brand.com).

Core Web Vitals and the technical SEO checklist are the major next steps after picking a domain.

Frequently Asked Questions

Will Google bring Google Domains back?

There's no official statement. The Squarespace deal is structured as "perpetual"; Google has no short-term intent to re-enter the consumer registrar market. The enterprise side (Cloud Domains) remains under Google's control, but it's intended for infrastructure — not marketed to end consumers.

Can I buy a ".tr" domain through Google?

No. Squarespace and Cloud Domains do not support the .tr extension. For .tr domains you must apply to a TRABIS-accredited Turkish registrar. See our.tr domain guide for a dedicated walkthrough.

Practical Notes on Cloud Domains, Workspace, and Google Sites

Cloud Domains runs inside a GCP project; you can open a zero-cost project with the Google Cloud Free Tier and buy a domain. Buying a domain via Workspace isn't extra-free — the Workspace subscription is separate from the domain fee, and the partner registrar charges the standard annual rate. Google Sites gives you a URL in the form sites.google.com/view/...; that's not a real domain, just a page under Google's subdomain. For professional use, you need to bring your own domain and connect it (via CNAME) to Google Sites; Google Sites cannot bind directly to a root domain (examplesite.com) — you bind www.examplesite.com and forward the root to it.

Decision Matrix in the Turkish Context

Compressing all this, the practical answer to "buy a domain from Google" depends on your profile.

• Personal/blog: .com, .dev, or .page via Squarespace Domains. Integrated with Cloudflare DNS. Annual budget $14-18.
• SMB website: Squarespace Domains .com + Cloudflare DNS + Workspace email. For the Turkish market, add .com.tr from a local registrar.
• Software/SaaS startup: .io/.dev/.app from Squarespace or Porkbun. Cloudflare DNS. Defensive domain portfolio.
• Enterprise GCP infrastructure: Cloud Domains. Managed via Terraform. Cloud DNS + DNSSEC.
• E-commerce: The .com + .com.tr + .shop trio. A mix of local registrar (TRABIS) and Squarespace. Cloudflare DNS.
• High-volume brand: A 20-50 domain defensive portfolio. Multi-year registrations. IaC-managed. Premium DNS provider.

Whichever path you choose, three principles stay the same: 2FA on the account, auto-renewal, and keeping DNS separate from the registrar. Any domain strategy missing those three will produce losses in the medium term.

Conclusion and Recommendation

"Google Domains is closed" wasn't the end of an era in domain land — it was the beginning of a transition. Google still indirectly remains a major player today: Cloud Domains is open for enterprise infrastructure, the Workspace setup flow offers the easiest email+domain integration, and the TLDs run by Google Registry (.dev,.app,.page) are strong picks for industry brand positioning. Squarespace fills the consumer gap; in practice, most former Google Domains users didn't lose anything, they just changed UI. The right mantra: pick the domain for the brand, the registrar for operations, the DNS for performance. Managing those three at separate layers eliminates vendor lock-in and lays the foundation for a long-lived digital asset.

Sources

• domains.google — migration notice and Squarespace redirect
• domains.squarespace.com — the new consumer domain platform
• Google Cloud Domains docs — enterprise API guide
• registry.google — Google Registry TLD information
• Google Workspace Sites
• ICANN — domain policy and transfer rules
• IANA Root Zone Database — TLD operators
• RFC 4033 — DNSSEC architecture
• RFC 7480 — RDAP HTTP transport
• hstspreload.org — HTTPS preload list
• dmarc.org — email authentication policies
• Cloudflare Learning Center DNS
• Google Search Console — site verification

Related Articles

• What Is a Domain Name?.com Domains and WHOIS Lookup
• Domain Lookup Tools: WHOIS, RDAP and DNS
• What Is DNS? DNS Settings, Changes and the Best DNS Servers
• Free SSL with Let's Encrypt: Certbot and Auto-Renewal
• What Is Hosting? Web Hosting Types and Pricing
• Technical SEO Checklist 2026
• E-commerce SEO Guide