SEO'n'AI

Mark your AI generated images — visibly for your visitors, machine-readably for everything else. One click in the media library gives an image both halves of the disclosure: a badge wherever the image appears on your site, and an IPTC / C2PA provenance label written losslessly into the file itself.

If the EU AI Act’s transparency rules are on your mind: this is the technical half of that disclosure. Whether it satisfies your obligations is a legal question, and the FAQ below is honest about it.

This is not a watermark plugin. It works on the layer underneath: the provenance metadata inside your image files. Image generators are increasingly expected to embed a machine-readable marking — an IPTC DigitalSourceType value in XMP, or a C2PA manifest. SEO’n’AI – AI Image check&mark opens your files and reads it. It tells you which images carry such a marking, which do not — and it can write the missing label into them.

What makes this different

• It labels both layers at once. Marking an image gives it the visible badge on the page and the machine-readable marking in the file — the human-readable and the machine-readable side of the same disclosure.
• It writes losslessly. The XMP packet is inserted into the container by hand — JPEG APP1, PNG iTXt, WebP RIFF chunk. The compressed image data is copied through byte for byte. Nothing is re-encoded, no quality is lost. Watermarking plugins cannot do this, because re-encoding is how they work.
• It does not touch a single pixel. The badge is a CSS overlay you can restyle or switch off at any moment.
• It reads provenance metadata, too. Uploads are inspected on arrival; if the file declares itself as AI generated — via IPTC in XMP or a C2PA / Content Credentials manifest — the image is marked automatically. No other step needed.
• It tells you where the badge does not appear — bluntly, on its own settings screen, instead of letting you assume it is everywhere.

Features

• A per-image checkbox in the attachment details panel, and a one-click “Mark as AI generated” link on every row of the media list
• A Marking details screen per image: what the file actually carries — IPTC DigitalSourceType, C2PA, per generated size — including the raw XMP block, so you can verify rather than trust
• A badge — the visible AI label — in the corner of every image WordPress renders, with configurable text, position, size and style
• An honest alt text, so screen reader users get the disclosure too
• A data-ai-generated="true" attribute on the image tag
• Detection of an existing marking (IPTC DigitalSourceType, C2PA) on upload, per image, for a hand-picked selection, and as one run across the whole library
• Automatic marking of uploads whose file already declares itself as AI generated
• Writing the marking into new uploads and into images already in your library, one at a time, or as one batch run over everything that is missing it
• A filter and a status column in the media library

Neither the reading nor the writing is held back: you can examine every image in your library, and write the marking into every image that needs one, with no limits and no quota. For running your own site, this plugin is complete.

A file is never given a second metadata block. If it already carries XMP from another tool — a photo editor, a stock library — that block is left exactly as it is and the plugin says so instead of writing next to it.

Honest about the limits

The badge — the visible half of the label — is a CSS overlay. It appears where WordPress renders the page, and nowhere else. It does not appear in:

• Social media previews — the platform loads the file, not your page
• The image file itself, when downloaded or opened by direct URL
• RSS feeds and newsletters
• Lightboxes that rebuild the image element
• Google Images, scrapers and hotlinking third parties

Images used as a CSS background used to be on that list as well. Page builders lean on backgrounds heavily — sliders, hero areas and section headers are almost always backgrounds rather than image tags — so a site could look completely unbadged while everything was in fact working. The smart check closes that gap: switch it on and the finished page is inspected once before it is sent, including the stylesheet files on your server, and the badge is placed onto whatever element carries a marked background. It is off by default, because it looks at the whole page.

One thing to remember either way: if you run a caching plugin, clear its cache after marking an image. A cached page was built before the marking existed and keeps being served exactly as it was, so the badge looks missing when the page is simply old.

The plugin says all of this plainly on its own settings screen, under “Where it reaches”, along with ways to deal with what is left.

Optional add-on

Read the full description on the official page →