Keep the site online with selective service control.
Titanium Service Zones lets you put only the affected part of WordPress into a Service Notice or HTTP 503 Maintenance state while the rest of the website stays available. Free includes up to three independent zones, Page and URL-path targeting, Impact Preview, Safety Check, overlap detection, Operational exceptions and an optional public service-status page. The existing Whole-Site Status controls remain available, while Pro adds the current scheduling, countdown, reusable notices and advanced AND/OR targeting tools.
- 3 Service Zones in Free
- Impact Preview + Safety Check
- HTTP 503 only where needed
- Pro scheduling + advanced targeting
Selective Service Zones are included in Free.
Create up to three independent zones for a WordPress Page or URL path. Keep each area Operational, show a Service Notice, or return HTTP 503 Maintenance while unrelated parts of the site stay online. Free also includes Impact Preview, Safety Check, Conflict Detection, optional Public Service Status and the original Whole-Site Status controls.
Control only the part of WordPress that is affected.
Service Zones are designed for partial outages and planned work where taking the whole website offline would be unnecessary.
Three Service Zones in Free
Create up to three independent areas with their own Operational, Service Notice or Maintenance state while the rest of the website keeps working.
Page and path targeting
Select a published WordPress Page, an exact URL path or a trailing-* prefix such as /account/* without writing custom PHP.
Impact Preview + Safety Check
Preview known matching Pages before activation and receive warnings for broad, protected or transaction-related routes.
Conflict-aware priority
Overlapping zones are detected and resolved deterministically. More-specific targets win, including Operational exceptions inside broader maintenance paths.
Automatic Public Service Status
Optionally publish a read-only /service-status/ page and JSON status endpoint without exposing private target paths or matching rules.
Whole-Site Status still included
Use Normal, Visitor Service Notice, Coming Soon or Maintenance Mode when the complete website really should change at once.
Correct HTTP and cache behaviour
Matched Maintenance Zones and whole-site maintenance return proper HTTP 503 handling, while supported WordPress page caches can be purged after changes.
Existing Pro automation
Pro keeps reusable Custom Notices, scheduling, countdowns and up to 1,000 AND/OR conditions across WordPress, WooCommerce, memberships and LMS integrations.
Free vs Pro
Service Zones are part of the shared Free core. Pro currently adds the existing automation and targeting tools; it does not increase the three-zone limit in this release.
Compare plans
See exactly what is included in the shared core and what unlocks in Pro.
| Feature | Free | Pro |
|---|---|---|
| Included in Free and Pro | ||
| Up to three independent Service ZonesKeep unaffected parts of the website online while selected areas use their own Operational, Service Notice or Maintenance state. | ✓ | ✓ |
| WordPress Page and URL path targetingTarget a published Page, an exact path such as /checkout/, or a trailing-* path prefix such as /account/*. | ✓ | ✓ |
| Operational, Service Notice or Maintenance per zoneEach zone has its own public state instead of forcing the complete website into one mode. | ✓ | ✓ |
| Zone-specific visitor title and messageExplain exactly what is affected without changing unrelated sections of the website. | ✓ | ✓ |
| HTTP 503 for matched Maintenance ZonesOnly matched maintenance requests receive the temporary-unavailable response; unaffected URLs keep their normal response. | ✓ | ✓ |
| Maintenance Impact PreviewPreview known published WordPress Pages that match the selected target before activation. | ✓ | ✓ |
| Built-in Safety CheckReceive warnings for very broad, protected WordPress, account, checkout, payment, webhook, callback and similar sensitive-looking routes. | ✓ | ✓ |
| Service Zone Conflict DetectorDetect overlapping zones before relying on them in production. | ✓ | ✓ |
| Deterministic specificity priorityPage targets outrank paths; exact paths outrank wildcard prefixes; longer wildcard prefixes win, and equal targets use the earlier zone. | ✓ | ✓ |
| Operational exceptions inside broader zonesKeep a smaller area live by placing a more-specific Operational zone inside a broader Service Notice or Maintenance path. | ✓ | ✓ |
| Automatic Public Service StatusOptionally publish /service-status/ from Whole-Site Status and configured zone states. | ✓ | ✓ |
| Read-only public JSON statusOptionally expose /wp-json/titanium-service-zones/v1/status without publishing private target paths or internal rules. | ✓ | ✓ |
| Normal, Visitor Service Notice, Coming Soon and Maintenance ModeWhole-Site Status remains available when the complete website should change at once. | ✓ | ✓ |
| HTTP 503 whole-site maintenance responseSends Retry-After, no-cache and search-engine headers when WordPress can still send headers. | ✓ | ✓ |
| Four ready-made Visitor Service NoticesHosting, performance, feature outage and service disruption presets. | ✓ | ✓ |
| Coming Soon and maintenance page customizationSet separate titles, messages, logos, background colours, accent colours and optional login buttons. | ✓ | ✓ |
| Custom login button and internal login URLUse the default WordPress login or a short internal path such as /login. | ✓ | ✓ |
| Administrator inclusion, bypass and remindersChoose whether administrators see the public state and keep clear frontend/wp-admin reminders. | ✓ | ✓ |
| Responsive output and admin dark modeResponsive public output with a light or dark administration interface. | ✓ | ✓ |
| Supported page-cache purgingLiteSpeed Cache, WP Rocket, WP Super Cache and W3 Total Cache integrations. | ✓ | ✓ |
| Transaction-protected settings and multisite lifecycleVerified rollback plus bounded activation, reset and uninstall processing. | ✓ | ✓ |
| Additional Pro features | ||
| Reusable Custom NoticesCreate and manage up to 500 reusable visitor notice headings and messages. | × | ✓ |
| Date and time schedulingSchedule supported Whole-Site Status modes with dates, weekdays, daily windows, overnight ranges and the WordPress site timezone. | × | ✓ |
| Schedule countdownShow the remaining time and reload automatically when the configured maintenance window ends. | × | ✓ |
| Advanced AND / OR condition groupsTarget supported Whole-Site Status modes with up to 1,000 validated AND / OR conditions. | × | ✓ |
| Login status, role and capability conditionsTarget logged-in/out visitors, standard or custom roles and WordPress capabilities. | × | ✓ |
| Specific content conditionsTarget pages, posts, products and other public custom content items. | × | ✓ |
| WordPress page-type and archive conditionsFront page, posts page, blog home, search, 404, singular content, archives and post-type archives. | × | ✓ |
| Taxonomy archive and term conditionsTarget public taxonomy archives and specific taxonomy terms. | × | ✓ |
| URL, query, device and browser conditionsTarget paths, query parameters, mobile/desktop devices and common browsers. | × | ✓ |
| WooCommerce page and account conditionsShop, product, cart, checkout, My Account and individual account endpoints. | × | ✓ |
| WooCommerce product and taxonomy conditionsSpecific products, product categories and product tags. | × | ✓ |
| WooCommerce customer-history conditionsPreviously purchased products and active WooCommerce Subscription products. | × | ✓ |
| Membership and learning integrationsPMPro, MemberPress, WooCommerce Memberships, Restrict Content / Pro, Paid Member Subscriptions, LifterLMS and LearnDash. | × | ✓ |
| Membership status conditionsSupported active, inactive, expired, cancelled, pending, paused, trial, complimentary and other recorded states. | × | ✓ |
Simple annual pricing
Choose the license that fits your site count. Every Pro plan includes all current Pro features, updates and premium support.
1 Site
For one WordPress site.
- All Pro features
- Use on 1 site
- Updates and support
3 Sites
For small client setups.
- All Pro features
- Use on 3 sites
- Updates and support
5 Sites
For active site owners and small agencies.
- All Pro features
- Use on 5 sites
- Updates and support
10 Sites
For freelancers and growing client work.
- All Pro features
- Use on 10 sites
- Updates and support
20 Sites
For larger client portfolios.
- All Pro features
- Use on 20 sites
- Updates and support
50 Sites
For agencies managing many sites.
- All Pro features
- Use on 50 sites
- Updates and support
Frequently asked questions
Answers about selective Service Zones, Whole-Site Status and the current Pro automation tools.
Where can I get the Free version?
Install Titanium Service Zones from WordPress.org using the new titanium-service-zones plugin slug.
What is a Service Zone?
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.
How many Service Zones are included in Free?
Three. The same three-zone core is included in Free and Pro; Pro does not increase the Service Zone limit in this release.
Can the rest of the website stay online?
Yes. That is the main purpose of Service Zones. Only the matching area changes state while unrelated public URLs continue normally.
Can I target a WordPress Page instead of typing a URL?
Yes. A zone can target a published WordPress Page directly or use an exact or trailing-* URL-path rule.
How do wildcard paths work?
Use a trailing wildcard such as /account/* to match that path prefix. Query strings are ignored by the zone path matcher.
What does Impact Preview show?
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.
What does the Safety Check do?
It warns about very broad rules, protected WordPress routes and transaction/account-looking paths such as checkout, payment, webhook, callback, cart and My Account.
What happens when two zones overlap?
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.
Can I keep one page live inside a broader maintenance path?
Yes. Create a more-specific Operational zone for that child area. The specificity rule lets it override a broader Service Notice or Maintenance path.
Does a Maintenance Zone return HTTP 503?
Yes. A matched Maintenance Zone returns HTTP 503 with Retry-After and noindex/no-cache handling when WordPress can still send headers.
What is Automatic Public Service Status?
When enabled, Titanium Service Zones publishes a read-only /service-status/ page generated from Whole-Site Status and configured zones.
Does the public status page reveal my URL rules?
No. It exposes configured zone names and current public states, not target paths, selected Page IDs, internal rules or administrator data.
Is there a JSON status endpoint?
Yes, when Automatic Public Service Status is enabled: /wp-json/titanium-service-zones/v1/status.
Can I still put the entire website into Maintenance Mode?
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.
What is the difference between Coming Soon and Maintenance Mode?
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.
What is Visitor Service Notice?
It is a non-blocking notice shown above eligible public frontend pages while the website remains available. Free includes four ready-made notice messages.
Can I customize the maintenance and Coming Soon pages?
Yes. They have separate titles, messages, logos, background colours, accent colours and optional login buttons.
Can administrators still access the normal website?
Yes. The existing administrator visibility setting can bypass the public replacement output while reminders make the active state visible.
Does it work with page caching?
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.
What does Pro scheduling add?
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.
How does Pro conditional logic work?
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.
What WooCommerce conditions are included in Pro?
Pro can target shop, product, cart, checkout, My Account and account endpoints, products, product taxonomies, purchase history and active WooCommerce Subscription products.
Which membership and learning integrations are supported?
Paid Memberships Pro, MemberPress, WooCommerce Memberships, Restrict Content / Pro, Paid Member Subscriptions, LifterLMS and LearnDash are supported where their required APIs are available.
How many Custom Notices can Pro store?
Up to 500 reusable Visitor Service Notice headings and messages.
What happens if Pro becomes unavailable?
Premium modules stop loading while the complete shared Free core and shared settings remain available.
Do all Pro license sizes include the same features?
Yes. The only difference between Pro plans is the number of websites covered by the license.
14 practical ways to manage WordPress with selective service control.
These tutorials start with the new Free Service Zones workflow: create independent zones, target Pages or URL paths, preview impact, review safety warnings, resolve overlaps and optionally publish an automatic service-status page. They also cover the existing Whole-Site Status controls and show how Pro keeps the current scheduling, countdown, Custom Notices and advanced AND/OR targeting tools.
- 3 Service Zones in Free
- Impact & Safety Preview
- Conflict-aware targeting
- Optional Public Service Status
Step-by-step Service Zones tutorials.
Start with the selective Free workflow, verify exactly what will be affected, then use Whole-Site Status or Pro automation only when the situation actually requires it.
How to choose between Whole-Site Status and Service Zones
Titanium Service Zones has two layers. Whole-Site Status changes the complete public website, while Service Zones change only selected Pages or URL paths. Keeping Whole-Site Status on Normal allows the independent zones to control only the affected areas.
Start with the correct control
- Install and activate Titanium Service Zones from the WordPress Plugins screen.
- Open Service Zones → Settings.
- Leave Whole-Site Status set to Normal when you want selective zones to control only part of the website.
- Use Visitor Service Notice, Coming Soon or Maintenance Mode under Whole-Site Status only when the complete public website should change at once.
- Scroll to Service Zones when only selected areas are affected.
- Save the settings and test in a logged-out private browser window.
How to create your first independent Service Zone
Each zone has a name, status, target and optional visitor title/message. This lets you describe one affected service without changing unrelated pages.
Create the zone
- Open Service Zones → Settings and find the Service Zones panel.
- Choose one of the three included zones and enter a clear Zone name such as Checkout, Member Area or Downloads.
- Choose Operational, Service Notice or Maintenance (HTTP 503).
- Choose WordPress Page or URL path as the Target type.
- Select the Page or enter the path that belongs to this service.
- Optionally add a zone-specific Visitor title and Visitor message.
- Use Preview Impact & Safety before relying on a new target, then Save Changes.
How to target a WordPress Page, exact path or wildcard path
Free includes practical Page and URL-path targeting. Use a saved Page when the affected service has a normal WordPress Page, or use a path rule for dynamic areas such as account or checkout endpoints.
Choose the target
- For a normal WordPress Page, choose Target type → WordPress Page and select the published Page.
- For one exact route, choose URL path and enter a path such as /checkout/.
- For a path family, use one trailing wildcard such as /account/*.
- Keep the rule as narrow as possible so unrelated routes stay online.
- Remember that query strings are ignored by Service Zone path matching.
- Run Preview Impact & Safety before activation and review the known matching Pages.
How to use Impact Preview and Safety Check before activation
The preview is designed to answer two questions before a zone goes live: which known Pages match, and does the selected route look dangerously broad or operationally sensitive?
Run the preview
- Configure the zone name, status and target first.
- Press Preview Impact & Safety.
- Review the known published WordPress Pages that match the target.
- Read every Safety Check warning before changing the zone from Operational.
- Narrow a rule that unintentionally covers a much larger part of the website.
- Pay extra attention to checkout, payment, webhook, callback, cart, account and similar transactional routes.
- Save only after the preview matches the intended service boundary.
How overlapping zones are resolved and how to create an Operational exception
Service Zones can overlap on purpose. The conflict detector makes those relationships visible, and a deterministic specificity rule decides which matching zone wins.
Understand the priority
- Create the broader zone first, for example /shop/* → Service Notice.
- Create a more-specific zone such as /shop/checkout/* → Maintenance when checkout needs a stronger state.
- Review the overlap warning shown by the Service Zones interface.
- Use a WordPress Page target when one specific saved Page should outrank path rules.
- Use a more-specific Operational zone when one child area must remain live inside a broader affected path.
- Save and test each overlapping route separately in a private browser.
How to publish the automatic Service Status page and JSON endpoint
Public Service Status turns the configured service names and states into a read-only status view. It is optional and stays disabled until an administrator enables it.
Enable public status
- Open Service Zones → Settings.
- Find Automatic Public Service Status.
- Enable the option and Save Changes.
- Open /service-status/ in a logged-out browser.
- Confirm that the displayed service names and states are appropriate for public visitors.
- When needed, use the read-only /wp-json/titanium-service-zones/v1/status endpoint for a machine-readable view.
- Disable the option again if the site should not expose public service state.
How to show a whole-site Visitor Service Notice
Visitor Service Notice is the non-blocking Whole-Site Status option for a degraded service that should be communicated across the live website without replacing the whole frontend.
Enable the notice
- Open Service Zones → Settings.
- Set Whole-Site Status to Visitor Service Notice.
- Choose the built-in service message that best matches the situation.
- Use the hosting, performance, feature outage or service disruption preset as appropriate.
- Choose whether administrators should also see the public notice.
- Keep the wp-admin reminder enabled when you want a clear operational reminder.
- Save and verify the visitor result while logged out.
How to build a branded Coming Soon page
Coming Soon is still available under Whole-Site Status for sites that are not yet launched. It has its own title, message, logo and colours and uses an HTTP 200 response.
Create the launch page
- Set Whole-Site Status to Coming Soon.
- Enter the public Page title and Message.
- Choose a logo from the WordPress Media Library or use the built-in fallback visual.
- Set the Background color and Accent color.
- Enable the login button only when staff or clients need a visible login path.
- Use the default WordPress login or a same-site internal custom path such as /login.
- Save and inspect the page while logged out.
How to use whole-site Maintenance Mode correctly
Whole-site Maintenance Mode remains available for situations where the entire public website really is temporarily unavailable. It returns the temporary-service response instead of an ordinary success page.
Configure whole-site maintenance
- Set Whole-Site Status to Maintenance Mode.
- Enter a clear Page title and visitor-focused Message.
- Choose the maintenance logo, Background color and Accent color.
- Configure the optional login button and same-site login URL if required.
- Decide whether administrators should receive the public maintenance replacement or bypass it.
- Save and verify the response from a logged-out private window.
- Return Whole-Site Status to Normal when the outage ends.
How to test access, administrator bypass and cache behaviour
Administrators can intentionally see a different result from public visitors, so the reliable test is always a logged-out browser. Titanium also purges supported WordPress page caches after relevant state changes.
Test the public result
- Save the selected Whole-Site Status and Service Zone configuration.
- Open a private/incognito browser where you are not logged into WordPress.
- Test every affected target and at least one unrelated page that should remain normal.
- Verify any configured login button and internal login path.
- Return to the administrator session and confirm that the reminder matches the active state.
- If a supported cache purge reports a failure, clear that cache manually.
- Also purge any external CDN or hosting cache when it can serve pages before WordPress runs.
How to automate supported Whole-Site Status modes with Pro scheduling
Pro keeps the existing schedule engine for premium whole-site workflows. It uses the WordPress site timezone and can combine absolute dates, selected weekdays and daily or overnight windows.
Build the schedule
- Select the Whole-Site Status mode you want to automate.
- Open Schedule and Conditional Logic and enable Schedule.
- Set an optional Start date and time.
- Set an optional End date and time.
- Choose Active weekdays when the workflow should apply only on selected days.
- Use Daily start and Daily end for recurring windows; overnight ranges continue into the following morning.
- Enable the countdown when the supported maintenance workflow has a future absolute end time.
- Save and verify using the WordPress site timezone.
How to build Pro AND/OR audience and request rules
Pro can restrict the supported Whole-Site Status workflow to selected visitors or requests. Conditions inside one group use AND; separate groups are alternatives joined by OR.
Create a rule tree
- Enable Conditional Logic under Schedule and Conditional Logic.
- Choose a Condition type such as login status, role, capability, specific content, URL path, query parameter, device or browser.
- Choose the operator and value.
- Add an AND condition when the same group needs another requirement.
- Add another Rule group when a different complete route should also match.
- Keep the tree understandable even though up to 1,000 validated conditions are supported.
- Save and test both a matching and non-matching request.
How to target WooCommerce, memberships and LMS access with Pro
When the required integrations are active, the existing Pro condition catalogue can use commerce history, membership access and learning-platform data without custom PHP.
Build an integration rule
- Confirm that the WooCommerce, membership or LMS plugin you need is active.
- Enable Pro Conditional Logic.
- Choose the relevant integration condition.
- For WooCommerce, target shop/product/cart/checkout/My Account, products, taxonomies, purchase history or active subscription products as required.
- For memberships or learning platforms, choose the matching level, plan, course or group.
- Select a supported recorded status when the integration exposes one.
- Combine with login status, content or URL conditions when needed.
- Test with real accounts that should match and should not match.
How to create reusable Visitor Service Notice messages
Pro keeps the existing Custom Notices library for recurring whole-site service messages. Each notice has a large heading and smaller message and becomes selectable after the library is saved.
Create a reusable notice
- Open Service Zones → Custom Notices.
- Press Add Custom Notice.
- Enter the Large heading.
- Enter the Smaller message with the visitor-facing explanation.
- Use the live preview to check the wording.
- Save the Notice Library; Pro supports up to 500 reusable notices.
- Return to Service Zones → Settings and select Visitor Service Notice under Whole-Site Status.
- Choose the saved custom message and Save Changes.
Keep unaffected parts of the website online.
Free includes up to three Service Zones, Page/path targeting, Operational/Service Notice/Maintenance states, Impact Preview, Safety Check, Conflict Detection, Operational exceptions, optional Public Service Status and the complete existing Whole-Site Status core. Pro keeps the same Service Zone core and adds the existing premium scheduling, countdown, reusable notices and advanced targeting tools.
Need scheduled or audience-specific whole-site control?
Use Titanium Service Zones Pro for the current premium automation layer: reusable Custom Notices, date/time schedules, countdowns and advanced AND/OR targeting across WordPress, WooCommerce, memberships and learning platforms.
View Pro Pricing