Skip to content
Admin Plugins
Titanium Service Zones Tutorials

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.

Get Free VersionView Pro Pricing
  • 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.

01
FreeGetting Started

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

  1. Install and activate Titanium Service Zones from the WordPress Plugins screen.
  2. Open Service Zones → Settings.
  3. Leave Whole-Site Status set to Normal when you want selective zones to control only part of the website.
  4. Use Visitor Service Notice, Coming Soon or Maintenance Mode under Whole-Site Status only when the complete public website should change at once.
  5. Scroll to Service Zones when only selected areas are affected.
  6. Save the settings and test in a logged-out private browser window.
02
FreeService Zones

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

  1. Open Service Zones → Settings and find the Service Zones panel.
  2. Choose one of the three included zones and enter a clear Zone name such as Checkout, Member Area or Downloads.
  3. Choose Operational, Service Notice or Maintenance (HTTP 503).
  4. Choose WordPress Page or URL path as the Target type.
  5. Select the Page or enter the path that belongs to this service.
  6. Optionally add a zone-specific Visitor title and Visitor message.
  7. Use Preview Impact & Safety before relying on a new target, then Save Changes.
03
FreeTargeting

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

  1. For a normal WordPress Page, choose Target type → WordPress Page and select the published Page.
  2. For one exact route, choose URL path and enter a path such as /checkout/.
  3. For a path family, use one trailing wildcard such as /account/*.
  4. Keep the rule as narrow as possible so unrelated routes stay online.
  5. Remember that query strings are ignored by Service Zone path matching.
  6. Run Preview Impact & Safety before activation and review the known matching Pages.
04
FreeSafety

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

  1. Configure the zone name, status and target first.
  2. Press Preview Impact & Safety.
  3. Review the known published WordPress Pages that match the target.
  4. Read every Safety Check warning before changing the zone from Operational.
  5. Narrow a rule that unintentionally covers a much larger part of the website.
  6. Pay extra attention to checkout, payment, webhook, callback, cart, account and similar transactional routes.
  7. Save only after the preview matches the intended service boundary.
05
FreeConflict Detection

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

  1. Create the broader zone first, for example /shop/* → Service Notice.
  2. Create a more-specific zone such as /shop/checkout/* → Maintenance when checkout needs a stronger state.
  3. Review the overlap warning shown by the Service Zones interface.
  4. Use a WordPress Page target when one specific saved Page should outrank path rules.
  5. Use a more-specific Operational zone when one child area must remain live inside a broader affected path.
  6. Save and test each overlapping route separately in a private browser.
06
FreePublic Status

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

  1. Open Service Zones → Settings.
  2. Find Automatic Public Service Status.
  3. Enable the option and Save Changes.
  4. Open /service-status/ in a logged-out browser.
  5. Confirm that the displayed service names and states are appropriate for public visitors.
  6. When needed, use the read-only /wp-json/titanium-service-zones/v1/status endpoint for a machine-readable view.
  7. Disable the option again if the site should not expose public service state.
07
FreeWhole-Site Status

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

  1. Open Service Zones → Settings.
  2. Set Whole-Site Status to Visitor Service Notice.
  3. Choose the built-in service message that best matches the situation.
  4. Use the hosting, performance, feature outage or service disruption preset as appropriate.
  5. Choose whether administrators should also see the public notice.
  6. Keep the wp-admin reminder enabled when you want a clear operational reminder.
  7. Save and verify the visitor result while logged out.
08
FreeComing Soon

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

  1. Set Whole-Site Status to Coming Soon.
  2. Enter the public Page title and Message.
  3. Choose a logo from the WordPress Media Library or use the built-in fallback visual.
  4. Set the Background color and Accent color.
  5. Enable the login button only when staff or clients need a visible login path.
  6. Use the default WordPress login or a same-site internal custom path such as /login.
  7. Save and inspect the page while logged out.
09
FreeHTTP 503

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

  1. Set Whole-Site Status to Maintenance Mode.
  2. Enter a clear Page title and visitor-focused Message.
  3. Choose the maintenance logo, Background color and Accent color.
  4. Configure the optional login button and same-site login URL if required.
  5. Decide whether administrators should receive the public maintenance replacement or bypass it.
  6. Save and verify the response from a logged-out private window.
  7. Return Whole-Site Status to Normal when the outage ends.
10
FreeTesting & Cache

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

  1. Save the selected Whole-Site Status and Service Zone configuration.
  2. Open a private/incognito browser where you are not logged into WordPress.
  3. Test every affected target and at least one unrelated page that should remain normal.
  4. Verify any configured login button and internal login path.
  5. Return to the administrator session and confirm that the reminder matches the active state.
  6. If a supported cache purge reports a failure, clear that cache manually.
  7. Also purge any external CDN or hosting cache when it can serve pages before WordPress runs.
11
ProSchedule & Countdown

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

  1. Select the Whole-Site Status mode you want to automate.
  2. Open Schedule and Conditional Logic and enable Schedule.
  3. Set an optional Start date and time.
  4. Set an optional End date and time.
  5. Choose Active weekdays when the workflow should apply only on selected days.
  6. Use Daily start and Daily end for recurring windows; overnight ranges continue into the following morning.
  7. Enable the countdown when the supported maintenance workflow has a future absolute end time.
  8. Save and verify using the WordPress site timezone.
12
ProConditional Logic

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

  1. Enable Conditional Logic under Schedule and Conditional Logic.
  2. Choose a Condition type such as login status, role, capability, specific content, URL path, query parameter, device or browser.
  3. Choose the operator and value.
  4. Add an AND condition when the same group needs another requirement.
  5. Add another Rule group when a different complete route should also match.
  6. Keep the tree understandable even though up to 1,000 validated conditions are supported.
  7. Save and test both a matching and non-matching request.
13
ProCommerce & Memberships

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

  1. Confirm that the WooCommerce, membership or LMS plugin you need is active.
  2. Enable Pro Conditional Logic.
  3. Choose the relevant integration condition.
  4. For WooCommerce, target shop/product/cart/checkout/My Account, products, taxonomies, purchase history or active subscription products as required.
  5. For memberships or learning platforms, choose the matching level, plan, course or group.
  6. Select a supported recorded status when the integration exposes one.
  7. Combine with login status, content or URL conditions when needed.
  8. Test with real accounts that should match and should not match.
14
ProCustom Notices

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

  1. Open Service Zones → Custom Notices.
  2. Press Add Custom Notice.
  3. Enter the Large heading.
  4. Enter the Smaller message with the visitor-facing explanation.
  5. Use the live preview to check the wording.
  6. Save the Notice Library; Pro supports up to 500 reusable notices.
  7. Return to Service Zones → Settings and select Visitor Service Notice under Whole-Site Status.
  8. 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.

Get Free Version

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