No. The live status banner ("all systems operational", current incident updates) belongs on a status page vendor that handles uptime monitoring, subscriber notifications, and real-time updates. SleekRank renders the historical archive at indexable URLs on your own domain. The two work together.

Yes. Statuspage, Better Stack, and Instatus all expose incident APIs. Configure a SleekRank REST data source pointing at the API, map the response into the expected columns (slug, title, start_time, severity, body), and the archive stays in sync automatically. Otherwise, a sheet keyed by slug works the same way.

Depends on cacheDuration. For incidents archive specifically, most teams set it to 300 seconds or shorter so a new row picked up from the status feed or pasted in the sheet appears within minutes. After a post-mortem is posted, clearing the items table makes the change visible on the next request.

Yes. Carry a status column on the row (open, resolved, post_mortem_published) and filter the page group on a status the customer should see. Open incidents can stay private until you choose to publish, or you can publish the incident page early with the summary and add the post_mortem_html later.

Carry severity values that match your internal scale (minor, major, critical, or P3, P2, P1). Render severity badges via selector mapping with conditional classes for color. Keep the taxonomy consistent across all incidents so the filtered views and trust-page references stay meaningful.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new incident rows get crawled after the next rewrite flush. Procurement and engineering teams searching for past incidents on a specific service can find the relevant /incidents/{slug}/ directly.

Yes. The /incidents/ URLs are stable and indexable, so a trust page or SOC 2 evidence page can link to specific past incidents or to /incidents/?severity=major to filter the view. Customers and auditors get one click from a summary statement to the underlying evidence.

Carry a visibility column on the sheet (public, archived) and filter the page group on visibility = public. Archived rows keep the historical record internally but stop resolving on the public URL. This is preferable to deletion, which would orphan any external links to the old incident page.