Tag Scout -- WordPress 插件

Tag Scout

开发者	zemraplugins
更新时间	2025年12月15日 05:33
PHP版本:	7.4 及以上
WordPress版本:	6.9
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0 1.0.1

详情介绍:

Tracking scripts can hide in many places — plugins, themes, and custom code. Tag Scout shows you exactly where each tracking code originates. It scans any URL on your site and detects: Google Analytics 4 (GA4) Universal Analytics (legacy) Google Tag Manager (GTM) Meta Pixel Hotjar Microsoft Clarity Tag Scout searches your WordPress installation for matching fragments in:

wp_options (option values)
wp_posts (post content across all post types, including Code Snippets CPT)
wp_postmeta (meta values: page builders, ACF, etc.)
Legacy Code Snippets table ({prefix}snippets), if present
Key theme files: header.php, footer.php, functions.php in parent and child themes

Results are shown as clean cards with: Provider name (GA4, UA, GTM, etc.) ID (Measurement ID, UA property, GTM container, etc.) Snippet preview “Found in…” list (options, posts, postmeta, Code Snippets, theme files) Tag Scout is read-only. It never changes your database or files — it just helps you find where to fix things. Tag Scout does not connect to any third-party APIs or services. It only requests your own site’s URL using wp_remote_get() and scans that HTML for known tracking patterns.

安装:

Upload the tag-scout folder to /wp-content/plugins/ or install via Plugins → Add New.
Activate the plugin.
Go to Tools → Tag Scout.
Enter a URL from your site and click Scan URL.

屏幕截图:

$**Single tracking script view**\$
$**No tracking scripts detected**\$

升级注意事项:

1.0.1 Improved tracking source detection for Code Snippets and theme files. Recommended update. 1.0.0 Initial release.

常见问题:

Does Tag Scout change anything on my site?

No. It is completely read-only. It only reads database values and theme files to show matches.

Will it find tracking code inside themes and plugins?

If the code is stored in options, posts, postmeta, Code Snippets, or in header.php, footer.php, or functions.php of the active theme (child or parent), Tag Scout can report it as a possible source.

Why does it sometimes say “No matching locations were found”?

That means the script is visible in the front-end HTML, but the exact fragment wasn’t found in the places Tag Scout searches. It may be injected dynamically at runtime by a plugin or only load under certain conditions.

Does it detect disabled Code Snippets?

Yes. Disabled snippets still exist in the database, so they can show up as locations even if they’re not currently running.

更新日志:

1.0.1

Improved tracking source detection for Code Snippets, including clearer active/inactive status.
Restored theme file scanning for header.php, footer.php, and functions.php in parent/child themes.

1.0.0

Initial public release.