Thanks for the replySteve Branson! I haven't found a solution either since my post. I've increased the accuracy required for a match to eliminate some of the results, but the issue is still there. I haven't put in a support ticket yet, but answering Kelly Gerrow's questions: it's a composite locator published as a geocoding service hosted on our own ArcGIS Server. I don't have local search enabled on the widget, because I originally thought that was the issue. Here's my app: Districts of Washtenaw County, MI . I've had users complain about incorrect political districts when I had the search bar within the Near Me widget because they wouldn't look at the result on the map and get 123 Main St locating to a different city than intended. I've now moved the address search out of the widget so they're forced to click on the map to use the Near Me widget, which hopefully forces them to validate the result if they use the address locator. The specific example I mentioned before is if you type in "6655 JACKSON RD" in my search bar, don't click the magnifying glass (like VillageDG was saying), and just click the first result that automatically appears "6655 JACKSON RD (VAC)", you get that No results error message.