Define and visualize service areas on an interactive map. Draw polygons, set radius zones, and export area data for local SEO pages.
A local business's coverage area usually lives in someone's head, not in a format a website can use. This tool captures it: drop a center point and pick a radius, or trace a custom polygon on the map, and it records the coordinates, measures the area, and exports the shape as GeoJSON for embedded maps and as Schema.org JSON-LD for the structured data on local SEO pages. The usual surprise is geometric: a radius zone is straight-line distance, so a 10-mile circle often includes areas that are 25 minutes of driving away.
A concrete input and expected output from the current implementation.
Input
Center: 40.7128, -74.0060 (New York, NY) Radius: 5 miles
Expected output
Zone type: radius Center: 40.7128, -74.0060 Radius: 5 mi Area: 78.5 sq mi Bounding box: SW (40.6403, -74.1016), NE (40.7853, -73.9104) Exports: GeoJSON polygon, JSON-LD areaServed
A 5-mile radius around that center gives area pi x 5^2 = 78.5 sq mi. The bounding box shifts the center by the radius converted to degrees: 5/69 of latitude and 5/(69 x cos 40.71 degrees) of longitude, because a degree of longitude narrows as latitude rises; the GeoJSON export is a polygon built from that circle, while the JSON-LD records the center and radius as GeoCircle properties.
The shape is exported twice from the same coordinates. The GeoJSON variant is a feature with a coordinate array, ready for a map embed. The JSON-LD variant expresses the same shape as Schema.org markup: a GeoPolygon for hand-drawn shapes, a GeoCircle for radius zones, whose center and radius are separate properties. Both describe the identical boundary, so the map and the markup agree.
A radius zone stores only a center point and a distance; its area is pi times the radius squared, 78.5 square miles for a 5-mile radius. Because GeoJSON has no circle primitive, the exported boundary is a polygon of many short straight segments. A hand-drawn polygon stores its vertex list instead, and its area is computed from those vertices, so it has no single radius value.
Structured data states your coverage to search engines; it is not a ranking lever by itself. The export is worth publishing because it describes the territory unambiguously and may qualify the page for rich results, but the page still needs real content about each town, and the boundary should only include areas the business can actually serve.
GeoJSON, the export format, only defines points, lines, and polygons, so a radius zone has to be converted into a polygon built from short line segments before it can be written out. The segments are dense enough that the shape looks round on a normal map; only heavy zoom reveals the flat edges.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Shorten URLs with local redirect tracking via localStorage. See click counts and generate a QR code for each link.
Build UTM-tagged URLs for campaign tracking with source, medium, campaign, term, and content parameters.
Enter 2+ headlines and see simulated previews in Google results, email subject lines, and social posts side-by-side.
Count characters for Twitter/X, LinkedIn, Facebook, and Instagram with platform-specific limits and warnings.
Calculate click-through rates from impressions and clicks with industry benchmarks and trend analysis.
Check email subject line length against best practices for desktop and mobile with preview text optimization.