geo

geo · Recommended

Appears in

LocalBusiness

What is it?

The geographic coordinates (latitude and longitude) of a physical business location. The geo field gives search engines and mapping services a precise pin-drop location, independent of the street address. This is especially important for businesses in areas where addresses are ambiguous, newly developed, or shared across multiple tenants in a large building.

Why this matters for AEO

When a user asks "How far is [business] from me?" or "Find [business type] near [location]," AI engines use geo coordinates to calculate distance and determine proximity. Without coordinates, the AI relies on geocoding the street address, which can be imprecise for rural locations, shopping centers, or buildings with multiple businesses.

What the specs say

Schema.org: GeoCoordinates, GeoShape. The geo coordinates of the place. schema.org/geo

Google: Recommended. "Geographic coordinates of the business." Google LocalBusiness docs

How to find your value

• Google Maps — Right-click your location on Google Maps > the coordinates appear at the top of the context menu
• Google Business Profile — Check your GBP listing pin location
• GPS app — Use any GPS app at the physical location
• Geocoding service — Enter your address into Google Maps Geocoding API or similar

Google recommends latitude values with at least 5 decimal places for precision (e.g., 37.39368, not 37.39).

Format and code

Use a GeoCoordinates object with latitude and longitude as numbers or strings.

{
  "@type": "GeoCoordinates",
  "latitude": 33.6405,
  "longitude": -117.8443
}

Full LocalBusiness example:

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Gene's Delicious Donuts",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Happy Lane",
    "addressLocality": "Irvine",
    "addressRegion": "CA",
    "postalCode": "92618"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": "40.75",
    "longitude": "73.98"
  }
}

Common invalid format (do not use a plain string):

{
  "geo": "40.75, 73.98"
}

Webflow implementation

Static pages

Hardcode the coordinates in your JSON-LD block. Look up the exact lat/long once and paste them in.

CMS template pages

Create two number fields in your CMS collection (Latitude and Longitude) and reference them:

"geo": {
  "@type": "GeoCoordinates",
  "latitude": "{{wf {"path":"latitude"} }}",
  "longitude": "{{wf {"path":"longitude"} }}"
}

In Schema HQ

The full geocoordinates object and publishes it as part of your localbusiness schema. enter coordinates once in the location settings.

Real examples

Gene's Delicious Donuts (from Whitespark LocalBusiness guide):

"geo": {
  "@type": "GeoCoordinates",
  "latitude": "40.75",
  "longitude": "73.98"
}

Note: The precision in this example (2 decimal places) is below Google's recommendation of 5+ decimal places. Production implementations should use full precision coordinates like 40.75032 and -73.98456.

Related fields

• address · the street address that geo coordinates supplement
• name · the business this location belongs to
• url · the website for this business location

FAQ

Is geo required for LocalBusiness?

Google lists geo as Recommended, not Required. However, including coordinates significantly improves accuracy for local search results and map-based queries. For businesses in areas with poor address geocoding, geo is effectively essential.

What precision should I use for latitude and longitude?

Use at least 5 decimal places (e.g., 37.39368). Five decimal places provide accuracy to approximately 1.1 meters, which is sufficient for pinpointing a building. Two decimal places (37.39) only narrow the location to about 1.1 kilometers.

Should longitude values be negative for Western Hemisphere locations?

Yes. Locations west of the Prime Meridian (the Americas) use negative longitude values. For example, New York City is approximately latitude 40.7128, longitude -74.0060.