Review AI output responsibly

POM AI never publishes. Every tool hands back a draft, an attachment or a proposed change, and a person decides what happens next. That person carries the responsibility for what appears on the public site.

This page describes what that review has to cover. It is deliberately specific, because "check it looks right" is not a review.

The output is a draft in your voice, not a finished asset

Generated text is fluent by construction. Fluency is not accuracy, and it is not your brand. Two habits prevent most problems:

• read the draft as an editor, not as a reader who is pleased something appeared;
• rewrite at least the opening and the claims into the site's own language before saving.

If a draft needs no edit at all, that is a reason to look harder, not a reason to publish faster.

Verify facts before publication

Check anything a reader could act on or a competitor could challenge:

• prices, discounts, delivery times and availability;
• dates, opening hours, addresses and contact details;
• names of people, products, certifications and partners;
• statistics, comparisons and superlatives;
• links, which may be plausible but wrong.

A generated article can state a number confidently without any source behind it. Treat every specific figure as unverified until you have checked it.

Regulated and legal claims

Some claims carry legal weight regardless of who wrote them. Do not publish generated text that makes health, medical, financial, safety, environmental or guarantee claims without review by someone qualified to approve that claim for your business.

The same applies to anything that reads as advice — legal, tax, medical or financial. Generated copy will produce it happily. Your sector's rules still apply.

Images

Generated and edited images need their own checks:

• Rights and likeness. Do not use a generated image that depicts an identifiable real person, a real trademark or a protected character as if it were your own photography.
• Honesty. A generated or enhanced product image must still show the product a customer will receive. An enhanced image that improves what is actually delivered is a misrepresentation.
• Alternative text. Generated alternative text describes what the model saw, which is not always what matters to your reader. Rewrite it so it conveys the purpose of the image in context, and leave it empty for purely decorative images.
• Background removal. Check the edges, hair, transparency and how the result looks on both light and dark backgrounds.
• Replacements. Replacing an existing attachment changes it everywhere it appears. Find those places before replacing, not after.

See Image tools for the mechanics.

Translations

A machine translation is a first draft in another language. Before publishing:

• have someone who reads the target language review it;
• check terminology that is specific to your industry or product;
• check locale conventions — currency, date format, address format, formality;
• confirm that links point to the translated destination;
• confirm that shortcodes, placeholders and formatting survived intact.

Bulk translation multiplies both the saving and the risk. Translate a small representative set first, review it properly, and only then run the batch. See Translation.

Metadata generated in bulk

Bulk image metadata is the operation most likely to write many low-quality values at once, precisely because nobody reads 400 alternative texts. Run it on a small selection, read every result in that selection, and only widen the scope once the output is genuinely usable.

Disclosure and authorship

Decide, as a policy, whether your site discloses AI assistance, and apply that policy consistently. Do not present generated text as a named person's first-hand account, testimonial or professional opinion. Do not generate reviews, testimonials or endorsements at all.

Accessibility

Generated markup and copy still have to meet your accessibility obligations: meaningful heading order, link text that makes sense out of context, sufficient contrast in generated images, and alternative text that serves the reader rather than a keyword.

Bulk and destructive operations

Anything that changes many records at once — bulk metadata, bulk translation, site-wide copy generation, MCP write operations — deserves the same care as a database migration:

• try it on staging first;
• know how to undo it before you start;
• run the smallest scope that proves the outcome;
• check the result before widening the scope.

For MCP specifically, read the current state before writing, use a dry run where the tool offers one, and fetch the result afterwards rather than assuming success. See MCP boundaries.

The short version

Generated output is a starting point produced by a system that does not know your business, cannot check a fact and has no stake in your reputation. Everything after that point is editorial work, and it is yours.