--- title: "WPML vs Polylang for Real Estate Agent Websites" description: "Compare WPML and Polylang for your agent website through editing tasks, translated forms, IDX boundaries, and a received Spanish buyer or seller inquiry." canonical: "https://scalewithsearch.com/articles/compare-wpml-polylang-agent-website" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # WPML vs Polylang for an agent website: translations, forms, and IDX checks Shortlist WPML when you need a central translation workflow for your agent website. Shortlist Polylang when a named editor will maintain individual translated pages. Choose after demonstrating a seller-page update, your actual form integration, and a received Spanish inquiry. WPML documents a central Translations dashboard with automatic and manual translation methods. Polylang offers a free plugin and a Pro edition with additional translation tools. These are documented options, not proof of compatibility with your website. [WPML content workflow, checked 2026.10.14](https://wpml.org/documentation/translating-your-contents/), [Polylang editions, checked 2026.10.14](https://wordpress.org/plugins/polylang/). This comparison addresses your own buyer and seller pages. The selection advice and acceptance checks below are editorial recommendations. ## Compare the publishing work you need Give each builder the same approved English seller page and Spanish translation. Ask the person who will maintain your website to make a correction. Then inspect both public versions. | Decision | WPML's documented route | Polylang's documented route | What to request for your agent website | | --- | --- | --- | --- | | Translation workflow | Central dashboard with manual and automatic methods. [Documentation](https://wpml.org/documentation/translating-your-contents/) | Page and post translation in WordPress; Pro adds duplication and synchronization tools. [Editions](https://wordpress.org/plugins/polylang/) | Demonstrate an approved seller-service change in both languages. | | Machine translation | Translate Everything Automatically can process new and updated content. [Documentation](https://wpml.org/documentation/translating-your-contents/) | Pro integrates DeepL with an API key and translates individual items. [DeepL guide](https://polylang.pro/documentation/support/guides/how-to-use-deepl-machine-translation-with-polylang-pro/) | Record what changes automatically and who reviews the result. | | Forms | Published Gravity Forms workflow using the GFML add-on. [Form guide](https://wpml.org/documentation/translating-your-contents/translate-gravity-forms/) | Published Contact Form 7 workflow using additional integration plugins. [Form guide](https://polylang.pro/how-to-translate-contact-forms-with-polylang/) | Identify the route for your installed form plugin and versions. | | IDX | Keep compatibility with your provider's configuration unresolved until confirmed. | Apply the same requirement. | Obtain written provider confirmation and test the property inquiry. | Vendor features in this table were checked on 2026.10.14. The form examples use different plugins. They illustrate documented integration routes; they do not establish which multilingual plugin is better for every form. For a small set of pages with supplied translations, start by demonstrating Polylang's editing workflow. For a content library requiring coordinated updates, compare WPML's central workflow against that same task. Include your editor's access and the review step in either proposal. ## Separate free software from the maintenance work Polylang's plugin listing distinguishes its core translation features from Pro features, including DeepL translation and XLIFF import and export. Its product page offers the free plugin alongside paid editions. [Plugin feature list, checked 2026.10.14](https://wordpress.org/plugins/polylang/), [Product options, checked 2026.10.14](https://polylang.pro/features/). Ask for the edition and current quote that cover your demonstrated requirements. Include translation-service usage, form extensions, maintenance, and human review where applicable. Record each account holder, renewal owner, and support contact. Avoid deciding from the initial license charge alone. Request a demonstration of the work after handover: correcting a biography, updating seller services, and repairing a failed inquiry. Put the responsible person beside each task. ## Check machine translation against your page builder Polylang's DeepL guide says its integration does not support content generated by Elementor or Divi, or the WordPress Site Editor. It supports Classic Editor and Block Editor content. These are limits of the documented DeepL integration, not a universal verdict on manually translating every builder page. [Polylang DeepL limitations, checked 2026.10.14](https://polylang.pro/documentation/support/guides/how-to-use-deepl-machine-translation-with-polylang-pro/). The same guide says an existing DeepL-generated translation does not automatically update after the original changes. Request a maintained workflow for revising the translated version. [Updating a Polylang translation, checked 2026.10.14](https://polylang.pro/documentation/support/guides/how-to-use-deepl-machine-translation-with-polylang-pro/). Have the builder record your editor, theme, multilingual plugin, form extensions, and versions. Require a preview built with that configuration. If a needed capability remains unsupported, resolve it before buying the plugin or approving the website change. For either tool, appoint a fluent reviewer. Require approval of brokerage identity, service descriptions, buttons, errors, and acknowledgements. Keep the source and approved translation together for later corrections. ## Translate the form through its supported integration WPML's Gravity Forms guide calls for Gravity Forms, WPML, String Translation, and GFML. It documents translation of fields, validation messages, confirmations, and notifications. Its workflow retains the same form block or shortcode across translated pages. [Gravity Forms translation, checked 2026.10.14](https://wpml.org/documentation/translating-your-contents/translate-gravity-forms/). Polylang's Contact Form 7 tutorial lists Polylang, Contact Form 7, Contact Form 7 Polylang Module, and Smart Grid-Layout Design for Contact Form 7. It creates translated forms and places each on its corresponding language page. The tutorial is dated 2023.11.21. Confirm current extension support and versions before relying on that arrangement. [Polylang's form tutorial, checked 2026.10.14](https://polylang.pro/how-to-translate-contact-forms-with-polylang/). If your website uses another form plugin, request its documented integration route. Keep support unresolved until the builder identifies the required extensions and demonstrates them together. Specify buyer and seller forms separately. Require the received record to preserve the original question, contact details, source page, and chosen reply language. Assign someone who can answer in that language. ## Treat IDX translation as a separate confirmation Ask your IDX vendor which parts of its search and inquiry experience support your proposed language workflow. Name the multilingual plugin, edition, page builder, and intended URLs. Require answers about search controls, listing details, validation messages, confirmations, and notifications. MLS display rules vary by MLS. IDX Broker documents that some MLS contracts prohibit combining their data with another MLS feed. This illustrates why a general plugin comparison cannot settle your display permissions. [IDX Broker's MLS display guidance, dated 2025.02.28; checked 2026.10.14](https://support.idxbroker.com/hc/en-us/articles/34489917048091-Commingling-MLS-Rules). Confirm translated listing content, attribution, required notices, and any proposed display changes with your MLS and IDX vendor. Request dated approval or support guidance for your configuration. Leave unconfirmed behavior out of the website's language claims. In the preview, follow a Spanish buyer page into the actual property search. Inspect the language at every step. If an approved part remains in English, require clear wording before that transition and a working contact alternative. Test the seller-service form independently. A property-search demonstration should not close the seller inquiry requirement. ## Assign translation updates at handover Name who edits the English page, who updates Spanish, and who approves publication. Ask the builder to demonstrate their assigned access. Keep account ownership and credentials transfer in the written handover. Google recommends separate URLs for different language versions and links that let visitors choose a language. It advises against automatically redirecting visitors based on an assumed language. [Google's multilingual-site guidance, checked 2026.10.14](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites). Require the language switch to connect equivalent buyer or seller pages. Ask for an agreed treatment when a translation is missing. Inspect navigation, contact buttons, and linked documents after an update. Keep the WordPress translation workflow distinct from any proposed replacement website. Request an explicit answer about which editing tools and translated pages survive the change. ## Accept the choice through a received inquiry Arrange marked submissions with synthetic details and receiving destinations you control. These are proposed checks, not completed tests. | Acceptance task | Evidence to request | | --- | --- | | Correct seller services | Both language versions show the approved change after fluent review. | | Submit a Spanish seller inquiry | The agreed destination receives the original question and reply-language choice. | | Submit a Spanish buyer inquiry | The destination receives the buyer question and relevant property reference. | | Correct an invalid entry | Reviewed Spanish messages identify the correction without losing usable input. | | Inspect confirmation and acknowledgement | Both describe the agreed next step in the intended language. | | Follow IDX search | The provider-confirmed language behavior matches the preview and any stated limitation. | | Make a later update | The assigned editor completes the change using handover access and repeats affected checks. | Record the page addresses, plugin versions, device, browser, submission result, and matching received record. Keep failures open until the repaired route passes. Choose the configuration that meets those requirements and has a named maintainer. ## Bring the requirements into your website brief Your multilingual brief identifies translation owners and WordPress functions that must remain available. Resolve that platform requirement at [whole website fix: multilingual WordPress requirements](/for/real-estate). The whole website fix is a static-site repair or rebuild. [Published website scope, checked 2026.10.14](https://scalewithsearch.com/work). - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) - [Own your real estate website: domain, hosting, editing, and leads](/articles/own-your-site) ## Related: Real estate - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) - [Own your real estate website: domain, hosting, editing, and leads](/articles/own-your-site) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```