Title: panosp's Replies | WordPress.org --- # panosp [ ](https://wordpress.org/support/users/panosp/) * [Profile](https://wordpress.org/support/users/panosp/) * [Topics Started](https://wordpress.org/support/users/panosp/topics/) * [Replies Created](https://wordpress.org/support/users/panosp/replies/) * [Reviews Written](https://wordpress.org/support/users/panosp/reviews/) * [Topics Replied To](https://wordpress.org/support/users/panosp/replied-to/) * [Engagements](https://wordpress.org/support/users/panosp/engagements/) * [Favorites](https://wordpress.org/support/users/panosp/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/users/panosp/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/panosp/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites] Canonical Fixed, but Language URLs Without Slug Translation Are Not Handled Corr](https://wordpress.org/support/topic/canonical-fixed-but-language-urls-without-slug-translation-are-not-handled-corr/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [4 months, 2 weeks ago](https://wordpress.org/support/topic/canonical-fixed-but-language-urls-without-slug-translation-are-not-handled-corr/#post-18792183) * Thank you for the clarifications regarding URL rewriting and translated aliases. I understand that enabling URL rewriting allows a language slug and that the sitemap only includes fully translated URLs with translated aliases. * However, there are a few problems we are still facing in practice: 1. **Google indexing issues:** If I choose **not to translate the URL alias** but still want a language slug (e.g., `/it/`, `/de/`, `/fr/`), the canonical URL still points to the original language page. This causes Google to treat the translated page as an alternate rather than a separate page, and sometimes it does not index the translated page at all. 2. **Page indexing warnings:** Google Search Console frequently reports **“Alternative page with proper canonical tag”**, which prevents proper indexing and ranking of the translated pages. 3. **Sitemap limitations:** Since pages without translated aliases are not included in the sitemap, I cannot submit them to Google for indexing. This also prevents caching plugins from preloading the translated pages, which affects performance and user experience. * In short, it would be ideal if: - I could **keep the language slug even without translating the URL alias** - Those URLs would be recognized as distinct by Google - They would be **included in the sitemap**, so both SEO and caching can work correctly * Currently, not translating the alias effectively makes the translated pages invisible to search engines and caching tools. * Thanks for considering this scenario for future improvements. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites] GPTranslate outputs translated URLs in sitemap, but canonical and og:url still p](https://wordpress.org/support/topic/gptranslate-outputs-translated-urls-in-sitemap-but-canonical-and-ogurl-still-p/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [5 months ago](https://wordpress.org/support/topic/gptranslate-outputs-translated-urls-in-sitemap-but-canonical-and-ogurl-still-p/#post-18773258) * Thank you for the detailed explanation and for confirming the upcoming improvements. Self-referencing canonicals per language will be a very important step for SEO and caching consistency. I look forward to testing the new release and continuing to work with you on further improvements. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites] Feature Request: Dynamic Sitemap Generation for Translated Languages to Support](https://wordpress.org/support/topic/feature-request-dynamic-sitemap-generation-for-translated-languages-to-support/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [5 months, 1 week ago](https://wordpress.org/support/topic/feature-request-dynamic-sitemap-generation-for-translated-languages-to-support/#post-18770238) * You can get a good reference from how **Yoast SEO** handles this. Any new content is automatically added to the sitemap without manual action, which is exactly the level of automation developers expect today. * In addition, an **automatic daily crawling / translation refresh** could be a strong SEO advantage, especially for sites with dynamic content such as reviews, where new pages are created every day. * From a structural point of view, having a predictable endpoint like: - mydomain.com/GPTranslate/es/ - mydomain.com/GPTranslate/fr/ * would make it much easier for: - Google Search Console submissions - cache preloaders - third-party integrations * From a business perspective, this matters as well. Strong Cache plugins have over 1,000,000 installations, and several others are in the same range. Seamless interoperability with them increases adoption, reduces friction, and directly impacts conversions for a paid plugin. * Glad to hear it’s noted for future versions. This kind of automation would definitely be a strong differentiator. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites] Feature Request: Dynamic Sitemap Generation for Translated Languages to Support](https://wordpress.org/support/topic/feature-request-dynamic-sitemap-generation-for-translated-languages-to-support/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [5 months, 1 week ago](https://wordpress.org/support/topic/feature-request-dynamic-sitemap-generation-for-translated-languages-to-support/#post-18770186) * Thank you for the clarification. * (Sorry for the previous message I wrote **GTranslate**. I was talking about your** GPTranslate** plugin.) * For a small or low-update website, this approach can work without major issues. However, speaking as a web developer managing multiple active sites where 2–3 new posts are published every week, the challenge is not whether a sitemap export exists, but how **automated and scalable** the workflow is. * Relying on a manual sitemap export button inside the crawler is not ideal for: - frequently updated content - automated cache preloading workflows - CI/CD or hands-off production environments * If the goal is for GPTranslate to stand out as a top-tier solution, features that go beyond current plugins become important, such as: - automatic regeneration of translated sitemaps on content updates - a persistent, publicly accessible language sitemap endpoint - hooks or filters for cache plugins to detect translated URLs programmatically - optional per-language sitemap files (for large or growing sites) * These are not blockers for small sites, but they are meaningful differentiators for agencies and developers managing content at scale. * So while the current functionality technically exists, improving automation and interoperability would significantly increase the plugin’s value compared to existing solutions. - This reply was modified 5 months, 1 week ago by [panosp](https://wordpress.org/support/users/panosp/). - This reply was modified 5 months, 1 week ago by [panosp](https://wordpress.org/support/users/panosp/). - This reply was modified 5 months, 1 week ago by [panosp](https://wordpress.org/support/users/panosp/). * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Wrong flags in country code at phone section](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [1 year, 11 months ago](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/#post-17878615) * Problem solved. I cleared the cached images and files in the chrome browser and everything is fine.Thank you for your support. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Wrong flags in country code at phone section](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [1 year, 11 months ago](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/#post-17878581) * email with attachments screenshot submitted. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Wrong flags in country code at phone section](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [1 year, 11 months ago](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/#post-17875873) * email submitted ! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Forminator Forms – Contact Form, Payment Form & Custom Form Builder] Wrong flags in country code at phone section](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [1 year, 11 months ago](https://wordpress.org/support/topic/wrong-flags-in-country-code-at-phone-section/#post-17872690) * Here is the export of the form: [https://justpaste.it/fknex](https://justpaste.it/fknex) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce] Email verification after woo order from guest ?](https://wordpress.org/support/topic/email-verification-after-woo-order-from-guest/) * [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [2 years, 7 months ago](https://wordpress.org/support/topic/email-verification-after-woo-order-from-guest/page/4/#post-17144484) * ok * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce] Email verification after woo order from guest ?](https://wordpress.org/support/topic/email-verification-after-woo-order-from-guest/) * [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [2 years, 10 months ago](https://wordpress.org/support/topic/email-verification-after-woo-order-from-guest/#post-16899821) * There is no answer behind that link!! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce] Email verification after woo order from guest ?](https://wordpress.org/support/topic/email-verification-after-woo-order-from-guest/) * [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [2 years, 11 months ago](https://wordpress.org/support/topic/email-verification-after-woo-order-from-guest/#post-16887407) * Same issue ! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Locale Gateways – select bank field – Custom CSS](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [4 years, 1 month ago](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/#post-15559902) * OK this works fine. thank you for your support. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Locale Gateways – select bank field – Custom CSS](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [4 years, 1 month ago](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/#post-15559870) * The code is working but there is no any change to text color “Select bank” * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Locale Gateways – select bank field – Custom CSS](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [4 years, 1 month ago](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/#post-15559830) * The code has a problem: * Message: The code snippet you are trying to save produced a fatal error on line 2: syntax error, unexpected ‘;’, expecting ‘]’ * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Locale Gateways – select bank field – Custom CSS](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/) * Thread Starter [panosp](https://wordpress.org/support/users/panosp/) * (@panosp) * [4 years, 1 month ago](https://wordpress.org/support/topic/locale-gateways-select-bank-field-custom-css/#post-15559718) * Thank you for your quick response. How do I use this?? Is it a Java script? Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/users/panosp/replies/page/2/?output_format=md) [→](https://wordpress.org/support/users/panosp/replies/page/2/?output_format=md)