When you find your photograph or infographic on someone else's page with no credit, the practical question is whether to ask for a credit link or to demand removal. Start with the credit request. It is a short, courteous email that asks for a visible credit line and, if possible, a working link back to your page. A copyright notice is a separate and heavier step. This is not legal advice.
This sequence suits photographers, infographic makers and owners of small shops who publish their own images. Example scenario: a chocolate workshop whose tempering photograph and bean-to-bar step graphic were placed on a food blog with no credit.
What a credit request asks, and what a copyright notice starts
A credit request and a copyright notice come from the same discovery but point in different directions. The first keeps the image on the page and adds your name beside it. The second aims to end the use. Mixing the two in one email asks the reader to say yes and to defend themselves in the same breath, and both goals suffer.
The credit you are asking for
A credit request names three things: who made the image, where the reader can find the original, and where on the page the credit line should sit. The editor can answer by editing one line. Treat the other side as a person who may have lifted the image from somewhere that dropped its source.
What a notice sets in motion
Google's legal requests page states that it is Google's policy to comply with notices of copyright infringement pursuant to the Digital Millennium Copyright Act, and it sends readers to the Copyright Help Center for the requirements of a complete notice. That is United States law, and it is described here as a general principle, not as the rule in your country. Read the Google legal requests page (Opens in a new tab) before deciding that a notice is the right tool.
Decision rule: which message goes first
- If the image is unaltered and used in a fitting context, and only your name is missing, send a credit request.
- If the image is cropped, relabelled or placed in a misleading setting, send a credit request that also asks for a correction, and keep the notice route in reserve.
- If the image is being sold in someone else's shop, treat it as a different matter from credit.
- If you cannot yet show that the image is yours, finish the evidence work before writing at all.
Practical suggestion: put the chosen route in one sentence in your log, so that later emails do not drift from the original goal.
Evidence first: original file, date and the page using it
Write nothing until three items sit in one folder: the original file, a dated record of when you made and published it, and a capture of the page that uses it. Together they show that the image is yours and where it appears. Even a friendly exchange goes better when you can answer the first question an editor will ask: how do you know this is yours?
The file you made
The camera file, the layered design file or the exported chart counts as the original. In the chocolate workshop, the unedited camera frame of the tempering demonstration and the resized version on the workshop's website are two files. Keep both and note the address where the published one lives. A web version alone still helps, though the original is the strongest piece.
Dates, each with its source
Record three dates: when the file was created, when you first published it on your own site, and when you first saw it on the other page. Editing timestamps can change when files are copied or exported, so none of them should carry the whole claim. Practical suggestion: write beside each date where it came from, for example the publishing record in your content system.
The page and the image address
Copy the full page address, capture the page the same day, and show where the image sits. Note the image file address as well. If the image is loaded from your own server, you can change what the file shows. If it was uploaded to the other site, a message to the owner is the only route to a change.
Before you write: the folder in seven items
- One master file per image, plus a note of every resized copy derived from it.
- A dated line for creation, your first publication and your first sighting elsewhere, each naming where the date was read.
- The other page's address, saved as a capture with the image visible and the date in the file name.
- The image's file address on the other site, to show whether it is hosted there or loaded from you.
- The wording of any credit already on the other page, even if it names someone else.
- A capture of your own page showing the credit text and usage line you want copied.
- The creator and creditText values stored in the file or on your page, if you filled them.
Which kind of image, which proof
Proof differs by format. A photograph rests on the camera file and the shooting date. A graphic rests on the design file and the data behind it. A product shot rests on the shooting setup and the listing date. Table: proof and credit wording by image type.
| Image type | First thing to pull from the archive | Line to propose | Watch for |
|---|---|---|---|
| Chart or screenshot | Source data, the day it was made, the page that published it | Source: the page where the chart first appeared | If the figures came from another institution, name that source as well |
| Product shot | Shoot file and the listing date on the product page | Image: shop name, linked to the product page | Use inside another seller's listing is a separate matter |
| Tempering photograph | Camera frame, the day of the demonstration, the event notice | Photo: workshop name, linked to the workshop page | People visible in the frame raise questions this request does not settle |
| Step graphic | Design file, the data table, the page where it was published | Source: workshop name, linked to the graphic's page | A cropped copy may have lost its source line |
The table is a practical suggestion. Rights of people who appear in a photograph are outside this topic.
Finding the right inbox
Practical suggestion: aim the message at whoever chose the image. Look for an author name, an editor or an owner on the page and in its about section. On a company site, a press or editorial address is better than a general contact form. On a personal blog, write to the owner.
Author and owner can be different people
A byline does not prove that the author placed the image. On a site with several editors, someone else may have picked the picture. Write to the site's general contact first, and to the author second if you need to. Move through them in turn rather than copying everyone at once.
Hosting companies are not the first stop
Practical suggestion: keep platform and host channels for notices of infringement and out of a credit request. If the credit request goes unanswered, those channels become a separate step.
A short polite first message: say exactly what you ask
The whole first email comes down to a single sentence: this image is mine, so please credit it in this form. Everything else supports that sentence. Write so that the editor can reply with one edit.
Subject line
Keep it calm and plain: a request about the credit on an image on your page. The subject tells the reader that this is not a legal threat. Practical suggestion: avoid capital letters, exclamation marks and deadlines in the subject, because they push the message towards a defensive reading.
Four sentences that carry the request
- Who you are and that the image is yours.
- Where the image appears on their page and where it is published on yours.
- The exact credit line you would like and the address it should link to.
- A thank-you and a time that suits you for a reply.
A sample message
Example scenario: the owner of the chocolate workshop writes to the food blog's editor.
Hello, the tempering photograph and the process graphic in your recent post were made by our workshop and are published on our own site. I have attached the address of your post and the addresses of both images on our pages at the end of this note. Could you add the line Photo and graphic: the workshop's name beneath them, linked to our page? If you let me know once it is done, I will gladly check the page. Thank you for your time.
Wording to leave out
- Accusations about intent. You do not know how the image arrived on their page.
- Hard deadlines in a first message, which can read as a threat.
- Offers of payment or a link in return. Google's spam policy lists buying or selling links for ranking purposes and excessive link exchanges among its link spam examples.
- Legal vocabulary piled into a request that is only about a credit line.
Writing the credit line you want
A request gets answered when it supplies the finished line. A vague ask such as please give us credit leaves the editor to guess the form. A ready line removes the guessing and shortens the reply.
Two parts are enough
Give the name of the creator and a link to your page. The link can point at the image's page or at the main page of your business. Suggest the business name as anchor text, not a string of keywords. Google's image license metadata page defines creditText as the name of the person or organisation credited when the image is published, so a credit line that matches your creditText value keeps your records tidy.
Where the line should sit
Directly under the image is the easiest place to read. A source list at the end of the post is a second option. Let the editor pick. Google's spam policy counts broadly distributed links in the footers or templates of various sites as link spam, so the credit belongs inside the content itself.
The rel value is the publisher's call
Do not dictate how the link is qualified. Practical suggestion: when a publisher adds a credit by its own editorial choice, ask nothing further about the link. Where money has changed hands, the spam policy names the sponsored value and mentions nofollow as another option. A credit request involves no payment, so the point does not arise in the email. The Google spam policies page (Opens in a new tab) has the full text. Practical suggestion: a visible credit line fulfils the main goal of the request even if the publisher decides to use nofollow.
Creator and creditText fields in image metadata
Metadata carries ownership information in the file and on the page. If your files already hold it, showing who made the image is easier. If they do not, the dated records in your evidence folder carry that job.
The IPTC trio
The IPTC photo metadata guide separates three fields. Creator holds the name of the person who made the image, and a company or organisation name can stand in when the artist cannot or should not be named. Copyright Notice names the current copyright holder. Credit Line shows how the image should be credited when it is published, and it can repeat details from Creator and Copyright Notice. Usage terms sit in a separate field. The IPTC user guide (Opens in a new tab) has the definitions.
The structured data properties
Google's image license metadata page lists creator, creditText, copyrightNotice, license and acquireLicensePage for ImageObject. The creator property names who made the image; creditText names the person or organisation credited when the image is published. The contentUrl property is required, and at least one of creator, creditText, copyrightNotice or license must accompany it. The page also says that if IPTC data and structured data conflict, Google uses the structured data. See the image license metadata page (Opens in a new tab) for the details.
| Field | What it states | Use in a credit request (practical suggestion) |
|---|---|---|
| creator | Who made the image | Shows the editor whose work it is |
| creditText | Who is credited when published | A model for the credit line you ask for |
| copyrightNotice | Copyright claim text | Names the rights holder |
| license and acquireLicensePage | Licence page and where to obtain a licence | Tells a publisher how the image may be used |
What the fields do not do
The page says Google does not guarantee that structured data or IPTC photo metadata will show up in search results. Treat the fields as a layer of information that identifies the owner. The page adds that removing metadata may be illegal in certain jurisdictions and recommends keeping the IPTC creator, credit line and copyright notice fields. For images produced with AI tools, see AI-generated images: IPTC digital source type and C2PA metadata.
Reading the reply
Replies arrive in recognisable shapes. Deciding the next move for each shape beforehand keeps you calm when one lands.
| What the editor says | Your response | What to file |
|---|---|---|
| Done, credit and link are in | Open the page, check both, say thanks | A fresh capture with the date |
| Done, but only the name, no link | Give one sentence on what the link does for readers, then accept the answer | The capture of the unlinked version |
| We swapped the image for another | Thank them and confirm that your image is gone from the page | The date of the swap |
| We found it on a free-image site | Ask for that address and show your own usage line | The address and their wording |
| Silence | One reminder on the thread, then a second channel | The date of each attempt |
Decision rule: while the other side cooperates, keep to the polite sequence. If they decline, or stay silent after a reminder and a second channel, move to the next step in one clear message and keep the earlier emails as records.
Objections you may hear
If the editor says the image looked free, point to the usage line on your page and rewrite the requested credit. If your page lacks a usage line, treat that as a gap to close for future posts. If the editor asks how they can tell the image is yours, show the publication date and your page address, and mention filled metadata fields where they exist. You do not have to send the full original file to answer that question.
If there is no reply: next steps and when legal advice enters
Silence does not prove bad intent. The email may sit in an unused mailbox or reach the wrong person. A calm follow-up resolves some cases, and in others the type of request has to change at the end.
One reminder on the same thread
After a waiting period of your choosing, send a short reminder as a reply to the first message. Include the page address, the credit line and the date of the original email. Nothing else needs repeating.
A second channel
Try one other route to the same site: the author's address, the site's social account or its contact form. Use the same short text on each. Writing through several channels on the same day can feel like pressure.
The removal route
If the credit request fails and the use still matters to you, a separate removal request comes into view. Google's legal requests page points to its Copyright Help Center for the requirements of a complete copyright notice. The Legal removals section of Google's spam policy adds that a significant volume of valid copyright removal requests involving a site can lead Google to demote other content from that site. That describes the general framework and does not decide your case.
Legal advice is a separate matter
Questions of ownership, licences and the law of a given country depend on individual facts and are outside this topic. Tidy records help in either case.
Preparing your own site for the next time
Requests start on your own pages. If a visitor can see your source, crediting you is easy. These steps do not guarantee anything, but they give your email a solid footing.
A usage line next to the image
Place the source, a one-sentence usage condition and a contact address near the image: you may use this image with a credit in this form. A page without any condition invites the assumption that the image is free to take. For licence wording and alt text, see article image alt text and stock image licensing; for who may use a piece once it is written, see article copyright transfer and usage rights.
File names and image search
A meaningful file name, accurate alt text and nearby descriptive text help tie an image to your page. The detail is in image SEO: optimizing images for Google.
Noticing a use
A reader message, a link report or plain luck can reveal a use. If your name appears in the text but not as a link, the situation differs; turning unlinked brand mentions into backlinks covers it. For routine watching, tracking brand mentions with Google Alerts is useful.
One owner for the process
Practical suggestion: let one person keep the evidence folder, send the emails and watch the replies. Dates and messages then stay in one place. In a small business that person is the owner; in a team, a publishing lead.
Example scenario: a chocolate workshop and a food blog
Example scenario: a chocolate workshop publishes a photograph of a tempering demonstration and a graphic of its bean-to-bar steps. A food blog places both in a post with no credit.
The day it is spotted
The workshop's owner learns about the post from a reader's message. She captures the blog page that day with both images visible and writes the address, the date and the source of her discovery into a new log file.
Pulling the originals
She finds the camera frame of the tempering demonstration, the web copy and the design file of the bean-to-bar graphic, and notes the page on her site where each is published. She also checks that the creditText value on the graphic's page is not empty.
Weighing the two routes
Both images are unaltered and sit beside a fitting article. Nothing is sold and nothing is relabelled, and she is content for them to stay. The only gap is her name, so she picks a credit request and writes the choice into the log in one sentence.
Sending the short email
She finds the editor's address in the blog's about section. The email carries the post address, both image addresses on her site, the line she would like and the page it should link to. It offers no payment and sets no deadline.
The quiet stretch and the close
Nothing comes back. She sends one reminder on the same thread and, some days later, tries the author's address. When the credit line appears she captures the page again, files the capture and closes the log. No removal request goes out at any point.
Pitfalls to check before sending
Clearing out earlier correspondence
Deleting old emails to tidy the inbox removes the only dated trail of what was asked and when. Keep every message on the thread, including the ones that went unanswered.
Writing to several contacts at one site on the same day
An editor, an author and a social account receiving the same request within hours can read as pressure. Move through the contacts in turn and note each date.
Leaving creditText empty on your own image page
If the metadata on your page carries no credit text, your requested line has nothing to match. Fill the field first, then copy its wording into the email.
Requesting a credit line that differs from your own page
A line written as Workshop X in the email and Workshop X Ltd on your page makes the page harder to verify. Use one spelling in the email, the metadata and the page.
Resting the claim on one timestamp
A single file date can change when a file is copied or exported. Pair it with the publishing record and the first-sighting date before you cite it.
Frequently Asked Questions
When does a credit request stop being enough?
When the page owner declines or stays silent after a reminder and a second channel, and the use still matters to you, a separate removal request comes into view. Google's legal requests page says it is Google's policy to comply with notices of copyright infringement under the Digital Millennium Copyright Act and points to its Copyright Help Center for the requirements of a complete notice. This is not legal advice.
Should the first email attach the original file?
A link to your own published page and a short description of the original file are enough to start. Attaching a large file to a first message adds weight without adding clarity. Practical suggestion: keep the original in your evidence folder and offer to share a proof if the editor asks.
Who decides how the credit link is marked up?
Google's spam policy treats links created mainly to manipulate rankings as link spam. For links bought or sold for advertising or sponsorship it names the rel sponsored value, with nofollow as another option. Practical suggestion: ask for a visible credit and a working link, and leave the markup decision to the publisher.
Which name should go into the credit line I request?
Google's image license metadata page defines creditText as the name of the person or organisation credited for the image when it is published. Practical suggestion: write your requested credit line with the same spelling you put in that value, so your file, your page and your email agree. The page does not promise that the metadata will appear in search results.
How long should I wait before following up?
The documentation has no statement on waiting periods for credit requests. Practical suggestion: choose a waiting period that fits the site, write it in your log, and send one short reminder on the same email thread when it passes.
What if the publisher agrees to credit me but not to link?
A visible credit line already meets the main part of the request. You can explain in one sentence that a link helps readers reach the original, and then accept the answer. Pressing for the link turns a favour into pressure.
Does a copyright notice affect the other pages of the site that used my image?
Google's spam policy has a Legal removals section. It says that when Google receives a significant volume of valid copyright removal requests involving a given site, it can demote other content from that site in its results. That describes Google's own handling, and it is not a reason to skip the polite request first.
Conclusion
When your image is used without credit, begin with a credit request: an evidence folder, one clear sentence and a finished credit line. A courteous reminder comes second, and a separate removal route comes third if it is still needed. The creator and creditText fields help show whose image it is the next time. This is not legal advice.
If you want to place your own articles and images with editorial publishers that credit their sources, you can look at the guest post product.
Post a comment
Please log in to leave a comment. Login