Add to Preferred Sources
Setting up a google sites custom domain connects your published site to a URL you own — www.yourbusiness.co.za instead of the default sites.google.com address — and takes under an hour if you already have the domain. If you are weighing this against other website builders available in South Africa before committing, know that Google Sites' custom domain works well for simple informational sites, but two technical issues trip up most SA operators: the DNS rules mean you cannot point the naked root domain directly without a workaround, and the setup path differs depending on whether you use a personal Google Account or Google Workspace.
This guide walks through both setup paths with the exact DNS records, explains the naked-domain problem and its practical fixes, and gives verified ZAR pricing for domain registration from South African registrars — so you start the process knowing exactly what to expect.
Quick Answer
A google sites custom domain connects via a CNAME DNS record: point the www subdomain (or another prefix) at ghs.googlehosted.com — the CNAME target that Google's setup wizard provides and that Google Sites specialists consistently document. Before adding the CNAME, verify domain ownership in Google Search Console using the TXT record Google provides. The naked root domain — yourbusiness.co.za without www — cannot use a CNAME directly due to a DNS protocol rule; fix it with URL forwarding at your registrar. DNS changes typically resolve within a few hours, though Google states up to 48 hours is possible.
In this guide
Need a site that does more than Google Sites allows?
Send us your requirements and we'll map out a web design approach sized to what your business actually needs — no commitment required.
Get a free assessmentWhat you need before connecting a Google Sites custom domain
A successful custom domain connection requires three things to be in place before you touch any DNS settings: a domain you control, a Google Site that is published and publicly visible, and login access to your domain registrar's DNS panel.
- A domain you own or are about to register. Google Sites does not provide domains — you buy them separately from a registrar such as xneelo, Afrihost, or Domains.co.za. For SA businesses, a .co.za domain is the standard choice; see the SA registrar pricing guide for a full breakdown of what registrars charge.
- A published Google Site set to public. If the site is not publicly shared, the custom domain redirects visitors back to the sites.google.com address. Confirm the setting in your site's Share menu before starting.
- Access to your registrar's DNS settings. You will add two DNS records: a TXT record for ownership verification and a CNAME record for the actual connection. Most SA registrar control panels label these clearly.
Two setup paths — personal Google Account vs Google Workspace
The path you follow depends on whether the Google Site was created under a personal Gmail account or a Google Workspace organisation — the underlying DNS work is identical, but the UI where you enter the custom domain for Google Sites is completely different, and the two accounts handle the naked domain differently.
| Factor | Personal Google Account | Google Workspace account |
|---|---|---|
| Where you configure the custom URL | Google Sites editor → Settings → Custom domains | Google Admin console → Apps → Google Workspace → Sites → Custom URL |
| Who can make the change | Anyone logged in as the site owner | A Google Workspace admin only |
| DNS record required | CNAME: www → ghs.googlehosted.com (typically) | CNAME: www → ghs.googlehosted.com (typically) |
| Naked domain (example.co.za) handling | URL forwarding at registrar (recommended) | Admin console redirect — HTTP only, not HTTPS; incompatible with HSTS-enabled domains |
| Additional cost | Domain registration fee only | Google Workspace subscription plus domain fee |
| Best for | Sole traders, side projects, micro-businesses | Teams already using Workspace for email on the same domain |
The Workspace path through the Admin console is worth knowing because some SA businesses land there accidentally — they build a site in their Workspace account and then try to set a google sites custom url through the Sites editor, which does not work for Workspace-hosted sites. If you see an error, check which account type the site lives in first.
If you are also evaluating how Google Sites compares to alternatives before committing to the custom domain setup, the platform comparison for SA businesses covers the trade-offs in detail.
How to connect a custom domain to Google Sites — step by step
Connecting a google sites custom domain requires completing DNS verification before the connection is accepted — skipping the verification step is the most common reason the setup fails.
Step 1 — Verify domain ownership in Google Search Console
Open Google Search Console with the same Google account that owns the site. Add your domain (enter just the domain name without http/https — for example, yourbusiness.co.za). Search Console will provide a TXT record value starting with google-site-verification=.
Log into your domain registrar's DNS management panel and add a new TXT record:
- Host / Name: @ (represents the root domain)
- Value: the full google-site-verification= string
- TTL: default or 3600 seconds
Allow the TXT record some time to propagate — this typically takes anywhere from a few minutes to an hour — then click Verify in Search Console. If the check fails on first attempt, wait and try again before troubleshooting.
Step 2 — Add the CNAME record
Still in your registrar's DNS panel, add a CNAME record:
- Host / Name: www
- Value / Target: ghs.googlehosted.com — typically the target Google's wizard provides; confirm in the Sites setup if in doubt
- TTL: default or 3600 seconds
If your domain is managed through Cloudflare, set the proxy status on this record to DNS only (grey cloud), not Proxied. The proxied setting intercepts traffic before it reaches Google's servers and breaks the connection.
Step 3 — Enter your custom domain in Google Sites
Personal account path: Open your site in the Google Sites editor. Click the gear icon (Settings) in the top-right corner. Select Custom domains from the left menu. The google sites domain setup prompt asks you to enter your domain in the format www.yourbusiness.co.za. Follow the on-screen confirmation steps.
Google Workspace path: Log into the Google Admin console (admin.google.com). Navigate to Apps → Google Workspace → Sites. Expand Custom URL and click the add (+) button. Choose New Sites, enter the site's published URL and the subdomain you want (typically www), then save. The status shows as Pending while Google configures the backend — this typically clears within 30–60 minutes.
Step 4 — Wait for propagation
DNS changes propagate globally within a few hours in most cases. Google's own documentation states up to 48 hours as the outer limit. If your site still shows the sites.google.com URL after several hours, confirm that the CNAME record is saved correctly and that the site's sharing is set to Anyone (public).
DNS record summary
Two records are required: (1) TXT record at @ with the google-site-verification= string from Google Search Console; (2) CNAME record with host = www and value = ghs.googlehosted.com (the target Google's setup wizard provides — typically this value, as documented by Google Sites specialists). No A record is needed. Cloudflare users: set the CNAME to DNS only, not Proxied.
The naked domain problem — and how to fix it
The single biggest technical surprise in this setup is discovering that yourbusiness.co.za (without www) cannot point directly to Google Sites — and understanding why is the key to fixing it cleanly.
DNS protocol does not allow a CNAME record at the root of a domain. A CNAME must point to another hostname (ghs.googlehosted.com), but root-level DNS entries must use A or AAAA records pointing to IP addresses. This is not a Google Sites limitation — it is a hard DNS rule that applies universally. The result: visitors who type yourbusiness.co.za without www either hit an error or land somewhere unexpected unless you set up forwarding.
You have two practical options:
Most SA registrars — including xneelo — provide a domain forwarding tool in the control panel. Set up a 301 (permanent) redirect from yourbusiness.co.za to https://www.yourbusiness.co.za. This is free, takes effect within the same DNS propagation window, and means anyone who types the bare domain reaches your site correctly.
If your registrar does not support URL forwarding, add an A record at @ pointing to 174.129.25.170 (the Wwwizer service). Wwwizer receives any request to your naked domain and issues a redirect to the www version. This requires your registrar to support A records at the root, which virtually all do.
The Google Workspace Admin console includes a naked domain redirect tool, but it only supports HTTP, not HTTPS. If your site is already live and serving pages over HTTPS — which applies to any site with a valid SSL certificate — the HTTP redirect the admin console issues will not complete correctly. Browsers that have previously seen HTTPS from your domain will reject the HTTP-only redirect, leaving visitors with a browser error. Use the registrar URL forwarding approach instead: it redirects correctly to https://www.yourdomain.co.za.
Which South African domain to register — and what it will cost
South African operators registering a domain specifically to connect to Google Sites face one key choice: .co.za or .com. Both work identically for this connection — the DNS setup is the same — but the two extensions behave differently for local search relevance and cost.
| Extension | Price at xneelo (2026) | Market range (SA registrars) | Best for |
|---|---|---|---|
| .co.za | R110/year (registration and renewal) | R90–R150/year | SA-facing businesses; local credibility |
| .com | R279 (first year) / R289 (renewal) | Varies widely | Businesses targeting international audiences |
xneelo pricing is fetched from xneelo's domain registration page (October 2026). Other SA registrars including Afrihost, Domains.co.za, and 1-grid offer similar pricing, and some run promotional first-year rates that reset to standard at renewal. Watch the renewal price — a promotional first-year rate that resets to double or triple the sign-up price at renewal will cost significantly more over time than a straightforward flat annual rate.
The .co.za extension is administered by ZADNA (the .za Domain Name Authority) and is generally the preferred choice for SA-facing sites. For purely informational intranet-style sites — an internal team handbook or a simple event page — the extension matters less; choose whichever you already own.
Domain registration checklist
Before buying a domain to use with Google Sites: check the renewal price (not just the first-year promo); confirm the registrar's control panel allows CNAME and TXT record editing; and verify the registrar supports URL forwarding for the naked domain redirect. All major SA registrars support these. If you need to connect domain to Google Sites using a registrar you are not familiar with, check these three capabilities — CNAME editing, TXT record support, and URL forwarding — before you buy.
When a custom domain on Google Sites is not enough
A branded custom URL solves the professionalism problem — visitors see your domain, not a Google subdirectory. It does not solve the platform limitations that matter for growth.
Google Sites was designed for internal wikis, team handbooks and simple event pages. For SA businesses that need to compete on search or convert visitors into leads, the platform hits ceilings quickly:
- No schema markup. Schema is how search engines surface rich results — star ratings, FAQs, event dates. Google Sites provides no mechanism to add it.
- Limited per-page SEO control. You cannot set individual meta descriptions for each page, which makes it harder to optimise for specific search queries.
- No ecommerce. Google Sites cannot take payments or manage a product catalogue. A business that starts with a Google Sites contact page and then adds online selling will need to move platforms entirely.
- Template constraints. The available layouts are limited and largely fixed, which creates a ceiling for businesses that need a distinct visual identity.
If you find yourself working around these limitations — trying to fake schema in text, maintaining a separate landing page on another platform, or rebuilding design elements repeatedly — the platform is telling you it has reached its limit for your use case.
Most SA operators start thinking seriously about a rebuild when something specific goes wrong: a potential client clicks through from a proposal email and sees a free-platform URL, or a consultant flags that the business cannot be found on search for its core service terms. The rebuild question is not whether the current platform is bad — it is whether the return on upgrading justifies the investment.
A properly built WordPress site with technical SEO in place, a mobile-optimised layout, and a contact form connected to a CRM can realistically move a near-zero enquiry rate to two or three per cent of monthly visitors. For a Johannesburg professional services firm receiving three hundred visitors a month, that is the difference between zero inbound enquiries and six per month from the same traffic.
Load-shedding is a genuinely SA-specific consideration here. A cloud-hosted free platform has no local infrastructure to fail during power interruptions. A self-hosted site on South African infrastructure — with a managed hosting provider that maintains generator or UPS backup — can match that uptime, but requires an informed choice of host. That choice matters more as the site grows in traffic and commercial importance.
The practical transition questions are platform choice, content migration, and SEO continuity — all of which are solvable with the right plan.
Outgrown Google Sites and not sure what comes next?
Tell us what your current site handles well and where it falls short — we will give you a straight assessment of whether a rebuild is worth it and what it would involve.
Request a website assessmentWhy South African Businesses Choose Growth Pulse Media for Web Design
GPM's web design work comes directly from hands-on experience running and scaling South African businesses, not from junior designers following templates. When a client has outgrown a Google Sites custom domain setup and needs a conversion-optimised site — with schema, proper SEO architecture, integrated payment options like PayFast or Peach Payments, and pages built around actual SA buyer behaviour — the rebuild is scoped and executed in-house by senior operators who have been through that transition themselves.
We work with a deliberately limited client load so every project receives senior attention from scoping through to launch. The web design service covers WordPress, headless builds, and platform migrations, with all technical SEO built in from the start. If you have been carrying a Google Sites site and know it is holding you back, the conversation starts at our contact page.
Who This Is NOT For
Google Sites cannot process payments or manage product catalogues. Adding a custom domain does not change this. If your primary goal is to sell online, Google Sites is the wrong platform — start on Shopify or WooCommerce and configure a custom domain there.
If you are competing for local search terms and need schema markup, optimised meta descriptions per page, and technical SEO control, Google Sites will limit you before you see results. A custom domain makes the site look professional but does not give the platform capabilities it does not have.
The setup requires editing DNS records correctly — adding TXT and CNAME entries, handling the naked domain redirect, waiting through propagation. If your business does not have someone comfortable with these steps, the hour or two it takes to figure it out may be better spent evaluating a managed website option instead.
If your site is live and serving pages over HTTPS — which applies to any site with a valid SSL certificate — the Google Workspace Admin console's naked domain redirect will not complete correctly. The admin console issues an HTTP redirect only, which browsers reject for sites already serving HTTPS. Use the registrar URL forwarding approach instead: it redirects to the https://www version of your address.
Ready to move past free website builders to a site built for growth?
Send us a brief about what your business needs from its website — we will come back within 24 hours with a no-obligation assessment of the right approach.
Start the conversationFrequently Asked Questions
Does connecting a google sites custom domain cost anything beyond the domain fee?
No. Google Sites itself is free, and there is no charge from Google to connect a custom domain you already own. You pay only the annual registration and renewal fee at your domain registrar — typically R90–R150 per year for a .co.za from a South African registrar. If you purchase a new domain directly through Google Sites, a Google Workspace subscription is also required, which adds a per-user monthly fee.
How long does it take for a google sites custom domain to go live?
DNS changes typically propagate within a few hours. Google's documentation states up to 48 hours as the maximum. Most SA operators see the custom domain working within one to two hours of completing the DNS setup. If it has not resolved after 24 hours, confirm the CNAME record is saved correctly and that the site's sharing is set to public.
Can I use a .co.za domain with Google Sites?
Yes, fully. A .co.za domain works exactly the same way as a .com when connected to Google Sites — you add the same TXT verification record and the same CNAME (www → ghs.googlehosted.com, the target Google's setup wizard typically provides). The only registration difference is that .co.za is administered by ZADNA and purchased through SA-accredited registrars like xneelo, Afrihost, or Domains.co.za.
Do I need Google Workspace to connect a custom domain to Google Sites?
No — if you already own a domain, you can connect it to a personal Google Account site without a Workspace subscription. The setup happens through the Google Sites editor under Settings → Custom domains. Google Workspace is only required if you want to buy a new domain directly through Google Sites, or if your site was built within a Workspace organisation account (in which case the connection goes through the Admin console, not the Sites editor).
Why is my Google Sites custom domain redirecting to sites.google.com?
The two most common causes are: (1) the site's sharing setting is not public — if the site is restricted to specific users, the custom domain redirects to the sites.google.com login; (2) the CNAME record has not yet propagated, or was entered incorrectly. Check that the CNAME host is www and the value is ghs.googlehosted.com exactly (the standard CNAME target for Google Sites, as provided by Google's setup wizard). Cloudflare users should also verify the CNAME is set to DNS only, not Proxied.
Growth Pulse Media — Web Design for SA Businesses That Have Outgrown DIY
When a Google Sites custom domain stops solving the problem and you need a site built for conversion, local SEO, and SA payment integrations — PayFast, Peach Payments, Yoco — we scope and build it in-house. No juniors, no subcontracting, no obligation. We will get back to you within 24 hours.
Get a free website assessment