Crop, resize, rename and geotag a whole set of photos for a Google Business Profile in one pass. Out comes a ZIP of spec sized JPEGs plus a manifest CSV. Your photos are processed in this tab and are never uploaded.
Google strips EXIF metadata from images after they are uploaded to a Business Profile, so the coordinates written here will not be visible on the listing. Google has never confirmed geotagging as a ranking factor, and the published tests disagree with each other. What this page reliably gives you is a correctly sized, correctly named, consistently described pack with the location data intact in your copies, your website and your client records, produced in one pass instead of by hand. If a page promises you rankings for geotagging, it is guessing.
These fill the file names and the description written into each photo.
In Google Maps, right click the business pin and the first line of the menu is the latitude and longitude. Click it to copy, then paste it here. Decimal, degrees minutes seconds and a full Maps URL are all understood.
Whatever you type in that box is written into both the EXIF Artist tag and the EXIF Copyright tag, so put the name that should own these photos, not your own agency name, unless you really do hold the copyright. Leave it blank and neither tag is written.
Non English characters are stripped from the description and photographer fields, because the EXIF tags used here are ASCII only and anything else corrupts them.
Drag the picture to move the crop.
Padding is right for a logo with transparent edges. Cropping is right for a photo.
| File | Type | Pixels | File size | Check |
|---|
The same list is in manifest.csv inside the ZIP, along with the coordinates and descriptions that were actually written into each file. A blank metadata cell there means nothing was written into that file.
Photos in, a finished upload pack out. Each photo is cropped to the size you pick for its slot, re encoded as a JPEG inside Google's 10 KB to 5 MB window, renamed to a consistent pattern built from the business name and city, and given a fresh EXIF block. That block holds nothing but this: the coordinates you paste, a plain language description, the name from the photographer box written into both the Artist tag and the Copyright tag, the date you pick if you pick one, and a Software tag naming this page. The ZIP also contains a manifest CSV listing every file with its size, its coordinates and a flag on anything that fell outside the limits, plus a short text file you can hand to a client.
Google removes EXIF data from images once they are uploaded to a Business Profile, so nobody looking at the listing will ever see these coordinates. Google has never confirmed geotagging as a ranking signal, and the public experiments contradict each other: one reported a lift on near me queries, several found no difference, and at least one measured a small drop. So treat this as a resizing, renaming and metadata tool, not a ranking trick. The coordinates are still worth writing, because your own site, your photo library and the client's records all keep them, and because you get a clean consistent pack in one pass instead of twenty minutes of manual cropping per location.
Google publishes these numbers for Business Profile photos: JPG or PNG, between 10 KB and 5 MB, minimum 250 by 250 pixels, recommended 720 by 720. The logo and square presets match that recommendation exactly. The 1024 by 576 cover and the 1200 by 900 presets are larger 16:9 and 4:3 crops for the cover slot and for Posts, both comfortably inside the file size limits. If a flat logo or a plain background shot compresses under the 10 KB floor, the quality is raised and, if that is still not enough, the pixel size is doubled. Anything that still lands outside the window is flagged in the manifest instead of being quietly shipped.
Open Google Maps, right click the business pin, and the first item in the menu is the latitude and longitude. Click it to copy. Paste it here in whatever shape you have: plain decimal like 30.1814, 71.4921, the degrees minutes seconds version, or the entire map URL. On the live https version of this page there is also a Use my location button, which asks your browser for the device position and fills the same box, handy when you are standing in the shop. That button is hidden wherever it could not work: on a browser with no geolocation support, on a page that is not a secure context, and on a copy of this file opened straight from disk. Even where it is shown, your browser can still refuse the request, and if it does, the reason is printed under the coordinate box.
Re encoding through a canvas drops everything that was in the original file, so the finished JPEGs carry only the fields listed above. That is on purpose. A phone photo taken by an owner at home carries the home coordinates, the device model and the original timestamp, and none of that belongs in a public upload. If you need the original camera data preserved, this is the wrong tool.
Your photos are read, cropped and encoded inside this tab. No photo, coordinate or name is ever sent anywhere. The page itself does make network requests: it loads three small code libraries from a public CDN and a page analytics script, it records an anonymous page view, and when a pack is built it records the number of photos that were in it. That count is the only thing a build sends. Written metadata uses ASCII only fields, so accented and non Latin characters are stripped rather than left to corrupt the tag.