Download websites that use Draftpress HFCM

About Draftpress HFCM

Draftpress HFCM exists so that somebody who is not a developer can put a snippet of code into a WordPress site without opening a theme file. Header and footer injection sounds trivial as a feature, and as software it is. As a signal about the site that installed it, the plugin is one of the more revealing things in a technology profile.

Installing a code manager implies a specific working arrangement. Somebody in marketing has scripts to add, tracking pixels, a chat widget, a verification tag, a conversion snippet, and no developer on hand to add them. Theme files are off limits, either because the theme is a purchased one that updates or because nobody wants to be the person who broke the site. Filed here under WordPress plugins, the plugin is the low end substitute for a full tag manager, which means its population is largely the set of sites where a real tag management deployment never happened.

For anyone selling a product that installs as a script, the implication is direct. A site running the plugin can adopt a new tag without a development ticket, a release cycle or an agency invoice, and the person who would paste it in is the same person who would decide to buy. Sites like that convert differently from sites where the same script needs an engineer. A security reader draws the opposite conclusion from the same fact, because an arbitrary code injection point administered by the least technical member of the team is exactly where a compromised login causes serious damage.

Draftpress has shipped the plugin since 2015 under the GPL v2 licence WordPress requires, written in PHP like the platform itself. As of October 2026 we detect it on 73,289 sites, with 31,560 of those assigned to United States and the domain mix leaning towards .com, a distribution that follows the plugin directory rather than any sales effort.

Detection deserves its own caveat. We identify the plugin from the wrapper markup it leaves around inserted snippets, so a site that strips comments during minification, or serves pages through a cache that removes them, drops out of the count. The recorded population is a floor. We can also see that the mechanism is present without knowing what was pasted into it, since an inserted script is indistinguishable from one placed by any other route.

The list is therefore most useful as a qualification layer rather than as an end in itself. Filtered by country, by the other tags already present and by whether a real tag manager runs alongside, it produces a set of sites that add third party code by hand and can do it again tomorrow. Checking one domain tells you that one site has the plugin installed. The population tells you how large the segment of self serve script adopters actually is, which is the number a growth team or a script based product needs before committing to a channel.