WordPress version checker: is this site up to date?

Paste any WordPress site's address. The result takes a few seconds.

Core versionSecurity statusWhere it was foundFree

We read the home page once, plus the feed or readme.html only if the version is hidden. Nothing is stored. Up to 20 checks per 10 minutes.

WordPress updates and fixes

WordPress, plugin and PHP updates done on a staging copy first, with backups and testing, and broken updates fixed. Free review and a fixed quote.

See the service

WordPress version checker: what it does.

Enter any website and this free WordPress version checker shows which version of WordPress it runs, where that number came from, and how it compares with the releases WordPress.org publishes today. You'll see whether the site is on the latest release, on an older release that still gets security fixes, or missing fixes it should already have. It's free, needs no sign-up or browser extension, and the answer takes a few seconds.

Where the checker finds the version.

WordPress writes its own version number in several public places. By default it adds a generator tag to the head of every page, such as <meta name="generator" content="WordPress 7.1.4">. It also adds ?ver= and the version to the address of its own stylesheets and scripts, so browsers fetch fresh copies after an update. And it prints a generator line in the RSS feed and in a small file called wp-links-opml.php.

The checker reads the site's home page once and looks for those signs in that order: the generator tag, then the ?ver= on core files such as the emoji script and the dashicons stylesheet, then the address of WordPress's own CDN copy of those files on sites that use Jetpack. If the page hides all of them, it reads the RSS feed and then wp-links-opml.php, which security plugins sometimes miss. The result always says which of these places the version came from.

Not every ?ver= is the WordPress version. Files in /wp-includes/js/dist/ carry a code fingerprint, such as ver=4d63a3d491d11ffd8ac6, and bundled libraries carry their own number, such as jQuery 3.7.1. The checker ignores those, so it doesn't report a library version as WordPress.

Then it compares the number with WordPress.org's official release list. That list names every branch that still gets updates and the newest release of each one, so the checker can tell an old but patched site from one that is missing security fixes.

What each result means.

Each result uses WordPress.org's own release list, read at most 12 hours earlier:

ResultWhat it means
Up to dateThe site runs the newest WordPress release. Nothing to do.
Missing security fixesA newer release of the same branch is out, for example 7.1.2 when 7.1.4 is available. Point releases are where security fixes ship, so update soon.
Older branch, still patchedThe site has the newest security release of an older version, such as 6.9.11. It still gets fixes for now, but only as a courtesy, so plan the move to the current version.
No longer updatedThe branch is older than any branch WordPress.org still updates. It gets no security fixes at all. Update as soon as you have a backup.
Pre-releaseA beta or release candidate of the next version. Normal for test sites and for WordPress.org itself, unusual for a business site.
Version hiddenWordPress was found, but every place the number usually appears is hidden. The checker says so rather than guessing.
Not WordPressThe home page shows no sign of WordPress. The Website Platform Checker names the platform it does use.

Why a WordPress version can be hidden.

Hiding the version is common, and it's a reasonable setting. It doesn't make an old site safe, because attackers' tools try known weaknesses whatever the page says, but it removes an easy clue. These are the usual reasons the checker can't see a number:

ReasonWhat you'll see
A security plugin removed the generator tag and the ?ver= numbersVersion hidden. The feed or wp-links-opml.php sometimes still shows it, and the checker tries both.
A speed plugin combined all files into one bundleVersion hidden, because the core files no longer load on their own.
The feed is turned off, redirected or blockedVersion hidden, unless the page itself still shows it.
Only readme.html is leftA rough range, such as 6.6 to 6.9, worked out from the minimum PHP version that file lists. It's an estimate, and the result says so.
The site runs on WordPress.comNo version. WordPress.com prints its own name in the generator tag.
A firewall or bot check answered instead of the siteAn error saying the site blocked the check. The checker doesn't try to get around it.

How to check a WordPress version without logging in.

You can confirm most results yourself in a minute. Open the site, right-click and choose View Page Source, then search the source with Ctrl+F (Cmd+F on a Mac):

Where to lookWhat to search for
Page sourcegenerator. A line such as content="WordPress 7.1.4" is the version.
Page source, when there's no generator tagwp-emoji-release or dashicons. The number after ?ver= on those files is the version.
The RSS feed: add /feed/ to the addressgenerator. A line such as wordpress.org/?v=7.1.4 is the version.
The links file: add /wp-links-opml.phpgenerator="WordPress/7.1.4" in a comment near the top.
readme.htmlNo version since WordPress 4.8. The minimum PHP version it lists gives only a rough range.

How to check the version of a site you run.

If you can log in, you don't need a checker. These all show the exact version, even when the public site hides it:

WhereWhat you'll find
Dashboard, then UpdatesYour version, and a button to update when a newer one is out
Dashboard home, At a Glance boxThe version and the active theme
Tools, then Site Health, then InfoWordPress, PHP and database versions in one list
The file wp-includes/version.phpThe line $wp_version = '7.1.4'; read it in your host's file manager or over SFTP
WP-CLI on the serverRun wp core version

Which WordPress versions still get security fixes?

WordPress.org's support policy is short: the only officially supported version is the latest major release. Older branches may get security fixes when serious problems are found, but the policy calls that a courtesy, with no guarantee and no timeframe. There is no long-term support version.

In practice the core team has kept patching old branches for years. On 15 November 2026, WordPress.org's update service still offered security releases for every branch from 4.7 to 7.1, and WordPress 7.1.4 and 7.0.8 came out together on 28 October 2026. The checker reads that list live, so the result changes on the day a new release ships.

Since WordPress 3.7, sites install minor and security releases automatically by default. A site that is behind on its own branch has usually had that turned off, or the update failed. Major versions update automatically only on new installs from WordPress 5.6 onwards, unless the owner turned that on.

What to do if the site is behind.

1. Take a full backup of the files and the database, and check you can restore it. Most hosts include backups; a plugin such as UpdraftPlus works too.

2. If the site is missing a security release on its own branch, such as 7.1.2 to 7.1.4, update now. Point releases fix bugs and security problems and rarely change how the site works.

3. For a jump to a new major version, update a staging copy first. Update plugins and the theme, then WordPress, and check the pages and forms that matter most, such as checkout, contact and booking.

4. Check the PHP version under Tools, then Site Health. Newer WordPress releases need newer PHP, and the minimum rises over time. Your host can change it.

5. Turn automatic minor updates back on if they were off, so security releases install on their own.

If a plugin breaks after an update, deactivate it, restore the backup if you have to, and find the conflict on the staging copy before trying again.

What a version checker can't see.

The checker sees what any visitor's browser receives. A page served from a full-page cache can show an older ?ver= for a short time after an update, and a site that hides the version everywhere can only be checked from its dashboard. The checker reports the WordPress core version only. Plugins and themes have their own versions and their own security updates; the WordPress theme and plugin detector lists those that load on the home page.

On a multisite network every site shares one WordPress install, so every site on the network shows the same version. Each check reads the home page and, only while the version is still unknown, up to three small public files. Nothing is stored, and checks are rate-limited so the tool stays fast and fair to the sites it reads.

Changes to the checker.

November 2026: first version. It reads the generator tag, core file versions, WordPress's CDN paths, the RSS feed and wp-links-opml.php, and compares the result with every branch WordPress.org still updates.

Need the update done for you?

I update WordPress sites the careful way: a full backup, a staging copy, plugins and theme first, then WordPress and PHP, with the key pages tested before anything changes on the live site. If an update has already broken something, I find the conflict and fix it. Send me the site address for a free review and a fixed quote.

WordPress Version Checker FAQs

What is the current WordPress version?+

The checker shows the latest release live from WordPress.org's update service, so it's always current. On 15 November 2026 it was WordPress 7.1.4, released on 28 October 2026, and WordPress 7.2 was in beta.

How do I find out what version of WordPress a site is running?+

Enter the address above. The checker reads the generator tag, the version on WordPress's own files, the RSS feed and wp-links-opml.php, and shows the version with where it was found. By hand, view the page source and search for generator, or add /feed/ to the address.

Why can't I see the WordPress version of some sites?+

Security and speed plugins often remove the generator tag and the ?ver= numbers, and some sites turn off or block the feed. When every source is hidden, the checker says the version is hidden instead of guessing. The owner can still see it under Dashboard, then Updates.

Is it safe to show my WordPress version?+

Showing it doesn't create a weakness, but it tells attackers which known problems to try. Hiding it is a reasonable extra step. Keeping WordPress updated matters far more, because automated attacks try old weaknesses whether the version is shown or not.

Is an old WordPress version dangerous?+

It can be. Security fixes ship in point releases, so a site missing them is open to problems that are already public. WordPress.org officially supports only the latest major release and patches older branches as a courtesy, with no guarantee.

Does WordPress update itself?+

Partly. Since WordPress 3.7, minor and security releases install automatically by default. Major versions update automatically only on sites installed with WordPress 5.6 or later, or when the owner turns it on. Plugins and themes have their own update settings.

Has WordPress 7 been released?+

Yes. WordPress 7.0 came out on 20 May 2026 and WordPress 7.1 on 19 August 2026, according to WordPress.org's release archive. The checker compares every site against the newest release, whichever number that is.

Is the WordPress version checker free?+

Yes. It's free with no sign-up and no browser extension. Each visitor can run up to 20 checks every 10 minutes.

Is your site behind on updates?

Send me the site address and what you need. I’ll reply with a clear next step within 24 hours.

Free review and a fixed quote.

Your inquiry is emailed directly to Ali. No mailing lists, ever. See the privacy policy.