Disable Topics API

This plugin does not exclude you (as a user of the web) from Topics API tracking. It excludes your website, and thus protects your website’s visitors. Many of them will probably use Chrome.

This plugin attempts to add an HTTP header. You can use your browser’s Dev Tools to check whether it gets added properly.

• Visit any page on your site using the browser of your choice.
• Press F12, or right-click anywhere on the page and click “Inspect element”.
• Switch to the network tab in the newly opened development tools pane.
• Turn on recording (if it’s not already active), and reload the page.
• You’ll see a number of requests appear as a list. The top one is usually the page itself.
• Click that line to open up its properties.
• Look for the header under “Response headers”.

I’ve also set up an online FLoC header checker. Simply enter your website’s homepage URL to see of the header is present.

HTTP headers can get added and/or removed on many levels in the server stack.

• By WordPress itself (which is what this plugin attempts).
• By the web server (NGINX, Apache, etc).
• By caching layers, proxies, etc.

Please note that there’s a known issue with many page caching plugins where the ‘hook’ that this plugin uses does not work. This is a fundamental issue in WordPress and not something that’s easy to work around. If the header does not get added by this plugin, your best option is to see if it can be added on one of the other levels. Or ask your system administrator to do this for you.

If you’re using WP Super Cache, make sure the ‘Cache HTTP headers with page content’ option is checked.

Please report security bugs found in the source code of the Disable Topics API plugin through the Patchstack Vulnerability Disclosure Program. The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin.”