Squarespace hosts millions of small-business and portfolio sites, and every one of those sites has the same problem: adding a small piece of live data — how many people are reading, which countries visit, where people click — usually means installing an extension you'll have to maintain, update and trust.
No extension. Squarespace renders raw HTML and script tags inside a Code Block, so there is nothing to install from the Extensions marketplace. Every widget below is one snippet, pasted in once. Pick one and the page tells you the exact menu path for Squarespace, the gotchas, and what to do if you're on an older theme or a page builder.
Squarespace keeps its editor simple, so there's no plugin system in the WordPress sense. Extensions exist, but they're mostly for commerce tasks such as shipping and inventory. For a small widget, the built-in Code Block or Code Injection is the way in: paste the FeedPulse snippet, save and check the live page. There's nothing to install or connect.
A Code Block puts the widget in a specific spot on a specific page, which suits countdowns, weather or a badge in a section. Code Injection adds a script to the header or footer of every page, which suits sitewide tools such as the heatmap or a footer counter. Both need a plan that allows JavaScript, which on current plans means Core or above. Each widget page below names the right one.
Goes in Settings → Advanced → Code Injection → Header, because it has to load on every page before your clicks happen, and it renders nothing visible.
Goes in Settings → Advanced → Code Injection → Footer, because an all-time total is a footer artefact — nobody scrolls up to check it.
Goes in a Code Block in the footer or a sidebar section, because local conditions are a glanceable sidebar item, not a content block.
Goes in a Code Block in the footer or a sidebar section, because a ticker reads best as a persistent strip beside the content.
Goes in a Code Block in the footer or a sidebar section, because quotes are reference data — visible, but never competing with the article.
Goes in a Code Block on the page, because a countdown works above the fold on the page that's actually selling the thing.
Goes in a Code Block on the page, because it's the most visual widget you have, so it earns a spot in the content rather than the chrome.
Goes in a Code Block inside the blog post, because it belongs directly under the article body, which means the blog-post template rather than a global widget area.
Goes in Settings → Advanced → Code Injection → Footer, because trust badges are read at the moment of hesitation, which is usually the footer.
Goes in a Code Block in the footer or a sidebar section, because a live pill is only useful if it's visible before the visitor decides to leave.
Goes in a Code Block in the footer or a sidebar section, because the whole point is catching someone while you're actually live.
Goes in a Code Block on the page, because it's social proof for a specific project, so it goes inline next to what it's vouching for.
Goes in a Code Block on the page, because it belongs beside the install command, in the post or docs page that teaches it.
Goes in a Code Block in the footer or a sidebar section, because a live member count is a standing invitation, so it should follow the reader down every page.
Goes in Settings → Advanced → Code Injection → Footer, because it's a floating bubble, so it only needs to exist once per page and should load last.
Goes in Settings → Advanced → Code Injection → Header, because one paste in the head gives every page its own score — the badge auto-detects which page it's on.
Goes in Settings → Advanced → Code Injection → Footer, because a ranked country list belongs at the bottom, where its lazy-loaded flags stay below the fold.
Goes in a Code Block on the page, because a live count only changes behaviour when it sits in the same line of sight as the price or the button.
Squarespace shows a placeholder for Code Blocks while you're editing and doesn't run injected scripts in the editor. Save, then open your live URL in a normal tab and do a hard refresh, because Squarespace caches pages. If you're on a 7.0 template that loads pages with AJAX, a widget may appear on the first page and disappear after you click to another; turning off AJAX loading in Site Styles fixes it.
Squarespace is popular with creatives, restaurants, studios and small businesses. A countdown timer works for events, launches and limited offers, the weather widget suits venues and outdoor businesses, a flag counter or visitor globe suits portfolios with international clients, and the verified traffic badge suits bloggers who take sponsorships.
Squarespace templates are built around generous spacing, so a widget dropped in without thought can look out of place. Put it inside a section with enough padding, pick a widget theme that matches your colours, and check the mobile layout, because Squarespace stacks blocks differently on phones.
Delete the Code Block, or the snippet in Code Injection, and save. Nothing else on your site depends on it.
On Squarespace's current plans, Code Injection (Settings → Advanced → Code Injection) is available on Core, Plus and Advanced, and on the older Business and Commerce plans, but not on Basic or the older Personal plan. Code Blocks exist on every plan, but JavaScript inside them only runs on those same higher plans, so on Basic you'll see the block but not the widget. Custom code never runs on checkout pages.