The most popular WordPress plugins in the Baltics, counted on 83,874 sites

Ask what the most popular WordPress plugins are and you get a list written by someone selling hosting. We can answer it with a count instead. The Baltic Web Audit, our near-census of the Latvian, Estonian and Lithuanian web in July and August 2026, found WordPress on 13,048 sites in Latvia, 33,398 in Estonia and 37,428 in Lithuania, first in every country, and it could see which plugins those 83,874 sites run.

In short

The Baltic WordPress web is one standard build repeated tens of thousands of times: Yoast SEO on at least 31 to 39% of WordPress sites, Contact Form 7 and Elementor on a quarter to a third each, WooCommerce on 17 to 23%, then a multilingual plugin, a slider and a cache. A plugin is only counted when it leaves a visible trace in the page, so every figure here is a floor. The list itself will surprise nobody. What matters is that each line on it is a dependency with its own owner, its own update schedule and, for three of the most common, a paid licence that somebody has to be holding.

The count

Plugin	Latvia	Estonia	Lithuania	Share of WordPress sites
Yoast SEO	4,011	13,016	13,516	31 / 39 / 36%
Contact Form 7	3,628	10,419	12,460	28 / 31 / 33%
Elementor	3,229	10,040	11,962	25 / 30 / 32%
WooCommerce	2,253	7,751	8,584	17 / 23 / 23%
WPML	1,919	5,363	2,668	15 / 16 / 7%
Slider Revolution	1,338	3,147	5,241	10 / 9 / 14%
All in One SEO	1,151	2,658	2,891	9 / 8 / 8%
Polylang	1,008	1,783	1,710	8 / 5 / 5%
WP Rocket	645	2,508	1,830	5 / 8 / 5%
MonsterInsights	347	1,290	1,300	3 / 4 / 3%

All figures are from the report’s WordPress chapter, and all of them are minimums. A cache plugin or a security plugin can do its whole job without leaving anything in the page a visitor receives, which is why the table leans toward plugins that print something: a meta tag, a form, a stylesheet.

The order matches the global one. On 19 September 2026 the WordPress.org directory reported more than 10 million active installations each for Yoast SEO, Contact Form 7 and Elementor, and more than 7 million for WooCommerce. The Baltics did not invent a local stack. They installed the default one.

What the list says about the region

WooCommerce is the region’s real shop platform. At 17% of WordPress sites in Latvia and 23% in Estonia and Lithuania, WooCommerce alone is larger than Shopify, OpenCart and PrestaShop combined in every one of the three countries. A Baltic shop is, more often than anything else, a WordPress site with a plugin. We wrote about what that means for the agency building it in what a store project carries that a site project does not.

Three officially monolingual countries run a multilingual web. Between them WPML and Polylang account for 2,927 detections in Latvia, 7,146 in Estonia and 4,378 in Lithuania. Estonia and Latvia pay for it: WPML outnumbers the free Polylang roughly three to one in Estonia and two to one in Latvia. Lithuania is closer to even, 2,668 against 1,710.

The homepage slider is not dead. The report calls it a design pattern the industry declared dead a decade ago. Slider Revolution is still on at least 9,726 Baltic sites, and on one Lithuanian WordPress site in seven.

Elementor is the page builder, singular. A quarter of Latvian WordPress sites and nearly a third of Estonian and Lithuanian ones are built in it. For an owner that is mostly good news, because the editing skills transfer between sites and between agencies. It also means a breaking change in one plugin lands on about 25,000 sites in the region in the same week.

The line that needs correcting: jQuery Migrate

The audit found jQuery Migrate on 9,309 Latvian, 25,755 Estonian and 27,384 Lithuanian WordPress sites, which is 71%, 77% and 73% of them. It is a compatibility script whose only job is to keep old jQuery code working, and a number like that reads as seven in ten site owners neglecting their JavaScript.

It is not that. WordPress core ships it. In the core source, the jquery script handle is registered with two dependencies, jquery-core and jquery-migrate, so any theme or plugin that asks WordPress for jQuery gets Migrate loaded with it. No owner chose it and most have never heard of it.

The history is worth a paragraph because it explains the number. In June 2020 the core team published a three-stage plan: remove the old jQuery Migrate 1.x in WordPress 5.5, update jQuery and add the latest Migrate in 5.6, and then “Remove jQuery Migrate. This is tentatively planned for WordPress 5.7 or later, depending on testing.” Six years on, stage three has not happened, and trunk still registers Migrate 3.4.1 beside jQuery 3.7.1. The helper plugin released to soften that transition, Enable jQuery Migrate Helper, is listed by the WordPress.org API as closed on 20 May 2026, reason “Security Issue”.

So those percentages are a measure of how much of the WordPress web still asks for jQuery, not of how many owners are careless. Stripping Migrate out by hand is a popular speed tip and a small win at best. The real saving is a theme and plugin set that no longer needs jQuery on the front end, and that is a rebuild decision, not a tweak.

Every line in the table has an owner. Find out who

This is the part of the list that matters to whoever pays for the site. Each plugin is software written by someone else, updated on their schedule, and the standard build has two kinds of owner.

The free ones are maintained in public. Anyone can read the record. On 19 September 2026 the WordPress.org plugin API showed Yoast SEO last updated on 15 September, WooCommerce on 18 September, Polylang on 8 September, Elementor on 31 August, All in One SEO on 28 August and Contact Form 7 on 17 August, every one of them tested against WordPress 7.1.1. Contact Form 7 has been in the directory since August 2007 and is still maintained. These are healthy dependencies, provided the site actually installs the updates.

The paid ones are not in the directory at all. Ask the same API for Slider Revolution or WP Rocket and it answers “Plugin not found”. WPML’s old listing has been closed since November 2017. Their updates come from the vendor, against a licence. Together those three account for 24,659 detections across the region, so the question is not rare: whose account is the licence in? If the answer is a developer who built the site years ago and has since moved on, the plugin may be running while its update channel is not, and nothing on the site will tell you.

What you can check yourself, and what needs a developer

Yourself, in ten minutes, with an administrator login:

• Open Plugins in the WordPress dashboard and count them. Then count the ones showing an update available. A long list of pending updates is the usual sign of a site nobody is maintaining.
• For each free plugin, open its WordPress.org page and read last updated and tested up to. Years-old dates, or a notice that the plugin is closed, mean it has no owner and needs a replacement.
• For each paid plugin, find out whose name the licence is under and whether it is active. Ask for it to be moved to an account your company controls.
• Turn on automatic updates for plugins you trust, knowing that WordPress applies them without testing them first.

What needs a developer:

• Replacing an abandoned plugin. The data it holds, the shortcodes it left in your pages and the templates that call it all have to be moved, which is why abandoned plugins stay installed for years.
• Updating a site that is far behind. When twenty updates are pending, including WooCommerce or Elementor across major versions, the safe order is a staging copy, a backup and one update at a time.
• Deciding whether the site still needs a slider, a page builder or jQuery at all. That is a design and build question, and it is the one that moves speed.

We maintain exactly this stack, so the honest summary is short. The standard Baltic build is a reasonable one, and nearly all of its risk sits in who is watching it. That is what a care plan is for, and what a monthly maintenance plan includes sets out the work line by line. If the site needs more than upkeep, WordPress development is where that conversation starts.

How the counting works

The audit visited 293,806 Baltic domains and identified technologies from what each homepage served: script and stylesheet paths, meta tags, markup patterns. A WordPress plugin that prints nothing into the page is invisible to this method, and a site that hides its plugin paths is undercounted too. That is why every figure in this piece is stated as a minimum, and why the true share of, say, WP Rocket is certainly higher than 5 to 8%. Percentages are of the WordPress sites detected in each country. The WordPress.org figures were read from its public plugin API on 19 September 2026, and any reader can repeat them by opening the plugin pages linked above.