You will learn where to find images safely, how to check licenses in plain language, and how to write credits that protect you and respect creators. Graphics are placed below each heading for clarity. Written in simple English for beginners, second‑person voice.
When you use images the right way, you protect your blog, your clients, and your own reputation. You also thank the people who created the work. This SOP gives you a simple path so you can find images fast, credit them correctly, and keep a clear record of permissions.
Decide why you need the image. If it explains something, you may need a screenshot or a simple chart. If it is decorative, consider your own photos or brand shapes. Planning first saves time and helps you avoid last‑minute, risky picks.
Best to worst for safety: create your own image (photo, screenshot, chart) → use paid stock from a reputable library → use free libraries with clear licenses. Avoid “random from social” or “found on Google Images” unless you have written permission.
Translate the license to everyday words. Answer: can you use it for commercial work (a paid blog or client site), can you edit it, do you need to credit, and are there limits like “no logos” or “no resale”?
Be careful with images that show clear trademarks, recognizable people, or private places that restrict photography. Stock sites usually flag these with “editorial use only.” If you need a marketing image, avoid editorial‑only photos.
Copy the page link, license link, and take a quick screenshot of the license terms. Add the date you downloaded it. Paste all of this in your source log. This keeps you safe if the site changes the license later.
Place the credit below the image or in a “Credits” section. Link the creator name to their page and link the site or license text to the license page. Keep one style across your site.
Web example (free CC BY): Photo by Jane Doe via Unsplash (CC BY 4.0). Web example (paid stock): © 2025 StockSite Standard License. Own work: Illustration: Your Name, © 2025.
Many licenses allow edits like crop or color correction. Most do not allow you to remove logos or change the meaning of the image. If the license says “no derivatives,” don’t edit beyond basic format changes.
Keep file sizes small for fast pages. Use descriptive filenames and write alt text that explains what the image shows. This helps readers and improves accessibility.
Save the optimized image in your images folder. Save the license screenshot and links in a “proof‑licenses” folder with the same base filename so it’s easy to match later.
Preview your page. Check that the credit shows correctly, the links open, and your source log has the record. Now you’re safe to publish.
Focus on what you can do: can you use it on a site that earns money, can you edit it, must you credit, and are there share‑alike conditions that pass to your work? If unsure, pick another image or write to the creator for permission.
Credits block example: Images: Photo by Jane Doe via Unsplash (CC BY 4.0); Graph by Your Name © 2025; Map © StockSite Standard License.
| Filename | Creator | Source URL | License | License URL | Use (post URL) | Notes | Date |
|---|---|---|---|---|---|---|---|
| travel‑adapter‑types.webp | Jane Doe | https://… | CC BY 4.0 | https://… | /blog/on‑page‑seo | Credit under image | 2025‑11‑03 |
Tip: Keep this table in your CMS, Notion, or spreadsheet. Paste the credit style you use so all posts are consistent.
Requesting permission (email): Hello [Name], I love your photo “[title/URL]” and would like to use it in a blog post on [site]. The post is non‑defamatory and family‑friendly. I will include a credit and link. May I have your permission to use it once on the web? Thank you, [Your Name]
Tip: Paste this into your CMS so teammates can tick items.
It means you can use the image for news, commentary, or education, but not for marketing or ads.
It means not connected to money (no ads, sales, or client work). Most blogs are commercial; avoid NC licenses unless your use fits.
No, but it’s kind to credit. It also helps you track sources later.