Title: Search Issues
Last modified: August 30, 2016

---

# Search Issues

 *  Resolved [MelmoSA](https://wordpress.org/support/users/melmosa/)
 * (@melmosa)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/search-issues-2/)
 * Good day, we are using version 2.0.3
 * We are having issues with our store locator search. We are in South Africa and
   our region in the settings is set to that. When we search for one of our stores
   it comes up with “No results found” even though there is a store in the area.
   The area in this case is Ceres, Western Cape. If we search surrounding areas 
   it does find the store but not if we search the specific area that it is in.
 * Upon reviewing the Documentation on your site specifically [http://wpstorelocator.co/document/searched-location-never-returns-results/](http://wpstorelocator.co/document/searched-location-never-returns-results/)
   we tested the API results from Google. We have found that when we search Ceres
   in the API it returns 2 results but the first being in a location in Argentina.
   I suspect this is why the plugin will not find results on our website. Is this
   the case? If so, how do we correct or fix it as it is paramount that we are able
   to search for the location Ceres and return the results on our website. Here 
   are our API tests:
 * Search Ceres in ZA (South Africa)
    [https://maps.googleapis.com/maps/api/geocode/json?address=ceres&sensor=false&region=za](https://maps.googleapis.com/maps/api/geocode/json?address=ceres&sensor=false&region=za)
 * Search Cape Town in ZA (South Africa)
    [https://maps.googleapis.com/maps/api/geocode/json?address=cape-town&sensor=false&region=za](https://maps.googleapis.com/maps/api/geocode/json?address=cape-town&sensor=false&region=za)
 * Search Durban in ZA (South Africa)
    [https://maps.googleapis.com/maps/api/geocode/json?address=durban&sensor=false&region=za](https://maps.googleapis.com/maps/api/geocode/json?address=durban&sensor=false&region=za)
 * Thank You 🙂
 * [https://wordpress.org/plugins/wp-store-locator/](https://wordpress.org/plugins/wp-store-locator/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Lisa Cerezo](https://wordpress.org/support/users/lisathirdsideco/)
 * (@lisathirdsideco)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/search-issues-2/#post-6757104)
 * I don’t know if this will help you at all, but I was having the same issue and
   just figured out what happened. Our “home” setting is Springfield, Illinois (
   USA) and all of our listings are in the state of Illinois. However, if I were
   to just type “Springfield” without specifying the state, it defaulted to Springfield,
   Missouri and never found any of our listings in Illinois, no matter how wide 
   a search radius we specified. Worked perfectly as soon as we put both “Springfield”
   and “Illinois” in the search box. Could there be another area near you with the
   same name?
 * Good luck!
 *  Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/)
 * (@tijmensmit)
 * [10 years, 6 months ago](https://wordpress.org/support/topic/search-issues-2/#post-6757142)
 * The only solution in cases like this is to include the [state](https://maps.googleapis.com/maps/api/geocode/json?address=ceres,%20Western%20Cape&sensor=false&region=za)
   as well in the search query.
 * But I think it’s a bit weird the Google API ignores the region parameter, and
   returns results for Argentina first. So I will look into this a bit more, there
   has to be a better way to get this to work, especially if the region is set to
   South Africa.
 *  Plugin Author [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/)
 * (@tijmensmit)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/search-issues-2/#post-6757286)
 * [@melmosa](https://wordpress.org/support/users/melmosa/) I found a better solution,
   at least in case when the location you search for is located in multiple countries.
 * The Google docs mentions this:
 * > Note that biasing only prefers results for a specific domain; if more relevant
   > results exist outside of this domain, they may be included.
 * In this case the geocoder feels the result in Argentina is more relevant, even
   though you set the bias to South Africa. But I found another option you can use
   that will restrict the returned results to a single country. I tested it with
   Ceres, and when I enable it, and set it to South Africa then it returns the expected
   result.
 * [With](https://maps.googleapis.com/maps/api/geocode/json?address=ceres&components=country:za)
   and [without](https://maps.googleapis.com/maps/api/geocode/json?address=ceres)
   the new option.
 * So I will add the option to restrict the search results to a single country in
   the 2.1 update. That will fix the problem when the location is in another country.
 * [@lisa](https://wordpress.org/support/users/lisa/) thirdside I haven’t had time
   to test it, but it looks like it’s also possible to restrict the returned results
   by state. If this is possible, then I will place an article on the website explaining
   how to do this after 2.1 is released.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Search Issues’ is closed to new replies.

 * ![](https://ps.w.org/wp-store-locator/assets/icon-256x256.jpg?rev=1007784)
 * [WP Store Locator](https://wordpress.org/plugins/wp-store-locator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-store-locator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-store-locator/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-store-locator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-store-locator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-store-locator/reviews/)

## Tags

 * [no results found](https://wordpress.org/support/topic-tag/no-results-found/)

 * 3 replies
 * 3 participants
 * Last reply from: [Tijmen Smit](https://wordpress.org/support/users/tijmensmit/)
 * Last activity: [10 years, 5 months ago](https://wordpress.org/support/topic/search-issues-2/#post-6757286)
 * Status: resolved