Quick tip: Disconnect Jetpack from the WordPress.com side

Before now, deleting Jetpack enabled sites from WordPress.com was pretty hard unless you were in the WordPress admin. Now you can finally do it from the WordPress.com side, which is nice when the site no longer exists.

About sixteen months ago, I wrote a post noting that it is really annoying to disconnect a WordPress.com account from a Jetpack install. More annoying yet, is that you could not get rid of nonexistent Jetpack enabled websites from the WordPress.com “My Sites” section at all without contacting support.

Over the years I collected quite a few Jetpack enabled websites connected to my WordPress.com username. Whether I was connecting a staging site or was too lazy to get a friend to setup their own account on WordPress.com, I ended up with a couple of dozen websites connected to my account that were not in my control.

The traditional way to disconnect Jetpack from WordPress.com was via the site admin in the Jetpack settings. But over time, many of the sites I managed have went stagnant or completely offline, and there was no way to disconnect them anymore. But finally, you can disconnect Jetpack from the WordPress.com side.

You can disconnect sites from the main “My Site” link (shown above) or the individual site (pictured below). Errored sites show up with a red warning side, and when you click the icon, the ability to permanently disconnect the site appears.


This has been a near daily annoyance of mine for years. I'm happy to see it finally get resolution. Special thanks to Automattician Jeremy Herve for never forgetting about me.

One more tip: if you go to your WordPress.com homepage often, and it doesn't open up the page you want to be default for stats, you can set your default site under your account settings. This is another annoyance of mine that I didn't know had a solution until just now.


I know creating really effective user interfaces and account management tools is really hard. But attention to small details is awesome. I'm glad the WordPress.com team took care of this one, even if it took a while.