Polylang
Free WordPress multilingual plugin allowing content creation in multiple languages with language switcher and RTL support.
Websites Using Polylang
What Is Polylang?
Polylang is a popular WordPress plugin that turns a standard single-language WordPress site into a fully multilingual one, letting you publish posts, pages, categories, tags, menus, and media in as many languages as you need. Rather than running a separate installation for each language or relying on machine translation, Polylang keeps every translation of a piece of content linked together inside one WordPress site, so a visitor, and a search engine, can move cleanly between the English, French, or Japanese version of the same page.
Polylang is widely regarded as one of the two dominant multilingual solutions for WordPress, alongside WPML, and is frequently described as having well over half a million active installations. It is published in both a free edition, available through the official WordPress plugin directory, and commercial Pro and Business tiers that add features such as duplicating content across languages, translating slugs, and machine-translation integrations. The free version alone is enough to run a genuinely multilingual site, which is a large part of its appeal.
It is important to be precise about what Polylang is and is not. It is a server-side WordPress plugin: it installs into a self-hosted WordPress site, stores its data in the WordPress database, and does its work as PHP code running on the server before a page is sent to the browser. It is not a hosted translation service, not a browser extension, and not a standalone application. StackOptic does not run inside the browser either; it fetches a URL from the server side and inspects the same HTML, headers, and link patterns that Polylang leaves behind.
A helpful way to frame Polylang is to understand the problem it solves. Search engines and browsers expect a multilingual site to expose each language version at a distinct, crawlable URL and to declare the relationships between those versions explicitly. Doing that by hand across hundreds of posts is impractical. Polylang automates the entire arrangement: it assigns a language to every piece of content, generates the language-specific URLs, builds the language switcher, and emits the hreflang annotations that tell Google which URL serves which language and region. That combination of content management and technical SEO plumbing is exactly why it has become a default choice for multilingual WordPress.
How Polylang Works
Under the hood, Polylang adds the concept of a language as a first-class taxonomy in WordPress. When you define the languages your site supports, Polylang stores each one with a locale (such as en_US or fr_FR), a flag, and a URL strategy. Every post, page, category, tag, and menu item is then assigned to exactly one language, and Polylang maintains a relationship table that links the translations of a given item together. Editing the German version of an article and its English counterpart are two separate posts in the database that Polylang knows are translations of each other.
The plugin offers three common URL strategies, and the one a site chooses shapes how it looks from the outside. The default approach uses a language directory in the path, producing URLs like /en/about/ and /fr/about/. A second option places the language in a subdomain (en.example.com). A third uses entirely different domains per language. Most Polylang sites use the path-prefix model because it is the simplest to set up and the easiest to recognize, but all three are supported.
When a request arrives, WordPress loads Polylang as part of its plugin stack. Polylang inspects the requested URL, determines the active language from the prefix, subdomain, or domain, and filters every subsequent query so the visitor sees only content in that language. It swaps the site's strings, menus, and widgets for their translated equivalents, and it injects the appropriate <html lang="..."> attribute and hreflang alternate links into the page head. The result is a page that is internally consistent in one language while advertising its sibling translations to search engines.
Polylang also exposes a language switcher, usually rendered as a small menu or list of flags, that links each translation together for human visitors. Developers can interact with the plugin through a family of template functions and constants prefixed with pll_ (for example pll_current_language(), pll_the_languages(), or pll__() for translating strings in theme code). These pll_ markers are part of why Polylang is recognizable: themes and child themes built for Polylang sites often reference these functions, and the plugin's own assets and body classes carry the same signature.
For deeper integrations, Polylang ships compatibility layers and companion plugins. There is an official integration for WooCommerce that translates products, categories, and checkout strings, and a string-translation interface that lets site owners translate text coming from themes and other plugins. The Pro edition adds slug translation (so the URL segment itself is localized, such as /fr/a-propos/ instead of /fr/about/), shared-slug handling, and an option to duplicate or synchronize content across languages to speed up the translation workflow. None of this changes the fundamental architecture: it all runs server-side and leaves traces in the delivered HTML.
How to Tell if a Website Uses Polylang
Multilingual plugins are among the easier WordPress add-ons to detect because their entire purpose is to expose multiple language versions through URLs and link annotations. StackOptic checks these signals from the server side, and you can confirm them by hand. Note that distinguishing Polylang specifically from other multilingual plugins (such as WPML) sometimes takes more than one signal, because both produce similar hreflang output.
Plugin asset paths. The most direct WordPress-level fingerprint is a request to /wp-content/plugins/polylang/ (and the Pro variant polylang-pro). Polylang enqueues a small front-end script and stylesheet from this directory, so seeing assets load from that path is strong proof the plugin is installed.
hreflang alternate links. Polylang injects <link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/..." /> tags into the page head for each language. The presence of a complete set of reciprocal hreflang tags, often including an x-default, is a hallmark of a multilingual plugin at work.
Language URL structure. Look for a consistent language prefix in the path (/en/, /fr/, /de/), or language subdomains. When the same article exists at /en/article and /fr/article and the two link to each other, a multilingual plugin like Polylang is almost certainly responsible.
pll_ markers and body classes. Polylang's developer functions are prefixed pll_, and pages frequently carry language-related body classes and a language switcher whose markup references Polylang. Theme code and HTML comments that mention pll_ or polylang are a recognizable tell.
The language switcher. A visible flag-and-language menu that links each translation together is a behavioral signal; inspecting its links usually reveals the language-prefixed URL pattern above.
| Method | What to do | What Polylang reveals |
|---|---|---|
| View Source | "View Page Source" and search for hreflang and polylang | hreflang alternate tags, asset paths under /wp-content/plugins/polylang/ |
| Browser DevTools | Inspect the Network tab and the <head> | Requests to the polylang plugin directory, hreflang link elements |
| curl -I / curl -s | `curl -s https://example.com | grep -i polylang` |
| Wappalyzer | Run the extension on the live page | Often identifies "Polylang" under WordPress plugins |
| BuiltWith | Look up the domain | Current and historical Polylang detection alongside the WordPress profile |
A fast terminal check is curl -s https://example.com | grep -iE 'polylang|hreflang'. If you see asset requests to the Polylang plugin folder together with a reciprocal set of hreflang tags and /xx/ language prefixes, the conclusion is reliable. For the broader methodology, see our guides on how to find out what technology a website uses and how to identify a WordPress theme and plugins. Because the whole point of Polylang is multilingual delivery, the concepts in what is international SEO and hreflang explain exactly why these signals exist and how to read them.
It is worth being honest about the limits of detection here. Because Polylang and WPML both generate hreflang tags and language-prefixed URLs, the hreflang output alone does not always tell you which plugin produced it. The decisive signal is usually the plugin asset path: a request to /wp-content/plugins/polylang/ points to Polylang, whereas /wp-content/plugins/sitepress-multilingual-cms/ points to WPML. A site can also be running on a multilingual setup that strips obvious plugin references, in which case the language URL structure and the switcher markup become the best remaining clues. Combining several signals, asset path, hreflang set, URL prefix, and pll_ references, is what makes the identification dependable, and pulling the raw server response makes those signals easy to read without a browser rewriting the DOM. If you want to confirm the underlying CMS first, the techniques in our guide on how to tell if a website is built with WordPress establish that foundation before you narrow down the specific multilingual plugin.
Key Features
- Unlimited languages. Define as many languages as you need, each with its own locale, flag, and URL strategy.
- Per-content translation linking. Every post, page, category, tag, and menu item can have a linked translation, all managed inside one WordPress site.
- Flexible URL structures. Choose between a language directory in the path, language subdomains, or separate domains per language.
- Automatic
hreflangoutput. Polylang emits reciprocalhreflangalternate tags and anx-default, handling a core piece of international SEO automatically. - Customizable language switcher. A configurable menu or widget that links each translation together for visitors.
- Developer API. A family of
pll_template functions and a string-translation interface for theme and plugin text. - WooCommerce and string translation. Official integrations translate store content and strings coming from themes and other plugins (some via Pro and companion add-ons).
Pros and Cons
Pros
- A capable free edition that can run a genuinely multilingual site without a paid license.
- Keeps everything in one WordPress install, avoiding the overhead of separate sites per language.
- Handles
hreflangand language URLs automatically, which removes a major source of international-SEO errors. - A lightweight footprint and a developer-friendly API make it popular with theme builders and agencies.
Cons
- The free version handles content translation but leaves automatic machine translation and slug translation to the paid tiers.
- Managing many languages and keeping translations in sync is inherently more work than a single-language site.
- Compatibility with some third-party plugins requires care, as not every plugin is multilingual-aware.
- Switching multilingual plugins later (for example to or from WPML) is a non-trivial migration.
Polylang vs Alternatives
Polylang competes with a handful of other approaches to multilingual WordPress. The table below clarifies where it fits.
| Solution | Approach | Cost model | Best for |
|---|---|---|---|
| Polylang | Native WordPress taxonomy, per-content translations | Free core, paid Pro/Business | Sites wanting a capable free multilingual base |
| WPML | Commercial multilingual plugin with translation management | Paid only | Sites needing built-in translation workflows and broad plugin compatibility |
| TranslatePress | Front-end visual translation, including automatic | Free core, paid add-ons | Teams who prefer translating directly on the live page |
| Weglot | Hosted translation layer via subdomain or subdirectory | Paid subscription | Sites wanting near-zero setup and managed translation |
| Multisite + manual | Separate WordPress site per language | Hosting cost only | Large orgs wanting full isolation per market |
If a site turns out to use a different multilingual tool, the same signals point to the real one; the closest comparison is the commercial WPML, which uses the sitepress-multilingual-cms plugin directory rather than Polylang's. For the SEO theory behind any of these, our explainer on what is international SEO and hreflang is the place to start.
Use Cases
Polylang is the natural choice for any WordPress site that needs to serve more than one language without splintering into multiple installations. Small and mid-size businesses targeting several markets use it to publish their marketing pages in each region's language while keeping a single content workflow. Agencies favor it for client sites because the free edition covers most needs and the pll_ API integrates cleanly into custom themes.
It also fits multilingual blogs and publications, documentation sites that must be available in several languages, and WooCommerce stores selling across borders that need translated products and checkout flows. For technology and market research, detecting Polylang on a site is a useful signal in its own right: it indicates an organization deliberately targeting multiple language markets, which often correlates with international ambitions or a multi-region customer base.
Consider a few concrete scenarios. A boutique hotel group might run one WordPress site with English, French, and German versions of every page so that travelers from each market land on content in their own language, with Polylang generating the hreflang tags that keep Google from serving the wrong version. A SaaS company expanding into Europe might localize its marketing site and blog, using Polylang's switcher so visitors can toggle languages and its URL prefixes so each locale is independently crawlable. A non-profit operating across several countries might maintain program pages in multiple languages from a single editorial team. In each case the common thread is reaching distinct language audiences from one manageable WordPress install.
From a sales-intelligence and competitive-analysis perspective, spotting Polylang, or any multilingual plugin, tells you something specific about a prospect. It signals an international or multi-market orientation, which is valuable context for vendors selling localization, translation, cross-border payments, or international-SEO services. Surfacing that signal automatically across many domains, rather than manually inspecting each site's language switcher, is exactly the kind of insight a server-side detection tool delivers in seconds. Pairing that with the ideas in what is technographics and using tech-stack data to qualify leads shows how a single plugin signal can sharpen account prioritization.
Frequently Asked Questions
Is Polylang free?
There is a free edition of Polylang available through the official WordPress plugin directory, and it is fully capable of running a multilingual site: defining languages, translating content, generating hreflang tags, and rendering a language switcher. Paid Pro and Business tiers add conveniences such as slug translation, content duplication across languages, and machine-translation integrations. Many sites run successfully on the free version alone, upgrading only when they need the workflow features.
How can I tell if a site uses Polylang instead of WPML?
Both plugins produce hreflang tags and language-prefixed URLs, so the hreflang output alone is not decisive. The reliable distinction is the plugin asset path: Polylang loads assets from /wp-content/plugins/polylang/ (or polylang-pro), while WPML uses /wp-content/plugins/sitepress-multilingual-cms/. Checking the page source or Network tab for those directories, alongside any pll_ references, tells the two apart.
Does Polylang help or hurt SEO?
Used correctly, Polylang helps international SEO by giving each language version a distinct, crawlable URL and emitting reciprocal hreflang annotations so search engines serve the right language to the right audience. This is exactly the structure Google expects from a multilingual site. As always, the underlying content quality and a clean site architecture matter most; the plugin handles the technical plumbing rather than the editorial work.
What do the /en/ and /fr/ prefixes in the URL mean?
Those prefixes are Polylang's default URL strategy, which places a short language code at the start of the path so that /en/about/ and /fr/about/ are the English and French versions of the same page. This keeps each language at its own address, which is necessary for both crawlers and the language switcher. Polylang can alternatively use language subdomains or separate domains, but the path prefix is the most common and the easiest to recognize.
Can I see which languages a Polylang site offers without visiting every page?
Often yes. The language switcher on any page links to each available translation, and the hreflang tags in the page head list every language version with its locale (for example hreflang="de-DE"). Reading those hreflang entries from the raw HTML reveals the full set of languages the site declares, without clicking through the switcher manually.
Want to detect Polylang and the rest of a site's stack automatically? Run any URL through StackOptic at https://stackoptic.com.
Alternatives to Polylang
Compare Polylang
Analyze a Website
Check if any website uses Polylang and discover its full technology stack.
Analyze Now