{"id":2642,"date":"2026-10-20T08:35:23","date_gmt":"2026-10-20T07:35:23","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/places-listings-page-as-homepage\/"},"modified":"2026-10-20T08:40:20","modified_gmt":"2026-10-20T07:40:20","slug":"places-listings-page-as-homepage","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/places-listings-page-as-homepage\/","title":{"rendered":"How to use the \/places\/ listings page as your homepage"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">WordPress can only use a page as the front page (Settings > Reading), and the \/places\/ listings page is a post type archive, not a page. GeoDirectory has no setting to put that archive on the front page. You can get the same result in one of two ways.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Build a home page with the same widgets<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The \/places\/ archive uses GD > Loop, which only works on the archive template. On an ordinary page, use GD > Listings in its place.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a new page.<\/li>\n\n\n\n<li>Add a GD > Search if you want a search bar.<\/li>\n\n\n\n<li>Add a GD > Map and set Filter by tags to <code>.geodir-listings<\/code>. With a CSS class in that setting, the map only shows markers for the listings on the page, the same way the archive map does.<\/li>\n\n\n\n<li>Add a GD > Listings for your post type with the sort order, number of listings and pagination you want.<\/li>\n\n\n\n<li>Go to Settings > Reading, choose A static page and select your new page as the homepage.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">As shortcodes, a page that lists places A to Z, ten per page, with a matching map looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-prismatic-blocks\"><code class=\"language-php\">&#091;gd_map width=&quot;100%&quot; height=&quot;425px&quot; tags=&quot;.geodir-listings&quot;&#093;\n&#091;gd_listings post_type=&quot;gd_place&quot; sort_by=&quot;az&quot; post_limit=&quot;10&quot; with_pagination=&quot;1&quot;&#093;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">More on the map setting: <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/extensions-features\/showing-filtered-list-of-listings-in-a-special-map\/\">Showing a filtered list of listings in a special map<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Redirect the homepage to \/places\/<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you want visitors to land on the archive itself, redirect the front page with a redirect plugin or this snippet:<\/p>\n\n\n\n<pre class=\"wp-block-prismatic-blocks\"><code class=\"language-php\">add_action( &#039;template_redirect&#039;, function() {\n\tif ( is_front_page() ) {\n\t\twp_safe_redirect( home_url( &#039;\/places\/&#039; ), 302 );\n\t\texit;\n\t}\n} );<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Change \/places\/ if your post type uses a different slug. With a redirect, your home URL has no content of its own, so the first option is usually better for search engines.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>WordPress can only use a page as the front page (Settings > Reading), and the \/places\/ listings page is a post type archive, not a page. GeoDirectory has no setting to put that archive on the front page. You can get the same result in one of two ways. Build a home page with the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,432],"class_list":["post-2642","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-how-tos"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2642","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=2642"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2642\/revisions"}],"predecessor-version":[{"id":2799,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2642\/revisions\/2799"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2642"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2642"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}