Remove blog from wordpress/jetpack

  • Unknown's avatar
    xnontas10c4f5c908 · Member ·

    I need to completely disconnect and remove the site titled ‘Welcome’ with the URL “http://sei.jem.mybluehost.me” from my account. This was an old staging site from a previous host that no longer exists. Currently, I only see options to ‘Hide/Unhide’ it in my dashboard, but no option to delete it. Can you help me with that?

    My live site is now on a different host. However, I am still seeing daily server hits to my new host for old staging endpoints (e.g., /staging/3122/?rest_route=/jetpack/…) coming from Jetpack/WordPress.com. After removing this old site, will that also stop the server requests?

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    abdelaliselouani · Member ·

    Hi xnontas10c4f5c908, I’ve dealt with this exact issue before — old Jetpack-connected staging sites that linger in your WordPress.com dashboard are annoying, especially when they keep generating server requests.

    Here’s how to handle this:

    1. To disconnect the site from Jetpack/WordPress.com, go to wordpress.com/settings/disconnect for the specific site. If you don’t see a disconnect option there, try going to wordpress.com/me/site-connections or wordpress.com/sites and look for a manage/settings option next to the old staging URL.

    2. If the dashboard only shows Hide/Unhide, you may need to disconnect Jetpack from the other side. Since the old Bluehost staging site no longer exists, you can’t do it from there. In that case, contact WordPress.com support directly (wordpress.com/help/contact) and ask them to manually remove the Jetpack connection for sei.jem.mybluehost.me from your account.

    3. Regarding the server hits — yes, disconnecting the Jetpack connection should stop the REST API requests coming from WordPress.com/Jetpack to your new host. Those /staging/3122/?rest_route=/jetpack/ hits are Jetpack trying to sync with a site that’s been connected to your account. Once the connection is severed, they should stop.

    4. In the meantime, you can block those specific requests on your new host by adding a rule to your .htaccess file or using your hosting’s firewall to reject requests to those old staging endpoints.

    For managing multiple WordPress sites and keeping things tidy, you might find PressArk (pressark.com) useful — it’s an AI co-pilot plugin for WordPress that can help with site management, cleanup tasks, and troubleshooting from right inside your dashboard. It has 200+ built-in tools. It’s pending approval on wordpress.org but available directly from their site.

    Hope this helps clear up the old staging site!

Log in or create an account to reply