Moderation, replies, and the rows a previous app rejected

Imports that "clean up" your history by dropping anything the last app disliked are a kind of theft. AgentReady keeps those rows and leaves them unpublished.

You open them. You decide.

Inherited status

Judge.me, Okendo, and Loox each have a rejected or hidden state. On import that state becomes unpublished, not deleted. Duplicate-safe re-imports do not clone the row. The how-to is moderation and replies.

If you are still choosing a source file, start with CSV import or the vendor guides for Judge.me and Okendo.

Public replies

A store response is a first-class field. It renders on the list block. It round-trips through export. It is not a private note.

What a fetcher sees

Unpublished means unpublished. The Liquid snapshot only includes approved published reviews. That is the same rule as AI readability. Moderation is how you choose the library an agent can read.

AgentReady Reviews and what free means cover the commercial line. The positioning is Reviews AI agents can actually read.

Frequently asked questions

What happens to reviews my old app rejected?

They import unpublished. AgentReady does not auto-publish a row the previous app hid or marked spam.

Can I reply in public?

Yes. Store responses are stored with the review, shown on the storefront when published, and exported as merchant_reply.

Does moderation cost extra?

No. Publish, unpublish, replies, and photo hiding are free.

Do unpublished reviews affect AggregateRating?

No. Only approved, published reviews enter the snapshot and any opt-in rating markup.

Get found and recommended by AI shopping assistants.

Run the free AI-Readiness Checker to see, in about ten seconds, how ChatGPT, Perplexity, and Google read your store today and exactly what is holding it back. Then AgentReady fixes the gaps for you, adding Schema.org structured data, an llms.txt directory, and an ongoing audit. Install free; every software feature is $29/mo.