If you have ever seen one of your own hotel photos in a third-party listicle, a regional travel feature, or some random aggregator with zero attribution and no idea where it came from, this post is for you. That image didn’t fall out of the sky. It started life on your camera roll or your photographer’s hard drive, traveled through your booking engine or a press kit, got scraped or screenshotted, and arrived at its destination naked. No credit. No rights. No way for anyone to trace it back to you.
The thing almost nobody tells independent hoteliers is that you can attach a persistent, machine-readable identity to every single image before it ships. It lives inside the file. It rides along when the photo gets downloaded, re-uploaded, and passed around. It’s called IPTC metadata, and setting it is one of those boring, ten-minute jobs that quietly pays you back for years.
I’m going to walk you through exactly which fields to set and why, because I’ve watched too many properties hand their best photography to the OTAs and the press with nothing embedded, then wonder why their images show up everywhere except in a way that sends anyone back to their direct site.
Why your photos lose their context the second they leave your building
Here’s the uncomfortable reality. The moment a high-quality photo of your property exists, it becomes a small unit of value that the entire travel ecosystem wants to use. Your booking-engine partner wants it. The OTAs want it for your listing. A travel writer wants it for the roundup. A destination marketing site wants it for the regional page. Some of those uses are great for you. Some are a slow bleed of your brand equity with nothing flowing back.
When an image gets copied from one system to another, the visual pixels survive perfectly. What gets thrown away is everything about the image: who made it, who owns it, what it shows, and what you’re allowed to do with it. Unless that information is embedded inside the file itself, it’s gone the first time someone right-clicks and saves.
This matters more now than it did five years ago, and not only because of the OTAs. AI engines and visual search are getting aggressive about understanding images. When a model or a search crawler encounters your photo, the embedded fields are part of how it figures out what it’s looking at and who it belongs to. If you’re already thinking about whether your property is even legible to these systems, my piece on whether your hotel is invisible to ChatGPT is a good companion read.
EXIF tells the world about the camera. IPTC tells the world about you. When your photo gets stripped of its surrounding webpage, the IPTC fields are the only part of your story that can travel inside the file.
EXIF versus IPTC, in plain English
Quick vocabulary, because these get muddled constantly.
EXIF is the technical capture data your camera writes automatically: aperture, ISO, shutter speed, lens, and sometimes GPS coordinates. Useful for photographers diagnosing a shot. Mostly irrelevant for protecting your brand, and in the case of GPS, sometimes something you want to strip for privacy.
IPTC is the descriptive and rights layer. This is the human-authored stuff: who created the image, who holds the copyright, a plain-language caption, keywords, and usage terms. The IPTC standard (formally the IPTC Photo Metadata Standard, maintained by the International Press Telecommunications Council) is what newsrooms, stock agencies, and serious image pipelines have used for decades. It’s the field set that actually carries your information.
For a hotel, IPTC is where the work happens. EXIF you mostly leave alone or clean up. IPTC you fill in deliberately.
The fields to set before a single image ships
You don’t need to fill out all 40-plus possible fields. You need the handful that carry credit, ownership, context, and contact. Here’s my working standard, the one I’d apply to every hero shot, room photo, and amenity image before any of it goes near a booking engine or a press kit.
| IPTC field | What you put in it | Why it matters |
|---|---|---|
| Creator / Byline | Photographer name or your studio name | Survives as the “who made this” credit; Google can surface it |
| Copyright Notice | ”(c) 2026 [Hotel Name]. All rights reserved.” | Your legal ownership statement, embedded in the file |
| Credit Line | ”[Hotel Name] / [Photographer]“ | The short attribution a publisher is meant to print |
| Caption / Description | One plain sentence describing the scene | Context for humans, search, and AI; doubles as alt-text seed |
| Keywords | Room type, view, amenity, city, neighborhood | Helps image search and internal asset management |
| Headline | Short title, e.g. “Oceanview King Suite at dusk” | A scannable label distinct from the longer caption |
| Source | Your hotel’s legal entity or brand name | The original origin, separate from the creator |
| Copyright Status | Marked as “Copyrighted” | A clear machine-readable rights flag |
| Web Statement of Rights | A URL to your image usage/licensing page | Points anyone who cares straight back to your terms |
| Creator Contact Info | Your direct booking URL or press email | The breadcrumb home, baked into the file |
That last one is the sleeper. The Creator Contact Info block lets you embed a website URL. Put your direct site there, not your OTA listing. If a journalist or a partner pulls the file and bothers to inspect it, the trail leads back to you, and you’re already nudging traffic toward booking direct instead of leaking it. That’s the same instinct behind everything in my book-direct CRO work: every breadcrumb should point home.
A note on the caption field
Write captions like a human, not a robot. “Oceanview King Suite at dusk, with the private balcony overlooking the marina” is worth ten times “IMG_4471 hotel room.” A good caption seeds your alt-text, gives visual search real context, and reads as a sentence a person would actually write. When that image lands in a press feature with the caption intact, you’ve quietly authored the words next to your own photo.
Will any of this actually survive the journey?
Honest answer: sometimes yes, sometimes no, and that’s fine.
Some platforms strip metadata on upload to save bandwidth. A lot of social networks are notorious for it. But plenty of systems preserve IPTC faithfully, including many CMS image pipelines, stock and DAM platforms, Google’s own image handling, and a good number of editorial workflows. Google in particular reads IPTC fields and can display a creator and credit panel in Google Images, with a “licensable” badge when you’ve set the rights fields and a licensing URL properly.
So the calculus is simple. Embedding costs you essentially nothing once you’ve set your standard. Wherever the metadata survives, your credit and rights travel with the file for free. Wherever it gets stripped, you’re no worse off than the hotel down the road that never bothered. This is insurance with a near-zero premium. There’s no guaranteed outcome here, and anyone who promises you that your credit will appear everywhere is selling something. You’re maximizing the odds that attribution sticks, which is the only honest framing.
I think of embedded metadata the way I think of a luggage tag. Most of the time the bag arrives the normal way and you never need it. But the one time it gets separated from you in a strange airport, that tag is the entire difference between getting it back and losing it forever.
How this connects to the OTA problem
Let’s be clear about what metadata does and doesn’t do. It will not let you escape the OTAs, and nothing will. The OTAs are a permanent part of distribution, and the goal is always a healthier mix where more of your bookings come direct, not a fantasy where they vanish. With commissions running roughly 15 to 25 percent of every reservation they send you, even a modest shift toward direct is real money. I lay out that arithmetic in detail in the book-direct math post, and the structural reasons OTAs out-rank you are in why your hotel ranks below the OTAs for your own name.
Where metadata fits: when your photography circulates with your credit and your direct URL embedded, every copy of that image is a tiny, persistent ambassador for your brand rather than an anonymous asset feeding someone else’s funnel. It’s a small lever. But the hotels that win direct bookings are the ones that pull dozens of small levers consistently, and visual assets are one of the most-copied, most-traveled things you own.
The practical workflow
You don’t need a complicated system. You need a standard and a habit.
- Decide your standard values once. Copyright notice, credit line format, source, web statement URL, and contact URL barely change shoot to shoot. Write them down. This is your template.
- Pick your tool. Adobe Lightroom and Bridge handle IPTC natively, including metadata presets you apply on import. If you’d rather not pay for Adobe, the free open-source tool ExifTool can batch-write every field across an entire folder from the command line. Both work fine.
- Apply on import, not at the end. The whole point is that no image leaves your building without the fields set. Make it the first step in your photo workflow, applied to the entire batch, so it’s never a thing you forget under deadline.
- Build a press kit that preserves it. When you hand images to media, deliver full-resolution originals with metadata intact, ideally as direct downloads rather than through a platform that re-compresses and strips. This ties directly into the kind of PR and authority work where you want every placement carrying your credit home.
- Decide on GPS. For a hotel, embedded GPS in guest-area photos is usually harmless and can even help local context, but think before you publish images that reveal private staff areas or security details. Strip what you don’t want public.
Set it once, apply it on every import, deliver originals to press. Three habits, and your photography stops traveling as an anonymous asset and starts traveling as a credited, rights-marked piece of your brand.
What I’d actually do this week
If you’re a boutique or independent operator reading this and feeling like one more technical chore just landed on your plate, here’s the compressed version. Open your last shoot. Pick your ten best images, the ones most likely to get borrowed by a writer or an OTA. Spend twenty minutes setting creator, copyright, credit line, caption, and your direct URL in the contact field. Save. That’s the proof of concept. Once you’ve felt how fast it goes, you’ll build it into the import step for everything going forward.
This is the kind of unglamorous, compounding detail that separates the properties that own their narrative across the web from the ones that just hope for the best. It pairs naturally with getting your local presence and Google Business Profile in order, because your photos and your listings are the two visual surfaces guests judge you on before they ever read a word.
If you want a second set of eyes on how your visual assets, your direct-booking story, and your search visibility all fit together, that’s exactly the work we do. Come book a call and we’ll look at where your photography is leaking value and how to plug it.