- Home
- Skills
- Marketing & SEO
- Site Tag and Verification Check: GA4 and Search Console
Works with the AI Agents you already use
Site Tag and Verification Check: GA4 and Search Console
Setup steps for a GA4 tag and Search Console verification, plus offline checks of the pages, verification evidence, sitemap and robots.txt you saved.
$5
Site Tag and Verification Check: GA4 and Search Console
Example session with this skill installed
Here are saved copies of my home page and two other pages. Is the GA4 tag on every one, and in the head? Then check my sitemap.xml and robots.txt before I submit the sitemap.
- Read your context and instructions
- Compiled the site tag
Summary
Both saved pages carry the GA4 tag for G-EXAMPLE123, the DNS TXT answer holds the verification token, and the sitemap and robots.txt pass. (Example site from the ZIP; ID, site and token are made up.)
$ python3 scripts/tag_check.py site/index.html site/about.html --expect-id G-EXAMPLE123
OK page #1 index.html: Google tag found: gtag.js and config for G-EXAMPLE123 (F4)
OK page #2 about.html: Google tag found: gtag.js and config for G-EXAMPLE123 (F4)
SETUP-CHECK ok=2 fix=0 warn=0 unknown=0 result=ok
$ python3 scripts/verification_check.py --property-type url-prefix --home site/index.html --dns-txt site/dns-txt.txt
INFO --home: token present (meta tag in the head, token length 43)
INFO --dns-txt: token present (1 record(s), token length 43)
OK url-prefix property: token present
SETUP-CHECK ok=1 fix=0 warn=0 unknown=0 result=ok
$ python3 scripts/sitemap_check.py site/sitemap.xml --sitemap-url "https://www.example.com/sitemap.xml" --robots site/robots.txt
OK sitemap: 2 <url> entries, 317 bytes (F7)
OK sitemap: 2 of 2 entries have one absolute <loc> on the same protocol and host; every <lastmod> is in W3C Datetime form (F7)
OK robots.txt: 1 Sitemap: line(s), all full URLs; no 'Disallow: /' or '/*' for all crawlers or Googlebot
SETUP-CHECK ok=3 fix=0 warn=0 unknown=0 result=ok
| Check | Result |
|---|---|
| GA4 tag on saved pages | 2 of 2 OK |
| Verification token | present (length only shown) |
| Sitemap + robots.txt | 3 of 3 OK |
Next steps
- Open the Realtime report in your own GA4 account to see whether data arrives; the scripts read saved files only.
- Look up in Search Console whether verification went through, then submit the sitemap there.
Connects securely to your tools. The creator never sees your data.
About this skill
Use when you add a GA4 tag to your pages and register them in Search Console yourself, and want offline checks of saved copies of your files, no network calls and no login, before and after. The skill gives the steps as text and quotes its sources.
It finds the gtag.js script and its config call in saved HTML pages (HTML comments, noscript and body text do not count; a config call inside a JavaScript comment still does), and warns when the tag sits outside the head (F4) or an ID is configured twice (source: heuristic).
It reports token present or token missing in the verification meta tag, the HTML verification file and a saved DNS TXT answer; no output line shows a token read from a file, or the name of the HTML verification file.
It checks a saved sitemap or sitemap index against the sitemaps protocol (size, entry count, UTF-8, absolute URLs on the same host, lastmod form), and robots.txt: its Sitemap line, and Disallow: / under User-agent * or Googlebot (source: heuristic).
Do not use when you need AdSense readiness, a tool page built, consent banners, Consent Mode, Tag Manager containers or GA4 reports.
Requires: Python 3.9+ (standard library only). You save the pages, the DNS answer, the sitemap and robots.txt yourself; the scripts read only those files and write nothing; they call no Google service, fetch no URL and resolve no name.
Independent tool. Not affiliated with or endorsed by Google. Also not affiliated with or endorsed by Anthropic, OpenAI, Anysphere (Cursor) or the sitemaps.org authors; product names are used only to describe what the skill is for and its compatibility.
The scripts see only the saved files: not tags added by JavaScript at run time, not tags inside a Google Tag Manager container, and not what a browser is served. "Token present" means the token is in the file; whether verification went through, and whether data arrives, is for you to look up in Search Console and in the Realtime report of your GA4 account (source: heuristic: where to look). No claim that a site gets indexed or ranks, and setup is never done automatically or through an API.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Requires