Blogging ethics starts with one question: whose work is this, and did I say so? Most problems with credit, copyright and images come from skipping that question in a hurry. The answers are simple, and they protect your readers, the people you learn from and you.

Copying and Quoting Are Different Things
Quoting means using a short piece of someone’s text, in quotation marks, with their name and a link. Your own writing carries the post, and the quote supports it. Copying means their words carry the post and yours only fill the gaps.
Changing a few words doesn’t fix it. If you follow someone’s article paragraph by paragraph and swap in synonyms, that is still copying. Facts and ideas are free to use. The exact wording, the structure and the examples belong to the writer.
Here is a fair test. Could a reader skip the original because you copied its useful part? If yes, rewrite your post. Explain what you learned in your own words, add your own example and link to the source for the rest.
Give Credit and Link to the Source
When a post or a comment taught you something, say so and link to it. Name the person in the sentence, not in a footnote. A link on “this explanation of indexes by Sam” tells the reader far more than “click here”.
Credit costs one sentence and does three jobs. It thanks the writer, it helps readers go deeper and it shows your post stands on real work. For a long quote, a full diagram or a whole script, ask permission first and keep the reply.
Code needs the same care. A script from a forum answer or a public repository carries a license and an author. Read the license, keep the credit line and link to the source. When no license is stated, ask the author.
Images You Can Use
A picture found through a search engine is not a free picture. Search engines show images, but they don’t grant rights to them. Use an image only if you made it, hold a license for it or have the owner’s yes in writing.
| Image source | What to do |
|---|---|
| Your own photo or screenshot | Crop out names, emails, keys and other people’s faces or work. |
| Licensed image, free or paid | Read the license. Keep the credit line and a copy of the terms. |
| AI-generated image | Read the tool’s terms. Write your own prompt. Name no living artist, real brand or real person. |
| Someone else’s image | Ask for written permission before you post it. |
AI-generated images need care because they feel free. They aren’t a loophole. A prompt that says “in the style of” a living artist borrows that artist’s work without asking. A result that shows a real logo or product uses a brand that isn’t yours.
Describe the scene, the colors and the mood in your own words instead. If the tool draws something that looks like a real person or a known brand, discard it and try again. A new picture costs a minute, and a complaint costs much more.
Keep Other People’s Secrets
Stories make posts better, and they can also expose people. Don’t name a client, an employer or a colleague unless they agreed. Remove company names, server names, addresses and real customer data from every example.
Build your examples from data you made up. A chat message or an email from a colleague is private too. Quote it only with permission, and say what you changed.
Tell Readers About Sponsors and Free Gifts
Say so in plain words if a company paid you, sent you a product or pays you per click. Put the note near the top of the post, not at the bottom of the page. “The company gave me this tool to try for free” is a complete disclosure.
Disclosure doesn’t weaken a post. A hidden payment does, once readers find it. Keep one rule: you can accept the gift, but the verdict stays yours. If you wouldn’t recommend the product without the payment, don’t write the post. Many countries also require disclosure by law.
Fix Mistakes in Public
Every blog has wrong posts. A command fails on a new version. A number was a typo. A link now points to a different page. What matters is what you do after a reader tells you.
Correct the post and add a short note with what was wrong, what is right and the date. Don’t erase the wrong text without a trace, because readers who copied it need to know it changed. Thank the person who found the error, in a reply under their comment.
I’ve written on this blog since 2006, and it holds more than 5,800 articles. At that size, old posts age. A habit of correcting them matters more than a perfect record.
Handle Comments With Care
A comment section is a conversation in your house. Reply politely to questions, even basic ones. Remove spam, abuse and personal attacks. Keep disagreement, because a polite “I think this is wrong” is how you find your mistakes.
Treat reader details as private. Never publish a commenter’s email address, and don’t add anyone to a mailing list unless they asked. If a reader sends a private message and you want to quote it, ask first.
“Doesn’t Everyone Do It?”
You could say that everyone grabs images and quotes freely, and almost nobody gets caught. Fair point. Many bloggers never hear a word about it.
But the price of getting caught is a takedown notice, a bill or a public call-out. The price of checking is ten minutes. Readers also remember who gives credit, and so do the writers you hope to learn from.
A Short Checklist Before You Publish
Run through these seven questions once per post. After a few weeks, they become a habit.
- Is every quote in quotation marks, with a name and a link?
- Is the explanation in my own words, with my own example?
- Do I own, license or have written permission for every image?
- Does every AI prompt avoid living artists, real brands and real people?
- Is any sponsor, gift or paid link named near the top?
- Did I remove private details from screenshots and examples?
- Do I know where to add a correction note if I’m wrong?
This is general guidance, not legal advice. Laws differ by country, so ask a lawyer when money or a dispute is involved. Blogging ethics goes beyond what the law requires, and the checklist above is the part you control.
Blogging ethics is not a legal skill, it is the habit of saying where things came from.
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
Discover more from SQL Authority with Pinal Dave
Subscribe to get the latest posts sent to your email.




