What GeoTag Photos does
GeoTag Photos helps local SEO agencies, photographers, field teams, and small businesses prepare image files with accurate GPS metadata. The app can read existing EXIF GPS data, add or replace coordinates, batch edit metadata fields, download tagged files, export ZIP batches, and create verification reports.
The product is intentionally tool-first. A visitor should be able to upload a photo, choose a location, and export a tagged copy without working through a marketing funnel.
Who it is built for
- Local SEO agencies preparing client photo batches for location pages, reports, Google Business Profile workflows, and internal QA.
- Photographers who need to add, correct, or verify location metadata after a shoot while keeping source files unchanged.
- Real estate, construction, field-service, and multi-location teams that need image files organized by property, branch, or job site.
- Small business marketers who need a practical GPS metadata workflow without desktop EXIF tools or file upload services.
How the product is different
- Original images are processed locally in the browser.
- JPEG GPS EXIF is treated as the most reliable output path.
- PNG and WebP support is presented with compatibility notes.
- Reports document filename, coordinate, format, status, and notes.
- Free and Pro limits are designed around real batch workflows.
Privacy-first processing
The core image pipeline runs in the browser. Reading metadata, writing GPS, resizing, watermarking, building ZIP files, and generating reports do not require uploading original images to our servers.
Server-side features are limited to account management, subscription status, usage limits, address search, payment webhooks, and optional saved location presets.
Our position on local SEO claims
GeoTag Photos is a metadata preparation and verification tool. It does not guarantee rankings in Google Search, Google Images, Google Maps, or any other platform.
We position geotagging as an operational workflow: accurate coordinates, clean metadata, format awareness, and a repeatable handoff record.
How our guides are written and reviewed
The GeoTag Photos Editorial Team documents workflows that can be checked against the current product. Instructions about reading, writing, exporting, and verifying metadata are reviewed alongside the browser implementation and automated tests.
Claims about image formats, browser APIs, Google products, and local search are linked to primary technical specifications or official provider documentation. We do not publish guaranteed ranking claims or invent customer results.
Our published test methods and scope
The metadata retention study uses test kit 1.0, test ID GTP-META-2026-001, published on 17 July 2026. Its recorded environment is Node.js v22.22.2, Sharp 0.34.5, and libvips 8.17.3. These are the original study versions, not a claim about the current production runtime.
The kit has three synthetic source files: one JPEG, one PNG, and one WebP, carrying the same known metadata. The five controlled delivery paths use one verified JPEG source: a byte-preserving copy, default JPEG and WebP re-encodes, and the corresponding re-encodes with metadata retention enabled. This is five paths for one source, not five independent platform experiments.
- Confirm the source filename, expected values, and SHA-256 against the manifest before testing.
- Name the transformation or upload surface and retrieve the exact output file being evaluated.
- Use Sharp to extract EXIF and XMP blocks and Exifr to parse them, then compare GPS, capture time, description, artist, copyright, software, and XMP keywords with the source baseline. Coordinate comparisons use a tolerance of less than 0.000001 degrees.
- Record dimensions, byte size, SHA-256, parsed values, and per-field checks. Classify the copy as byte-identical, retained, partial, or stripped according to the hash and field comparisons.
The platform record contains one X web observation from 17 July 2026. It covers the browser-rendered small JPEG retrieved from the public photo page, measuring 680 by 425 pixels. It does not establish what X stores internally or what every upload or download route returns. The published record does not specify an OS or browser version.
Controlled output files, manifests, hashes, and reproduction notes are public. The X record publishes dimensions, hashes, and field checks, but excludes account and post identifiers and does not distribute the returned image binary. Other viewers, file formats, app versions, regions, and retrieval routes may behave differently. These tests do not measure search rankings, customer outcomes, or AI citations.
See the full retention report, source manifest, controlled results, scoped X observation, and reproduction notes. Examples use synthetic files and are not location evidence or customer results.
Corrections and documentation updates
Test dates belong to the recorded experiments. A later documentation update does not mean a platform was retested. To report an error, contact product support with the page URL and a reproducible description, using synthetic files rather than private photos.
Roadmap focus
Near-term product work is focused on stronger batch review, clearer format diagnostics, saved location workflows, CSV validation, more useful reports, and better documentation for agencies and local teams.
Contact
General inquiries: hi@geotagphotos.app
Product support: support@geotagphotos.app
Follow GeoTag Photos
Watch product tutorials and practical GPS metadata workflows on our official YouTube channel. Follow founder updates on X for release notes, product progress, and workflow ideas.
Ready to use the product? Open GeoTag Photos.
Last updated: September 15, 2026.