{"id":2940,"date":"2026-10-20T08:40:00","date_gmt":"2026-10-20T07:40:00","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/change-geodirectory-language-2\/"},"modified":"2026-10-20T08:40:00","modified_gmt":"2026-10-20T07:40:00","slug":"change-geodirectory-language-2","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/translations\/change-geodirectory-language-2\/","title":{"rendered":"How to change the language of GeoDirectory"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">GeoDirectory uses your WordPress site language. There is no separate language setting in GeoDirectory itself, so to show it in German, Spanish or any other language you change the site language and make sure the translation files are in place.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Change the site language<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to Settings > General in WordPress.<\/li>\n\n\n\n<li>Choose your language in Site Language and save.<\/li>\n\n\n\n<li>Go to Dashboard > Updates and update translations, so WordPress downloads the available language packs for your plugins.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Use your own translation files<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you have your own .po and .mo files, the file names must include the full locale code. GeoDirectory loads files named like this:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>geodirectory-de_DE.mo<\/code> for German<\/li>\n\n\n\n<li><code>geodirectory-es_ES.mo<\/code> for Spanish<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A file named <code>geodirectory-de.mo<\/code> will not load. This is the most common reason a translation seems to be ignored.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Upload custom files to <code>wp-content\/languages\/geodirectory\/<\/code>. GeoDirectory checks that folder first, so files there take priority over language packs and are not overwritten by updates. Add-ons use their own text domains and need their own files.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Text that still shows in English<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Some text is not part of the translation files at all. Widget and block titles you typed yourself, such as a &#8220;Popular Categories&#8221; heading, are saved in your page or widget settings, so edit them there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Map labels come from the map provider. You can set them in GeoDirectory > Settings > General with the Default map language setting (click Show Advanced).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To change a single phrase without translating the whole plugin, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/translations\/how-to-change-just-one-language-string\/\">how to change just one language string<\/a>. For translating everything, see <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/how-to-translate-or-localize-geodirectory\/\">how to translate or localize GeoDirectory<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>GeoDirectory uses your WordPress site language. There is no separate language setting in GeoDirectory itself, so to show it in German, Spanish or any other language you change the site language and make sure the translation files are in place. Change the site language Use your own translation files If you have your own .po [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,434],"class_list":["post-2940","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-translations"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2940","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=2940"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2940\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2940"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2940"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2940"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}