An image in a travel article has two jobs: it should help the reader understand a place, object, route or decision, and the publisher should be able to explain why it can be used. “It was visible online” is not a rights record. A Google Images result, a social post, a map screenshot or a photograph taken in a public place can still carry copyright, privacy, trademark, licence or contract limits.
Use this as an editorial workflow, not legal advice. Record the exact source page, licence or permission, photographer, date, scope, attribution, model or property concerns, crop and intended placements. Rules differ by jurisdiction and medium; ask a qualified rights professional or responsible authority when the use is uncertain. If evidence is missing, choose a documented replacement and keep the article useful.
The short answer
Choose an image for a clear reader purpose, then verify the exact asset and permission before publishing. Save the source page, licence wording, photographer, checked date, permitted uses, required credit, model or property notes, crop limits and removal contact. Credit does not replace permission, and public visibility does not prove permission. Write captions and alt text that add information, not claims the image cannot support. Remove or replace an asset when its terms or provenance cannot be confirmed.
Start with the reader purpose
Name what the reader should learn from the image: the shape of a route, the position of a station, the equipment needed for a planning task, a surface or access condition, or the difference between two options. A decorative beach photograph may not explain a transfer, and a generic laptop may not support a claim about a booking tool. If the image has no explanatory job, omit it or use a simple visual that does.
Record the audience, article section and decision the image supports. A family reader may need a clear step-free entrance photograph; a newsletter reader may need a labelled map or a crop that remains legible on a phone. Purpose controls selection, caption and alt text. It does not justify stretching a licence beyond its stated scope.
Verify the exact source page
Save the exact page where the asset was obtained, not only a CDN URL or search result. Record the page title, photographer or provider, asset identifier, download or preview URL, access date, licence link, account or subscription context and the file you actually stored. Recheck that the preview matches the source page; similarly named files and recropped derivatives can carry different terms.
The source page is evidence of provenance, not automatic permission for every use. If a provider uses a standard licence, preserve the licence version and any exclusions. If a person or organisation supplied the file, keep written permission that identifies the asset, channels, territory, duration, edits and whether commercial use is included. Missing fields are a reason to pause, not to guess.
Read the licence in context
Read the current licence and the provider’s restrictions together. Check whether the use is editorial, commercial, sponsored, paid, newsletter, social, print, client work or resale; whether attribution is required; whether modifications are allowed; and whether the licence can be revoked or expires. A “free” label is not a legal category that overrides the actual terms.
For standard Unsplash assets, keep the exact source page, photographer profile and current Unsplash licence with the record. The licence may cover the image file while separate rights can apply to people, logos, artworks, private locations or depicted products. Do not imply that an Unsplash asset proves a destination fact or a person’s endorsement.
Separate copyright from permission to depict
Copyright or licence status answers only one part of the question. A recognisable person, child, private interior, artwork, logo, product or event may raise privacy, publicity, property, trademark, contract or local-law questions. The answer depends on the image, use, jurisdiction and audience. Do not promise that a model release, property release or permission is always or never required.
Describe what you checked and what remains outside scope. If the asset shows a person in a sensitive setting, a private home, a restricted venue or a recognisable brand, ask a qualified rights adviser whether the intended use is appropriate. Blur, crop or substitution can reduce risk but cannot be treated as a universal legal solution.
Build a rights record that another editor can use
Use one record per exact asset: internal ID, source page, provider, photographer, file name, licence URL, licence version or wording, downloaded date, allowed channels, territory, duration, required credit, model or property notes, edits permitted, original file location, article placements and review owner. Add a screenshot or saved copy only when your policy allows it, and keep a change log when a provider updates terms.
Do not store passwords, private account tokens or unnecessary personal data in the record. If a contributor sends a photo, retain the permission message in the approved system and link it from the asset record. The record should let an editor answer “why can this exact crop appear here?” without relying on a memory of a search result.
Handle commissioned and contributor images separately
For commissioned work, write down who owns copyright, what licence or assignment was agreed, where the image can appear, whether edits and translations are allowed, how the photographer is credited, and whether exclusivity or a fee applies. A payment or friendly email does not automatically answer those terms. For a reader or local contributor, obtain permission that names the image and intended publication rather than assuming a message about “using the photos” covers every channel.
Keep contributor identity, contact and payment information separate from the public article. Do not publish a person’s name, route, home or location unless the permission and editorial need support it. When the agreement is silent, pause the asset or ask the owner to clarify in writing.
Do not treat public visibility as permission
A photograph taken in a street, station or public square may still be protected by copyright and may show people, children, artworks, signs or private activity. “Public place” describes where the camera was, not the complete permission analysis. The same file can have different risks when used in a personal note, a commercial article, a paid campaign or a product page.
Identify the source and purpose, avoid unnecessary identifiable faces and check local rules when the image is central to a claim. If a scene is useful only as atmosphere, replace it with a rights-documented asset that explains the reader’s decision. Never use a person’s presence to imply a testimonial, endorsement or lived experience.
Make attribution accurate and visible
Follow the licence’s required credit format and place it where the reader can find it on the article, newsletter or social version. Record the photographer name exactly as supplied, link the required source page and do not add a statement that suggests sponsorship or endorsement. If no credit is required, a transparent source record is still good editorial maintenance.
Attribution is not a substitute for permission, a model release, privacy review or a correct licence. Do not alter a photographer’s name, remove a required notice during translation, or detach a credit when a crop is reused. Check every export and syndication route because a CMS may drop captions or credit fields.
Write a factual caption
The caption should identify what is visibly relevant and explain why the image appears. “A map beside notes for comparing route options” is safer than “the easiest route” when the image cannot prove ease. Name a place only when the source and context confirm it. State when an image is illustrative, a file photo or a supplied asset if that distinction matters to the reader.
Do not turn a stock image into evidence of a hotel, meal, crowd, weather event, accessibility condition or personal experience that was not verified. Captions survive social previews and search snippets, so keep the factual limit clear. If a crop removes the feature the caption names, rewrite the caption or choose another image.
Write useful alt text without repeating the caption
Alt text should identify the meaningful visual information for someone who cannot see the image. Mention the object, action, layout or condition that helps the article’s decision, for example “open notebook beside a phone and route map” when that is what is visible. Do not stuff destinations, keywords, photographer names or licence language into alt text.
If the image is purely decorative, use the accessibility setting that marks it decorative rather than giving it a misleading description. For an infographic or map, provide the key information in nearby text as well; alt text alone may not carry every label or route constraint. Review translated alt text for accuracy and ordinary language.
Record crops, overlays and transformations
Save the original and note every crop, resize, overlay, colour change, face blur, translation or composite. Check that the licence permits the edit and that the change does not remove a required notice or create a misleading scene. A crop can change who appears identifiable or hide a step, gradient, sign or access feature that the caption claims to show.
Never add a person, landmark, weather condition or product to make a travel image more persuasive. If an AI or design tool generates or materially changes an image, record that fact and follow the publication policy; do not present it as a witnessed destination photograph. When the edit changes meaning, choose an honest label or a different asset.
Check the CMS and newsletter path
Upload the approved file with its internal ID, source page, photographer, licence, alt text, caption and placement. Confirm that the CMS stores the credit, serves the intended crop, preserves the source link and does not expose a private file path. Check responsive versions, dark mode, email clients, social cards and RSS because a credit or alt field can disappear during export.
Use a smaller, accessible format where possible and keep a replacement ready if the image is removed. WordPress’s current documentation can explain general publishing setup, but it does not grant image permission or replace the source licence. The publisher remains responsible for the exact asset and placement.
Plan reuse across channels
An article, newsletter, video thumbnail and social post may have different crop, attribution, audience and commercial context. Write the permitted channels in the rights record and obtain additional permission when the original licence does not cover the new use. A source page that permits a blog image does not automatically permit a paid advertisement, merchandise, client deck or press kit.
When a newsletter is forwarded or a social card is generated, keep the credit and avoid a caption that implies endorsement. Tell collaborators which version is approved and where the source record lives. If the channel cannot carry the required credit or disclosure, use another asset or redesign the placement.
Schedule review and takedown
Assign an owner and review interval for every image whose source, licence, person, venue, product or claim may change. Recheck a provider licence when the article is substantially revised, a campaign begins, a complaint arrives or the source page changes. Record the decision and next date instead of silently refreshing a file.
Create a takedown route that can remove the image, caption, social card and cached derivative, then publish a documented replacement. Do not wait for a dispute to discover where the original file, permission and credit live. If provenance cannot be restored, remove the asset and keep the article’s useful text.
Keep a rights-safe fallback
For every important placement, keep a replacement with a complete record or publish the information without an image. A clear text route, accessible table, verified map link or simple diagram may answer the reader better than an attractive but uncertain photograph. Do not let a missing image pressure an editor into accepting a screenshot or social download without provenance.
If a licence ends, a contributor withdraws permission or a person asks for removal, use the fallback while the rights question is reviewed. Update the caption and alt text so they describe the replacement, and record the change. A rights-safe fallback is part of continuity planning, not a sign that the article failed.
- Purpose: What reader decision or factual detail does this exact image support?
- Source: Do you have the exact source page, photographer, file and checked date?
- Licence: Does the current licence cover this channel, audience, territory, duration and edit?
- People and property: Have privacy, model, property, artwork, logo and local-law questions been escalated where needed?
- Record: Are credit, permission, restrictions, internal ID and review owner stored together?
- Caption and alt: Are they factual, accessible and honest about what the image cannot prove?
- Reuse: Will every newsletter, social, client or paid version preserve the required terms?
- Fallback: Can the image be removed and replaced without losing the reader’s answer?
When to stop and replace an image
Stop when the exact source or licence is missing, a required credit cannot travel with the asset, a person or property concern is unresolved, the crop changes the meaning, or the image implies a fact or experience you cannot verify. Use the documented fallback and keep the article’s useful guidance. Do not publish first and investigate provenance later.
Questions publishers ask
Can I use a Google Images result? A result is a discovery path, not permission; open the exact source and verify its terms. Does credit make an image lawful? No. Credit may be required, but it does not replace the permission or licence analysis. Can a public-place photo be used freely? Public visibility does not answer copyright, privacy, property or local-law questions. Is a free-stock label enough? Read the current licence and check people, logos, artwork, edits and channel limits. What if a source page disappears? Remove or replace the asset unless your approved record still proves the intended use, then document the decision.
Choose travel-blog images for a reader purpose, verify the exact source and permission, record credit and limits, write factual captions and useful alt text, and keep a replacement ready. Licence wording, privacy, publicity, property and disclosure rules vary by jurisdiction, so unresolved questions belong with a qualified rights adviser. A well-documented image can strengthen an article; an attractive file with uncertain provenance can undermine the entire publication. When evidence is incomplete, publish the useful information without the image.
