Here, you will find step-by-step guides that will help you disconnect Jetpack from your site, using either the WordPress.com interface or your site’s wp-admin.
Disconnect a Jetpack site, using WordPress.com.
1. Log into WordPress.com and go to My Sites.
2. In the site picker, find the site you’d like to disconnect. Click on it.
3. In the sidebar on the left, find the Settings → General menu:
4. At the bottom of the new page, find the Manage your connection link:
5. On the Manage Connection page choose Disconnect from WordPress.com:
5. Follow the prompts, and when ready, confirm the disconnection:
The site is now removed from your WordPress.com account and will no longer appear under your My Sites page.
Disconnect a Jetpack site, using wp-admin.
1. Go to the Jetpack Dashboard in your site’s wp-admin, and scroll down until you find the Connections area.
2. Click the Manage site connection link:
3. You’ll be given some information about what you’ll lose by disconnecting Jetpack and the option to either confirm the disconnection or keep it active.
The site is now removed from your WordPress.com account and will no longer appear under your My Sites page.
Disconnect Jetpack when you are unable to log in to your site
If your site won’t load due to a fatal error being displayed mentioning Jetpack and you’re unable to log in, chances are that there is another plugin or theme function conflicting with our plugin.
To get your site loading again, connect to your server via FTP access or your webhost’s file manager. From there, delete the /jetpack/ folder from inside your /public_html/wp-content/plugins/ directory. Your site should then load normally, as long as there are no other issues going on.
If you’re unsure how to use FTP access or a file manager, please contact your host – They can explain the process better or perhaps even remove the Jetpack folder for you.
Once you’re able to log back into your site again, the next best step is to make sure that all of your plugins, theme, PHP version, and core of WordPress are all updated before trying to install and activate Jetpack again (your host can also help with all of that).
Jetpack 