Geo-Tagging SOP — Image and Content Geographic Signal Embedding

Why Geo-Tagging Matters for Local SEO

Google's image recognition systems extract location signals from multiple layers of an image and its surrounding context. A photo taken at a job site in Tampa that includes geographic metadata, a descriptive filename, location-specific alt text, and geo coordinates in the page schema sends a constellation of local entity signals — each individually weak, but collectively significant. Google's local ranking algorithms treat geographic signal density as a proxy for genuine local presence.

Signal Layer 1: EXIF Geo-Metadata

EXIF (Exchangeable Image File Format) data embeds GPS coordinates, device, and timestamp directly in image files. Google's image crawler reads EXIF data. Images with accurate GPS coordinates matching the business location or service area provide a direct geographic signal.

How to add/verify EXIF GPS data:

Modern smartphone photos automatically embed GPS coordinates if location services are enabled. For manually tagged images:

Windows: right-click image → Properties → Details tab → GPS Latitude/Longitude fields
ExifTool (command line): exiftool -GPSLatitude="27.9506" -GPSLongitude="-82.4572" image.jpg
Paid tools: GeoImgr, Jeffrey's Exif Viewer

EXIF best practice:

Use images taken at actual job sites or business locations (authentic GPS coordinates)
Do not fabricate GPS coordinates — Google's image recognition can identify location mismatches via visual scene recognition
For stock photos or designed images (infographics, diagrams): skip GPS tagging, focus on filename and alt text instead

Signal Layer 2: Image Filename Conventions

Image filenames are indexed by Google. A generic filename (IMG_4721.jpg) provides zero signal. A geo-tagged filename provides direct entity co-occurrence.

Filename convention:

[service-entity]-[location-entity]-[descriptor]-[optional-number].jpg

Examples:

roof-replacement-tampa-metal-shingles-2024.jpg
hvac-installation-sarasota-residential-lennox.jpg
moving-company-st-petersburg-piano-move.jpg

Rules:

All lowercase with hyphens (no spaces, no underscores for SEO images)
Service entity first, location entity second
Specific descriptor (material, type, context) third
Avoid generic terms: photo, image, pic, img

Signal Layer 3: Alt Text with Location Entities

Alt text is the highest-weight image SEO signal after filename. It is also critical for accessibility compliance (ADA, WCAG 2.1).

Alt text formula:

[Primary service/subject] [location] [specific context/descriptor]

Examples:

alt="metal roof installation Tampa residential 2024"
alt="moving truck loading piano St. Petersburg Florida apartment complex"
alt="Smith Roofing team completing storm damage repair Sarasota home"

The NAP image protocol (Merlino standard): Every hero image and primary page image should include a version with logo, NAP, website URL, keyword, and service embedded as image text (using Canva or Photoshop). This applies especially to Google My Business photos. Example alt text for NAP-embedded images: alt="Smith Roofing Tampa — 813-555-0100 — metal roof replacement — smithroofing.com"

Signal Layer 4: Geographic Schema (Page-Level)

LocalBusiness schema with geo coordinates locates the business entity on Google's knowledge graph map layer. This is separate from the GMB listing but reinforces it.

{
  "@type": "LocalBusiness",
  "name": "Smith Roofing",
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 27.9506,
    "longitude": -82.4572
  },
  "areaServed": [
    {"@type": "City", "name": "Tampa"},
    {"@type": "City", "name": "St. Petersburg"},
    {"@type": "City", "name": "Clearwater"}
  ]
}

areaServed is the schema signal for service area businesses. Include every city in the service area — this is one of the few schema fields where breadth matters.

Signal Layer 5: KML Service Area Files

KML (Keyhole Markup Language) is a geographic data format originally developed for Google Earth, still supported in Google Maps. Service area KML files can be:

Submitted to Google Maps Platform as service area definitions
Embedded in location pages as visual maps
Used as source data for areaServed schema generation

KML for SEO purposes: Generate a KML file defining the service area polygon for each location. Embed as an interactive map on the location page. The geographic polygon signals to Google precisely which area the location page serves.

Geo-Tagging Workflow for New Content

For each piece of local content (blog post, location page, service page):

Source images: Prefer images taken at actual local job sites (authentic EXIF data)
Rename files: Apply [service]-[location]-[descriptor] naming convention before uploading
Write alt text: One alt text per image following the formula above
Add EXIF if missing: Use ExifTool or GeoImgr for stock/designed images where location is known
Install schema: LocalBusiness schema with geo coordinates and areaServed on the page
Compress and convert: WebP format, under 200KB for inline images

GMB Photo Geo-Tagging

Google My Business photos are a direct local pack ranking signal. GMB photo best practices:

Photos taken at the actual business location (authentic GPS in EXIF)
Services photos: take at job sites in the target city
Caption field: include service entity + city name in first 10 words
Category: select the most specific category available (Interior, Exterior, At Work, Team)
Upload frequency: minimum 1 new photo per week (freshness signal)

Cross-References

geo-relevance-semantic-mastery — content-layer geographic signals that complement image tagging
local-seo-silo-generator — site architecture that geo-tagged content populates
daryl-local-seo — schema cascade that amplifies geographic entity signals
schema-template-library — LocalBusiness schema with geo coordinates

#seo-sop #seo #geo-tagging #local-seo #images #geographic-signals