WordPress, the popular web content management System, has announced that a new version will host code to disable Google’s FLoC System.
FLoC has become very controversial in recent times.
Various web activists have decided in a relatively coordinated move to express their direct opposition to Google’s new System for creating users’ online profiles. In this regard, another activist has recently joined the anti-Google front and made news.
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 more use of people’s data and discrimination among 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 says that webmasters who have enough information about 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 turn the FLoC feature on or off, making it easier for web admins to use.
VVersion 5.8 of thisCMSm applies a new version of WordPress applies a new version of WordPress, the release of which is scheduled for July 2021.
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 the serious opposition of 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 said to be seeking action.
Google is trying to replace artificial intelligence-based FLoC, which is based on artificial intelligence, with more targeted cookies. Using machine learning technology, FLoC monitors search history and other information and puts users into different 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 a specific group of users to increase the effectiveness of the ad.
For Admins Who Want FLoC
Websites opting into FLoC likely have the technical expertise to bypass any proposed filter in Core. 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-portingder 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.