When you build a page in one language and then translate it, shortcodes and Elementor widgets often carry hard-coded IDs — a specific property, a specific agent, a list of taxonomy terms. Those IDs are correct for the original language, but wrong for every other language. WPResidence Translate fixes this automatically through a process called ID remapping. It is the glue that makes a multilingual page actually look multilingual. Full context on building a multi-language real estate website is on our main docs page.

Why Remapping Is Needed

Consider a WPResidence page that displays three featured properties via a shortcode:

[estate_property_list property_ids="128,144,157"]

IDs 128, 144, 157 are the English properties. When a French visitor lands on the translated page, you want them to see the French versions of those same three properties — not the English ones. Remapping does exactly that, transparently, at render time.

What Gets Remapped

WPResidence Translate remaps three types of references in shortcodes and Elementor widgets:

• Single IDs in attributes named id, post_id, property_id, agent_id, developer_id, and similar.
• ID lists in attributes named ids, post_ids, property_ids, agent_ids, developer_ids, and similar.
• Taxonomy term references used by the Search Form Builder and Agent Grids widgets (action, category, city, area, county, status, features).

If a specific ID has no translation in the active language, the original ID is kept — so the widget still renders something instead of going blank.

Which Shortcodes Are Handled

Remapping runs on shortcodes whose tag starts with:

• wpestate_
• wpresidence_
• estate_

Plus a small fixed list: property_page, property_page_advanced, estate_property, estate_properties. This covers the standard WPResidence shortcode catalog.

Search Form Builder Remapping

The WPResidence Search Form Builder lets you pre-select taxonomy terms as tab chips or filter defaults. Those terms are stored as numeric term IDs. On the frontend, WPResidence Translate reads the active language, looks up the translated term for each ID, and primes a cache so the search form displays the translated label and filters results under the translated taxonomy.

Agent Grid Remapping

The WPResidence Agent Grids widget stores a list of agent post IDs. When the viewer is on a non-default language, WPResidence Translate swaps those source-language agent IDs for their translated counterparts, so the grid shows the translated agent cards and links to the translated agent single pages.

Fallback Behavior

Remapping is conservative. If the active language has no translation for a given ID, the plugin falls back in this order:

1. Active language translation, if available.
2. Source language translation (the original post).
3. First translation in the group that is published and available.
4. The original ID, unchanged.

This means a half-translated site still renders — users see source-language items for content that has not been translated yet instead of empty widgets.

How to Tell Remapping Is Working

• Switch to the non-default language on the frontend.
• Inspect property, agent, or developer cards rendered by shortcodes or the Elementor widgets above. They should show translated titles and link to the translated single pages.
• If a card still shows the original language, the referenced post does not yet have a translation for that language. Create the translation and reload.

Turning Remapping Off

Remapping is controlled by the plugin’s Elementor compatibility toggle in WPEstate Translate > Settings. In almost every case you want it on. If you disable it, every shortcode and widget will render with the original IDs regardless of the active language.

Non-Latin IDs

IDs are numeric, so non-Latin alphabets do not apply here. The content those IDs point to — property titles, agent names, taxonomy terms — preserves Cyrillic, Arabic, Chinese, and other non-Latin characters exactly as you enter them.

Common Issues

• An agent card shows the source language name. The agent is not translated yet for the active language. Create the translation.
• Search form shows wrong filter terms. The taxonomy term is not translated. Go to Taxonomy Translation and translate it.
• Widget output is empty. The widget may reference terms or posts that are hidden from the current language. Confirm all referenced items are published.

What To Read Next

• Elementor Widget Translation — the widget-specific companion to this article.
• Taxonomy Translation — translate the terms referenced by search forms and filters.
• Translating Posts & Pages — create the property, agent, or page translations that remapping relies on.

See also our main guide on multi-language real estate website for an end-to-end walkthrough.