SGEN site health monitoring overview
In short. SGEN gives you four health signals, each answering a different question. Site Vitals (Dashboard home) scores your homepage performance 0-100, refreshed every 12 hours — above 80 is healthy. Activity log (Dashboard → Activity) shows the last 50 admin actions by your team — open it every morning. Notifications inbox (Dashboard → Notifications) queues pending blog comments for moderation. Form submission alerts (Forms → per-form Notifications tab) emails you when a visitor fills in a contact form. None of these overlap. A five-minute morning check of all four keeps you ahead of most issues before visitors notice them. That's the gist — everything below is the same idea in depth.
On this page: What is this for? · The four surfaces · Fields and options reference · Good use cases · Troubleshooting · Related features
This page maps every customer-visible surface in SGEN that answers "how is my site doing right now?" Each surface has its own dedicated guide — this page tells you what each one is, what question it answers, and when to reach for it. For traffic charts and visitor data, see Analytics data pipeline overview — that is a separate system.
What is this for?
SGEN gives site owners four distinct health signals. Each answers a different question:
| Signal | Question it answers | Where it lives |
|---|---|---|
| Dashboard — Site Vitals | Is my site fast and healthy right now? | Dashboard home |
| Activity log | What did my team do recently? | Dashboard → Activity |
| Notifications inbox | Is there anything waiting for my attention? | Dashboard → Notifications |
| Form submission alerts | Did my contact form get a new lead? | Forms → per-form settings |
None of these four duplicate each other.
When all four numbers look plausible, the site is in good shape. When one changes unexpectedly, that is the signal to investigate.
Anatomy — the four surfaces
Surface 1: Dashboard — Site Vitals
The dashboard home page includes a Site Vitals panel. It scores your homepage performance using the same signals Google's PageSpeed tool uses — load time, layout stability, and image efficiency. The score refreshes roughly every 12 hours.
What it tells you: A score between 0 and 100. Above 80 is healthy. Below 60 needs attention.
What typically triggers a drop: A large uncompressed hero image, a slow third-party embed, or a significant page structure change. When the score drops unexpectedly, compare the timing with the Activity log to find the coinciding change.
Surface 2: Activity log
The Activity log is a chronological feed of the last 50 admin actions on your site. Every time a team member creates a page, edits a post, adds a redirect, uploads a file, or changes a settings value, an event is appended with a timestamp and the email of the person who did it.
What it tells you: Who did what, and when. The feed is append-only — entries cannot be edited or deleted.
Typical use: Open the feed first thing in the morning to see what your team did overnight. Filter to a single event type (Posts, Pages, Redirects, Users, Media, Settings) when hunting for a specific type of change.
Full guide: See what changed on your site recently.
Surface 3: Notifications inbox
The Notifications inbox collects items waiting for your action — primarily pending blog comments that need moderation before they go live. The inbox is per-admin: your read state is separate from your co-admin's.
What it tells you: Something is waiting for your attention. The bell icon in the top admin navigation shows a count of unread items.
Typical use: Check the Unread tab at the start of your day. Review each pending comment, approve or mark as spam, and mark items Read once handled.
Full guide: Manage your Notifications inbox.
Surface 4: Form submission alerts
When a visitor fills in a contact form on your public site, SGEN can send an email to one or more addresses you configure.
What it tells you: A specific form was submitted, by whom, and what they wrote.
Typical use: Configure your main contact form to email your inbox and a backup address. If you expect submissions but are not receiving alerts, check the Forms area — a misconfigured alert email is the most common cause.
Fields and options reference
| Surface | Refresh cadence | Scope | Alert type | Requires action? |
|---|---|---|---|---|
| Site Vitals score | Every ~12 hours | Homepage performance | Passive indicator | Only if score drops |
| Activity log | Near real-time | Admin actions by team | Passive log | Only if something looks wrong |
| Notifications inbox | Near real-time | Comment moderation | Active queue | Yes — moderate comments |
| Form submission alerts | Real-time on submit | Per-form leads | Email push | Yes — follow up with lead |
Score (Site Vitals): 0-100. At or above 80 is healthy. 60-79 is worth watching. Below 60 needs attention.
Activity event types: Post / Page / Redirect / User / Media / Settings. Ecommerce sites also log Product and Order events.
Notification states: Unread and Read. Bulk-action available. State is per-admin — your co-admin's read/unread does not affect yours.
Form alert recipients: One or more email addresses per form. Keep the list short to avoid alert fatigue.
Where to find it
When to use each surface
| Situation | Where to look |
|---|---|
| Daily check-in | Dashboard → Site Vitals score + Activity log top entries + Notifications unread count. Five minutes covers all four. |
| Something looks broken | Site Vitals (did the score drop?) + Activity log filtered to Media and Pages in the last 48 hours. |
| Form has gone quiet | Forms → select the form → Notifications tab. Confirm the alert email address is correct. |
| Unexpected admin action | Activity log. If you see an action you did not authorize, revoke that account's access immediately via User management, then contact support. |
| After a content sprint | Activity log, filter by event type to confirm every expected change landed. |
What these surfaces are not for: uptime alerting (none will tell you your site is down before visitors do — Site Vitals refreshes every 12 hours), field-level content diffs (the log records that a page was edited, not what changed inside it), or visitor behavior analytics (see Analytics data pipeline overview for that).
Worked example: diagnosing a Site Vitals score drop
Your site's score drops from 87 to 58 over the weekend. Open the Activity log, filter to Media events in the last 48 hours:
Re-upload the banner with compression enabled. Site Vitals rescans within 12 hours.
Troubleshooting — where to look when something seems off
Related features — see also
| Where to go | What it covers |
|---|---|
| Your SGEN dashboard — what each panel tells you | Full dashboard reference including Site Vitals panel |
| See what changed on your site recently | Complete Activity log guide |
| Manage your Notifications inbox | Comment moderation workflow |
| Analytics data pipeline overview | Traffic data, visitor analytics — a separate system |
| Backup and restore | Recovering content after the Activity log shows a deletion |
| Permissions and roles | Which team members can access which admin surfaces |
| Performance and reliability | Platform-side performance context for Site Vitals scores |
Access and scope
You need an admin account to access any of these surfaces. If you cannot see the Activity log or Notifications menu item, your role may not have access — ask your site owner to check your permissions. Each SGEN site has its own Activity log, Notifications inbox, and Site Vitals reading; switch sites from the top navigation to check a different one.
What SGEN does not expose to customers
- Server error rates and response time percentiles — visible to SGEN's platform team, not to site owners.
- CDN cache hit rates — internal metric, not surfaced in the admin.
- Email delivery status for transactional emails — not visible in the admin. Contact support if this matters for your workflow.
- Activity log history beyond 50 events — older history is held server-side; contact support to request it.
If you are looking for a monitoring surface and cannot find it here or in Analytics, it is either not yet customer-facing or a platform-side concern — check with your SGEN contact.
