AI images used to be a novelty. Now they’re ordinary production tools.

That creates a simple problem for small businesses: the same tool that helps you make a blog graphic in five minutes can also make your website look less honest if you use it in the wrong place.

A generated background illustration is one thing. A fake technician standing in a fake customer’s home is another. A product mockup is useful. A fake before-and-after result is dangerous. A stylized blog thumbnail is fine. A fake client testimonial photo is not.

The line is not “AI or no AI.” The line is whether the image affects trust.

That line matters more in 2026 because disclosure expectations are getting clearer. The EU AI Act’s Article 50 says deployers of AI systems that generate or manipulate image, audio, or video content constituting a deep fake must disclose that the content was artificially generated or manipulated. The European Commission’s page on the AI-generated content Code of Practice says the transparency obligations are meant to address risks of deception and manipulation. Adobe describes Content Credentials as a durable, industry-standard metadata type that works like a digital nutrition label for content, showing how it was made, including whether AI was involved.

Most small businesses don’t need to panic. They do need a policy.

Start with the buyer’s question

The fastest test is this: what is the buyer using the image to decide?

If the image is just decoration, the disclosure standard can be lighter. If the image is evidence, it needs to be real or clearly labeled.

For example, a generated abstract background on a blog post about tax planning probably doesn’t change what a buyer believes about your service. A generated photo of a smiling accountant shaking hands with a client does. That second image suggests a real person, a real office, and a real customer interaction.

The same applies to local service businesses. A fake electrician in a fake attic doesn’t prove your crew knows what it’s doing. A fake landscaping project doesn’t prove you can make a yard look that way. A fake dental patient doesn’t prove anyone had a good experience in your office.

This is where many small business websites get themselves in trouble. They treat every image as filler. Buyers don’t. Buyers use images as proof.

The images that need clear disclosure

You don’t need a 20-page AI policy to make good decisions. You need a short list of high-risk image types.

Label AI involvement clearly when an image shows:

  • A person who looks like a real customer, employee, owner, expert, or patient
  • A product, project, room, vehicle, storefront, facility, or result that a buyer might assume is real
  • A before-and-after comparison, testimonial, review, case study, portfolio piece, or safety-related example
  • A location-specific scene, such as a local office, restaurant interior, job site, neighborhood, or event
  • A product variation, bundle, packaging design, installation, or finished outcome that does not physically exist yet

That list may feel strict, but it protects the parts of your website that do the heaviest sales work.

The FTC’s business guidance on artificial intelligence warns companies not to make deceptive claims about AI products or outcomes, and the agency’s broader AI page collects enforcement and guidance around AI-related deception. The FTC’s rule on consumer reviews and testimonials also targets fake reviews, false testimonials, and misrepresented endorsements. If an AI image makes a fake person look like a satisfied customer, disclosure does not magically make that safe.

A plain rule works better: don’t invent proof.

What a good AI image label looks like

A useful label is short, visible, and specific. It should tell the visitor what they’re looking at without making them read a legal note.

Good labels sound like this:

  • “AI-generated illustration”
  • “AI-assisted product concept, not a finished installation”
  • “Generated example image, not an actual client project”
  • “AI-created background image”
  • “Concept rendering based on our design direction”

Bad labels sound like this:

  • “Enhanced visual”
  • “Representative image”
  • “For illustrative purposes only”
  • “Digitally optimized”
  • “Creative asset”

Those phrases are too slippery. They make the business look like it’s trying to dodge the question.

Put the label close to the image. A caption under the image is usually better than a sitewide disclosure in the footer. If the image appears in an ad, landing page, product page, case study, or social post, the disclosure should travel with it.

Adobe’s Content Credentials overview is useful because it frames provenance as a digital nutrition label. That is the right mental model. People don’t need a lecture. They need a quick, understandable signal.

Content Credentials help, but they don’t replace plain labels

Content Credentials and C2PA are worth watching. C2PA’s conformance page says the Interim Trust List has been retired and the newer C2PA Trust List is governed under the C2PA Conformance Program. The C2PA Conformance Explorer also lists conformant tools and providers.

That matters because provenance is moving from a nice idea into real infrastructure.

But for a small business website, metadata alone is not enough. Most visitors will not click into image credentials before deciding whether to call you. Many platforms also strip metadata when images are uploaded, resized, compressed, or shared.

Use Content Credentials when your tools support them. Keep original files. Save source prompts or creative briefs for important AI-assisted assets. Maintain a folder that shows which images are real photography, which are edited, and which are generated.

Then still use plain-language captions for anything that affects trust.

Think of it like food packaging. The detailed nutrition label is useful, but the front of the package still needs to be honest.

Where AI images are usually safe

AI visuals can still be a good fit. The mistake is using them as evidence instead of design support.

Safer uses include blog thumbnails, abstract backgrounds, icons, explainer graphics, concept sketches, moodboard visuals, pattern images, and early design directions. Those images help explain an idea or make a page feel finished without pretending to document real-world proof.

For example, a plumber could use an AI-generated illustration for a blog post about winter pipe protection. That is different from using an AI-generated “customer basement flood” as a case study image.

A manufacturer could use an AI-assisted concept graphic to explain a new service process. That is different from showing a generated photo of a finished part and letting buyers think it came off the shop floor.

A consultant could use a generated header image on a newsletter. That is different from creating fake audience photos for a speaking page.

This distinction keeps AI useful without letting it blur the facts.

Where AI images should stay out

Some parts of a website should be boringly real.

Your team page should show real people. Your portfolio should show real work. Your testimonials should come from real customers. Your before-and-after images should document real outcomes. Your product photos should show what buyers can actually receive, unless they’re labeled as concepts or renderings.

The reason is practical, not moralistic. These areas reduce buyer risk.

A homeowner hiring a contractor wants proof that the crew is real. A patient choosing a clinic wants to know what the office and people are actually like. A buyer comparing manufacturers wants confidence that the examples reflect real capability. A restaurant customer wants the food and room to match expectations.

If AI fills those slots, it may make the page prettier while making the business less believable.

That trade is usually not worth it.

Build a simple AI image policy for your website

A small business policy can fit on one page. It should answer four questions.

First, what types of images are allowed to be AI-generated? Put low-risk items here: blog graphics, abstract art, icons, diagrams, moodboards, and concept visuals.

Second, what types are not allowed? Put proof-based items here: employees, customers, reviews, case studies, before-and-after work, local facilities, finished projects, products for sale, and safety examples.

Third, when is a label required? Require a label whenever the image could change a buyer’s belief about who you are, what you’ve done, what you sell, where you operate, or what result they can expect.

Fourth, who approves the image before it goes live? For a very small business, that might be the owner. For a bigger team, it might be marketing plus whoever owns the product, service, or client relationship.

Keep the policy practical. You are not trying to slow the team down. You’re trying to stop the bad shortcuts before they become public.

A quick audit you can run this week

Open your homepage, service pages, about page, product pages, case studies, testimonials, and highest-spend ad landing pages.

For each important image, ask three questions:

  1. Would a normal visitor assume this is a real person, place, product, customer, or result?
  2. If the visitor later learned it was AI-generated, would they feel misled?
  3. Would the image affect whether they contact us, buy from us, trust us, or believe a claim?

If the answer is yes, either replace the image with real photography, add a clear label, or move the image to a less proof-heavy role.

This audit often reveals easy wins. Replace fake team imagery with a quick phone photo. Swap a generated project scene for a real job site photo. Move concept art from a case study into a clearly labeled planning section. Add captions to AI-assisted product renderings. Save originals so your team knows what is real later.

The goal is not perfection. The goal is not making your site visually plain. The goal is making sure the images that carry trust are honest.

The business case: trust beats polish

Small businesses often overestimate polish and underestimate proof.

A slick fake image can make a page look expensive. A slightly imperfect real image can make the business feel believable. On the pages where buyers are trying to reduce risk, believable wins.

This is especially true for service businesses, contractors, professional firms, healthcare practices, local retailers, manufacturers, and B2B companies with long sales cycles. The visitor is not just buying a look. They’re deciding whether to let you into their house, put you in front of their boss, trust you with their data, or spend money on something they can’t easily undo.

If you’re using AI visuals, use them where they speed up production and clarify ideas. Keep them away from the parts of the site that are supposed to prove real experience.

That one rule will keep you out of most trouble.

Need help cleaning this up?

If your website has a mix of stock photos, AI visuals, old project images, and unclear product shots, this is a good time to audit it before buyers start asking harder questions.

YourWebTeam can help you sort what to keep, what to label, what to replace, and where real proof will improve conversions. Start here: /get-started/.