# Places - entry points for Google links

**URL:** https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298
**Category:** United Kingdom
**Created:** [March 22, 2021, 10:38am UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298 "2021-03-22T10:38:19Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![titchy](https://www.waze.com/discuss/user_avatar/www.waze.com/titchy/32/79030_2.png) [@titchy](https://www.waze.com/discuss/u/titchy)
#### Post date: [March 22, 2021, 10:38am UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/1 "2021-03-22T10:38:19Z")

</div>

Is there a reason why the entry point for a Google place that is linked to the Waze place is different? Surely the point of the link is that the Google result links back to the Waze place?

[This place](https://www.waze.com/editor/?env=row&lon=-1.44392&lat=53.38351&zoom=6&venues=235012630.-1945103142.3403344) has an entry point set to the PLR leading to the front door. If the user selects the Waze place from their search result they will be directed here. But, if they select the Google result (which is linked) the will be directed past the ramp leading into the retail park. Why doesn’t the Google result link to the Waze entry point?

Sorry if this is a known issue which I’ve not been aware of.

---

<div class="post-metadata">

### Author: ![Keith\_KJ](https://www.waze.com/discuss/user_avatar/www.waze.com/keith_kj/32/78885_2.png) [@Keith\_KJ](https://www.waze.com/discuss/u/Keith_KJ)
#### Post date: [March 22, 2021, 10:41am UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/2 "2021-03-22T10:41:42Z")

</div>

It’s the same for me. Are you sure you’re they’re picking up an old cache/saved location? Ask them to delete their saved entry from the recent list and do a new search, which should then pickup the linked nav point.

---

<div class="post-metadata">

### Author: ![titchy](https://www.waze.com/discuss/user_avatar/www.waze.com/titchy/32/79030_2.png) [@titchy](https://www.waze.com/discuss/u/titchy)
#### Post date: [March 22, 2021, 10:53am UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/3 "2021-03-22T10:53:09Z")

</div>

They could be, but I’ve tested this myself on the app and it’s the same.

---

<div class="post-metadata">

### Author: ![Kevintiobraid](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/k/FF5252/32.png) [@Kevintiobraid](https://www.waze.com/discuss/u/Kevintiobraid)
#### Post date: [March 22, 2021, 11:54am UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/4 "2021-03-22T11:54:50Z")

</div>

If they are using Android Auto, it could also be due to the results from this. I’ve found AA searches to be hit and miss over the past few weeks, sometimes it only gives you the Google result which would result in incorrect routing.

---

<div class="post-metadata">

### Author: ![titchy](https://www.waze.com/discuss/user_avatar/www.waze.com/titchy/32/79030_2.png) [@titchy](https://www.waze.com/discuss/u/titchy)
#### Post date: [March 22, 2021, 1:59pm UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/5 "2021-03-22T13:59:44Z")

</div>

Yeah the query was more why doesn’t it link to the Waze result and therefore entry point. Otherwise I’m failing to see the point of the link if it’s a case of we need to make sure we select Waze places when searching.

---

<div class="post-metadata">

### Author: ![Kevintiobraid](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/k/FF5252/32.png) [@Kevintiobraid](https://www.waze.com/discuss/u/Kevintiobraid)
#### Post date: [March 22, 2021, 6:09pm UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/6 "2021-03-22T18:09:31Z")

</div>

Do you mean if you select “more results” then select the “Google” tab in the search window? If you do that, then you are forcing Waze to navigate to the Google point, regardless of whether its linked to a Waze place or not.

---

<div class="post-metadata">

### Author: ![titchy](https://www.waze.com/discuss/user_avatar/www.waze.com/titchy/32/79030_2.png) [@titchy](https://www.waze.com/discuss/u/titchy)
#### Post date: [March 22, 2021, 8:13pm UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/7 "2021-03-22T20:13:42Z")

</div>

That’s right. So, forgive my ignorance but the point of the link is? I always thought it was for when someone selects a Google place from wherever it then links back to the Waze place.

It’s the same on the LiveMap which I understand is Google results.

---

<div class="post-metadata">

### Author: ![Kevintiobraid](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/k/FF5252/32.png) [@Kevintiobraid](https://www.waze.com/discuss/u/Kevintiobraid)
#### Post date: [March 22, 2021, 8:59pm UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/8 "2021-03-22T20:59:10Z")

</div>

Yes, thats the point of linking the Google place. If you search for a place, the Google result will appear on the first page as you type. E.g. If I search for “Matalan Sheffield” (but don’t press the “more results”) then I get the Google result “Matalan, Cricket Inn Road, Sheffield”. If I click on this then I am presented with the Waze place, because it has been linked in WME. This is how I search on Waze, and I guess how most people do.  
To force Waze to send you to the Google place, you would need to tap on “more results” and then tap on the “Google” tab, which most people won’t do

---

<div class="post-metadata">

### Author: ![Kevintiobraid](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/k/FF5252/32.png) [@Kevintiobraid](https://www.waze.com/discuss/u/Kevintiobraid)
#### Post date: [March 22, 2021, 9:07pm UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/9 "2021-03-22T21:07:23Z")

</div>

Btw, you can tell whether its a Google or Waze result if the pin colour is blue (waze) or white (Google)

![](https://i.imgur.com/IFiw8co.png?1)

---

<div class="post-metadata">

### Author: ![titchy](https://www.waze.com/discuss/user_avatar/www.waze.com/titchy/32/79030_2.png) [@titchy](https://www.waze.com/discuss/u/titchy)
#### Post date: [March 23, 2021, 8:25am UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/10 "2021-03-23T08:25:50Z")

</div>

Cheers Kevin. I knew about how the search works, I just didn’t realise that even when deliberately selecting a Google result it didn’t still link back to the Waze one. Every day’s a school day.

---

<div class="post-metadata">

### Author: ![atrophicshiner](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/a/1BAB50/32.png) [@atrophicshiner](https://www.waze.com/discuss/u/atrophicshiner)
#### Post date: [March 23, 2021, 3:08pm UTC](https://www.waze.com/discuss/t/places-entry-points-for-google-links/127298/11 "2021-03-23T15:08:44Z")

</div>

> [@Kevintiobraid](#):
>
> Btw, you can tell whether its a Google or Waze result if the pin colour is blue (waze) or white (Google)

Only if you are running in debug mode.
