Google Maps Timeline wrong location: what to fix first

Separate a wrong Timeline entry from a wrong live blue dot

A Google Maps Timeline wrong location can mean two different things. The live blue dot may be inaccurate now, or a saved Timeline day may name the wrong place. Fixing current location access can improve future recording, but it does not rewrite an old route. Start by checking which screen is wrong.

If the live blue dot is gray, missing, or surrounded by a wide light-blue circle, Google Maps is uncertain about the current position. If the blue dot is accurate but yesterday's Timeline lists a nearby restaurant, treat it as a saved Timeline entry that needs review.

Check location access and signal quality

Do not change several privacy or battery settings and then assume the last change fixed the history. Test the live blue dot first, record what changed, and review the next journey in Timeline.

1. On Android: Turn on device Location Accuracy and allow Google Maps to use location. Turn off Battery Saver while testing.
2. On iPhone or iPad: Turn on Location Services for Google Maps. Google's current guidance says Timeline works best with access set to Always. Turn off Low Power Mode while checking a jumping position.
3. Check connectivity: Keep mobile data or Wi-Fi on and make sure Airplane mode is off.
4. Move into a clearer area: Leave a parking garage, tunnel, or dense indoor space before judging the result. Weak GPS and Wi-Fi signals can make the position coarse even when every permission looks correct.

Calibrate Maps before collecting another trip

The light-blue circle around the blue dot is useful evidence. A smaller circle means Maps is more certain. Tap a low-accuracy message for the suggested fix. Google may offer Lens calibration or compass calibration. Restart the phone if the location remains wrong.

Google explains that Maps estimates location from GPS, nearby Wi-Fi networks, and cell towers. GPS can be accurate to roughly 20 meters in favorable conditions, but it is often worse indoors or underground. A cell-tower estimate can be far coarser. A calibration can improve the current reading; it cannot recover samples that were never saved.

Edit the wrong place and time in Timeline

When the historical day contains the wrong venue, edit that entry in the Google Maps app. Google specifically notes that dense urban areas can cause Timeline to choose one restaurant when the person visited another nearby. Correcting the place and time is more reliable than asking a video tool to infer the venue from one coordinate.

Timeline lets you choose whether edits and related data are shared with Google to improve Maps. Review that control in My Google Activity if it matters to you. Also remember that edits on one device may not appear on another device, so export from the device where you confirmed the correction.

1. Open the day. In Google Maps, open Your Timeline, tap Edit, and choose Edit day.
2. Select the entry. Scroll to the incorrect visit.
3. Correct the place. Choose a place from the dropdown or search for the correct one.
4. Correct the time. Tap the entry time if it also needs adjustment, then save it and tap Done.
5. Remove a false interval if necessary. Google also provides a Remove action for an incorrect time period.

Handle wrong transport modes and straight lines

A wrong transport mode, a straight line between stops, and a completely missing visit are related symptoms but not identical data. If Google Maps offers an edit control for the recorded activity, use it there. If the samples between two visits are absent, changing a label cannot reconstruct the path, distance, or departure time.

Do not smooth an impossible jump and present it as fact. For a story video, exclude the bad interval or describe the date range as partial. Endpoint privacy removal is not an accuracy repair; it deliberately removes sensitive points and should not be used to hide unexplained errors.

What community reports add to the picture

Community reports show the range of symptoms, not their prevalence. One Pixel 9 Pro XL poster described wrong places, wrong times, wrong transport modes, and missing visits in the same week. Replies mentioned highway travel labeled as walking, straight-line commutes, and short errands that disappeared.

One reply cut against the pattern: Timeline became much better while another app was actively using GPS. Background sampling or power management may have contributed on that device, but the reply does not establish a general cause. It also does not show that the phone model itself was defective.

A later Pixel discussion reported slower loading and less detailed history after the move to device storage. Commenters disagreed about whether recording itself had become less accurate or older data had been consolidated. That explanation is a community hypothesis, not a statement from Google. A separate editing report had only one reply, so it is weak corroboration.

Reddit threads attract users with problems, and posters cannot verify one another's permissions, signal conditions, or account state. They support a practical testing checklist, not a claim that all Pixel or iPhone users have inaccurate Timeline data.

Export and inspect the corrected date

Once the date looks correct in Google Maps, export a new file from that same device. On Android, use Settings, Location, Location services, Timeline, and Export Timeline data. On iPhone or iPad, use Google Maps, Profile, Settings, Location & Privacy, and Export Timeline data. Keep the original file unchanged.

Use the local JSON viewer to verify the date coverage and inspect outlier warnings before loading map tiles. Timeline to Video excludes invalid coordinates and can flag suspicious jumps. It does not name an unknown venue, manufacture missing points, or convert an uncertain activity into a confident transport mode.

Leave an unresolved wrong location out of the video

If the wrong interval remains, leave it outside the selected video range. A shorter route that matches the source is more useful than a polished animation of a trip the file never recorded accurately.