ipromiseaustralia.com.au Tracking & SEO Audit — Grade B
A saved report based on tracking and pages observed during this scan.
Your website's tracking setup has a few areas that need attention. Currently, one of your Google Tag Manager (GTM) containers is not loading correctly, which could affect your data accuracy. On the home page, the Meta Pixel, Google Ads, and Google Analytics 4 tags fired successfully, indicating that basic tracking is operational. However, there is a warning regarding the absence of Google Consent Mode API calls, which could impact compliance with privacy regulations. Additionally, the page load performance for GTM is slower than ideal, which might affect user experience. For Shopify stores, there is no detection of Shopify-native analytics like Trekkie or the Web Pixels API, which could lead to missing insights. Next, you should audit your product pages, cart, and checkout processes to ensure all critical events are tracked accurately. Given the issues identified, I recommend connecting your store to PayHelm AI for a more comprehensive analysis and to address these gaps effectively.
GTM container installed and loading.
GA4 is installed and sending data.
4 of 4 key funnel stages look healthy.
No data-quality issues found in tracked events.
Consent Mode not detected.
Tag loading is slower than ideal.
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.
Google Tag Manager loaded in 2.7s — 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 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 basics are mostly in place with a few opportunities to improve.
Title is 58 characters — within the ideal 30–70 character range.
iPromise Australia - Energy Company in Victoria, Australia (58 chars)Meta description is 184 characters. Google may truncate descriptions over ~160 chars.
iPromise is a 100% Australian-owned energy company in Victoria that provides energy-saving solutions… (184 chars)One H1 heading found — the recommended structure for every page.
WE OFFER COMMERCIAL LIGHTING FOR FREE UPGRADES UNDER THE VEU REBATE PROGRAM.No noindex directive — the page is eligible to be indexed.
robots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1Canonical tag points to the page itself — no duplicate-content signals sent to search engines.
https://ipromiseaustralia.com.au/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 present2 AI discoverability gaps found — closing them improves your odds of being cited by ChatGPT, Claude, Perplexity, and Google AI Overviews.
llms.txt exists but doesn't follow the standard format. Use a top-level heading plus markdown links to your most important pages.
Found at /llms.txt but missing the expected structure (a top-level # heading and markdown links).robots.txt doesn't block any major AI crawler — ChatGPT, Claude, Perplexity, and Google's AI features can all fetch and cite your content.
All 15 known AI crawlers are allowed.GPTBot's User-Agent successfully fetched the real page (HTTP 200, ~509 words) — AI crawlers are not blocked at the server level.
GPTBot's User-Agent received HTTP 200 with ~509 words of visible text.Structured data (JSON-LD) is present with types AI answer engines commonly extract facts from (e.g. FAQPage, Product, Organization).
Schema.org types found: BreadcrumbList, WebSite, Organization.Meaningful text content is present in the raw HTML response — AI crawlers that don't execute JavaScript can still read and cite this page.
~3382 words of text visible in the raw HTML response.No sitemap.xml found. Without one, crawlers (including AI crawlers) can only discover pages by following links, which may miss deeper content.
No /sitemap.xml found.- Reformat llms.txt to follow the standard: a top-level `# Site Name` heading, a one-line summary, then markdown links (`[Page](url): description`) to your key pages.
- Publish a sitemap.xml — it's the fastest way for both search engines and AI crawlers to discover every page worth citing, not just the ones linked from your homepage.
WooCommerce markup (woocommerce / wc-* classes) in HTML
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 (2)— 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 (2)— 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-P8L6WBJT, GTM-T5838KJZ
A Google Tag Manager container is installed on this page.
1/2 container(s) returned a successful gtm.js response.
Some containers loaded but at least one did not — check the container ID is published and not blocked.
Fix this issueFound <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 is defined before the container snippet.
Data is available to tags from the very first event.
G-HT7WMSL3X1 — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
1 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.
WooCommerce markup (woocommerce / wc-* classes) in HTML
This site runs on WooCommerce. Tracking setup and common pitfalls differ by platform, which is factored into this audit.
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 2678ms, DOMContentLoaded 3312ms
Google Tag Manager loaded in 2.7s — 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.
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
Not observable on home pages — 'view_item' only fires on product detail pages. Audit that page type to verify coverage.
Cart Activity
Not observable on home pages — 'add_to_cart' only fires on product pages and cart. Audit that page type to verify coverage.
Not observable on home pages — 'remove_from_cart' only fires on cart page. Audit that page type to verify coverage.
Not observable on home pages — 'view_cart' only fires on cart page. Audit that page type to verify coverage.
Checkout Funnel
Not observable on home pages — 'begin_checkout' only fires on checkout entry page. Audit that page type to verify coverage.
Not observable on home pages — 'add_shipping_info' only fires on checkout shipping step. Audit that page type to verify coverage.
Not observable on home pages — 'add_payment_info' only fires on checkout payment step. Audit that page type to verify coverage.
Not observable on home pages — 'purchase' only fires on order confirmation / thank-you page. Audit that page type to verify coverage.
Post-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.
Meta Pixel script (fbevents.js) found hardcoded directly in the page HTML.
Fix: Remove the hardcoded snippet and use a GTM 'Facebook Pixel' or 'Custom HTML' tag instead.
Risk: If GTM also fires Meta Pixel, you'll double-count conversions and inflate ROAS. Centralising in GTM also lets you pause, version, and conditionally fire without a code deploy.
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.
Cannot read properties of null (reading 'style')
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.