dikshitech.com Tracking & SEO Audit — Grade B
A saved report based on tracking and pages observed during this scan.
Your website's tracking setup shows some areas working well, but there are a few issues to address. Google Tag Manager (GTM) is properly installed and active, and Google Analytics 4 (GA4) is successfully recording data. However, there are warnings due to the GTM snippet not being placed high enough in the HTML and the absence of a <noscript> fallback, which could affect data accuracy for users with JavaScript disabled. Additionally, the page load performance for GTM and GA4 is slower than ideal, which might impact tracking efficiency. Meta Pixel is firing correctly, but there are several console errors related to content security policies that need attention to ensure all scripts load as intended. Since your site is not on Shopify, there's no need to worry about Trekkie or Web Pixels API. Next, it would be beneficial to audit other pages like product, cart, checkout, and order-confirmation to ensure comprehensive tracking across your site. Given the current issues, I recommend connecting your store to PayHelm AI for a more detailed analysis and assistance in optimizing your tracking setup.
GTM container installed and loading.
GA4 is installed and sending data.
Not an ecommerce store — scored on basic analytics coverage.
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. 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.
Google Tag Manager took 3.3s to load. Slow tag loading delays tracking and can hurt page performance — consider reducing the number of tags or loading them later.
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 basics are mostly in place with a few opportunities to improve.
Title is 54 characters — within the ideal 30–70 character range.
Dikshi Technologies | Software & App Development India (54 chars)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)One H1 heading found — the recommended structure for every page.
Dikshi TechnologiesNo noindex directive — the page is eligible to be indexed.
robots: index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1No canonical tag found. Adding one prevents duplicate-content issues when a page is accessible via multiple URLs.
No canonical link tag found.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 presentThe basics for AI access are in place, but there's no llms.txt yet — an easy, high-leverage addition.
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).No skill.md file found. This is an emerging convention for describing agent-callable capabilities/tools to AI agents — optional today, but worth watching as adoption grows.
No /skill.md or /.well-known/skill.md found.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 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.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.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.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.There were no outbound links in llms.txt or skill.md to check for hallucinated endpoints or domains.
Skipped — no llms.txt or skill.md found.- 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.
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.
GTM-58786CDV
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.
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 issuedataLayer is defined before the container snippet.
Data is available to tags from the very first event.
G-Y7LEJTZYDQ — collect hit observed.
Google Analytics 4 is actively sending pageview/event data.
28 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. 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.
GTM 3316ms, GA4 first hit 3648ms, DOMContentLoaded 1587ms
Google Tag Manager took 3.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 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.
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.
Refused to load the script 'https://www.clarity.ms/tag/yoaqoop4lz?ref=gtm' 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.ahrefs.com". N
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=75277934.1791528853>m=45je6a72h1v9248879722za20ozb9233066115zd9233066115xf1&rcb=16&aip=1&dma=0&gcd=13l3l3l3l1l1&npa=0&frm=0&tag_exp=115938465~115938468~118897920~118897930~120213116~120385423~120469145~120469
Refused to connect to 'https://www.merchant-center-analytics.goog/mc/collect?v=2&tid=MC-S1KF0N663Z>m=45je6a72h1v9248879722za20ozb9233066115zd9233066115xf1&_p=1791528849899&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=Ag&are=1&cid=75277934.1791528853&frm=0&pscdl=noapi&rcb=16&sr=800x600&uaa=&uab=&uafvl=&uam=&ua
Refused to connect to 'https://www.merchant-center-analytics.goog/mc/collect?v=2&tid=MC-S1KF0N663Z>m=45je6a72h1v9248879722za20ozb9233066115zd9233066115xf1&_p=1791528849899&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=Ag&are=1&cid=75277934.1791528853&frm=0&pscdl=noapi&rcb=16&sr=800x600&uaa=&uab=&uafvl=&uam=&ua
Refused to connect to 'https://www.merchant-center-analytics.goog/mc/collect?v=2&tid=MC-S1KF0N663Z>m=45je6a72h1v9248879722za20gzb9233066115zd9233066115xf1&_p=1791528849899&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=AAgAAAQ&are=1&cid=75277934.1791528853&frm=0&pscdl=noapi&rcb=16&sr=800x600&uaa=&uab=&uafvl=&ua
Refused to connect to 'https://www.merchant-center-analytics.goog/mc/collect?v=2&tid=MC-S1KF0N663Z>m=45je6a72h1v9248879722za20gzb9233066115zd9233066115xf1&_p=1791528849899&gcd=13l3l3l3l1l1&npa=0&dma=0&_eu=AAgAAAQ&are=1&cid=75277934.1791528853&frm=0&pscdl=noapi&rcb=16&sr=800x600&uaa=&uab=&uafvl=&ua
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 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 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 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 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.
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.
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.
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.
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.
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.