WordPress plugin

Plugin troubleshooting

Fix the common plugin problems, from scans that stop and scheduled scans that never run to failed connects, missing Pro features and builder content.

4 min read

Most plugin problems come from the host, WP-Cron or the connection. By the end of this page you will know the likely cause of each problem and the fix.

Plan: these fixes apply to every plan. Problems with Pro features point to the connection or your Pro slots.

The scan stops or never finishes

The scan runs in short steps sized to your host's time limit. A step that fails on the network is retried three times.

If the scan still stops, check these causes:

  • You closed the tab. A manual scan needs the page open. Start a new scan and keep the tab open.
  • A firewall blocks the scan. Some security plugins and host firewalls block background requests from wp-admin. Allow them for administrators, or ask your host.
  • The host limit is very short. A PHP time limit under about 15 seconds leaves little room for each step. Ask your host to raise it.
  • The site is very large. Set Links per scan in the settings to scan part of the site at a time.

Update to the latest version of the plugin first. Scans on large sites got much more reliable in version 3.0.9.

Scheduled scans never run

  • The site has no Pro. Scheduled scans need a site with Pro. Check the plan badge under the plugin logo.
  • The schedule is set to Manual. Open the General tab and pick Daily, Weekly or Monthly.
  • WP-Cron does not fire. WP-Cron needs visitors, and some hosts turn it off. A server cron job that calls WordPress fixes both. Ask your host to set one up.
  • You use an old version. Scheduled scans were repaired in version 3.1.0. Version 3.1.3 fixed saving a schedule on sites with Pro.

The Watch WP-Cron card on the Uptime Monitor page alerts you when WP-Cron stops. Uptime in wp-admin shows how.

The report email never arrives

Only scheduled scans send the report, and only when they find broken links. The mail goes out through your own WordPress site. If other site mail also fails, set up an SMTP plugin. Scheduled scans has the details.

Connecting fails

The plugin shows the reason with a Try again link:

  • "The connect request expired before it was approved." Approve within 30 minutes of clicking Connect this site. Use the newest tab if you clicked the button twice.
  • "This site could not reach brokenlinkchecker.io. Your host may block outgoing requests." Ask your host to allow outgoing HTTPS requests from your server.
  • "brokenlinkchecker.io did not accept the connect code." Start again from Connect this site.
  • "The connection was approved for a different site address." Your WordPress address differs from the one you approved, for example www against no www. Check the address under Settings, then General, in wp-admin, and connect again.
  • "Could not complete the connection." Try again in a few minutes. If it keeps failing, contact us.

You pay, but the plugin shows Free

  • The site holds no Pro slot. Your earlier connected sites fill your slots first. The connection bar shows how many sites you use. Disconnect a site you no longer need, or move to a bigger plan.
  • The plan change has not arrived yet. The plugin checks your plan about every 12 hours. Click Refresh connection in the connection bar.

Pro slots and covered domains explains which sites hold your slots.

Pro turned off by itself

  • The site was disconnected on the website. Connect it again from the plugin's settings.
  • The plugin could not reach brokenlinkchecker.io for two weeks. It keeps your last plan for 14 days, then falls back to Free. Ask your host to allow outgoing HTTPS requests, then click Refresh connection.

These actions need the exact URL in the post's saved content. Links from page builders, shortcodes, sliders and comments live elsewhere, and images never get Unlink.

Open the page in the editor that built it and fix the link there. Find opens the page so you can spot the link.

  • The server blocks automated checks. Mark the link as Not broken. Every future scan then skips it.
  • The server is slow. Raise the Timeout in the settings. On strict hosts, the plugin may still use a shorter timeout.
  • You use an old version. Earlier versions misread some anchors, subfolder installs and bot-protected hosts. Update to the latest version.

A tool page says "Could not load"

The page could not reach brokenlinkchecker.io, so click Retry in a moment. A change you made on the website can take up to five minutes to show in wp-admin.

Still stuck

Contact support with your plugin version and WordPress version. The page shows where to find both.