How-To Guides
An Honest Review Policy You Can Actually Publish
Write a public policy that protects readers and your storefront accounts. What to ban, what to allow, and how to say it in plain English.
This is a publishing explanation you can adapt for your own site. It is not legal advice. Store rules change, and the law that applies to you depends on where you live and where you sell. Read the current policy on each retailer you use. If you need advice about a contract, a paid partnership, or a complaint, ask a lawyer. ReaderMagnet's own public rules are on the honest review policy and the ARC compliance page. Yours should match the way you actually behave, not the way a template sounds.
A review policy is a public promise about what you will and will not ask of a reader. You publish it so a stranger can see the terms before they take a free book, and so future-you has something to point at when a well-meaning friend offers to "round up five-star reviews." If the policy says one thing and your email says another, the email is the real policy, and the page is decoration.
What is the policy trying to protect?
Three things, in this order.
The reader, who should be able to take a free copy without owing you a mood. The store account, which can be damaged by reviews that look bought or required. Your future self, who will be tempted, during a bad launch week, to hint that advance readers should "help the book" by polishing a rating.
The policy is not a marketing asset. It should not be cute. It should be specific enough that a reader can tell whether they are allowed to dislike the book in public. If the answer is no, you do not have an honest-review policy. You have a fan club with extra steps.
Readers who want the short public version of how ReaderMagnet treats this can start at Become a reviewer. Authors who want the campaign around the policy can read How to run an ARC campaign.
What should the page say in plain language?
Use headings a person can skim on a phone. Here is a structure that covers the decisions. Rewrite the sentences in your voice. Do not publish them if you will not follow them.
The copy is free. The review is not required. Say that the advance file is a free copy, not a payment for a rating. Say that a reader may stop, may skip the review, and may post a negative review. Say that you will not charge them, punish them, or remove them from a list as revenge for a low star count. You can still choose not to invite someone back if they abused the file or harassed you. Those are different facts. Write them as different facts.
Honesty includes the parts that did not work. Say you would rather have a specific two-star review than a vague five-star review the reader does not mean. You do not have to sound thrilled about negative reviews. You do have to stop asking people to hide them.
Disclose the free copy. Tell readers that if they post, they should follow the store's current disclosure rules. A simple line they can use, if it still matches the store's language when you publish: "I received a free advance copy. The review is my own." Do not hand them a paragraph of praise and call it a disclosure.
No payment, gifts, or extra books for a rating. Ban the obvious deals: gift cards, cash, a bonus novella, a place in a contest, or entry into a street team that requires stars. A free advance copy is already the access. Adding a prize for a positive review changes the nature of the post. The FTC's Endorsement Guides are the public explanation of why a material connection between a reviewer and a seller has to be clear. Read them. Do not rely on this article as a substitute.
You will not coach the wording. Say that you may send a link to the store page. Say that you will not send required phrases, forbidden phrases, or a target star count. Say that you will not ask a reader to change a review because it hurt your feelings or your rank.
Where reviews can go. Name the stores you care about. Tell readers a review on a retailer, a bookseller page, or a reader site is their choice. Do not require a screenshot as proof. Screenshots of stars are how policies become quotas.
How to reach you. Give one address for file problems and a different instruction for reviews: file problems come to you, reviews go on the store, and you do not discuss the star count by email. ARC support is the support door when the copy is hosted on ReaderMagnet.
Updates. Put a date on the page. When you change the policy, change the date. A policy with no date looks copied.
What should you explicitly forbid?
Write the bans as behaviors, not as attitudes.
- Do not require a review in exchange for the file.
- Do not require a positive review, a minimum star rating, or a "helpful" tone.
- Do not pay for reviews, directly or through a prize that depends on the rating.
- Do not ask readers to review a book they have not read, including a book they returned or did not finish. Some stores allow a review after a partial read. Your policy can still say you only want reviews from people who are telling the truth about how much they read.
- Do not review-trade with other authors in a way that exists to inflate both of you. A sincere review of a book you finished is different from a pact. If you cannot tell the difference in a sentence, do not do the pact.
- Do not ask family members to post as if they were customers who stumbled on the book, if the store forbids that kind of close relationship. Read the store's current rule rather than guessing.
- Do not use a review policy page to attack a reader who left a review you dislike. The page is terms, not a rebuttal.
If a service offers "guaranteed reviews" or "verified five stars," the policy should be the reason you say no. Put that refusal in the page if you want the reminder in public. "I don't hire review services" is a useful sentence on a bad afternoon.
How do you publish it so people can find it?
Put the policy on your site at a stable URL. Link it from the ARC landing page, from the delivery email, and from the magnet's back matter if you also ask for anything that could be confused with a review. One link is enough. You do not need a pop-up.
On the landing page, a short version can sit beside the claim button: "Reviews are optional and unpaid. The full policy is here." The long version can live on its own page so the claim screen stays readable. Landing pages fail when they become the policy. The split is described in Landing pages for ARCs that reduce support.
Match the email sequence to the page. If the page says optional and the third email says "I really need your review today," you have unpublished the policy. The mail should be able to survive being read next to the page. See ARC email sequences that don't nag.
If you use ReaderMagnet, you do not need a second, contradictory policy for the same campaign. Point at one page. During open beta you can list your book without a card until January 1, 2027, and the reviewer-facing language should still be yours.
Add the link to your author site in the footer or the book page, not only inside a PDF nobody will reopen. People look for policies when something feels off. They will not look inside the EPUB.
What do you do when a review hurts?
Follow the policy you published. Read the review once for a real error: a broken file, a missing chapter, a description that promised a different book. Fix the error if it is in your control. Do not reply on the store if the store tells authors not to argue with reviews. Do not write to the reader asking them to revise the star count.
You may write a private thank-you if you already have a relationship and you can do it without a request attached. Many authors should not. The urge to "clarify" is the urge to manage the record. The policy exists to interrupt that urge.
If the review reveals a private detail or is abusive rather than negative, use the store's report tools. That is not the same as disliking a paragraph about your pacing. Learn the difference before you are angry, and write it into an internal note if you need to. The public policy can stay short.
A thin launch with honest reviews is a better record than a padded launch you have to worry about later. You cannot unpublish the fact that you asked for a quota. You can decide not to ask.
How do you keep the policy true six months from now?
Reread it when you copy a campaign forward. The dangerous moment is not the day you publish the page. It is the day a promo service, a group admin, or a tired co-author suggests a workaround. Compare the suggestion to the bans. If it conflicts, decline. You do not need a new philosophy for each offer.
If your practice changes, change the page first, then the emails. Do not let the mail drift for a month because you are busy. Drift is how authors end up with a policy that forbids paid reviews and a calendar full of "reviewer appreciation gifts" that only go to five-star posts. If the gift depends on the stars, it is not appreciation. It is a payment. Take it out, or take the policy down and stop calling the process honest.
Keep a copy of what you sent. If a retailer asks what you promised readers, you want the email and the page, not a memory of your intentions. Intentions are not the record. The sentence "in exchange for an honest review" is a record, and it is the wrong sentence even when you meant well. Prefer "if you want to leave an honest review, here is the link."
The disclaimer posture is the right one for the footer of your policy too: you are telling readers how you run the campaign, and you are not offering them legal advice either.
A page you can finish this week
- Write the bans as a list you are willing to follow on launch day.
- Write the positive promise in a paragraph a tired reader can finish: free copy, optional review, disclosure, no coaching.
- Add the date, your contact for file problems, and links to the retailer policies you actually checked.
- Put the page on a URL you will not change.
- Link it from the claim page and from the delivery email.
- Delete any older template that contradicts it, including the one in your downloads folder with the subject line "review swap."
Then stop decorating the page. A plain policy that you follow is the whole assignment. Readers do not need a manifesto. They need to know they can tell the truth and keep the book.
How should co-authors and early trade reviews be named?
If the book has two authors, the policy should say which of you talks to readers and that neither of you will coach a rating. A reader should not get one email from each of you with a slightly different ask. Pick one sender for the campaign. The policy page can name both authors and the single address for file help.
A trade with another author is the situation most likely to rot a clean policy. You may read their book because you want to. You may post about it if the store allows that relationship and you describe it honestly. You may not agree, even informally, that you will exchange positive reviews of a specified star level. Write that refusal down. In the week a friend is scared about a launch, the written line is easier to keep than a vibe.
If you quote a reader in your own marketing, ask first, quote the words they actually wrote, and do not attach the quote to a star graphic they did not approve. A policy that forbids coaching reviews and then mashes those reviews into advertisements will not survive a careful reader. Either leave the quotes off the claim page or treat them as heavily as you treat the review itself: accurate, optional, and not a condition of the free copy.