in.puma.com Tracking & SEO Audit — Grade C
A saved report based on tracking and pages observed during this scan.
Your website's tracking setup shows a few areas that need attention. Both Google Tag Manager containers are loading correctly, but GA4 did not fire on this page, which is a concern since it should be tracking page views. Universal Analytics, which is outdated, was detected and should be phased out. There a…
Read the full audit summary
Your website's tracking setup shows a few areas that need attention. Both Google Tag Manager containers are loading correctly, but GA4 did not fire on this page, which is a concern since it should be tracking page views. Universal Analytics, which is outdated, was detected and should be phased out. There are also warnings about the placement of the GTM snippet and the absence of a <noscript> fallback, which could affect data accuracy. Additionally, the page experienced multiple JavaScript errors, which might impact user experience and data collection. Since this is not a Shopify store, Trekkie and Web Pixels API are not applicable. Next, you should audit key pages like product, cart, checkout, and order-confirmation to ensure all critical events are firing. Given these issues, I recommend connecting your store to PayHelm AI for a comprehensive analysis and guidance.
Your website's tracking setup shows a few areas that need attention. Both Google Tag Manager containers are loading correctly, but GA4 did not fire on this page, which is a concern since it should be tracking page views. Universal Analytics, which is outdated, was detected and should be phased out. There are also warnings about the placement of the GTM snippet and the absence of a <noscript> fallback, which could affect data accuracy. Additionally, the page experienced multiple JavaScript errors, which might impact user experience and data collection. Since this is not a Shopify store, Trekkie and Web Pixels API are not applicable. Next, you should audit key pages like product, cart, checkout, and order-confirmation to ensure all critical events are firing. Given these issues, I recommend connecting your store to PayHelm AI for a comprehensive analysis and guidance.
What to look at first
Priorities below are taken directly from findings in this report.
1 critical SEO issue detected — fix these to avoid being excluded from search results.
Title is 38 characters — within the ideal 30–70 character range.
PUMA.COM | Forever Faster | PUMA India (38 chars)Meta description is 153 characters — within the ideal 70–160 character range.
Puma India - Shop Online for Puma shoes & apparels and get Free Shipping. Buy Puma Shoes, Clothi… (153 chars)One H1 heading found — the recommended structure for every page.
FLAT 40% OFFThe page has a noindex directive — search engines will NOT index this page. Remove it if the page should appear in search results.
robots: noindex, followCanonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://in.puma.com/in/enAll 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 presentAI Build Signals
Not assessedNot assessed in this saved report
Builder attribution is separate from AI discovery and SEO. A rescan can look for public clues; it cannot prove how a site was created.
Marketing & 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.
Marketing & 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.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
GTM container installed and loading.
GA4 configured but no hits observed (may be consent-gated).
4 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode v2 configured.
Tag loading is slower than ideal.
Conflicting or deprecated analytics IDs detected.
Consent Mode v2 is configured via OneTrust. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
Google Tag Manager loaded in 2.8s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.
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 appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
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.
GTM-PZGBHQT, GTM-TSWKBGX3
A Google Tag Manager container is installed on this page.
2/2 container(s) returned a successful gtm.js response.
The container's JavaScript downloaded successfully, so GTM can run.
No <noscript> fallback found in the HTML source.
The recommended <noscript> fallback is missing. It's minor, but Google's standard install includes it.
Fix this issueGTM snippet was not found high in <head>.
The container loads later than recommended. Tags may fire late and miss early page activity.
Fix this issueG-X8YL1E9ZV6 — 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 issueFound UA tag.
Universal Analytics stopped processing data in 2023. These tags do nothing and should be removed.
Fix this issue15 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.
default=true, update=true, signals=[ad_storage, analytics_storage, ad_user_data, ad_personalization], CMP=OneTrust
Consent Mode v2 is configured via OneTrust. The default and update calls and the v2 signals (ad_user_data, ad_personalization) are all present.
GTM 2809ms, GA4 first hit 6010ms, DOMContentLoaded 1863ms
Google Tag Manager loaded in 2.8s — a little slow. Keeping it under ~1.5s helps both tracking accuracy and page speed.
Fix this issueNo 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.
allow_enhanced_conversions in code; enhanced_conversion_data in code
Google Ads Enhanced Conversions appear to be set up — hashed first-party data is being passed to improve conversion accuracy.
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. Confirm 'view_item_list' is configured on your collection/category/search pages.
Not observed during this load — 'select_item' requires user interaction on collection/category pages. Verify by manually testing the action on that page.
Consideration
Not observed firing, but 'view_item' was found configured in the site's JavaScript. It may fire only when users take specific actions or visit the relevant page type. Not observed on this page. Verify 'view_item' is firing on your product detail pages — important for attribution and conversion reporting.
Cart 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. Confirm 'view_cart' is configured on your cart page.
Checkout Funnel
Not observed firing, but 'begin_checkout' was found configured in the site's JavaScript. It may fire only when users take specific actions or visit the relevant page type. Not observed on this page. Verify 'begin_checkout' is firing on your checkout entry page — important for attribution and conversion reporting.
Not 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.
Not observed firing, but 'purchase' was found configured in the site's JavaScript. It may fire only when users take specific actions or visit the relevant page type. Not observed on this page. Verify 'purchase' is firing on your order confirmation / thank-you page — important for attribution and conversion reporting.
Post-Purchase
This event fires server-side (server-side or order management system) and cannot be observed by a browser-based audit.
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.