Why your analytics code disappears after publishing
If you build your site with a desktop program — WebSite X5, Xara, Mobirise, Pinegrow, Adobe Muse and friends — and your analytics stopped reporting for no apparent reason, this is almost certainly what happened. It is not a bug in your analytics tool, and it is not something you did wrong.
What actually happens
These programs keep the real version of your site on your own computer. When you press Publish, they upload their own copy of each page over FTP and overwrite whatever is on the server. Anything you added directly to the published files — a tracking snippet pasted into the HTML, a verification tag, a chat widget — is not part of the program's project, so it is not in the copy being uploaded. It vanishes.
The reason it is so hard to notice: it happens one page at a time. The program only re-uploads pages you changed, so your snippet survives on the pages you have not touched. Your numbers do not drop to zero — they just drift downwards over weeks while you assume traffic is falling. We have seen a real site lose its home page first and keep reporting from a handful of inner pages for three more weeks.
The fix: paste the code in the program, not in the pages
Every one of these builders has a place to put custom code that becomes part of the project, so it is re-inserted into every page on every publish. That is where a tracking snippet belongs.
WebSite X5 (step by step)
Step 1 — Settings → Advanced → Custom Code. In some versions the same screen is labelled Statistics, SEO and Code; either way it is inside Step 1's Advanced tab.
You will see a Position dropdown that chooses where the code is injected. The two that matter:
| Position | Use it for |
|---|---|
Before the </head> tag | Analytics and tracking pixels — anything that should load before the visible content. This is where the Logly snippet goes. |
Before the </body> tag | Heavier scripts, chat widgets, anything that manipulates the page and shouldn't block the initial render. |
Paste the full snippet — including the <script> and
</script> tags — into the text box and publish. From that moment the code
is part of the project: every page gets it on every publish, including pages you create later.
The same box accepts a plain reference to an external file, if you ever need one:
There is also a per-page equivalent in Step 3 — Map → page Properties → Expert. Avoid it for analytics: per-page means remembering to repeat it on every page you ever add, which is how sites end up measuring half their traffic.
The same idea in other builders
| Builder | Where to look |
|---|---|
| WebSite X5 | Step 1 → Settings → Advanced → Statistics, SEO and Code |
| Mobirise | Site Settings → Head/End of body code |
| Xara Web Designer | Website Properties → Head/Body HTML code |
| Pinegrow | Edit the page template rather than individual pages |
| Any builder | Search its settings for "custom code", "HTML head", "header/footer code" or "tracking code" |
The rule that covers all of them: if you can only paste the code into a published file, you are pasting it in the wrong place. Find the setting that lives inside the project.
The Logly snippet
Under 1 KB, no cookies, no consent banner needed. Put it in the <head> field
of your builder. Your site id is on your dashboard next to the site name.
How to tell whether it is working
Open your published site in a browser, right-click and choose "View page source", then search for
logly. If it is there, you are fine. Do this on more than the home page —
checking only the front page is exactly how this problem stays hidden for weeks.
Logly tells you when this happens. If a site that was reporting normally goes quiet, we notice and look into it, because a tracker that silently stops is worse than no tracker at all — you keep making decisions on numbers that stopped being true.
We are not affiliated with any of these companies
Logly has no relationship, partnership or affiliate deal with Incomedia or with any other builder mentioned on this page, and nothing here is sponsored. We wrote it because one of our users lost their analytics this way and it took us weeks to work out why. The instructions are useful whichever analytics tool you use — including the one that came with your builder.
Still stuck?
Use the chat widget in the bottom-right corner of this page, or write to [email protected]. Tell us which program you use and we will find the right field for it — even if you end up not using Logly.