{"id":708,"date":"2025-03-24T14:27:28","date_gmt":"2025-03-24T14:27:28","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/understanding-expired-and-closed-listings\/"},"modified":"2025-04-03T15:23:48","modified_gmt":"2025-04-03T14:23:48","slug":"understanding-expired-and-closed-listings","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/explore-settings\/understanding-expired-and-closed-listings\/","title":{"rendered":"Understanding &#8220;Expired&#8221; and &#8220;Closed&#8221; Listings"},"content":{"rendered":"<p>\n\tGeoDirectory adds two custom post statuses for all CPTs &#8212; <strong>Expired <\/strong>and <strong>Closed. <\/strong>Each of these statuses is different from the other. This article will explain the basic differences between the two.&nbsp;<\/p>\n<h2>Expired Listings<\/h2>\n<p>\n\tSimply put, an &#8220;expired&#8221; listing is one which is time-sensitive in nature. After a particular date, it will &#8220;expire&#8221; and no longer be available for active usage.&nbsp;<\/p>\n<section class=\"alert alert-info\">\n\tExpired listings are ideal if you wish to add listings under a paid package using the <a href=\"https:\/\/wpgeodirectory.com\/downloads\/pricing-manager\/\">Pricing Manager<\/a> extension. You can set listings to expire when their package expires.&nbsp;<\/section>\n<p>\n\tThat said, <strong>even after a given listing &#8220;expires&#8221;, it is not deleted by GeoDirectory.<\/strong> Instead, it remains published, but users can see that it has expired. Administrators can delete the listing from the backend.&nbsp;<\/p>\n<p> <strong>Expired listings do not show up in the GD loop or archives.<\/strong> However, the Listing Details (single listing view) page can still be viewed for expired listings, unless it is disabled or deleted by an administrator.&nbsp;<\/p>\n<h2>Closed Listings<\/h2>\n<p>\n\tClosed Listings are also similar to Expired ones, as these do not show up in the GD loop or archive pages either.&nbsp;<\/p>\n<p>\n\tHowever, a &#8220;closed&#8221; listing is one that might have shut shop or closed down &#8212; such listings are generally not time-sensitive as these are not set to expire on a given date.&nbsp;<\/p>\n<h2>\nWhy doesn&#8217;t GeoDirectory simply delete Expired or Closed Listings?&nbsp;<\/h2>\n<p>\n\tThe GD loop and archives only show listings with post status set to &#8220;Published&#8221;. This naturally excludes Drafts, Pending, Expired and Closed listings. As such, why not simply delete expired or closed listings?&nbsp;<\/p>\n<p>\n\tThere are two reasons why we do not delete expired\/closed listings.&nbsp;<\/p>\n<p>\n\tFirst,<strong> SEO.<\/strong> Search engines may have indexed Listing Details pages for such listings, and 404 errors (after deletion of such pages) may adversely affect the overall SEO health.&nbsp;<\/p>\n<p>\n\tSecondly, certain site owners might want to <strong>renew listings<\/strong> as and when they expire. As such, deleting expired listings is not recommended.&nbsp;<\/p>\n<p>\n\tAdmins can, obviously, delete or trash any listing irrespective of its status from the WP backend.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>GeoDirectory adds two custom post statuses for all CPTs &#8212; Expired and Closed. Each of these statuses is different from the other. This article will explain the basic differences between the two.&nbsp; Expired Listings Simply put, an &#8220;expired&#8221; listing is one which is time-sensitive in nature. After a particular date, it will &#8220;expire&#8221; and no [&hellip;]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[517,518],"article\/categories":[208,396],"class_list":["post-708","gd_place","type-gd_place","status-publish","hentry","gd_place_tags-expired-listings","gd_place_tags-closed-listings","gd_placecategory-getting-started","gd_placecategory-explore-settings"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/708","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"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=708"}],"version-history":[{"count":0,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/708\/revisions"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=708"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=708"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}