For years, small websites added Facebook's Like button and Comments box to blog posts and product pages. Meta has now retired both. In a post on its developer blog on November 10, 2025, Meta announced that the Like button and Comments plugin for external websites would be discontinued on February 10, 2026. If your site still carries that code, here is what happened to it and how to tidy up.
What Meta Changed
- Which plugins: the Facebook Like button, which let people like content on outside websites, and the Comments plugin, which let people comment on outside websites using Facebook.
- When: discontinued on February 10, 2026.
- What happens to existing code: Meta said the plugins would gracefully degrade, rendering as an invisible 0x0 pixel element instead of producing errors.
- Action required: Meta described it as not a breaking change and said removing the plugin code is optional.
- Replacement: none was announced.
The change concerns the plugins on external websites. Liking and commenting on posts inside Facebook itself carries on as before.
Why It Is Still Worth Cleaning Up
An invisible plugin will not break your site, but it can still cause problems:
- Empty spaces and orphaned headings, such as a "Comments" title with nothing under it.
- Lost conversations. Comments people left through the plugin lived on Facebook, so they no longer appear on your pages.
- Unneeded scripts. Facebook's code may still load on every page, adding weight and connecting to Facebook's servers, which may need to be covered in your privacy and cookie notices.
- Missing social proof. Like counts that used to reassure visitors are gone, so the page may look emptier than before.
How to Clean Up
- Find every place the plugins were used. Check theme settings, page builder blocks and social media plugins, and search your templates for Facebook plugin code.
- Remove the blocks and any headings or wrappers around them, so no gaps are left behind.
- Check whether anything else needs Facebook's script. If no other Facebook feature on your site uses it, remove the script, then update your privacy and cookie notices to match.
- Clear your site's cache and check the affected pages on a phone and a computer.
What to Use Instead
- Simple share links, or buttons that link to your social profiles, without loading third-party scripts.
- Your website platform's own comments, if conversation on posts really matters to you, with moderation switched on.
- A clear invitation to reply by email or message, which often brings more thoughtful responses than public comments.
- Reviews and testimonials on product and service pages, which do more for trust than a like count ever did.
If comments were an important part of your site, for example on recipe posts or a community blog, think about what those conversations did for you. Readers asked questions, shared tips and showed new visitors that real people use your content. You can bring some of that back by adding a short "Questions readers asked" section to popular posts, updated from the emails and messages you receive. It keeps the useful parts of the conversation without the moderation work of an open comment box.
A Reminder About Third-Party Widgets
This is one more example of a feature that lived on your website but was controlled by another company. Keep a list of embedded widgets, such as social buttons, feeds, chat boxes and review badges, and check each one once or twice a year to make sure it still works and still earns its place on the page. Every widget you remove is one less script to load, one less thing to explain in your privacy notice and one less surprise when a provider changes its plans.
Next Step
Open your most visited blog post and your best-selling product page, look for empty spaces where Facebook buttons or comments used to be, and remove them. Then decide whether you need comments at all, and if you do, switch on your platform's own comments or invite email replies instead.