{"id":2343,"date":"2026-10-20T08:32:18","date_gmt":"2026-10-20T07:32:18","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/query-geodirectory-listings-by-field\/"},"modified":"2026-10-20T08:39:39","modified_gmt":"2026-10-20T07:39:39","slug":"query-geodirectory-listings-by-field","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/api\/query-geodirectory-listings-by-field\/","title":{"rendered":"How to query GeoDirectory listings by city, zip or other fields"},"content":{"rendered":"\n

A WP_Query<\/code> with a meta_query<\/code> won’t find GeoDirectory listings by address or custom fields, because GeoDirectory doesn’t store them as post meta. Each post type has its own table, such as wp_geodir_gd_place_detail<\/code>, with one row per listing and one column per field (city<\/code>, region<\/code>, zip<\/code>, your custom fields and so on).<\/p>\n\n\n\n

Read fields for one listing<\/h2>\n\n\n\n

On a listing page the global $gd_post<\/code> already holds every field. For any other listing, use the helper functions:<\/p>\n\n\n\n

global $gd_post;\n$zip = $gd_post->zip;\n\n\/\/ Or for a specific listing ID.\n$zip  = geodir_get_post_meta( $post_id, 'zip', true );\n$info = geodir_get_post_info( $post_id ); \/\/ Object with all fields.<\/code><\/pre>\n\n\n\n
Find listings that match a field<\/h2>\n\n\n\n
Join the posts table to the detail table. geodir_db_cpt_table()<\/code> returns the right table name for a post type:<\/p>\n\n\n\n
global $wpdb;\n\n$table = geodir_db_cpt_table( 'gd_place' );\n\n$count = (int) $wpdb->get_var(\n\t$wpdb->prepare(\n\t\t"SELECT COUNT(p.ID) FROM {$wpdb->posts} p\n\t\tINNER JOIN {$table} d ON d.post_id = p.ID\n\t\tWHERE p.post_type = %s AND p.post_status = 'publish' AND d.zip = %s",\n\t\t'gd_place',\n\t\t'11949'\n\t)\n);<\/code><\/pre>\n\n\n\n
Swap d.zip<\/code> for d.city<\/code>, d.region<\/code> or the key of any custom field, and use SELECT p.ID<\/code> with $wpdb->get_col()<\/code> when you want the IDs instead of a count.<\/p>\n\n\n\n
Show the results in the usual listings layout<\/h2>\n\n\n\n
You don’t need to write your own HTML. Pass the IDs to the GD > Listings shortcode with post_ids<\/code>. This example adds a [my_same_zip_places]<\/code> shortcode that you can place on the Details page template to list other places with the same zip code:<\/p>\n\n\n\n
add_shortcode( 'my_same_zip_places', function () {\n\tglobal $wpdb, $gd_post;\n\n\tif ( empty( $gd_post->zip ) ) {\n\t\treturn '';\n\t}\n\n\t$table = geodir_db_cpt_table( 'gd_place' );\n\n\t$ids = $wpdb->get_col(\n\t\t$wpdb->prepare(\n\t\t\t"SELECT p.ID FROM {$wpdb->posts} p\n\t\t\tINNER JOIN {$table} d ON d.post_id = p.ID\n\t\t\tWHERE p.post_type = 'gd_place' AND p.post_status = 'publish'\n\t\t\tAND d.zip = %s AND p.ID != %d",\n\t\t\t$gd_post->zip,\n\t\t\t$gd_post->ID\n\t\t)\n\t);\n\n\tif ( empty( $ids ) ) {\n\t\treturn '';\n\t}\n\n\t$ids = implode( ',', array_map( 'absint', $ids ) );\n\n\treturn do_shortcode( '[gd_listings post_type="gd_place" post_limit="20" post_ids="' . $ids . '"]' );\n} );<\/code><\/pre>\n\n\n\n
If you only need the standard filters (category, tags, author, featured and so on), the GD > Listings<\/a> widget can do it without any code. For remote access there’s also the GeoDirectory REST API<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
A WP_Query with a meta_query won’t find GeoDirectory listings by address or custom fields, because GeoDirectory doesn’t store them as post meta. Each post type has its own table, such as wp_geodir_gd_place_detail, with one row per listing and one column per field (city, region, zip, your custom fields and so on). Read fields for one […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[882,883],"class_list":["post-2343","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-api","gd_placecategory-developer-docs"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2343","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=2343"}],"version-history":[{"count":2,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2343\/revisions"}],"predecessor-version":[{"id":2611,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2343\/revisions\/2611"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2343"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2343"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2343"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}