Monday morning you sent an invoice from your Squarespace-connected domain and waited. By Wednesday, three clients are asking why you ghosted them, and your replies never arrived in their inboxes. Google Workspace is silently bouncing every message you send because the MX records on your domain no longer point where Google expects them to. For a small business that runs on email, that gap between sending and receiving is the difference between a paid invoice and an awkward follow-up call.
This is one of the more common failure modes we see with small businesses that bought a domain through Squarespace, layered Google Workspace on top for professional email, and then watched the whole setup quietly break months or years later. The fix is usually straightforward once you understand what an MX record does and where Squarespace hides the controls. The painful part is the downtime while you figure it out.
In the sections ahead, we’ll walk through why a working email setup suddenly stops working, how MX records actually route business email, how to diagnose the problem on a Squarespace-managed domain, and the exact records to change and where to change them. We’ll also compare Squarespace against other registrars for email-critical domains, cover how to prevent the next outage, and close with a bottom-line checklist you can run this week.
Why a Working Email Setup Suddenly Stops Working
One Tuesday morning, the invoices stop landing. A prospect calls because they “never heard back” on a quote you swear you sent. A vendor leaves a voicemail asking if your address has changed. Nothing on your screen looks broken — Gmail still opens, the logo still shows on your domain — but somewhere between the public internet and your inbox, the wires have come loose. For a small business running on a Squarespace-managed domain pointed at Google Workspace, this is the classic failure mode: everything appears fine until you realize, hours or days later, that mail has been quietly disappearing.
The trigger is almost always the same. DNS records at your domain registrar drift out of sync with what Google Workspace expects. Google Workspace requires specific MX records added to your DNS provider, and if those records get edited, overwritten, or migrated to a new host without being re-created exactly, inbound mail has nowhere to go. Squarespace exposes those settings through a dedicated panel for managed-domain DNS, which is convenient — and also exactly the surface where a well-meaning edit can break everything.
The Common Triggers
Most outages trace back to a small number of moments. Specifically, the breakage tends to follow one of these events:
- A domain transfer between registrars (for example, moving from Bluehost to Squarespace, or the reverse), which wipes the old DNS zone and leaves you to rebuild it from memory.
- A “cleanup” edit in the Squarespace DNS panel where an MX record is deleted because nobody recognized it.
- A Google Workspace plan change, reseller switch, or admin handoff that changes which records Google expects.
- A new vendor (a CRM, a marketing tool, a help desk) writing its own DNS records and inadvertently displacing the mail ones, a pattern Cloudflare documents under vendor-specific records.
The pain is real enough that small business owners routinely post paid help requests describing exactly this scenario — listings on Freelancer, for instance, ask for someone with expertise in Bluehost and Squarespace DNS plus Google Workspace email configurations to untangle the mess.
What You Notice First, and What It Costs
The symptoms are rarely a dramatic error message. Furthermore, what tips most owners off is indirect: a customer mentions on a sales call that they replied last week, a recurring client follows up because an invoice never arrived, or your own test email from a personal Gmail bounces back hours after you sent it. By the time the pattern is obvious, you’ve usually lost a full business day or more.
What this means for your business: even one day of broken inbound mail can mean missed quotes, late invoices, and a quiet erosion of the trust customers place in you to be reachable. The good news is that the fix is almost always a DNS correction, not a rebuild — and the rest of this article walks through exactly how to find and apply it.
How MX Records Actually Route Your Business Email
An MX record — short for Mail Exchange record — is the line of DNS that tells the rest of the internet where to deliver mail addressed to your domain. When someone hits send on a message to you@yourbusiness.com, their mail server does not magically know that your inbox lives at Google. It performs a DNS lookup, reads your MX records, and hands the message to whichever servers those records point at. If those records are missing, wrong, or pointing at the wrong provider, inbound mail stops at the door. That is the entire mechanism, and understanding it is the difference between a five-minute fix and a week of guessing.
Two Systems, One Handshake
Here is the part that trips up most small business owners. Your domain registrar and your email provider are two separate companies running two separate systems, and they only work together if their settings agree. Squarespace, in its role as registrar, hosts the DNS panel where your records live; Squarespace documents how to reach that panel so you can edit records directly. Google, meanwhile, runs the mail servers that actually accept and store your messages. Neither one can speak for the other. The MX record is the handshake — the instruction that lives on the registrar side and tells the world to route mail to the provider side.
Consequently, when something breaks, the first diagnostic question is always: which panel controls what? You log into Squarespace to see and edit the records. You log into Google Workspace to see and use the mailbox. Mixing those up is a common source of wasted hours.
Why Google Publishes a Specific List
Google Workspace does not accept mail at a random address; it requires a specific set of MX records to be present on your DNS provider. Cloudflare’s own DNS documentation notes that Google Workspace requires specific MX records added at your DNS host, and the same requirement holds whether your DNS lives at Squarespace, Cloudflare, or anywhere else. The records are not optional, and partial matches will not work — if the list on your registrar does not match what Google expects, delivery fails.
Pros of letting your registrar (Squarespace) handle DNS:
– One login for domain renewals and DNS edits
– No extra service to pay for or learn
– Squarespace’s interface is friendlier than most registrar panels
Cons:
– Squarespace’s DNS controls are less granular than a dedicated provider like Cloudflare
– Diagnostics tools are limited compared with what a developer would use
– If you ever migrate your site away from Squarespace, you have to remember the DNS lives there too
What This Means for Your Business
You do not need to become a sysadmin to keep your mail flowing. You do, however, need to know which panel controls what, and you need to recognize that Google publishes the authoritative list of records that must be present. Furthermore, every time you change website hosts, change email providers, or have a developer “clean up” your DNS, those MX records are at risk of being overwritten. A thirty-second check after any such change — confirming the records still match Google’s published list — is cheaper than a day of bounced mail and frantic customer calls.
Diagnosing the Problem on a Squarespace-Managed Domain
Before you change anything, you need to confirm what is actually broken. Mail delivery problems on a Squarespace-managed domain almost always trace back to one of three layers: the MX records themselves, the authentication records that sit alongside them, or a mismatch between what Squarespace shows in its panel and what the rest of the internet sees. Diagnosing in that order saves hours and prevents you from “fixing” a record that was never the problem.
Getting Into the DNS Panel
Squarespace publishes a walkthrough for accessing your Squarespace-managed domain’s DNS settings, and that is the document to keep open in another tab while you work. From your Squarespace account, open the domain, then open DNS settings, and scroll to the custom records table. You are looking for five MX entries pointing to Google’s mail servers. If you see only one or two, or if the priorities are wrong, or if there is a stray MX pointing somewhere unfamiliar like a previous host, you have found your problem. A healthy Google Workspace MX configuration is uniform across providers — the same five hostnames and priorities apply whether the records live at Squarespace, Cloudflare, or another registrar, as Cloudflare’s own vendor-specific records reference demonstrates with its Google Workspace section.
Free Tools That Tell the Truth
DNS panels can lie to you. A record may appear saved in Squarespace yet not propagate, or it may have propagated but with a typo you cannot spot by skimming. Two free external tools settle the argument quickly.
- MXToolbox — Pros: instant lookup, flags missing or duplicate MX entries, surfaces blacklist hits. Cons: free tier rate-limits frequent checks; some reports nudge you toward paid monitoring.
- Google Admin Toolbox Check MX — Pros: explicitly compares your records to what Google Workspace expects and tells you what to add. Cons: only useful for Google-hosted mail; will not help if you are mixing providers.
Run both. If they agree your MX is healthy, the problem is elsewhere.
When MX Is a Red Herring
Furthermore, plenty of “email stopped sending” tickets are not MX problems at all. Outbound mail from Google Workspace depends on SPF, DKIM, and DMARC records that authenticate your domain to receiving servers. A missing SPF TXT record, an unrotated DKIM key, or a DMARC policy set to p=reject without the right alignment can cause receivers like Gmail and Outlook to silently drop your messages while your own send queue looks perfectly happy. For a small business, the symptom is identical to an MX failure: customers stop replying. The fix, however, is in the TXT records, not the MX rows. Check authentication before you blame Squarespace.
The MX Record Fix: What to Change and Where
When MX records drift, the repair is mechanical: open the DNS panel on your domain registrar, replace whatever is there with the exact set Google Workspace requires, and remove anything legacy that does not belong. For a domain registered through Squarespace, that work happens inside the Squarespace-managed domain’s DNS settings panel, which is where you add, edit, and delete records without touching a server or cPanel. The mechanics are not the hard part. The hard part is doing it in the right order, with the right values, and resisting the urge to keep “just in case” rows from a previous provider.
Replacing the Records in the Squarespace DNS Panel
Open your Squarespace domain’s DNS panel and scroll to the section that lists MX entries. Delete every existing MX row, including any that point to a previous host like Bluehost, GoDaddy, or an older mail provider. Leaving a stale row in place is one of the most common causes of these incidents — freelance listings to fix Google Workspace email issues routinely reference exactly this: tangled MX rows split between two registrars, with no one record set winning cleanly. Then add the MX records Google Workspace publishes for your account, copying the priority numbers and hostnames verbatim. Save. That is the entire change.
Order, TTL, and Why Legacy Rows Bite
Priority matters. Lower numbers are tried first, and a forgotten high-priority row pointing at a dead server can intercept mail before Google’s servers ever see it. TTL — the time-to-live value attached to each record — controls how long resolvers cache the answer. A long TTL on the old record means receivers worldwide will keep delivering to the wrong host until that cache expires. Specifically, if you anticipate a cutover, lower the TTL to 300 seconds (5 minutes) a day before the change, then raise it back to a normal value once the new records are stable.
Pros and cons of editing DNS directly at Squarespace versus delegating to a third-party DNS host like Cloudflare:
- Pros of staying at Squarespace: one less account to manage, one less bill, edits happen where your domain lives, and the panel itself is straightforward.
- Cons of staying at Squarespace: less granular control than dedicated DNS platforms; Cloudflare’s documentation on vendor-specific DNS records shows how a specialist host structures provider templates for Google Workspace and others, which can reduce typos on complex setups.
Timing and What to Tell Your Customers
DNS propagation is not the multi-day wait it was a decade ago. In practice, MX changes propagate in minutes to a few hours for most resolvers, depending on the prior TTL. However, until propagation completes, some senders may still try the old host. Therefore, schedule the fix during a low-traffic window — early morning before the inbox fills, or a quiet weekend hour — and send a short note to your most active clients warning that messages from the last 24 to 48 hours may not have reached you and asking them to resend anything urgent. For a small business, that one-paragraph email protects revenue more than any technical fix: customers who heard nothing assume you ignored them, and a brief explanation reframes silence as a fixable hiccup rather than neglect.
Squarespace Versus Other Registrars for Email-Critical Domains
Once you’ve recovered from an MX outage, a fair question follows: should the domain stay where it is? Squarespace earned its reputation as a website builder, and its DNS tooling reflects that priority. For some small businesses, the convenience outweighs the constraints. For others — particularly those whose revenue flows through email — moving DNS to a dedicated provider is the safer long-term posture. The choice depends on how technical your team is, how often DNS records change, and how much downtime your inbox can absorb.
What Squarespace Does Well
For a non-technical owner who already manages a Squarespace site, keeping the domain on the same platform is genuinely simpler. One login, one dashboard, one support channel. The DNS panel is documented in plain language, and Squarespace publishes step-by-step guides for accessing and editing DNS records on a Squarespace-managed domain. If your website and email both live in the Google and Squarespace ecosystems, the integration reduces the number of places a mistake can happen.
Pros of staying on Squarespace:
– Single dashboard for site and DNS
– Lower learning curve for non-technical owners
– Tightly integrated with the website builder
– Support team familiar with the common Google Workspace setup
Cons of staying on Squarespace:
– Fewer advanced DNS controls than dedicated providers
– Less granular logging when records change
– The DNS panel can feel hidden behind the website builder UI
– Bulk edits and templated record sets are limited
When Moving DNS Elsewhere Makes Sense
Furthermore, a business that depends heavily on email — a law firm, a brokerage, a contractor whose entire intake runs through a single inbox — benefits from a host built specifically for DNS. Cloudflare is the most common destination, and its documentation walks through vendor-specific records for Google Workspace and similar services, including the exact MX entries that broke in the scenario this article opened with. Moving DNS does not require moving the registrar; you can keep the domain registered with Squarespace and simply change the nameservers.
Specifically, you should consider a dedicated DNS host when any of the following apply: you run more than one mail-related record set (SPF, DKIM, DMARC, plus aliases), you need faster propagation for frequent changes, you want audit logs of who changed what, or you’ve already had one outage caused by a UI quirk. A guide on setting up Google Workspace for a small business walks through the same MX and TXT records regardless of where DNS lives, which means the migration is mostly a copy-and-paste exercise rather than a re-architecture.
What this means for your business: if your last email outage cost you a single client meeting, the convenience of Squarespace DNS probably still wins. However, if it cost you a contract, the afternoon spent moving DNS to a provider with better controls pays for itself the next time something goes sideways.
Preventing the Next Email Outage
The hardest part of an email outage is the helpless feeling while it’s happening. The easier part is making sure it does not happen again. Once your MX records are pointing back at Google and mail is flowing, you have a narrow window where the pain is fresh and the motivation is high. Spend that window building a few small safeguards, and the next DNS surprise becomes a five-minute fix instead of a three-day fire drill.
Document the configuration before you forget it
Open a plain document — Google Doc, Notion page, or a text file in your password manager — and write down every DNS record currently on your domain. Note the type (MX, TXT, CNAME), the host, the value, and the priority. Add a sentence next to each one explaining what it does and what would break if it were removed or changed. The MX records send mail to Google. The SPF TXT record tells the world which servers are allowed to send on your behalf. The DKIM CNAME signs outbound messages. The Squarespace verification records prove you own the domain. Six months from now, when a contractor or a future-you logs into the Squarespace DNS settings panel and sees a list of cryptic strings, that document is what prevents a well-meaning cleanup from nuking your mail flow.
Monitor mail flow so customers do not tell you first
You should never learn about an email outage from a client asking why you ghosted them. Set up basic monitoring that pings your domain’s MX records and sends a test message through your own mail server on a schedule. Free tiers from UptimeRobot, Better Stack, and similar services cover this for most small businesses. Additionally, send yourself a weekly test message from an outside address — a personal Gmail works fine — and confirm it lands in your business inbox. Furthermore, watch for DNS misconfiguration warnings inside the Google Admin console itself; Google flags many MX problems before mail starts bouncing.
Quarterly DNS audit and when to call for help
Put a recurring 30-minute calendar block on the first Monday of each quarter. In that block, you compare your live DNS records against your documentation, confirm SPF and DKIM still pass, and check that no orphaned records from a discontinued service are still attached. This is small business IT hygiene at its most basic, and it costs nothing but the time.
The decision of whether to handle this in-house comes down to ROI. A developer or managed IT partner who knows DNS can usually fix a broken mail configuration in under an hour. Compare that to the three-day outage that began this article.
In-house DNS management — pros and cons:
- Pro: No outside invoice, full control over timing
- Pro: You build real knowledge of your own stack
- Con: One wrong record and mail stops cold, as the troubleshooting requests posted by small business owners on freelance marketplaces make obvious
- Con: Diagnosis time during an outage is unpaid stress
Hiring a developer or managed IT partner — pros and cons:
- Pro: Fast diagnosis from someone who has seen the failure mode before
- Pro: Documented work you can hand to the next vendor
- Con: A retainer or hourly cost that is hard to justify until the day you desperately need it
The honest answer for most small businesses sits in the middle. Handle documentation, monitoring, and the quarterly audit in-house. Keep a relationship with a developer warm enough that when something breaks, you are not cold-emailing strangers from your phone while clients wonder where your reply went.
Need Help with Your Small Business Website?
If you’re a small business owner looking to build, redesign, or improve your website, we’d be happy to discuss your specific needs. Monir Tech Solutions specializes in small business website design, development, and maintenance for small businesses across the Boston area and beyond — including custom websites, e-commerce, POS integration, and ongoing support.
Reach out anytime at info@monirtechsolutions.com and we’ll respond within 24 hours.
The Bottom Line
Email outages on Squarespace-connected domains almost always trace back to MX records that no longer match what Google Workspace expects, and the fix is mechanical once you know where to look. The DNS panel that controls your mail routing is the same panel that controls your website, which is precisely why a well-intentioned theme update, a domain transfer, or a forgotten registrar login can silently break inbound mail for days. Furthermore, the silent-bounce scenario is the worst kind of outage because nothing alarms — your site loads, your dashboard looks normal, and clients quietly assume you are ignoring them.
What to remember
Three ideas carry most of the weight. First, the authoritative DNS panel for a Squarespace-managed domain lives inside Squarespace itself, and Squarespace documents how to reach those DNS settings directly from the domain panel. Second, Google Workspace publishes a specific set of MX records that must be present and unblocked by competing records; Cloudflare’s vendor reference notes that Google Workspace requires specific MX records at your DNS provider, and the same principle applies regardless of which provider hosts the zone. Third, documentation is the cheapest insurance you will ever buy. A screenshot of a working DNS panel, dated and saved, is worth more than a maintenance retainer when the records drift.
Trade-offs at a glance
- Pros of fixing it yourself: no consulting fees, faster turnaround, and you build durable institutional knowledge about your own stack.
- Cons of fixing it yourself: a wrong record can extend the outage, propagation delays mask whether your change worked, and troubleshooting layered issues across Squarespace and Google Workspace can stall a non-technical owner.
If you are a solo operator with one domain and a calm afternoon, fix it yourself using the Squarespace DNS panel and Google’s published MX list. If you are juggling Squarespace, a separate registrar, and Google Workspace across multiple staff mailboxes, hire a specialist; listings on Freelancer for exactly this kind of Google Workspace email triage show the work is well-scoped and inexpensive relative to the cost of missed client mail.
Your next step this week
Log into your Squarespace DNS panel today, open Google’s published MX record list in a second tab, and confirm every record matches line for line. Then take a screenshot of the working configuration, drop it into a shared folder labeled with the date, and put a recurring quarterly reminder on your calendar to repeat the check. Therefore, the next time something looks off, you will have a known-good baseline to compare against instead of guessing.
