Website Tracking & Analytics Audit
Free SEO + tracking audit — see exactly what's broken in under 60 seconds
The audit of your website's tracking setup shows that the foundational infrastructure is mostly in place, with Google Tag Manager (GTM) and Google Analytics 4 (GA4) successfully firing on the page. However, there are a few areas that need attention. The dataLayer was not clearly initialized before the GTM container, which could affect data accuracy, and there were no consent API calls observed, which is important for compliance with privacy regulations. Additionally, since your site is not using Shopify, there are no concerns about Trekkie/Web Pixels API or duplicate pixel risks. On this specific page type, no critical events like 'view_item' or 'purchase' were expected to fire, so their absence is not a gap. However, the lack of a clear dataLayer initialization and the absence of consent API calls are areas that should be addressed. For a comprehensive audit, consider reviewing product pages, cart, checkout, and order-confirmation pages next. Given the current issues, it would be beneficial to connect your store to PayHelm AI for a more detailed analysis and guidance.
GTM container installed and loading.
GA4 is installed and sending data.
1 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tags load quickly.
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.
Tags loaded quickly (GTM in 0.55s) — no performance concern.
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.
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
SEO fundamentals look solid across all checks.
Title is 33 characters — within the ideal 30–70 character range.
AM Estate - Недвижимость в Батуми (33 chars)Meta description is 149 characters — within the ideal 70–160 character range.
Агентство недвижимости в Батуми — AM Estate. Помогаем купить квартиры и новостройки у моря: подбор, … (149 chars)One H1 heading found — the recommended structure for every page.
Недвижимость в Батуми,которой можно доверять.No noindex directive — the page is eligible to be indexed.
No robots meta tag (defaults to index, follow).Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://amestate.ge/ru/All 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 presentMarketing & analytics tags observed sending data while the page loaded.
Every dataLayer push observed during page load — with full payload and configuration analysis.
›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.
Data points present in the dataLayer that your tags can read (the values pushed alongside each event).
The actual tracking requests your browser sent — the ground-truth proof that a tag fired.
GTM-PCZ966F9
A Google Tag Manager container is installed on this page.
1/1 container(s) returned a successful gtm.js response.
The container's JavaScript downloaded successfully, so GTM can run.
Found <noscript> ns.html iframe.
The fallback for visitors with JavaScript disabled is in place.
GTM snippet appears inside <head>.
The container is loaded early, as Google recommends, so tags fire as soon as possible.
dataLayer was not clearly initialised before the container snippet.
If the container loads before dataLayer is ready, early values (like ecommerce data) can be lost.
Fix this issueG-M7J4BTX1S4 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
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 issueGTM 545ms, GA4 first hit 1028ms, DOMContentLoaded 752ms
Tags loaded quickly (GTM in 0.55s) — no performance concern.
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.
purchase observed=false, checkout page audited=false
We couldn't reach the checkout or order-confirmation page during this audit, so purchase tracking is unverified. Purchase is the single most important event to get right — test it with a real or test order and confirm the 'purchase' event fires once on the thank-you page.
Fix this issueFunnel events are page-specific: purchase only fires on order confirmation, add_to_cart requires a user click. Events shown as are not observable on this page type — audit each page separately for full coverage.
Discovery
Not observed on this page. Set up 'view_item_list' on your collection/category/search pages for funnel visibility.
Fix this gapNot observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.
Consideration
No ecommerce tracking detected on this page. Add a 'view_item' dataLayer push on your product detail pages.
Fix this gapCart Activity
Not observed during this load — 'add_to_cart' requires user interaction on product pages and cart. Verify by manually testing the action on that page.
Not observed during this load — 'remove_from_cart' requires user interaction on cart page. Verify by manually testing the action on that page.
Not observed on this page. Set up 'view_cart' on your cart page for funnel visibility.
Fix this gapCheckout Funnel
No ecommerce tracking detected on this page. Add a 'begin_checkout' dataLayer push on your checkout entry page.
Fix this gapNot observed during this load — 'add_shipping_info' requires user interaction on checkout shipping step. Verify by manually testing the action on that page.
Not observed during this load — 'add_payment_info' requires user interaction on checkout payment step. Verify by manually testing the action on that page.
No ecommerce tracking detected on this page. Add a 'purchase' dataLayer push on your order confirmation / thank-you page.
Fix this gapPost-Purchase
This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.
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.
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.