
WordPress reCAPTCHA Invalid Site Key Error
Fix an invalid reCAPTCHA site key by matching the public key, secret, hostname, and integration type. Remove stale copies and rotate any exposed secret.
wp-login.php is the most attacked URL on any WordPress site. Not because it is weak, but because it is at a known address on millions of sites, which makes it worth attacking automatically and continuously. Most owners discover this from a log file rather than a breach.
These guides cover the defences, roughly in order of how much they help. Moving the login URL removes you from the easiest scans. Limiting attempts stops the patient ones. Allowlisting your own addresses and blocking the worst offenders narrows it further. A captcha stops most automated submissions, and two-factor authentication is the one that still protects you when a password has already leaked.
Each of those has a failure mode, and they are covered too. A custom login URL that a cache serves to the wrong person or that returns 404 after a permalink change. A URL you moved and then forgot. Attempts that continue after the move because something is still reaching the old file directly.
One group is about being locked out, which is the risk you take on when you harden a login. Losing the phone with the authenticator on it, a redirect loop after a correct password, sessions that end after minutes, cookies the browser will not set.
If you are hardening a site today, read the recovery articles before the hardening ones. Knowing the way back in is what makes the rest safe to do.

Fix an invalid reCAPTCHA site key by matching the public key, secret, hostname, and integration type. Remove stale copies and rotate any exposed secret.

Add reCAPTCHA to WordPress login with the correct integration type, environment-specific keys, anonymous testing, accessible failure handling, and a recovery route.

Recover WordPress access after losing a 2FA device through recovery codes, another factor, a trusted session, or a verified administrator reset—never a global shutdown.

Add two-factor authentication to WordPress without locking out legitimate users. Plan enrollment, recovery, enforcement, testing, and secure factor resets.

Slow password guessing with temporary, measurable WordPress login limits. Account for shared networks, proxies, recovery, distributed attacks, strong passwords, and 2FA.

Recover an undocumented custom WordPress login URL through authorized records, the responsible plugin or setting, and a tested return to normal access.

Trace a WordPress admin login loop through redirects, proxy scheme detection, and authentication cookies, then correct the first layer that contradicts the intended state.

Move the WordPress login to a custom route without locking out administrators, breaking password recovery, or mistaking obscurity for authentication security.