Only Self Pings

Saving an empty list blocks all outgoing pingbacks handled by this plugin, including self-pings. A missing or structurally damaged option defaults to your current public site URL. Invalid entries within a saved list are ignored, not treated as permission to ping any site.

Your saved list is retained, but URL matching is deliberately stricter. External HTTPS URLs are no longer allowed automatically. Lookalike hostnames and partial path matches are blocked. HTTP and HTTPS are separate, and paths are case-sensitive.

Review your settings after upgrading, particularly if your site moved to HTTPS or another domain. Saved URLs are not automatically rewritten. Old entries containing query strings, fragments, credentials or ambiguous paths no longer allow pings; replace them with the intended origin/path rule. Saving the settings warns about invalid entries and removes them.

No. It filters outgoing pingback target URLs in WordPress’s pre_ping hook. It does not restrict incoming pingbacks, trackbacks, update services, visitor referrers, search engines or HTTP requests made by other plugins.

Allowed pages can redirect or advertise a pingback endpoint on another host. WordPress handles that discovery and delivery; this plugin does not enforce an HTTP firewall over those later requests. Only allow sites you trust.

Not necessarily. The receiving pingback service normally needs to fetch and verify the linking article. Authentication, disabled XML-RPC/pingbacks, hosting rules or other plugins can prevent delivery. This plugin preserves eligible self-pings; it does not implement an independent backlink index.

The plugin can be activated per site or network-wide. Each site has its own allowed URLs and Settings page. A site without saved settings defaults to its current public site URL. There is no network-wide allowlist.

Deactivation keeps the settings. Deleting the plugin removes its own OnlySelfPingsOpts option, including per-site options on Multisite. It never edits or deletes WP-HideRefer settings.