GO4Monitoring platform
Monitor response status, speed and expected page content — using Server HTML or the Browser DOM after JavaScript when dynamic storefront elements matter.
HTTP / Page checks combine transport-level health with simple storefront expectations. A page can return 200 while loading the wrong template, an error message or an unusually small response.
GO4 can flag a response mismatch, slow response, unexpectedly small body or known storefront error pattern even when the URL itself still opens.
Add one focused content assertion when availability alone is not enough. GO4 supports four read-only assertion types and does not execute custom JavaScript as part of the rule.
.product-formConfirm that an expected page element exists. You can require a minimum number of matches.
.maintenance-bannerWarn when a selector that should be absent appears in the checked page source.
Add to cartVerify expected text in raw server content or visible browser text after JavaScript.
Liquid errorDetect text that should never be present on a healthy storefront page.
The simpler Must contain / Must NOT contain fields remain available for raw page HTML. Enabling Additional content assertion switches the check to the richer selector/text rule.
The same content expectation can need a different observation point depending on how the storefront is built. GO4 lets the check use the raw response or a controlled browser after JavaScript.
Evaluate the raw HTML body returned by the server. This is the direct choice for content that should already exist before browser-side rendering.
Open the page in GO4’s controlled browser, wait for the configured post-load window and evaluate the DOM or visible text after JavaScript and third-party widgets have had time to render.
Rendered assertions have configurable browser timeout, wait-after-load and resource mode so the check can be tuned to the storefront element being verified.
HTTP / Page checks also support SSL certificate expiry-only mode. In this mode GO4 inspects the HTTPS certificate itself and ignores page body, content, expected-status, slow-response and body-size rules.
Use a dedicated certificate check when the question is simply whether HTTPS remains valid and whether the certificate is approaching the warning window.
Page Monitoring works best when each check answers a clear operational question about an important URL or element.
Verify that the product form or another key purchase-control selector exists on a product page.
CSS selector must existUse Browser DOM after JavaScript for reviews, galleries or other storefront widgets injected after the initial HTML.
Rendered selector assertionCatch a known failure phrase such as a Liquid or maintenance message even when the URL still responds.
Text must not appearSet a minimum body size alongside the expected HTTP status to detect suspiciously incomplete responses.
Minimum body bytesGO4 has several browser-related capabilities because each answers a different operational question. Page Monitoring is the focused check for response behavior and expected page content.
Is this URL responding as expected, and is the content condition I care about present or absent?
How did a controlled browser experience this page, and what changed compared with earlier runs?
Which third-party dependency groups exist around representative storefront pages, and what changed?
What browser-side evidence is arriving from actual storefront pageviews that match active JS Agent checks?
A scheduled HTTP / Page check evaluates the response and configured page rules, returns the check status and feeds the same incident and alerting workflow used across GO4.
GO4 fetches the configured URL with the check timeout and expected HTTP behavior.
Status, timing, body size and known error patterns are evaluated.
When enabled, GO4 evaluates the selected server-HTML or browser-DOM assertion.
Warnings or failures can flow into the existing incident and notification lifecycle.
When the monitored condition returns to normal, GO4 can reflect that recovery in check history and incident state.
GO4 distinguishes some bot-challenge, rate-limit and host-cooldown conditions from ordinary page failures. Cooldown/deferred behavior helps recurring monitoring avoid repeatedly hammering a protected storefront.
Page Monitoring is a focused verification layer for important URLs. It complements deeper browser diagnostics and real-user evidence rather than replacing them.
No. Availability is part of it, but an HTTP / Page check can also validate the expected HTTP status, response time, minimum body size, expected or unexpected text, one optional content assertion and SSL certificate expiry-only mode.
Yes. Additional content assertion supports “CSS selector must exist” and can require a minimum number of found elements. It also supports “CSS selector must not exist”.
Yes. Set the assertion source to Browser DOM / after JavaScript so GO4 evaluates the page after a controlled browser has rendered it. Browser timeout, wait-after-load and resource mode are configurable.
Server HTML checks the raw response body before browser-side rendering. Browser DOM uses a controlled browser and checks the page after JavaScript has run, which is useful for dynamically injected storefront content.
No. Page Monitoring verifies a page and its content. Multi-step clicks and purchase-path verification belong to Action Journeys.
Page Monitoring asks whether a URL and a focused content condition are healthy. Browser Lab collects broader controlled-browser evidence such as performance, screenshots, resource diagnostics and historical comparisons.
Yes. SSL certificate expiry-only mode verifies HTTPS certificate validity and warns when the certificate enters the configured expiry window. Invalid or expired certificates fail the check.
Not necessarily. The HTTP runtime classifies bot challenges and rate limiting separately and can start a host cooldown. Runtime-deferred fetches are also represented separately from ordinary content failures.
Use HTTP / Page checks for direct response health, focused content verification and certificate monitoring — then investigate deeper with the right GO4 layer when needed.