blog posts

WordPress Sites Block Google Floc By Default

According to MSPoweruser, WordPress opposes Google’s FLoC system in a statement. Its grouping of people based on their search habits is likely to lead to greater use of their data and discrimination against them. Google’s new system also predominantly targets simple customers and shares user data without their knowledge.

WordPress says that without the institute’s action, most WordPress-based non-technical websites will unknowingly join Google’s FLoC System and help this giant Mountain View online profile user.

Therefore, WordPress has decided to add the following code to its source code and announce that it will not participate in Google’s large FLoC project:

function disable_floc ($ headers) { $ headers ['Permissions-Policy'] = 'interest-cohort = ()'; return $ headers; } add_filter ('wp_headers', 'disable_floc');

WordPress states that webmasters who understand its nature can remove the above code from their site and contribute to the FLoC system if they wish.

It has also been suggested that future versions of WordPress may offer an option to enable or disable the FLoC feature, making it easier for web admins to manage.

WordPress is also considering adding FloC-disabled code to earlier versions of its content management System to expand the scope of new change coverage.

Recently, we have seen strong opposition from many browsers to Google’s FLoC System.

The main concern is that Google will use its unwarranted Web dominance to pressure website owners to participate in FLoC. If it becomes ubiquitous, WordPress probably won’t be able to block web admins effectively.

In such a situation, direct action by regulators would be the only solution. Fifteen attorneys general in the United States are reportedly seeking action.

Google is trying to replace the AI-based FLoC with more targeted cookies. Using machine learning, FLoC monitors search history and other data and segments users into groups based on their behavior.
These groups will include thousands of people with common interests.

Then, Google’s partner advertising companies can target their ads to specific user groups to improve effectiveness.

For Admins Who Want FLoC

Websites that opt into FLoC likely have the technical expertise to bypass any proposed Core filter. However, when weighing stakeholder interests, the needs of unaware website administrators and their visitors’ privacy take clear priority.

Additionally, we could implement a simple toggle for WordPress versions with privacy settings to allow sites to opt in. This would require minimal additional code—just a few lines and a couple of new strings.

Why Treat This Like a Security Concern?

The proposal is to:

• Include the patch in the next minor release instead of waiting for a major one.
• Backport the previous WordPress versions.

Why Not Wait for the Next Major Release?

Stay tuned—a ticket for future releases is on the way!

While it’s unusual to handle a new “feature” this way, there’s precedent: past updates (like a non-critical comments fix) were backported to benefit.

WordPress 5.8 is only slated for July 2021, but FLoC may roll out this month. Since many WordPress sites only update to minor versions, back-porting protection maximizes the impact for both sites and visitors.

Join the Discussion!

Your input matters! Whether you:
✅ Support the approach,
❌ Disagree strongly, or
💡 Want to refine the implementation?

Share your thoughts below!

While discussions happen elsewhere (like Twitter), not all feedback reaches Core developers. By commenting here, you ensure your voice is heard in dev meetings and when the ticket is drafted (consensus starts here!).

Key Improvements:

• More apparent structure with headings and bullet points.
• More concise phrasing while keeping the original meaning.
• Stronger call-to-action for engagement.
• Polished tone—professional yet approachable.

FAQ