WP Manifestindependent plugin directory
manifest / developer / wordpress-at-head-tag

At Head Tag WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

Add trusted HTML, CSS, JavaScript, meta and link snippets to the WordPress <head>.

★ 0stars
19release downloads
≈10active sites
v1.4.2latest · 1mo ago

Install

Download at-head-tag.zip From the v1.4.2 release on GitHub, Sep 21, 2026

Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/cemfirat/wordpress-at-head-tag/releases/download/v1.4.2/at-head-tag.zip
Updates itself. It ships its own updater, so new versions appear under Dashboard → Updates.

A small WordPress plugin for adding trusted HTML, CSS, JavaScript, meta and link snippets to the front-end <head>.

Author: Cem Firat
License: GPL-2.0-or-later
Requirements: WordPress 5.8+ and PHP 7.4+.

What it does

At Head Tag stores one trusted source snippet and prints it inside clear source markers in wp_head:

<!-- at-head-tag START -->
<meta name="example" content="value">
<script defer src="https://example.com/app.js"></script>
<!-- at-head-tag END -->

The settings screen provides a WordPress code editor, an enable/disable switch, configurable hook priority, escaped output preview, non-blocking lint feedback for common head-code mistakes, and a real front-end output check.

Security model

Raw head code is powerful. Editing therefore requires both manage_options and WordPress's unfiltered_html capability. On Multisite this normally means a Super Admin. Unauthorized submissions retain the previously saved snippet instead of silently rewriting it.

The plugin stores trusted source as entered, apart from invalid text encoding/NUL handling. The preview is escaped and never executes the saved snippet.

Lint checks

The plugin can warn about:

  • elements that normally do not belong in <head>
  • multiple meta charset or title elements
  • HTTP resources on HTTPS-oriented sites
  • preload links without an as attribute
  • external scripts without async or defer
  • parser problems when PHP DOM is available

These are warnings, not an HTML policy engine. They do not replace browser or application testing.

Install

  1. Download at-head-tag.zip from the latest release.
  2. In WordPress open Plugins → Add New → Upload Plugin and upload the ZIP.
  3. Activate At Head Tag.
  4. Open Settings → At Head Tag.
  5. Add trusted head code and save.

Existing installations of the earlier single-file plugin should install the release ZIP once. After that, stable GitHub releases can be discovered through WordPress's native plugin update flow.

Updates and privacy

Stable updates are delivered from this public GitHub repository using WordPress's Update URI integration. Update checks contact api.github.com; package downloads use github.com. Saved head code is never sent to GitHub.

The settings screen includes Check updates now, which uses WordPress's explicit update refresh and clears both the plugin release cache and WordPress plugin-update state before the new check. It also includes Check front-end output, which fetches the home page with a cache-busting query and confirms whether the saved snippet is actually present inside <head>.

Development

Run:

php tests/run.php
python3 scripts/package.py

GitHub Actions also runs syntax checks, WordPress 5.8/PHP 7.4 integration tests, latest WordPress/PHP 8.3 integration tests, real ZIP upgrades and real front-end output checks.

Copyright © 2026 Cem Firat. At Head Tag is licensed under GPL-2.0-or-later.

Releases

3 releases. Each count is every asset in that release; expand a row for the breakdown.

Tag
Published
Assets
Downloads
v1.4.2 latest
Sep 21, 2026 1mo ago
at-head-tag.zip
10
Sep 21, 2026 1mo ago
at-head-tag.zip
8
Sep 21, 2026 1mo ago
at-head-tag.zip
1

Active-site estimate ≈10 comes from the median of recent superseded releases. Method.

A grade

Security

At Head Tag 1.4.2 · audited by WP Registry

No security issues found.

Audited release
1.4.2
Findings
none
Worst severity
—
Content hash
e0b48cd19b6e3785ac5f57c6…

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.