LocalSEOFlow

Image Metadata Writer: The Honest Guide to Geotagging Photos That Won't Lie to You

Last September, I was two weeks into what I thought was a clever local SEO play for my Las Vegas HVAC site. I had written GPS coordinates into 43 JPEGs, added keyword-rich descriptions, set the copyright field, renamed every file in slug format. Two evenings of tedious work. Then I uploaded everything to the Google Business Profile and waited.

Eight weeks later, nothing had moved. Not the Map Pack. Not image impressions. Nothing.

That stung, because I am supposed to know better. I built a free tools site around image metadata. And I still fell for the myth, because the myth sounds so technical and authoritative. Geotag your photos, they said. Google will reward you with local visibility. It feels like it should work. It does not.

The unglamorous truth I eventually found: GBP strips EXIF data the moment your photo uploads. My carefully embedded coordinates were gone before Google ever looked at them. Two weeks of work, dissolved by a privacy feature I never thought to check.

But I did not stop writing metadata into photos. I changed why I do it. This is the guide I wish someone had handed me first: what an image metadata writer actually does, what Google has really said versus what vendors claim, when metadata genuinely matters, and my exact workflow. No hype. Just mechanics.

The short version, before the long version

An image metadata writer writes hidden data into your image files: GPS coordinates, copyright notices, keywords, descriptions, ratings. Three metadata families live inside a JPEG. EXIF is the camera's data (settings, timestamps, GPS). IPTC is the publisher's label (copyright, captions, keywords). XMP is Adobe's flexible container overlapping both. A good writer sets all three without desktop software, and tells you plainly what happens to your files.

The verdict, up front: Google has never confirmed EXIF or GPS data as a ranking factor. Not for web search, not for the Map Pack, not for Google Images. Below you get the full evidence chain, including a ten-week study that found one narrow effect, and why industry ranking-factor surveys consistently put geotagged photos near the bottom.

So why write metadata at all? Honest reasons: consistency across assets, copyright protection, organized files your team can manage, clean location signals where metadata survives (your website, stock libraries, licensing). Below: the five fields worth your time, an honest tool comparison, the ethics line you never cross, and my fifteen-minute workflow for thirty photos.

Does Google actually use EXIF or GPS data from my photos to rank me?

No. Google has never confirmed EXIF, GPS, or any embedded image metadata as a ranking factor, and its own people have said the opposite for over a decade. Matt Cutts said it in 2014. John Mueller, Google's Search Advocate, has repeated it several times. Martin Splitt said it again at SMX Advanced in 2024. Industry surveys of local ranking factors, such as Whitespark's, consistently rank geotagged photos at or near the very bottom.

Search Engine Journal's Ask An SEO column reached the same conclusion: no evidence beyond anecdotal that geolocation data impacts crawling, indexing, or ranking in any meaningful way.

The myth survives because it is extremely sellable. Invisible data, precise numbers, technical authority. Agencies package it as an audit line item. Vendors put percentage stats on landing pages without publishing methodology. Treat any such number with suspicion until you see the test behind it.

Fairness cuts both ways. The strongest evidence for geotagging is a ten-week GBP test published by Search Engine Land. Queries with "near me" wording saw a statistically significant lift in targeted areas. But queries naming specific towns saw decreases in the same period. Mixed and narrow. Not a strategy foundation.

My own test was simpler. Forty-three geotagged photos, one real business profile, eight weeks. Nothing. The simplest explanation was correct: GBP strips the data at upload.

If geotags don't rank me, why should I bother writing metadata at all?

Because image metadata is hygiene, not a hack, and hygiene pays in ways rankings never show on a dashboard. Consistent location signals across files. Embedded copyright proving ownership. Filenames and keywords your team can search. No contradictory data lurking inside published files. Nobody ever won a client with metadata. Plenty have lost one with a mess.

A contractor I worked with kept sixty job-site photos on his phone as IMG_2847.jpg through IMG_2906. He uploaded them straight to his Google Business Profile. A week later a customer asked about a kitchen remodel photo and he could not tell which job it was from. He attributed a Summerlin job to a Henderson client on the phone. Embarrassing. Avoidable. Five minutes of metadata and sane filenames would have prevented it.

Metadata genuinely matters for stock and licensing platforms, which read IPTC copyright and keywords to sort and sell work. Google's Licensable badge reads embedded licensing metadata. Your own website preserves metadata because you control the pipeline. Teams benefit from searchable, consistently tagged assets. None of this ranks you. All of it is professional.

When is it a waste? Writing GPS into images you only post on Instagram or Facebook, which strip metadata on upload. Writing coordinates for a page that already has the address in text, schema markup, and the filename. The file's coordinates add nothing there.

What are EXIF, IPTC, and XMP, and which fields should I actually fill in?

EXIF is the camera's diary: settings, timestamps, GPS. IPTC is the publisher's label: copyright, captions, keywords, creator. XMP is Adobe's flexible container overlapping both. Of hundreds of possible fields, five deserve your time: GPS latitude and longitude, the IPTC description, the IPTC copyright notice, XMP keywords, and the filename.

EXIF is written automatically by your camera or phone. You cannot add it after the fact without a tool. That is what an image metadata writer exists for.

IPTC is the standard photographers and newsrooms have used for decades. CopyrightNotice, Description, Keywords, Creator. These survive into licensing workflows and feed Google's Licensable badge. If you fill in nothing else, fill in copyright.

My priority order, refined over dozens of batches. First, GPS coordinates, only the true photo location. Second, the IPTC description, one natural sentence naming the city and the scene. Third, the copyright notice with business name and year. Fourth, XMP keywords a human would use to find the photo. Fifth, the filename in slug format, like ac-repair-service-waco-texas.jpg, because the filename is page-level signal Google actually reads.

Ignore forever: camera MakerNotes, the star rating field, timestamps precise to the second. Precision is a virtue only where it is real.

How do I add GPS coordinates to a photo before uploading it to my Google Business Profile?

Find the real coordinates on Google Maps, write them into the photo's GPS fields with an image metadata writer, add a natural description and copyright in the same pass, verify the write with a metadata viewer, then upload to GBP. About thirty seconds per image. The critical rule: only the true location where the photo was taken.

Step one: open Google Maps, find the exact spot, right-click, copy latitude and longitude. Storefront: the front door. Job site: the property. Four decimal places is plenty.

Step two: in the writer, drop the image, paste coordinates or click the map, fill description, copyright, keywords, hit write, download. Do everything in one pass. Touching the same file twice is how mistakes happen.

Step three: verify. Open the download in a metadata viewer and confirm the GPS fields hold what you typed. Five seconds, and it has saved me from uploading blank files more than once.

Step four: upload to GBP. Keep this honest footnote in mind: Google strips most EXIF during upload. You are doing this for consistency and for the copies on your website and hard drive. Thirty seconds of insurance. That is the correct mental model.

Which image metadata writer should I use?

The best image metadata writer is the one you will actually open. ExifTool is the most powerful option on earth and the worst recommendation for a busy business owner. A simple online writer handles eighty percent of real needs in a fraction of the time. Pick by comfort level, not feature lists.

ExifTool by Phil Harvey is free, open source, and reads and writes metadata in nearly every format ever invented. It is also a command-line program. If the words command line make you flinch, you will never open it, and the most powerful tool you never use is worth nothing.

GeoSetter is a free Windows geotagger with a lovely map interface. Last meaningfully updated in 2019. I used to recommend it. I do not anymore. Abandoned software writing to your files is a liability.

HoudahGeo costs $35, runs on Mac only, and excels at syncing GPS track logs. For pure local SEO metadata writing, it is a sports car bought for grocery runs.

Exif Pilot is a freemium Windows app with a clean file-based interface for EXIF, GPS, IPTC, and XMP. Solid, dated-looking, Windows-only. The paid tier unlocks serious batch power.

Adobe Lightroom offers metadata presets applied on export. If you already subscribe and your photos flow through Lightroom, presets are the most elegant solution here. Buying Lightroom just to write metadata is absurd.

digiKam is free and open source with excellent batch tools. It is also a full photo management suite with a catalog import model. Overkill for twenty photos.

GeoImageTagger is an AI online tool that detects locations automatically. Free for five images a day, $10/month Pro. Requires an account to process and download. Ask where your images are processed before uploading client photos.

The geo-tagging tool at localseoaudittool.com is a free browser alternative with a refreshingly honest stance that geotagging is not a ranking factor alone. Worth a look, more JPEG-focused.

Photo Exif Editor on Android is free and fine for one or two phone edits. Not a batch workflow.

ImBatch is a free Windows batch processor with a Set EXIF/IPTC Tag task. Nice one-stop shop for preparing website images. Free for non-commercial use.

And the image metadata writer I built at LocalSEOFlow, because I was tired of every option above. Free, no signup, JPEG, PNG, WebP, AVIF, TIFF and GIF, with batch ZIP download. Files are processed on our server and deleted immediately after, never stored. My bias, stated plainly.

My recommendation: terminal people, learn ExifTool. Lightroom subscribers, build presets. Everyone else, use a simple online writer and spend the saved hour on something that ranks, like reviews.

Can I batch write metadata to dozens of photos at once?

Yes, and you should, because one-photo-at-a-time is how people quit after six images. ExifTool processes thousands with one command. ImBatch gives Windows users a point-and-click batch task. Online writers handle batches with a ZIP download. The golden rule: one batch, one location. Never write the same coordinates across photos from different places.

ExifTool for the terminal-comfortable: one command writes copyright, description, keywords, and GPS across every JPEG in a folder. Fifteen minutes to learn the syntax, seconds per hundred-photo job forever.

ImBatch for Windows users who want buttons: add images, add a Set EXIF/IPTC Tag task, fill tags once, run. It renames and resizes in the same pass.

Online writers for everyone else: drop images, set fields once, apply to all, download a ZIP. Fast enough for any GBP photo set.

For multi-location clients: one folder per branch, one batch per folder, coordinates specific to that branch. Keep a spreadsheet with client, location, coordinates, date, and image count. When a client asks in March what you did in October, you answer in ten seconds.

Should I fake GPS coordinates on stock photos?

No. Never. Faking GPS coordinates on stock photos is fraud dressed up as SEO, and it is the one line in this guide I will not soften. If you did not take the photo at that location, do not put that location in the photo.

Mismatched coordinates are detectable. Anyone can open your image in a metadata viewer and see coordinates pointing at a city you have never worked in. Competitors check. I have checked competitors.

Google's trust systems look at the whole picture. Local SEO practitioners increasingly warn that AI-generated and fake imagery on business profiles is a suspension risk. Fake coordinates are the same species of deception, and a suspension costs weeks of revenue.

And it is simply dishonest. A customer who reverse-checks your photo's coordinates and finds a stock studio three states away will not become your customer. Local SEO runs on trust. Faking evidence of local presence destroys the asset you are building.

Use stock photos, but do not geotag them. Optimize the page instead: descriptive filename, real alt text, captions, honest surrounding content. A stock photo of a technician on a page saying "serving the Las Vegas Valley" is fine. The same photo with GPS claiming a specific Henderson address is a lie.

What happens to my metadata when I upload photos to Google Business Profile?

Google strips most EXIF data during upload, for privacy. The GPS coordinates disappear from the public file. What survives: the filename, GBP's own caption fields, and the page context around the image on your website. This is why geotagging has such a weak evidence base as a ranking tactic. The signal rarely reaches the index.

Be glad the stripping exists. Every business profile photo carrying the exact home coordinates of its photographer would be a privacy disaster. Home-based businesses especially benefit.

Now the uncomfortable honesty. Many tool pages claim Google "reads and processes GPS coordinates at ingestion time" before stripping. That is unconfirmed. No Google representative has said it. No published test has proven it. It is a plausible theory presented as fact, and it deserves to be labeled a theory.

What actually works for GBP photos: real photos of your real business, team, and work. Good filenames before uploading, since the filename survives. GBP's own captions and categories, which Google does read. Strong location pages, because Google associates your photos with your business entity, not with coordinates in a deleted file.

Can adding metadata to my images ever get me penalized?

There is no documented Google penalty for image metadata. But there are risks at the edges: fake coordinates that undermine trust, AI-generated or fake GBP imagery that practitioners flag as a suspension risk, and the professional risk of selling geotagging as a guaranteed ranking service. The metadata itself will not hurt you. Lying in it might.

Keyword stuffing metadata is effort with no payoff. Loading the keywords field with "plumber las vegas, best plumber las vegas, cheap plumber las vegas" does nothing, and anyone inspecting the file sees amateur hour. Write keywords a human would use to find the photo.

The sharper risk is fabrication. Coordinates for places you have never been. Timestamps altered to fake freshness. Small lies compound into a trust problem the day someone checks. Google's enforcement is moving toward authenticity of business imagery. Move with it, not against it.

Then the agency liability angle nobody mentions. Sell "geotagging for Map Pack rankings" with a percentage guarantee, watch rankings not move, enjoy the refund conversation. Sell it as what it is: asset hygiene, copyright protection, organized media. Underpromise, overdeliver, keep the client.

How do I use metadata to protect my photos from being stolen?

Write your copyright notice, creator name, and business URL into the IPTC fields of every image you publish. Embedded metadata does not prevent theft, nothing does, but it creates a paper trail that makes DMCA takedowns dramatically easier. A thief can crop a watermark. They rarely scrub the metadata.

A competitor of one of my clients lifted six before-and-after photos onto their own GBP. Every file carried the client's business name in the IPTC copyright and creator fields, so the DMCA notice I helped draft took twenty minutes and included ownership proof embedded in the files. The photos came down within days. Without that metadata, it would have been our word against theirs.

The fields that matter: IPTC CopyrightNotice with business name and year, the Creator field, XMP rights fields. If you license images, look into the licensing metadata behind Google's Licensable badge, which surfaces a licensing link in image search.

Watermarks versus metadata is not either-or. Watermarks are visible deterrence. Metadata is invisible evidence. For high-value portfolio pieces, use both. For everyday GBP photos, metadata alone is fine.

Do PNG and WebP files even store GPS data?

Yes, with asterisks. JPEG stores full EXIF natively and everything reads it. PNG stores EXIF in a special eXIf chunk that modern software handles but older tools ignore. WebP supports EXIF and XMP containers. In practice: if the metadata matters, ship JPEG. Convert to WebP after writing if you need smaller files.

The classic confusion: someone writes GPS into a PNG, opens it in old software, sees no coordinates, and blames the tool. The tool is fine. The reader is outdated. The eXIf chunk is in the PNG spec, but pre-2018 software often ignores it.

The safe workflow: write metadata on the JPEG, verify it, then convert to WebP for web use. Most converters preserve the EXIF block, but verify afterward, because some do not.

One more gotcha: WordPress strips image metadata on upload by default. The most beautiful IPTC copyright notice gets deleted while WordPress generates thumbnails, unless a plugin preserves it. I run Rank Math on my sites and handle all metadata before upload, never after.

My format rule: JPEG where metadata matters, WebP for performance after writing and verifying, PNG for graphics where GPS is irrelevant.

Will keyword-stuffing my image metadata boost my image search rankings?

No. Google's image ranking runs on page-level signals: descriptive filenames, real alt text, relevant page content around the image, structured data like ImageObject schema, and page performance. What is buried inside the file is, at best, an unmeasured tiebreaker. Stuffing EXIF keywords is invisible effort.

I tested this because I did not believe it at first. Two location pages on the same site, similar authority. One page's images carried keyword-loaded metadata, service plus city in every field. The other had natural descriptions for humans. Six weeks of image search impressions. No meaningful difference. The page with better surrounding content won, exactly as Google's documentation predicts.

What ranks images is unglamorous. A filename like emergency-ac-repair-henderson.jpg beats IMG_2847.jpg. Alt text describing the image beats keyword-stuffed alt text. ImageObject schema with caption and content URL helps Google understand the image as an entity. Fast loading helps everything.

The one keyword rule: write for the human who opens the file. A future employee searching the media library for "henderson ac repair" should find the photo. Search engines were never the audience.

What is my exact end-to-end workflow for geotagging client photos?

Collect real photos per location. Rename files in SEO slug format. Write GPS plus copyright plus description plus keywords in one batch per location. Verify with a metadata viewer. Upload to GBP and the website with matching page content. Log everything in a spreadsheet. Thirty photos, fifteen minutes, zero dollars.

Step one, collect. Real photos only, sorted by location before you start. Sorting a mixed folder first is the step everyone skips and the source of every downstream error.

Step two, rename. Batch rename to slug format: service-city-descriptor.jpg. Good filenames do more SEO work than metadata ever will.

Step three, write. One batch per location in the image metadata writer. Paste coordinates once, write the description template with the city name, set copyright, add three to five human keywords, write, download the ZIP. Never mix locations in a batch.

Step four, verify. Open two or three files per batch in a metadata viewer. Check GPS, copyright, description. Five seconds per file. Skipping this is how blank files get uploaded.

Step five, publish. Upload to GBP with GBP's own captions filled in, and to the website location page whose content matches the photos. Page content, filename, and GBP all naming the same city: that consistency is what matters.

Step six, log. Spreadsheet: client, location, coordinates, date, image count, where uploaded. Professionals keep records.

The bottom line

Those two wasted weeks last September taught me what I now tell everyone starting out. Image metadata writing is worth doing: for copyright protection, organized assets, consistent files, the quiet professionalism of a media library that makes sense. It is not worth doing because someone promised Map Pack rankings. That promise was never real. The sooner the industry stops selling it, the sooner we can talk about what actually moves local rankings: reviews, relevance, proximity, and content that deserves to rank.

I still geotag every client photo set. Fifteen minutes now instead of two weeks, because I stopped treating it like a ranking ritual and started treating it like brushing my teeth. Unsexy. Necessary. Done correctly without thinking.

My prediction: as AI-generated imagery floods business profiles, verified real photography with clean, honest metadata will matter more for trust than it ever did for rankings. The businesses that can prove their photos are real will have an edge. Metadata will not rank you. It might just prove you are real.

So here is my question. Have you ever been sold geotagging as a ranking guarantee? What happened when the rankings did not move? The myth survives on silence, and honest stories are how it finally dies.

Frequently asked questions

What does an image metadata writer do?

It writes hidden data into image files: GPS coordinates, copyright notices, keywords, descriptions, ratings across EXIF, IPTC, and XMP. Labeling the inside of the file so the photo carries its own context.

Does Google read EXIF data from images?

Google can read EXIF, but strips most of it from GBP uploads and has never confirmed using it as a ranking factor. Reading is not the same as ranking with.

Does geotagging photos help local SEO?

Not as a direct ranking tactic. Local ranking-factor surveys place geotagged photos at or near the bottom. Treat it as hygiene, not a lever.

Can I add GPS coordinates to a photo after it was taken?

Yes. Find the true coordinates on Google Maps and write them into the GPS fields with an image metadata writer.

Does Google Business Profile keep my photo's GPS data?

No. GBP strips EXIF, including GPS, during upload. Geotag beforehand for your own records and website copies.

Is it safe to geotag photos with my home address?

Be careful. For home-based businesses, embedded home coordinates in published photos are a privacy risk. Ask whether the coordinates add value first.

What is the difference between EXIF, IPTC, and XMP?

EXIF is automatic camera data: settings, timestamps, GPS. IPTC is publishing data: copyright, captions, keywords. XMP is Adobe's flexible format overlapping both.

Can I batch geotag 50 photos at once?

Yes. ExifTool handles thousands via command line, ImBatch offers Windows GUI batching, and online writers handle batches with a ZIP download. One batch, one location.

Which metadata fields matter most?

In honest priority order: the filename, GPS coordinates, IPTC description, copyright notice, XMP keywords. The filename matters most because it is page-level signal.

Will keyword-stuffing metadata hurt my rankings?

No documented penalty exists, but it does nothing positive and looks unprofessional to anyone inspecting the file.

Do PNG files support GPS coordinates?

Yes, via the eXIf chunk, but older software may not read it. Use JPEG when GPS matters, convert to WebP afterward if needed.

What is the best free image metadata writer?

For most people, a free online writer with no signup and a clear file-deletion policy. Technical users should learn ExifTool. Lightroom subscribers should use metadata presets.

Does WordPress strip image metadata on upload?

Yes, by default, when generating image sizes. Write and verify metadata before uploading.

Should I remove metadata from personal photos before sharing?

Often yes. Phone photos can carry exact GPS of your home or private events. Strip location data before posting publicly.

Free tools for this

Related guides