Titanium Service Zones Pro

Install Titanium Service Zones from WordPress.org using the new titanium-service-zones plugin slug.

A Service Zone is one selected part of the public website. It can target a WordPress Page, an exact URL path or a trailing-wildcard path prefix and can be Operational, show a Service Notice or return HTTP 503 Maintenance.

Three. The same three-zone core is included in Free and Pro; Pro does not increase the Service Zone limit in this release.

Yes. That is the main purpose of Service Zones. Only the matching area changes state while unrelated public URLs continue normally.

Yes. A zone can target a published WordPress Page directly or use an exact or trailing-* URL-path rule.

Use a trailing wildcard such as /account/* to match that path prefix. Query strings are ignored by the zone path matcher.

It shows known published WordPress Pages that match the selected target. Dynamic runtime endpoints may not exist as stored Pages, so the preview is intentionally not presented as a complete site crawler.

It warns about very broad rules, protected WordPress routes and transaction/account-looking paths such as checkout, payment, webhook, callback, cart and My Account.

The more-specific target wins. Page targets outrank path rules, exact paths outrank wildcard prefixes, longer wildcard prefixes outrank shorter ones, and equal specificity uses the earlier zone.

Yes. Create a more-specific Operational zone for that child area. The specificity rule lets it override a broader Service Notice or Maintenance path.

Yes. A matched Maintenance Zone returns HTTP 503 with Retry-After and noindex/no-cache handling when WordPress can still send headers.

When enabled, Titanium Service Zones publishes a read-only /service-status/ page generated from Whole-Site Status and configured zones.

No. It exposes configured zone names and current public states, not target paths, selected Page IDs, internal rules or administrator data.

Yes, when Automatic Public Service Status is enabled: /wp-json/titanium-service-zones/v1/status.

Yes. Whole-Site Status still provides Normal, Visitor Service Notice, Coming Soon and Maintenance Mode. A non-Normal Whole-Site Status takes priority over Service Zones.

Coming Soon is an available launch placeholder and uses HTTP 200. Maintenance Mode represents a temporary outage and returns HTTP 503 with Retry-After when headers can still be sent.

It is a non-blocking notice shown above eligible public frontend pages while the website remains available. Free includes four ready-made notice messages.

Yes. They have separate titles, messages, logos, background colours, accent colours and optional login buttons.

Yes. The existing administrator visibility setting can bypass the public replacement output while reminders make the active state visible.

The plugin marks eligible Service Zone and Whole-Site Status responses as non-cacheable and can purge LiteSpeed Cache, WP Rocket, WP Super Cache and W3 Total Cache. External CDN or host-level caches may still require their own purge.

Pro adds start/end dates, selected weekdays, daily and overnight time windows, WordPress-site timezone handling and an optional countdown for supported Whole-Site Status workflows.

Conditions inside a group use AND logic and separate groups use OR. Pro supports up to 1,000 validated conditions for the existing premium Whole-Site Status targeting system.

Pro can target shop, product, cart, checkout, My Account and account endpoints, products, product taxonomies, purchase history and active WooCommerce Subscription products.

Paid Memberships Pro, MemberPress, WooCommerce Memberships, Restrict Content / Pro, Paid Member Subscriptions, LifterLMS and LearnDash are supported where their required APIs are available.

Up to 500 reusable Visitor Service Notice headings and messages.

Premium modules stop loading while the complete shared Free core and shared settings remain available.

Yes. The only difference between Pro plans is the number of websites covered by the license.