How do I remove the "Made with" badge from my website?

The supported way off, on the builders we checked

There is no general answer, because the badge is part of each platform's pricing rather than a web standard. We read the vendors' own documentation on 14 September 2026, and the three we checked show the three shapes you will meet:

• Framer. Its help centre says the "Made in Framer" badge disappears once you connect a custom domain or move the site to a paid subscription, and that you have to republish the site afterwards for it to go.
• Lovable. Its documentation says the "Edit with Lovable" badge can be hidden on paid plans, with a Hide Lovable badge setting under the project's publishing settings. The switch is per project and takes effect on the live site without a republish, and after a downgrade the badge returns at your next publish.
• AgentCeres. Pages we host carry a small "Made with AgentCeres" link, and today there is no setting that removes it on any plan. We would rather say so here than have you find out after building.

Other builders follow one of those patterns: a paid-plan switch, a custom domain, or no way off at all. Look it up on the platform's own help pages rather than in a guide, because this is exactly the kind of detail that moves with a pricing change, and third-party write-ups are the first thing to fall out of date.

Why the CSS trick is a poor trade

Most guides to this question end in the same rule: find the badge's id and set it to display none. It can work for a while. It is also a disagreement with code you do not control, running on infrastructure you do not own, and the platform gets the next move. A badge added when the page is served can be added again on the next request, locked in place with styles no page rule can override, or caught when you publish.

On a free plan the badge is usually the part of the deal you are paying with, so the honest options are to keep it, pay for the version without it, or host the site somewhere else. A rule that hides it is none of those, and it tends to outlive the reason it was written: upgrade later or move hosts, and it stays in your stylesheet doing nothing anyone remembers.

What we learned putting a badge on customer sites

AgentCeres — the AI Growth Officer at agentceres.com — hosts the websites its agents build for customers, and those pages carry our badge. So we have seen this question from the platform's side, and the first thing it taught us is that the request is often not about branding.

In September 2026 a customer asked their agent to hide the badge, and the agent did it with a CSS rule. When we looked into why, the badge was floating in the bottom-right corner above everything else on the page, and that customer's page had its own bar fixed to the bottom of the screen. It was not an isolated layout: 31 of the 101 live pages we hosted had controls pinned to the bottom of the screen, including 19 floating elements in that same corner, 5 of them WhatsApp contact buttons, and 11 full-width bottom bars. On a phone, our badge could sit on top of the thing a visitor was meant to press.

The fix was ours to make. The badge still floats on a wide screen, but on a phone it now sits at the very end of the page, below the content, with room left above it for a page's own bottom bar. Pages that try to hide it are now refused when they are published, with a message telling the agent to say plainly that it cannot be removed today. A rule on one page would never have fixed the other thirty, which is the case for reporting a placement problem instead of hiding it.

Before you pay to remove it

1. Look at it on a phone. Open the published page on a real handset, scroll to the end, and press every button you pinned to the bottom of the screen. If the badge covers one, send the platform a screenshot. It is a placement bug, and it almost certainly affects other sites they host.
2. Decide whether it costs you anything. On a personal project, a portfolio or a first test page, a small builder link is ordinary. On a business page asking strangers to trust you with an enquiry, a vendor's name can make the page read as unfinished. That is a judgement about your buyers, not a rule.
3. Price the real alternative. If a paid plan or a custom domain removes it, that is usually cheaper than rebuilding somewhere else, and a custom domain is worth having for its own sake. If the platform has no way off, moving the site is the only honest route.

If the page is new, the bigger question is usually whether anyone sees it at all: how do I get traffic to a website I built with AI covers that, and should I use AI to build my website covers what to check before you publish.