Understanding editor feedback
What "changes requested" and "rejected" mean and how to act on them.
The editor has three buttons when reviewing a post: Approve, Request changes, and Reject. This page covers what each means for you as the author.
Approve¶
The post is published. You will see an in-app notification within seconds and, if you have the email toggle on for "My blog post is published", an email with a link to the live post. Your slug is locked at this point; if you edit the post later, the URL stays the same.
Request changes¶
The editor wants edits before publishing. The post returns to draft so you can keep working, and the editor's message lands as a yellow callout under the post on your blog dashboard. Open the post, address the feedback, and submit again. There is no limit on how many revision rounds you can do.
You will see an in-app notification and, if the email toggle is on, an email with the editor's message. Both link straight back to the editor for that post.
Reject¶
The editor decided the post is not a fit for the blog. The post moves to rejected status and the editor's reason is stored alongside it. You can write a new post any time, but you cannot resubmit a rejected post. If you think a rejection was a mistake, reply to the email you received and a human will take another look.
Picking notifications¶
All three events are individually toggleable on your notification preferences page under the Blog & comments group. You can receive in-app notifications, emails, or both, on a per-event basis.