Current website status
See whether the active project website is currently recorded as up, down, timed out, or unreachable before opening the deeper evidence.
Website Uptime Monitoring with Alerts
Check whether a Screpy project website is reachable, measure its 30-day availability and response times, review HTTP failures and incident recovery, and notify the right inbox without turning uptime into a ranking promise.
TL;DR
Too Long; Didn't Read
Show summary Hide summary
TL;DR
Too Long; Didn't Read
What Is Website Uptime Monitoring?
Screpy Uptime Monitoring repeatedly checks the public website configured for a project, records HTTP availability and response time, and summarizes the latest 30 days with incidents and supported email notifications. It provides external monitoring evidence; it does not diagnose infrastructure or guarantee search visibility.
Configure the project check
- Screpy monitors the public website URL configured for the current project.
- Uptime monitoring can be enabled or disabled in project settings.
- The available check interval depends on the active plan.
- An optional notification address can receive supported outage emails.
Read 30-day health
- Current status shows the result of the latest completed check.
- Uptime percentage summarizes successful checks from the latest 30 days.
- Average response time uses successful checks from the same period.
- Last checked and total checks make monitoring freshness visible.
Inspect check evidence
- HTTP 2xx and 3xx responses are recorded as available.
- Other HTTP responses, timeouts, and connection errors remain distinguishable.
- Recent checks include status, response time, HTTP code, and timestamp.
- Incident records keep outage start and recovery timestamps together.
Understand the boundaries
- Each project monitors its configured website rather than an arbitrary endpoint list.
- External HTTP checks do not replace infrastructure or transaction monitoring.
- Screpy records symptoms and recovery but does not claim automatic root-cause analysis.
- Availability supports crawl access but does not guarantee indexing or rankings.
See availability, response time, and incidents in one view.
Start with the current state, then use the 30-day summary, recent checks, response timeline, and incident timestamps to decide whether the project website needs investigation.
30-day uptime percentage
Calculate the share of successful checks recorded during the latest 30-day window instead of judging reliability from one request.
Average response time
Review the average response time from successful checks in the same 30-day period so availability and delivery latency stay distinct.
Response-time timeline
Follow recent response-time measurements on a chart and compare slow periods with deployments, traffic events, or infrastructure changes.
Recent HTTP checks
Inspect the recorded status, HTTP response code, response time, safe error state, and timestamp for recent project website checks.
Status distribution
Separate successful, down, timeout, and connection-error results to see whether a problem is isolated or repeated within the reporting window.
Incident and recovery history
Review open and resolved incidents with their start and recovery timestamps instead of losing the event after the website becomes available again.
Email notifications
Send supported outage and recovery notifications to project members and an optional project notification address when the incident qualifies.
Monitor the public website configured for each project.
Screpy sends recurring external HTTP checks to the project website at the interval available on the active plan, then keeps the result connected to the same SEO workspace.
- Use the website URL already configured for the project
- Record HTTP 2xx and 3xx responses as available
- Distinguish HTTP failures, timeouts, and connection errors
Read uptime and response time as a pattern.
A rolling 30-day view turns individual checks into a useful reliability history without hiding the latest result or the freshness of the monitoring data.
- Review current status and 30-day uptime percentage
- Compare average response time with the response-time series
- Inspect recent checks and the full status distribution
Keep downtime and recovery in the same timeline.
Failed checks open or update an incident, and the next successful check records its resolution so the outage has a clear beginning, duration, and recovery state.
- Track open and resolved incidents separately
- Keep incident start and resolution timestamps
- Send supported outage and recovery email notifications
Set up a useful uptime monitoring loop.
A check is valuable when the target is public, the interval matches the site\'s importance, notifications reach a responsible inbox, and every incident ends with a verified recovery.
- 01
Use the public project website URL
Choose a stable public target that represents the website visitors and crawlers must reach. Avoid private admin routes or intentionally unavailable paths.
- 02
Enable checks and configure the interval
Turn on Uptime Monitoring in project settings, use the interval available to the project, and add an optional notification email for operational ownership.
- 03
Read the 30-day pattern before escalating
Compare current status, uptime percentage, response-time history, HTTP results, and repeated failure states instead of declaring an outage from one isolated datapoint.
- 04
Investigate and confirm recovery
Check deployment, DNS, TLS, hosting, firewall, and application evidence outside Screpy, then confirm that a later successful check resolves the incident.
Prioritize websites where downtime carries real cost.
Use recurring checks for projects where availability affects sales, leads, campaigns, customer access, or the ability of search crawlers to retrieve public content.
Revenue websites
Keep the storefront, booking site, subscription product, or lead-generation website under recurring external availability checks.
Organic search properties
Watch the public site that search crawlers and organic visitors must reach before content quality or ranking work can matter.
Launch and campaign sites
Track the project website during launches, migrations, redesigns, and active campaigns when an availability problem carries more immediate cost.
Multi-project portfolios
Review uptime separately for each available Screpy project so agencies and in-house teams can keep client or brand websites in one workflow.
Know the boundary of an uptime result.
Screpy supplies external HTTP evidence and incident history for the configured project website. Use infrastructure, logs, transaction testing, and search data when the question extends beyond that scope.
One project website target
Uptime Monitoring checks the public website URL configured for the Screpy project. It is not a general-purpose list of independent endpoint monitors.
External check, not infrastructure telemetry
The result describes whether the public target responded. It does not inspect CPU, memory, containers, databases, private networks, or server logs.
Incident evidence, not root-cause proof
HTTP status, timing, and incident timestamps narrow the investigation but cannot prove whether DNS, TLS, hosting, deployment, firewall, or application code caused it.
Availability is not an SEO guarantee
A working public page is necessary for visitors and crawling, but a high uptime percentage alone cannot guarantee indexing, rankings, traffic, revenue, or conversions.
Use the website-health workflow that matches the failure.
Monitor reachability over time, audit the wider website when failed URLs or crawl patterns repeat, or inspect page performance after availability is stable.
Track the project website's current status, 30-day uptime, response-time history, recent HTTP checks, and incidents.
Crawl the wider website to find repeated failed pages, redirect problems, broken destinations, and technical patterns around an availability issue.
Run recurring lab performance checks when the website is reachable but loading or responsiveness still needs investigation.
Screpy documentation
Learn how to monitor website uptime
Follow the Screpy guide to choose a useful public project URL, configure the plan-dependent interval and notification email, interpret 30-day availability evidence, and verify incident recovery.
Related SEO guides
Learn the concepts behind this workflow and apply them with practical SEO guidance.
GEO
How Do You Find AI Visibility Gaps?
AI visibility gaps emerge when you compare brand mentions, citations, and competitor coverage across priority prompts, AI platforms, and topic clusters.
Read article GEO
How Do You Monitor Brand Mentions in ChatGPT?
Monitor brand mentions in ChatGPT with a repeatable prompt set, tracking citation sources, competitor share of voice, sentiment, and response trends over time.
Read article GEO
Which Prompts Should You Track for AI Search Visibility?
AI search visibility improves when you monitor category, use-case, comparison and branded prompts by audience and funnel stage, then review mentions and citations.
Read article GEO
How Do You Calculate AI Visibility ROI?
AI visibility ROI connects citations, share of voice, branded search, assisted conversions, and revenue to costs for a practical, defensible ROI model.
Read articleWebsite Uptime Monitoring FAQ
Understand the target URL, HTTP status logic, check interval, 30-day history, response times, incident recovery, notification scope, and the difference between uptime and full infrastructure monitoring.
What does Screpy Uptime Monitoring measure?
Screpy checks the public website URL configured for a project and records its availability status, HTTP response code, response time, check timestamp, and safe error state. The dashboard summarizes the latest 30 days with uptime percentage, average response time, recent checks, status distribution, and incidents.
What does Screpy count as up or down?
A completed HTTP response in the 200 or 300 range is recorded as up. Other HTTP responses are recorded as down, while connection timeouts and other request failures are recorded separately as timeout or error states.
How often does Screpy check website uptime?
Screpy uses the interval configured for the project. Available defaults and feature access depend on the current plan, and eligible plans can use intervals as short as one minute. The dashboard shows the last check so you can judge freshness directly.
Does Uptime Monitoring show response-time history?
Yes. The Uptime view charts recent response times and reports the 30-day average for successful checks. Response time is useful operational context, but it is not the same as full page-load performance or real-user experience.
How do downtime incidents and recovery work?
A failed check opens or updates the current incident. When a later check succeeds, Screpy resolves the open incident and records the recovery time, preserving the event for review.
Does Screpy send downtime alerts?
Screpy can email project members and an optional project notification address for supported outage events. A recovery message can follow a notified incident. Review the incident list as the source of truth because not every failure state is guaranteed to produce an email.
Does uptime monitoring replace server or transaction monitoring?
No. Screpy verifies the configured public project website from outside the application. It does not inspect private infrastructure or test multi-step journeys such as login, search, form submission, or checkout completion.
Can website downtime affect crawling or indexing?
Availability problems can prevent crawlers from retrieving a page, and repeated server errors or timeouts can reduce crawling. Uptime Monitoring provides evidence for investigation, but it cannot guarantee when a search engine will crawl, index, or rank a URL.
SEO That Fits Your Budget
Explore how Screpy combines audits, rankings, AI visibility and monitoring, with clear plan limits.