Analytics counting every visit twice on a site builder: one tag, one route, one check

Two routes for one tag

Each builder offers a built-in way to connect Google Analytics, and each also lets you paste the same tag as code. Use both and the tag loads twice, and every page view is counted twice. Webflow's own advice is blunt: add the Google tag in one place only, either the integration in site settings or the head code. If you later install Webflow's Google site tools app, remove the older site-settings integration afterwards.

On Squarespace, the built-in integration takes a measurement ID that starts with G- and works without script code. The code injection help says that if you use the built-in integration you should not also add code in code injection. On Wix, the question usually runs the other way: Google Analytics, Tag Manager and the Facebook and TikTok pixels do not work through Custom Code at all, so a pasted copy either does nothing or collides with the marketing integration.

• List every place the measurement ID appears: integration fields, head code, footer code and any tag manager container.
• Keep one route and remove the others.
• Note the date of the change so reports can be read across it.

Scripts that run again

A tag can also fire twice from a single installation. Squarespace warns that customers can revisit an order status page, which may trigger a tracking script more than once, and says to wrap the script in a first-page-view condition so it runs only on the first visit. If your purchase count is higher than your real orders, this is the first place to look.

Another source is a single-page navigation: a tag may fire on the first load and again as the visitor moves between pages that do not fully reload. The Squarespace Google Analytics article says a version 7.0 site with Ajax loading logs only the first page of a visit until Ajax loading is turned off, which is the opposite fault, undercounting.

• Check purchases against your real orders for the same days.
• Test the order confirmation page twice in a fresh browser window.
• Compare views per visit for the sign of undercounting.

How to count what actually fires

Do not read your reports to find the fault; read the page. Google's Tag Assistant connects to your site, adds a debug signal to the address and lists the tags that fire and the hits sent as you move around. In the browser developer tools, the network panel filtered by your measurement ID shows each request; one page load should show one page-view request.

Remember what is not a fault. Squarespace data can take up to 24 hours to appear in Google Analytics, and with a cookie banner and consent choices turned on, Squarespace's own visitor counts can run well above Google Analytics'. Those gaps are about consent and timing, not duplicate tags.

• Load the page once and count the page-view requests.
• Repeat on the order confirmation page and one other page type.
• Wait a day before judging reports after a change.

What does not fit, and acceptance

Consent banners, legal choices and the design of events and goals are outside any tag fix, and Squarespace says it cannot help set up or troubleshoot Tag Manager. If the faulty tag belongs to a vendor's app, only the vendor can change it.

The fixed-scope fix of one snippet, tag or widget is priced at £125 as an untested proposal and paid only after you sign off. For a tag it is accepted when the network panel or Tag Assistant shows one page-view request per load on each named page, the change list names every place the tag was found, and each can be reversed. A monthly check of forms and tags is available as a separate standing service.