Website Tracking & Analytics Audit

Free SEO + tracking audit — see exactly what's broken in under 60 seconds

Works, with issueshttps://www.dikshitech.com/

Your website's tracking setup shows mixed results. The Google Tag Manager (GTM) is correctly installed and functioning, and your Google Analytics 4 (GA4) is firing as expected on the homepage. However, there are some issues to address: the GTM snippet is not optimally placed in the HTML, and there's no <noscript> fallback, which could affect tracking if users have JavaScript disabled. Additionally, there are several console errors related to content security policies that need attention. Since your site is not on Shopify, there's no need to worry about Trekkie or Web Pixels API. Next, it would be wise to audit other key pages like product, cart, checkout, and order-confirmation pages to ensure comprehensive tracking. Given the issues identified, I recommend connecting your store to PayHelm AI for more detailed insights and solutions.

Tracking Health: 84/100 · BSEO Score: 90/100 · AAI SEO Score: 48/100 · D

Overall Tracking Health

84out of 100Grade BGood

Tag manager installed20/20

GTM container installed and loading.

GA4 tracking20/20

GA4 is installed and sending data.

Pageview / event coverage20/20

Not an ecommerce store — scored on basic analytics coverage.

Data quality15/15

No data-quality issues found in tracked events.

Consent Mode0/10

Consent Mode not detected.

Performance4/10

Tag loading is slower than ideal.

No conflicts5/5

No conflicting analytics IDs.

Advanced Tracking Features

Consent Mode v2Info

No Google Consent Mode was detected. This mainly matters if you run Google Ads with EEA/UK traffic — no Google Ads pixel was seen on this site, so it's lower priority for now.

default: noupdate: no✗ ad_user_data✗ ad_personalization

Tag PerformanceWarning

Google Tag Manager took 4.3s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.

GTM 4.32sGA4 first hit 4.54sDOM ready 1.83sPage load 1.84s

Cross-domain TrackingInfo

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.

Enhanced ConversionsInfo

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.

User-ID TrackingInfo

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 Review

90out of 100Grade AExcellent

SEO basics are mostly in place with a few opportunities to improve.

Title tagPass

Title is 54 characters — within the ideal 30–70 character range.

Dikshi Technologies | Software & App Development India (54 chars)

Meta descriptionPass

Meta description is 154 characters — within the ideal 70–160 character range.

Dikshi Technologies provides ERP, billing, mobile apps, AI & RFID solutions for retail, jewellery, r… (154 chars)

H1 headingPass

One H1 heading found — the recommended structure for every page.

Dikshi Technologies

Robots / indexabilityPass

No noindex directive — the page is eligible to be indexed.

robots: index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1

Canonical URLWarning

No canonical tag found. Adding one prevents duplicate-content issues when a page is accessible via multiple URLs.

No canonical link tag found.

Open Graph tagsPass

All core Open Graph tags found — links display richly when shared on social media.

og:title ✓ og:description ✓ og:image ✓

Structured data (Schema.org)Pass

Structured data found — search engines can use it to generate rich results (star ratings, FAQs, products, breadcrumbs, etc.).

JSON-LD script found

Mobile viewportPass

Viewport meta tag found — the page is set up for mobile-friendly rendering.

viewport meta tag present

AI Discovery & AI SEOOpen to AI

48out of 100Grade DNeeds work

The basics for AI access are in place, but there's no llms.txt yet — an easy, high-leverage addition.

llms.txt fileWarning

No llms.txt file found. This is a plain-text, markdown-style index of your key pages that AI assistants (ChatGPT, Claude, Perplexity) increasingly check to understand a site quickly.

No /llms.txt found (404 or empty).

AI crawler access (robots.txt)Pass

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.

Live AI crawler testWarning

GPTBot's User-Agent was let through (HTTP 200) but received a near-empty page (~45 words) — possibly a lighter/JS-only response served specifically to crawlers.

GPTBot's User-Agent received HTTP 200 with ~45 words of visible text.

Structured data for AI answersWarning

JSON-LD is present, but not using the schema types AI engines rely on most (FAQPage, Product, Organization, Article). Consider adding one that matches your content.

Schema.org types found: SoftwareCompany, PostalAddress, ContactPoint.

Server-rendered contentWarning

Very little text is present in the raw HTML — this page likely relies on client-side JavaScript to render content. Most AI crawlers (GPTBot, ClaudeBot, PerplexityBot) don't execute JavaScript, so they may see a near-empty page.

~37 words of text visible in the raw HTML response.

XML sitemapPass

A sitemap is available at /sitemap.xml, helping both search engines and AI crawlers discover your full set of pages efficiently.

Found at /sitemap.xml.

AI crawlers

GPTBot ✓OAI-SearchBot ✓ChatGPT-User ✓ClaudeBot ✓Claude-Web ✓anthropic-ai ✓PerplexityBot ✓Perplexity-User ✓Google-Extended ✓Applebot-Extended ✓Bytespider ✓CCBot ✓Amazonbot ✓cohere-ai ✓Meta-ExternalAgent ✓

Opportunities

Add an /llms.txt file listing your most important pages (pricing, docs, product pages) in markdown format — it gives AI assistants a fast, reliable summary of your site instead of guessing from crawled HTML.
GPTBot can reach your server, but the response it gets back is nearly empty — check for User-Agent-based content rules serving a stripped-down page to crawlers.
Add FAQPage or Organization structured data (JSON-LD) — AI answer engines pull facts directly from these schema types when citing sources.
Server-render (or pre-render) key page content — most AI crawlers don't run JavaScript, so client-side-only rendering makes your content invisible to them even though it looks fine in a browser.

GTM-58786CDVbody

Loaded

Tags(3)

Marketing & analytics tags observed sending data while the page loaded.

Google Analytics 4GA4 Event · G-Y7LEJTZYDQ

1 hit

Meta PixelPixel

4 hits

GA4 / ServerGA4 Event · G-Y7LEJTZYDQ

1 hit

Triggers(5)

Every dataLayer push observed during page load — with full payload and configuration analysis.

›GTM lifecycle events (3)— gtm.js, gtm.dom, gtm.load, etc.

Variables(5)

Data points present in the dataLayer that your tags can read (the values pushed alongside each event).

gtm.starteventgtm.uniqueEventIdcmdtarget

Network hits(9)

The actual tracking requests your browser sent — the ground-truth proof that a tag fired.

200gtm.jshttps://www.googletagmanager.com/gtm.js?id=GTM-58786CDV

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=G-Y7LEJTZYDQ

200gtag.jshttps://www.googletagmanager.com/gtag/js?id=G-Y7LEJTZYDQ&cx=c&gtm=4e69e1

beaconga4-collecthttps://analytics.google.com/g/collect?v=2&tid=G-Y7LEJTZYDQ&gtm=45je69e1v9248879722z89233066115za20gzb9233066115zd9233066115&_p=1789555585699&_gaz=1&gcd=13l3l3l

200pixelhttps://connect.facebook.net/en_US/fbevents.js

200ga4-collecthttps://www.googletagmanager.com/a?v=3&t=l&pid=1361100860&rv=69e1&tag_exp=115616986~115938466~115938468~118897920~118897930~120213116~120385422~120412528~120469

200pixelhttps://connect.facebook.net/signals/config/866088869422882?v=2.9.401&r=stable&domain=www.dikshitech.com&hme=2506fb1e365be93f3ccf36e3d92699c622e55613e451d1a2c96

200pixelhttps://www.facebook.com/tr/?id=866088869422882&ev=PageView&dl=https%3A%2F%2Fwww.dikshitech.com%2F&rl=&if=false&ts=1789555589931&iw=false&sw=800&sh=600&v=2.9.40

200pixelhttps://www.facebook.com/tr/?id=866088869422882&ev=PageView&dl=https%3A%2F%2Fwww.dikshitech.com%2F&rl=&if=false&ts=1789555589957&iw=false&sw=800&sh=600&v=2.9.40

Checks

GTM container detectedPass

GTM-58786CDV

A Google Tag Manager container is installed on this page.

Container script loads (gtm.js)Pass

1/1 container(s) returned a successful gtm.js response.

The container's JavaScript downloaded successfully, so GTM can run.

Noscript fallback presentWarning

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 issue

Snippet placement in <head>Warning

GTM snippet was not found high in <head>.

The container loads later than recommended. Tags may fire late and miss early page activity.

Fix this issue

dataLayer initialised before GTMPass

dataLayer is defined before the container snippet.

Data is available to tags from the very first event.

GA4 firingPass

G-Y7LEJTZYDQ — collect hit observed.

Google Analytics 4 is actively sending pageview/event data.

JavaScript errors during loadInfo

16 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.

Google Consent Mode v2Info

No consent API calls observed

No Google Consent Mode was detected. This mainly matters if you run Google Ads with EEA/UK traffic — no Google Ads pixel was seen on this site, so it's lower priority for now.

Tag load performanceWarning

GTM 4317ms, GA4 first hit 4536ms, DOMContentLoaded 1828ms

Google Tag Manager took 4.3s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.

Fix this issue

Cross-domain trackingInfo

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.

Enhanced Conversions (Google Ads)Info

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.

User-ID tracking (GA4)Info

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.

JavaScript errors (16)

Refused to load the script 'https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-5606724582126955' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://cdn.dikshitech.com https://www.googletagmanager.com https://conne

Refused to load the script 'https://apis.google.com/js/platform.js?onload=renderOptIn' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://cdn.dikshitech.com https://www.googletagmanager.com https://connect.facebook.net https://analytics.ah

Refused to connect to 'https://stats.g.doubleclick.net/g/collect?v=2&tid=G-Y7LEJTZYDQ&cid=777675713.1789555589&gtm=45je69e1v9248879722z89233066115za20gzb9233066115zd9233066115&rcb=16&aip=1&dma=0&gcd=13l3l3l3l1l1&npa=0&frm=0&tag_exp=115616986~115938466~115938468~118897920~118897930~120213116~12038542

Refused to connect to 'https://www.merchant-center-analytics.goog/mc/collect?v=2&tid=MC-S1KF0N663Z&gtm=45je69e1v9248879722z89233066115za20gzb9233066115zd9233066115&_p=1789555585699&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=Ag&are=1&cid=777675713.1789555589&frm=0&pscdl=noapi&rcb=16&sr=800x600&uaa=&uab=&uafvl=

Refused to connect to 'https://www.merchant-center-analytics.goog/mc/collect?v=2&tid=MC-S1KF0N663Z&gtm=45je69e1v9248879722za20gzb9233066115zd9233066115&_p=1789555585699&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=AAgAAAQ&are=1&cid=777675713.1789555589&frm=0&pscdl=noapi&rcb=16&sr=800x600&uaa=&uab=&uafvl=&uam=&u

Refused to connect to 'https://mpc2-prod-28-is5qnl632q-ue.a.run.app/events?cee=no' because it violates the following Content Security Policy directive: "connect-src 'self' https://www.dikshitech.com https://dikshitech.com https://www.googletagmanager.com https://www.google-analytics.com https://regi

Refused to connect to 'https://mpc2-prod-28-is5qnl632q-ue.a.run.app/events?cee=no' because it violates the document's Content Security Policy.

Refused to load the script 'https://capi-automation.s3.us-east-2.amazonaws.com/public/client_js/capiParamBuilder/clientParamBuilder.bundle.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' https://cdn.dikshitech.com https://www.googletagmanag

Refused to connect to 'https://5z-2b6b7616f94640c2840d1841e1ac24c3.ecs.us-east-1.on.aws/events?cee=no' because it violates the following Content Security Policy directive: "connect-src 'self' https://www.dikshitech.com https://dikshitech.com https://www.googletagmanager.com https://www.google-analyt

Refused to connect to 'https://5z-2b6b7616f94640c2840d1841e1ac24c3.ecs.us-east-1.on.aws/events?cee=no' because it violates the document's Content Security Policy.

Report ID: 05bcb6332d

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.

Fix this issue Try PayHelm free

Ask a follow-up question