Some problems on your site can be caused by a conflict between Jetpack and other plugins or a theme. Get to the root of the problem by running a conflict test.
A conflict test involves testing with a default WordPress theme (for example, Twenty Twenty Two) and only Jetpack plugins installed. This allows you to isolate issues so that you can understand their cause.
Important: Before deactivating any plugins or changing your theme, we recommend backing up your site first. If you don’t already have a way to back up your site, you can try Jetpack VaultPress Backup.
Use the Health Check & Troubleshooting plugin to identify conflicts
If you don’t want to temporarily deactivate plugins or switch themes on your live site, then you can use the Health Check & Troubleshooting plugin.
The Health Check plugin includes a troubleshooting mode, so you can deactivate plugins and switch themes in a local browser session and view the changed version of the site without actually affecting what your visitors see. While this won’t fix issues, it can help identify them without disrupting your visitors’ experience.
Install the plugin
Follow these steps to install the Health Check plugin:
- Visit your WP Admin dashboard.
- Go to: Plugins > Add New.
- Search for Health Check & Troubleshooting.
- Select Install Now, and then Activate.
Enable troubleshooting mode
In WP Admin, go to Tools > Site Health > Troubleshooting and then click the button that says Enable Troubleshooting Mode.
At this point, you’ll be redirected to your WP Admin dashboard, which should now have a Troubleshooting Mode section at the top.
Check for plugin conflicts
- Expand the Available plugins section. All plugins start as “deactivated.”
- Check your site to see if the issue is still occurring. If the issue is resolved, then this confirms the issue is being caused by a plugin, and you’ll need to determine which plugin(s) are responsible for the issue.
- Activate one of the plugins. You can start from the top of the list, or with the plugins you most suspect. Then, test to see if the issue on your site still exists.
- Activate the next plugin, and then check again to see if the issue returns. Eventually, this will tell you which plugin is causing the problem because the issue will return when you reactivate a particular plugin. At that point, you would need to reach out to the developer of the plugin causing the issue for assistance.
If the issue doesn’t go away with all plugins deactivated and persists with just Jetpack activated, then try to deactivate then reactivate the Jetpack features on the Modules page to narrow down the issue. If that doesn’t help, then proceed to the steps below to see if your theme is responsible.
Check for theme conflicts
- At the top of the page, click on the toggle arrow beside Available themes.
- Activate a default WordPress theme, like Twenty Twenty Two.
- Check to see if the issue still occurs. If it doesn’t, then your theme is causing the issue. You can either change your theme, or contact the author of the theme and ask them for assistance.
Exit troubleshooting mode
When you’re done testing for plugin and theme conflicts, you can exit troubleshooting mode by clicking Disable Troubleshooting Mode on your site’s dashboard or admin bar.
Troubleshoot manually
If you’re working on a staging site, or your site doesn’t get very much traffic, then you can troubleshoot manually by running tests directly on the live site. This approach does not require the Health Check and Troubleshooting plugin.
Deactivate and reactivate plugins
- Go to Plugins → Installed Plugins and temporarily deactivate all plugins.
- Check if the issue still exists. If the problem is no longer present, then this confirms the issue is being caused by a plugin. Proceed to step 3.
- Reactivate each plugin one by one, checking for the issue again after each plugin is reactivated.
- When the issue occurs again, you will know it’s due to the most recent plugin you reactivated.
- Contact the developers of that plugin for next steps.
If after Step 2, the issue persists with just Jetpack activated, then try to deactivate and reactivate the Jetpack features on the Modules page to narrow down the issue. If that doesn’t help, then proceed to the steps below to see if your theme is responsible.
Switch themes
- Go to Appearance → Themes.
- Switch to a default WordPress theme, like Twenty Twenty Two.
- If the issue is resolved, then the problem is being caused by your theme.
- You can change your theme, or contact the author of your theme and ask them to help with the issue.
Need more help?
If you’ve followed these steps and determined that Jetpack is causing a problem on your site, please contact us for further support.
Jetpack 