Quick summary
A tracking implementation note about adding call tracking, Google Tag Manager, and Search Console verification to a client-routed static site without duplicating scripts.
The problem
A statically generated site needed a coordinated measurement setup, but an older number-swap loader conflicted with the new call-tracking provider and client-side navigation could skip rescans.
What I checked
- Existing number-swap and booking-form scripts
- Client-side navigation behavior
- Privacy opt-out handling
- Tag-manager head and noscript placement
- Live script duplication and browser console output
What I changed
- Added the supplied call-tracking loader sitewide
- Removed the competing number-swap loader while preserving booking forms
- Triggered rescans after client-side route changes
- Added tag-manager consent initialization, noscript fallback, and site verification
- Updated environment documentation and passed the full production build
Result
The site now has coordinated call tracking, tag management, and ownership verification that survives client-side navigation without loading competing number-replacement scripts.
Where this fix usually leads next
This kind of work usually connects back to Analytics & Tracking, Technical SEO and API & Integrations so the fix note can lead into a clearer support path instead of staying as an isolated one-off task.
What I'd watch next
- Whether container tags assume libraries the site does not use
- Whether future route changes still trigger call-number rescans
- Whether privacy controls stay aligned with new tracking tags