Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →The simplest no-code solution is a notification plugin configured with a Post Published trigger and the post author’s email as the recipient. In the plugin’s recipient field, use {post_author_user_email}; include {post_title} and {post_permalink} in the message so the author can identify and open the published article.
What WordPress needs to send
An author alert requires two separate settings:
- Event: the article changes to a published state.
- Recipient: the email address belonging to that article’s author.
This is different from a subscriber newsletter and from comment notifications. WordPress discussion settings and developer references document comment- and note-related alerts, not a general publication email addressed to the content author.
Option 1: Configure the Notification plugin
The WordPress.org listing for the Notification plugin describes a workflow specifically for notifying authors when their posts are published.
- Install and activate the plugin from the WordPress dashboard.
- Create a new notification.
- Choose the Post Published trigger.
- Add an Email carrier.
- Set the recipient to
{post_author_user_email}. - Write a subject such as
Your article is live: {post_title}. - Include the title and public link in the message, for example:
{post_title}followed by{post_permalink}. - Save the notification and publish a test article assigned to a test author.
The plugin listing itself uses the question “How do I notify authors when their post is published?” and answers with the Post Published trigger and {post_author_user_email} recipient. Treat those merge tags as this plugin’s documented syntax, not as WordPress core fields.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
Check the content types before relying on it
Confirm which post types the installed version can monitor. A site that publishes pages, products, or custom editorial types may need additional configuration, and a trigger that works for standard posts may not automatically cover every type. Also check whether the notification fires only on first publication or again when an already-published item is updated.
Option 2: Use Publish Post Email Notification
The Publish Post Email Notification listing describes a more focused workflow: it automatically emails the post author when an administrator publishes and approves the content.
This can fit a moderated newsroom in which authors submit drafts and an editor makes them public. Verify the current plugin description and plan terms before installing: the listing places custom post type support in its Pro version. If your workflow includes a custom post type, do not assume the free version will cover it.
Option 3: Have a developer add a publish hook
Custom PHP can send an email when WordPress transitions content into the published state. WPBeginner presents both a plugin method and a PHP publish-hook example. A developer should adapt that approach to your WordPress version, post types, editorial statuses, and mail configuration rather than pasting an unreviewed snippet into production.
Decisions to settle before coding
- Should the message fire only when a draft becomes public, or also when a scheduled post publishes?
- Should revisions, status changes, pages, and custom post types be included?
- What should happen if the author has no usable email address?
- How will the code prevent duplicate messages when a save operation repeats?
- Will the site use
wp_mail()directly or an SMTP-backed mail path?
Put custom code in a maintainable site-specific plugin or equivalent deployment mechanism, not in a theme file that may be replaced during a theme change.
Plugin versus custom code
| Approach | Setup and maintenance | Recipient and message control | Pages or custom post types | Delivery diagnosis |
|---|---|---|---|---|
| Notification plugin | Dashboard configuration; updates and feature changes remain the plugin’s responsibility. | Documented recipient merge tag and post fields such as title and permalink. | Verify the installed version’s supported types. | Depends on the plugin and site mail configuration. |
| Publish Post Email Notification | Simple author-focused setup. | Designed for an author email after administrator approval and publication. | Custom post type support is listed as a Pro feature; confirm current terms. | Check the plugin’s own settings and the site’s mail path. |
| Custom PHP | Requires development, testing, deployment, and future compatibility checks. | Most flexible: conditional recipients, templates, and status rules can be coded. | Can be tailored to selected post types and transitions. | You must add your own logging and failure handling. |
These are feature-level distinctions, not independent reliability tests. Plugin features, plan limits, and compatibility can change.
When an email does not arrive
- Confirm the author address. Check the user account assigned to the post and make sure its email is current and deliverable.
- Confirm the event. Test a genuine transition to published status, not merely an edit to an article that was already public.
- Confirm the scope. Make sure the notification covers the post type and editorial workflow you are testing.
- Check notification settings and logs. Review any debug, history, or failed-send information exposed by the chosen plugin.
- Test the mail path. The PostNotify listing describes SMTP support and an SMTP configuration test. Use an SMTP-backed setup and run its test when the host’s default mail path is suspect; a successful configuration test still does not guarantee inbox placement on every host.
- Check spam and authentication. Inspect the recipient’s spam folder and your domain’s mail-authentication and hosting policies with the site administrator.
Recommended setup for a typical editorial site
Start with a dashboard-configured notification: select Post Published, address it with {post_author_user_email}, and add {post_title} plus {post_permalink}. Test both a normal post and every important custom content type. If the workflow requires administrator approval semantics, evaluate Publish Post Email Notification and verify its current plan limits. Choose custom code only when you need rules or content-type coverage that the plugins cannot provide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
