Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
Your website's tracking setup has a few areas that need attention. Currently, Google Analytics 4 (GA4) is set up but did not successfully fire on your homepage, which means visitor data might not be captured accurately. There is no Google Tag Manager (GTM) container detected, and instead, a direct gtag.js setup is present, which could limit flexibility in managing tags. Additionally, there are several console errors related to your site's Content Security Policy, which could affect how scripts and styles are executed. Since your store is not on Shopify, Trekkie and Web Pixels API do not apply, so there's no risk of duplicate pixels from those sources. Next, it would be wise to audit other key pages like the product page, cart, and checkout to ensure tracking is functioning correctly across your site. Given the issues identified, I recommend connecting your store to PayHelm AI for a more comprehensive analysis and assistance in resolving these gaps.
Tag setup present but not confirmed loading.
GA4 configured but no hits observed (may be consent-gated).
Not an ecommerce store — scored on basic analytics coverage.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag load timing not measured.
No conflicting analytics IDs.
No Google Consent Mode was detected. Since March 2024 Google requires Consent Mode v2 for sites with EEA/UK traffic running Google Ads — without it, conversion and remarketing data is lost for users who haven't consented.
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
SEO fundamentals look solid across all checks.
Title is 48 characters — within the ideal 30–70 character range.
Golf breaks in Spain - Almeria, Murcia, Alicante (48 chars)Meta description is 123 characters — within the ideal 70–160 character range.
Golf holidays to the beautiful Spanish regions of Almeria, Murcia and Alicante. Discount green fees … (123 chars)One H1 heading found — the recommended structure for every page.
Golf breaks in SpainNo noindex directive — the page is eligible to be indexed.
robots: index, followCanonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://click2mojacar.co.ukAll core Open Graph tags found — links display richly when shared on social media.
og:title ✓ og:description ✓ og:image ✓Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).
JSON-LD script foundViewport meta tag found — the page is set up for mobile-friendly rendering.
viewport meta tag presentNo GTM-XXXX container; gtag.js present instead.
Tags are loaded directly via gtag.js rather than through Tag Manager. That works, but you lose GTM's centralised management, versioning, and conditional firing controls.
Fix this issueG-J4BEG8PMR3 — no /g/collect hit observed.
GA4 is configured but we did not see it send data on this page — it may be gated behind cookie consent or misconfigured.
Fix this issue8 error(s) logged.
JavaScript errors were logged during page load. These don't necessarily affect tracking — only errors that directly interrupt pixel execution matter. See any vendor-specific errors below for actionable issues.
No consent API calls observed
No Google Consent Mode was detected. Since March 2024 Google requires Consent Mode v2 for sites with EEA/UK traffic running Google Ads — without it, conversion and remarketing data is lost for users who haven't consented.
Fix this issueDOMContentLoaded 609ms
No tag load timing was captured (the container may not have loaded, or timing was unavailable).
No linker configuration observed
No cross-domain (linker) tracking was detected. If your checkout or other steps live on a different domain, set up linker tracking so visits aren't split into separate sessions.
Not detected
Google Ads Enhanced Conversions were not detected. They send hashed first-party data (email/phone) to recover conversions lost to cookie restrictions — worth enabling if you run Google Ads.
Not detected
GA4 User-ID tracking was not detected. If you have logged-in users, setting a User-ID lets GA4 join their activity across devices and sessions.
Ecommerce Funnel — Not Applicable
This site doesn't appear to be an online store, so the ecommerce funnel report has been skipped. GTM tag coverage, triggers, variables, and on-page scripts are still audited above.
If this site does sell products, try re-running the audit on a product page URL — that will surface add-to-cart, checkout, and purchase event coverage.
These tracking scripts are hardcoded directly in your page HTML. Moving them into GTM makes them easier to update, pause, version, and conditionally fire — without touching your code.
GA4 gtag.js snippet installed directly in the page HTML (outside GTM).
Fix: Remove the hardcoded GA4 snippet and manage it via a GTM 'Google Analytics: GA4 Configuration' tag.
Risk: Running GA4 both directly and via GTM sends duplicate pageviews and inflates every metric in your reports.
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-pUlYSz6vYltzdVx6OpMB0aYbqVH2k2opba0iFHB8COw='), or a nonce ('nonce-...') is required to enable inline execution.
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-FaB40muXmfFscX47urxW2OCWqaRAAMJTxzx5oJmFm+M='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-FaB40muXmfFscX47urxW2OCWqaRAAMJTxzx5oJmFm+M='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-FaB40muXmfFscX47urxW2OCWqaRAAMJTxzx5oJmFm+M='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-dHjToVmJw+JAvsn/gwM4QwAy3M6elPDUmbuAzD7KQfY='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-2UZqx0UwkEqZjnLFczW2e7LZfnpvTTay0iKSZXUnKRQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-2UZqx0UwkEqZjnLFczW2e7LZfnpvTTay0iKSZXUnKRQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src https:". Either the 'unsafe-inline' keyword, a hash ('sha256-2UZqx0UwkEqZjnLFczW2e7LZfnpvTTay0iKSZXUnKRQ='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes
Your tracking has gaps — PayHelm can fix this.
Broken tags mean lost attribution and bad decisions. PayHelm unifies your ecommerce, ad, and analytics data so every number is trustworthy — no guesswork.