A single announce function taking optional specific URLs, a reason and a force flag. It hashes the full live URL set — static pages plus every published post — compares it to the stored hash, narrows the instant ping to what actually changed, resubmits the sitemap to Search Console, and stores the new hash only if at least one announcement succeeded. An unchanged URL set is a no-op unless forced. There is also a standalone job for re-announcing on demand, and a dry-run mode.
Also called: published a post and nothing happened · sitemap ping · announce change · publish notification
- 1Publish, unpublish, delete, edit or a new marketing page calls announceSiteChange.
- 2The live URL set is built from the canonical page list plus published posts.
- 3An order-independent hash detects real change.
- 4The instant ping is narrowed to the changed URLs; the sitemap resubmit always reflects the full set.
- 5The hash is stored only when something landed, so a failed announcement retries on the next tick.
The function header is a post-mortem of three partial implementations: 'the panel's Publish pinged the post URL but never updated the change hash, the daily cron hashed only the static pages so it never noticed a post at all, and unpublish/delete announced nothing whatsoever. Three partial implementations meant a post could go live and be told to nobody — which is exactly what happened on 08-21.' The standalone job exists for a practical reason: the daily sweep 'is bundled with rank checks that cost real money per keyword, so "just re-announce the sitemap" was not something anyone could actually trigger.'
- Three separate half-implementations meant publishes went unannounced.
- The change hash ignored blog posts entirely.
- Re-announcing required running a job that costs money per keyword.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →