jsonld@web
jsonld@web:/latitude-and-longitude-converter$  ./latlon --address
tool · running google geocoding api

> latitude and longitude converter

Address in, coordinates out. Plug the result into a LocalBusiness or Organization schema.

Last updated April 18, 2026 by Patrick Coombe

Address Latitude and Longitude Converter Directions: Enter the address of the place that you wish to obtain latitude and longitude coordinates for, and our tool will return both latitude and longitude in text format. You can use a full address or partial address.

In general, most address formats should work including specific addresses, cities, states, zip codes and counties. Sometimes a business name might even work if there is 1 location such as "Elite Strategies" but for others such as "McDonalds" it obviously would not return the correct location.

If you enter a city, zip, county, state etc it will generally return the center most coordinate for that location.

For the purposes of JSON-LD I would always use the full address including zip code. Here are some examples.

      • 33487
      • 551 NW 77th Street Boca Raton FL 33487
      • 33487
      • Boca Raton, FL
      • Florida
      • FL
      • Elite Strategies
      • Palm Beach County, FL
      • United States

 

Use these coordinates in JSON-LD

Once you have your latitude and longitude, plug them into our free JSON-LD Generator under Local Business → Geo Coordinates to produce valid schema markup for your site.

Common reference coordinates. Use the tool above for a precise address lookup, or copy these directly into LocalBusiness or Place schema.

City Latitude Longitude
New York, NY40.7128-74.0060
Los Angeles, CA34.0522-118.2437
Chicago, IL41.8781-87.6298
Houston, TX29.7604-95.3698
Phoenix, AZ33.4484-112.0740
Philadelphia, PA39.9526-75.1652
San Antonio, TX29.4241-98.4936
San Diego, CA32.7157-117.1611
Dallas, TX32.7767-96.7970
Austin, TX30.2672-97.7431
Seattle, WA47.6062-122.3321
Denver, CO39.7392-104.9903
Boston, MA42.3601-71.0589
Atlanta, GA33.7490-84.3880
Miami, FL25.7617-80.1918
Tampa, FL27.9506-82.4572
Boca Raton, FL26.3683-80.1289
Orlando, FL28.5383-81.3792
San Francisco, CA37.7749-122.4194
Las Vegas, NV36.1699-115.1398
Portland, OR45.5152-122.6784
Minneapolis, MN44.9778-93.2650
Detroit, MI42.3314-83.0458
Washington, DC38.9072-77.0369
Honolulu, HI21.3099-157.8581

Using the result in JSON-LD

For LocalBusiness, Place, Restaurant, and similar schema types, geo coordinates go inside a geo object of @type GeoCoordinates:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Cafe",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Main St",
    "addressLocality": "Boca Raton",
    "addressRegion": "FL",
    "postalCode": "33487"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 26.3683,
    "longitude": -80.1289
  }
}

Need help building the rest of the schema? The JSON-LD generator has a LocalBusiness preset with a Geo Coordinates field already wired up.

Common questions

How precise are the coordinates? The Google Geocoding API behind this tool returns rooftop accuracy for most US street addresses. For partial inputs (just a city, ZIP, or state), it returns the centroid of that area, which is usually within a few hundred meters of the geographic center. For schema markup, that level of precision is always sufficient.

What format does Google expect for schema? Decimal degrees as numbers (not strings), with up to 6 decimal places. Negative values for west and south. Example: -80.1289 for Boca Raton longitude, not "80.1289W".

Does this work outside the US? Yes. The geocoder handles addresses in every country Google Maps supports. Try a UK postcode, a Tokyo address, a Mumbai landmark.