khalidA-55

Problem:
The client is experiencing a 'Mismatched Price' error in Google Merchant Center due to schema markup showing USD instead of EUR for German visitors on a WooCommerce site using WPML and WooCommerce Multilingual. Despite correct frontend display of prices, the schema markup does not reflect the visitor's currency.
Solution:
We explained that Google uses a bot to index websites, often from the USA, which is why USD is fetched as the currency. This behavior is determined by Google and not something we can directly influence. More information on how Google handles locale-adaptive pages can be found here: Google's documentation on locale-adaptive pages.

For the issue of displaying MAD for Moroccan visitors while maintaining language-based currency settings for others, we suggested implementing a geolocation-based override. This can be achieved via custom coding using the

wcml_client_currency

hook. More details on this hook can be found here: WCML client currency hook. If custom coding is required, we recommend hiring a professional from the WPML contractors list: WPML Contractors.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at WPML Support Forum.

Problem:
The client is experiencing issues with Google Search Console showing over 685 errors named 'Alternate Page with Proper Canonical Tag'. The client is confused about the meaning of this status and how to identify pages that should be indexed after activating WPML.
Solution:
We explained that the 'Alternate Page with Proper Canonical Tag' status in Google Search Console is not an error but an informative alert indicating that Google has recognized multiple versions of a page with the same canonical URL. One version is treated as the primary, and others are not indexed as duplicates. This setup is typical when using WPML with the WPML SEO and Yoast SEO plugins, which manage canonical tags for all languages. To ensure that the correct pages are indexed:
1. Confirm that your canonical tags reflect your indexing intentions.
2. Use tools like Screaming Frog SEO Spider to audit your site's canonical tags.
3. Adjust canonical tags where necessary to ensure each unique content page is recognized by Google.
For more details, check the documentation here: WPML SEO documentation

If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML Support Forum.

Problem:
The client is trying to translate

admin_texts_wpseo_titles

for SEO purposes and is unsure how to handle placeholders and actual text within the string.
Solution:
We recommend translating only the actual text within the string and keeping the placeholders identical across languages. For example, in the string

%%term_title%% Archives %%page%% %%sep%% %%sitename%%

, only the word "Archives" should be translated, while placeholders like

%%term_title%%

,

%%page%%

,

%%sep%%

, and

%%sitename%%

should remain unchanged. Here is how you should translate it:

English Original: %%term_title%% Archives %%page%% %%sep%% %%sitename%%

 German Translation: %%term_title%% Archive %%page%% %%sep%% %%sitename%%

For further details on how these placeholders work, you can refer to Yoast's documentation here: Yoast SEO Snippet Variables.

If this solution does not resolve your issue or seems outdated, please check for related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if needed.