{"id":2588,"date":"2026-10-20T08:35:19","date_gmt":"2026-10-20T07:35:19","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/remove-something-missing-why-not-add-a-listing\/"},"modified":"2026-10-20T08:39:38","modified_gmt":"2026-10-20T07:39:38","slug":"remove-something-missing-why-not-add-a-listing","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/how-tos\/remove-something-missing-why-not-add-a-listing\/","title":{"rendered":"How to remove &#8220;Something missing? Why not add a listing?&#8221; from GeoDirectory search results"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">When a search or category has no results, GeoDirectory shows &#8220;No listings were found matching your selection. Something missing? Why not add a listing?&#8221;. The second sentence only appears when visitors are allowed to add listings from the front end. You can drop it in three ways.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Turn off front end adding<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you do not let visitors submit listings, this is the cleanest fix. GeoDirectory then shows only &#8220;No listings were found matching your selection.&#8221;<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Go to Places &gt; Settings &gt; General.<\/li>\n\n\n\n<li>Show the advanced settings with the toggle at the top of the page.<\/li>\n\n\n\n<li>Tick <em>Disable frontend add<\/em> and save.<\/li>\n\n\n\n<li>Repeat for every other post type you have. The message links to any post type that still allows adding, so all of them need the setting.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Change the message with a snippet<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This keeps front end adding on and replaces the whole message. Add it with the <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/useful-plugins\/code-snippets-plugin\/\">Code Snippets plugin<\/a> or your child theme&#8217;s functions.php:<\/p>\n\n\n\n<pre class=\"wp-block-prismatic-blocks\"><code class=\"language-php\">add_filter( &#039;geodir_no_listings_found_message&#039;, &#039;my_gd_no_listings_message&#039;, 10, 2 );\nfunction my_gd_no_listings_message( $message, $post_type ) {\n\treturn __( &#039;No listings were found matching your selection.&#039;, &#039;geodirectory&#039; );\n}<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Translate the string<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The text is one translatable string, so you can also replace it with a translation tool such as Loco Translate or Poedit. Search for the full string, which contains a link placeholder, and translate it to just the first sentence. <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/translations\/how-to-change-just-one-language-string\/\">How to change just one language string<\/a> walks through it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hiding it with CSS is possible but the whole notice shares one element, so <code>.geodir-info<\/code> hides the &#8220;No listings were found&#8221; part as well.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a search or category has no results, GeoDirectory shows &#8220;No listings were found matching your selection. Something missing? Why not add a listing?&#8221;. The second sentence only appears when visitors are allowed to add listings from the front end. You can drop it in three ways. Turn off front end adding If you do [&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-2588","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\/2588","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=2588"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2588\/revisions"}],"predecessor-version":[{"id":2771,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2588\/revisions\/2771"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2588"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2588"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2588"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}