Short answer: Google Takeout is an account backup, so its file has no usable latitude and longitude. Google's own systems look up the location from names and Plus Codes. Paste your list's share link into the converter above to get real coordinates as GPX, KML, GeoJSON or CSV.
Why does Google Takeout leave out coordinates?
If you've ever exported a Google Maps list through Takeout hoping for a clean file of coordinates, you've probably found the opposite: a JSON or CSV full of place names, sometimes a Plus Code, and no usable latitude/longitude column you can hand to a GPS device.
That's not a bug you're hitting by accident, it's just how Takeout was built. Takeout is designed to back up your account data, not to produce a navigation-ready waypoint file. The place records it exports are meant to be read by Google's own systems, which already know how to resolve a name or a Plus Code back into a location. Your Garmin, your offline hiking app, or your GPX-reading device doesn't have that lookup step, it just needs the number.
What do people do instead, and why does it fall short?
So people end up doing one of two things: manually looking up and typing in coordinates for every single pin (fine for 3 places, brutal for 30), or running the export through a third-party geocoder that guesses at coordinates from the place name and sometimes gets it wrong, landing you a few hundred meters from the actual pin, which matters a lot more on a trail than it does in a browser.
How do I get real coordinates from a Google Maps list?
MapsLinkQuest skips the export step entirely. Instead of asking Google for a backup file and then trying to reverse-engineer coordinates out of it, MapsLinkQuest reads the actual shared list page, the same page your pins are already rendered on, and pulls the real coordinates directly from it. No Takeout, no geocoding guesswork, no missing lat/long column. Paste your list link, get a GPX or KML file with every pin's real position, ready for Garmin, Gaia GPS, OnX, or any GPX-reading app.