# Regional or product sub-pages for incident scope

> Create status sub-pages for regions or product lines so local incidents do not read like global outages.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/regional-or-product-sub-pages-for-incident-scope/
- Source: [docs.incident.io](https://docs.incident.io/en/articles/8391002-setting-up-sub-pages)
- GrowthDex source hub: [incident.io Docs: Setting up sub-pages](/sources/incident-io-docs-setting-up-sub-pages-docs-incident-io/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: medium
- Channels: Support, Brand, Product
- Stages: regional products, incident comms, support deflection, ux


## Why this can grow

Incident communication breaks down when every issue gets posted to one global page. Users in Europe do not need a North America outage to look like their own emergency. incident.io's sub-pages are useful because they let teams publish to a parent page while automatically limiting the visibility of incidents to the sub-pages where the affected components belong. That makes the communication calmer and more accurate. It also protects trust because the page answers the first question fast: does this affect me or not.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where regional or product sub-pages for incident scope can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Brand channel.
3. Use the evidence from docs.incident.io to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

incident.io says sub-pages are useful when users need a more specific view by product or region, and incidents published to the parent page automatically appear only on sub-pages where the impacted components are visible.

## Adjacent tactics in the same lane

- [Status embed on help center and app shell](/growth-ideas/status-embed-on-help-center-and-app-shell/) - 2 shared channels, 2 shared stages
- [Issue or PR link instead of status handwave](/growth-ideas/issue-or-pr-link-instead-of-status-handwave/) - 3 shared channels
- [Hide unreleased docs until the version is real](/growth-ideas/hide-unreleased-docs-until-the-version-is-real/) - 2 shared channels, 1 shared stage
- [Dedicated status domain before first incident](/growth-ideas/dedicated-status-domain-before-first-incident/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The status page should answer who is affected before support opens](/blog/the-status-page-should-answer-who-is-affected-before-support-opens/) - brand trust, support-led growth, operations

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.