Which has better reviews, Published By or Stealth Update?

Published By (5.0★, 1 reviews) and Stealth Update (5.0★, 5 reviews) are essentially tied on rating. Look at review velocity and individual reviewer quotes — both visible on each app's detail page — to differentiate.

Should I choose Published By or Stealth Update?

AppRanks cannot separate these two on rating — both sit at 5.0★. Stealth Update does carry the larger published review base (5 vs 1). Read both apps' detail pages for the feature breakdown and recent listing changes.

Which is faster to set up, Published By or Stealth Update?

Both apps are one-click installs from the WordPress Plugin Directory. Stealth Update has the deeper published review base (5 vs 1), which often — though not always — accompanies better-tested setup docs. AppRanks doesn't measure setup time directly: read the recent reviews on each app's detail page for user-reported install experience.

Which works better for small vs large WordPress Plugin Directory site owners?

Published By typically suits early-stage and growth-mode teams based on its published review base (1 reviews). Stealth Update typically suits early-stage and growth-mode teams based on its published review base (5 reviews). A larger review base generally means the app has been exercised at scale — relevant if you are processing high volume or handling enterprise compliance requirements.

Can I migrate data between Published By and Stealth Update?

Migration support varies by app and category. Published By and Stealth Update both publish their export options on their marketplace listing pages (or in their support docs); some apps offer one-click import from competitors, others require CSV. The fastest check: search "import from Published By" in each app's help center. AppRanks does not track migration tooling directly — this is a category-specific capability worth verifying before commitment.

AppRanks

Published By vs Stealth Update — WordPress

Published By vs Stealth Update

Name: Published By
Rating: 5 (1 reviews)

Side-by-side comparison · 24 data points

Published By

5.0·1reviews·50+installs

wordpress

Change

Reset

1. Listing metadata

Field-level data

	Published By	Stealth Update
Tagline	—	—
Description	1553 / 5000 chars31% used	2360 / 5000 chars47% used
Screenshots	—	—
Languages
Platforms	WordPress	WordPress
Developer	Scott Reilly	Scott Reilly
Listed	—	—
Last updated	—	—

2. Categories & rankings

Shared categories on the same row · in-category position inline

Published By

Stealth Update

Shared

At a glance

4 metrics · auto-computed

Feature comparison between Published By and Stealth Update
Metric	Published By	Stealth Update
Rating	5.0 ★	5.0 ★
Total reviews	1	★ 5
Active installs	50+	100+
Free plan	—	—

3. App details

Long-form description · keyword frequency

Published By

This plugin records which user actually published a post, which in a multi-author environment may not always be the original post author. This helps to maintain accountability for who was ultimately responsible for a post appearing live on a site. The admin listing of posts is amended with a new “Published By” column that shows the name of the person who published the post (for those posts that have actually been published). A dropdown above admin post listings allows for the listing to be filtered by a particular publishing user (but only includes posts with a known publishing user). For posts that were published prior to the use of this plugin (and thus the plugin could not directly record who published those posts), the plugin makes a best guess attempt to ascertain who published the post. After failing to find the publisher of the post as recorded by the plugin, it checks for who last edited the post, then who is responsible for the latest revision of the post, and finally failing those, it assumes it was the post author. In cases where it had to go through this process, the name of the person it deduced as the likely publisher appears italicized and with a question mark at the end. If you’d rather the plugin not make an attempt to guess the publisher, you can disable the checks by including this snippet in your theme’s functions.php (or, ideally, a site-specific mu-plugin): Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage

Top keywords

post10×3.94%
published7×2.76%
posts5×1.97%
author3×1.18%
publisher3×1.18%
user3×1.18%
actually2×0.79%
admin2×0.79%
attempt2×0.79%
checks2×0.79%
failing2×0.79%
guess2×0.79%

Stealth Update

This plugin allows you to choose to update a post without having WordPress automatically update the post’s post_modified timestamp. WordPress maintains a post field called post_modified which tracks the date the post was last edited. This value is used by feeds to indicate the latest update to each post or to report the latest updated post. Plugins and themes may also reference the post modification date to call attention to posts that have been updated. However, if an update is such that you don’t want it to be recorded in the post_modified date field (perhaps due to the update being a small formatting/editing change or fixing a typo, or if you just want to keep quiet about an update), then this plugin is for you. This plugin adds a “Stealth update?” checkbox to the “Publish” box of any post’s or page’s “Edit Post” admin page. Note: The plugin records when a post is stealth updated, so subsequent edits of the post will have the “Stealth update?” checkbox checked by default. Links: Plugin Homepage | Plugin Directory Page | Author Homepage Filters The plugin is further customizable via two filters. Typically, these customizations would be put into your active theme’s functions.php file, or used by another plugin. c2c_stealth_update_meta_key (filter) The ‘c2c_stealth_update_meta_key’ filter allows you to override the name of the custom field key used by the plugin to store a post’s stealth update status. This isn’t a common need. Arguments: $custom_field_key (string): The custom field key to be used by the plugin. By default this is ‘_stealth-update’. Example: /** * Defines a custom meta key to be used by Stealth Update. * * @param string $custom_field_key The default custom field key name. * @return string */ function override_stealth_update_key( $custom_field_key ) { return '_my_custom_stealth-update'; } add_filter( 'c2c_stealth_update_meta_key', 'override_stealth_update_key' ); c2c_stealth_update_default (filter) The ‘c2c_stealth_update_default’ filter allows you to override the default state of the ‘Stealth Update?’ checkbox. Arguments: $state (boolean): The default state of the checkbox. By default this is false. $post (WP_Post): The post currently being created/edited. Example: // Have the Stealth Update? checkbox checked by default. add_filter( 'c2c_stealth_update_default', '__return_true' );

Top keywords

update20×5.14%
post18×4.63%
stealth15×3.86%

Published By vs Stealth Update

Published By

1. Listing metadata

2. Categories & rankings

Stealth Update

At a glance

AppRanks verdict

3. App details

Frequently asked

Which has better reviews, Published By or Stealth Update?

Should I choose Published By or Stealth Update?

Which is faster to set up, Published By or Stealth Update?

Which works better for small vs large WordPress Plugin Directory site owners?

Can I migrate data between Published By and Stealth Update?

See full keyword rankings, install trends, and weekly alerts

More popular comparisons