If the Squarespace editor is the thing misbehaving, a Chrome extension is the cause about half the time — ad blockers and privacy extensions strip the scripts the editor needs. Open the same page in an Incognito window, where Chrome disables extensions by default. If it works there, an extension is the culprit and you have your answer in twenty seconds.

 A blank Squarespace page is almost always custom code you added, not a Squarespace fault, and almost always fully recoverable.

Something further down the cascade is beating Site Styles, and in most cases it is Custom CSS you or a previous designer added. Squarespace 7.1 loads the Custom CSS panel after the generated Site Styles stylesheet, so an equally specific rule there always wins.

If the embed is blank while you're logged in, nothing is broken. Squarespace disables embedded scripts in the editor as a security measure and shows the message "This block contains embedded scripts.

The product's Visibility is almost certainly set to Hidden or Scheduled rather than Public. In Squarespace 7.1 that control lives in the product editor under Organization → Visibility, and it is the one field people skip when duplicating an existing product to save time.

 If you're seeing Times New Roman or a generic sans-serif where your font should be, the font file never loaded and the browser fell back. On Squarespace 7.1 that is nearly always a broken @font-face rule — usually a mismatched font-family name or a mangled src: url() path. If the font is right but the weight is wrong, the file for that weight simply doesn't exist. Two different problems, two different fixes.

 In Squarespace 7.1 there is no separate publish step — saving an edit makes it live immediately on a public site. So if the live page hasn't changed, either the edit was never saved, or your browser is showing you a cached copy. Check in a private window first.

 your browser is almost certainly serving a cached icon. Browsers cache favicons far more aggressively than they cache pages, and a normal refresh will not touch them. Load your site in a private window first. If the favicon appears there, the file uploaded correctly and you are looking at cache. If it is missing there too, the problem is the file itself — usually format or file size.

 If your Squarespace 7.1 store shows "Checkout is closed. This store isn't set up to take orders", your payment processor is disconnected — reconnect it in Settings → Selling → Payments and you're trading again in two minutes.

If a page is missing from your menu, it's almost certainly sitting in the Not linked section of the Pages panel. Squarespace 7.1 puts some new pages there by default, and pages in Not linked stay live and indexable — they just don't appear in navigation. Drag it up into Main Navigation and it returns.

You cannot manually force a Squarespace certificate to issue — but you can remove what's blocking it. In almost every stuck case the domain isn't fully pointing at Squarespace yet, or a CAA record at the registrar is refusing the certificate authority permission to issue.

The Squarespace 7.1 mobile menu is almost never broken by Squarespace. Tapping the burger adds a header--menu-open class to the .header element, and CSS flips the .header-menu overlay from visibility: hidden to visible. If custom CSS overrides those properties, or a JavaScript error stops the class from being added at all, the tap does nothing.

Most Squarespace images are not broken, they are unloaded. Squarespace 7.1 ships images with an empty or placeholder src and a real data-src, then swaps them in with JavaScript once the browser knows the viewport width.

In most cases the code is fine and you are looking at it from the wrong place. Squarespace deliberately disables embedded scripts while you are logged in and editing, so injected code that works perfectly for visitors appears dead to you. Log out, open the page in a private window, and check again before changing anything.

A genuine Squarespace platform outage is the least likely explanation, despite being the first thing everyone checks. Open your built-in yoursite.squarespace.com URL.

Most "domain not connecting" cases are one of two things — the records haven't finished propagating yet, or an old record left behind at your registrar is still answering for the domain. Squarespace needs four A records on the apex, one www CNAME and one verification CNAME.

In most cases the form has no storage destination. Squarespace requires at least one — a mailing list, an email address, Google Drive, Mailchimp, Zapier or the Contacts panel — and without one, visitors physically cannot submit.

In most cases your CSS is fine and the selector is wrong. Squarespace 7.1 renames and restructures classes between sections, and Fluid Engine writes inline styles that beat anything in your stylesheet.

A genuine Squarespace platform outage is rare. In almost every case the problem is one of four things — your domain or DNS, your billing or visibility settings, custom code you or someone else added, or your own browser.

If your banner image looks cropped on mobile in Squarespace 7.1, this guide shows you how to keep the full image visible. Learn simple layout adjustments and CSS tweaks to make sure your hero section looks balanced and intentional on smaller screens.