Know sooner when your site, SEO signals or Shopify sales path has a problem.

GO4 is a self-hosted monitoring platform for Shopify stores and public websites. It brings together availability, SEO checks, Sitemap SEO audit, Shopify collection audit, browser signals, incidents, alerts and noise control.

The platform is designed for practical work: it shows not only “there is a problem”, but what the problem is, which URL it affects, whether it is critical, whether it is muted and how it changed over time.

• Suitable for Shopify stores, SEO teams, agencies, support teams and site owners.
• Separates operational issues from quality warnings.
• Keeps history and evidence for every check run.
• Provides a clear panel for active incidents and findings instead of relying only on manual checks.

Many store issues start quietly: an empty collection, a noindex page in the sitemap, a broken canonical, a slow page, temporary bot protection or a cart path that does not behave as expected.

GO4 reduces the time between issue appearance and response. That protects revenue, SEO visibility, ad spend and customer trust.

• Fewer missed issues after theme, app, SEO or collection changes.
• Faster response for critical pages and the sales path.
• Clearer communication between owners, developers, SEO and marketing teams.
• Less noise by muting accepted findings and separating quality from real downtime.

The Dashboard shows the overall state of monitored sites, latest checks and open incidents. It is the first place to see whether anything needs immediate attention.

GO4 separates operational health from quality warnings. An SEO issue does not look like full downtime, and a real critical failure is not lost among softer warnings.

• Global site filter for working with multiple projects quickly.
• Critical checks, quality warnings and incidents appear as separate layers.
• Latest runs provide recent context.
• Useful for daily review by an owner, operator or support team.

The Sites section controls workspace, name, Base URL, platform, active state, JS Agent settings and Shopify-only settings for Shopify sites.

The platform value matters: a Shopify site shows Shopify checks and Shopify crawler signature settings. A generic site hides those settings and does not use a Shopify crawler signature.

• JS Agent is enabled at site level, while active Client-side JS Agent checks decide which events are relevant.
• Sampling, query parameters, sensitive parameter cleanup and retention are controlled by the site.
• Shopify crawler signature is configured separately for each Shopify domain.
• Expired Shopify crawler signatures are not sent to Shopify.

Sitemap SEO audit discovers URLs from sitemap sources and builds a persistent URL inventory. It then checks pages gradually and shows Sources, URLs, Findings and Progress in separate views.

This is useful for large sites where manually checking every important URL is slow and it is easy to miss noindex, missing title/meta, canonical problems, H1 signals or content hygiene issues.

• Discovers URLs from sitemap indexes and child sitemap files.
• Shows active findings per URL, not only a generic summary.
• Supports Recheck with server diagnostics, live HTML preview and browser/rendered diagnostics.
• Lets you mark a URL as removed from the sitemap without resetting the entire inventory.
• Failed URL retry can be set to 1–2 hours for Shopify 502/503/429 situations.

GO4 extends Shopify collection rules with a “Collections from sitemap” mode. Instead of monitoring only one collection, the system can discover collection URLs from the Shopify sitemap and audit them in batches.

This helps detect empty collections, collections below the configured product minimum, public Shopify JSON endpoint issues and changes when a collection is no longer present in the sitemap.

• Automatic discovery of collection sitemaps and collection URLs.
• Product count checks through the lightweight products_count endpoint, with products.json fallback.
• 250+ display when the fallback endpoint reaches the Shopify limit.
• Overview, Collections, Findings and Progress tabs for each check.
• Muted collection findings do not affect status, incidents or alerts.

For Shopify sites, GO4 can use Shopify Web Bot Auth data stored as a Shopify crawler signature. The signature belongs to a specific domain and helps Shopify recognize GO4 requests.

This is useful for server checks, Sitemap SEO audit, Shopify collection audit and browser diagnostics, especially when Shopify protection returns 429, 502, 503 or challenge pages.

• Configured only for Shopify sites.
• GO4 reads the expiry time from Signature-Input.
• Expired signatures are not sent.
• Status is visible in Diagnostics and System.
• Each Shopify domain needs its own signature.

Some SEO and storefront problems do not look the same in a direct server request and in a browser after rendering. GO4 provides separate server diagnostics and browser/rendered diagnostics.

This helps with JavaScript-heavy pages, dynamic meta tags, canonical changes, theme/app effects and cases where server HTML and browser DOM disagree.

• Server diagnostics keep a structured snapshot instead of raw HTML by default.
• Live server HTML preview allows quick manual inspection without changing status.
• Browser diagnostics use a controlled local browser worker.
• Server/browser comparison shows whether the browser confirms or changes the warning.

JS Agent is a lightweight passive script that can be installed on a monitored website. It sends data about the real browser experience: load timing, JavaScript errors, SEO signals from the DOM, cart.js status and custom DOM checks.

The agent is observation-only. It does not change the DOM, does not add products to cart, does not start checkout and does not execute custom JavaScript from the admin.

• Uses a check-driven model: active Client-side JS Agent checks decide which events are relevant.
• Supports heartbeat, built-in browser signals, custom DOM rules or a combination of them.
• Tracks title, meta description, canonical, robots/noindex, page type and performance.
• Can report JS errors and passive Shopify cart.js status.
• JS Agent events do not open incidents directly; incidents are opened through active checks.

For Shopify stores, GO4 adds checks aimed at real storefront risks: cart behavior, products, collections, collection sitemaps, SEO signals and browser-side cart.js status.

The goal is to catch issues that affect sales and visibility without installing heavy logic inside the store.

• Cart add simulation with a valid available variant ID.
• Product rules for tags, availability and images.
• Specific collection mode for one important collection.
• Collections from sitemap mode for catalogue-level monitoring.
• Product count endpoint support and 250+ display at the Shopify endpoint cap.

GO4 includes a runtime protection layer that prevents overly aggressive repeated requests to the same host. This matters for large sitemaps, Shopify catalogue checks and temporary protections such as 429 or bot challenge pages.

Deferred automatic checks can be visible in Diagnostics or System without creating false cascades of SEO or collection errors.

• Host cooldown after 429, bot challenge, temporary 5xx and network errors.
• Per-process host budget for safer large batch checks.
• Deferred checks keep the previous real status unless stricter behavior is enabled.
• Owners can see worker diagnostics, active cooldowns and history in System.

Incidents are a focused queue for problems that need attention. Instead of watching raw history only, teams can see active cases and close them when recovered.

Alerts help the team respond in time, while health impact settings control which checks are allowed to create incidents.

• Operational checks can open critical incidents.
• Quality checks can show warnings without looking like downtime.
• Telegram alerts can include buttons to the incident, audit view or Runs history.
• Muted findings do not create new noise for accepted issues.
• History remains available for review after an incident is closed.

Muting in GO4 is precise. You can accept one specific finding for one specific check without disabling the whole monitoring layer or hiding future different problems.

That matters in real work because not every signal is urgent. Some are accepted, temporary or business decisions, but the system still needs to stay alert for everything else.

• Mute one specific issue instead of the whole site.
• Muted findings remain visible as an audit trail.
• Muted findings do not affect health rollups, incidents or alerts.
• Remove a mute rule when the issue should become active again.

GO4 is designed for more than one website and more than one person. Workspaces and roles make it possible to separate clients, stores, operators and read-only access.

This is useful for agencies, internal teams and owners who want people to see or manage only what they need.

• Owner can see and manage everything.
• Admin manages assigned workspaces and sites.
• Manager, Operator and Viewer roles provide more precise control.
• Backend permissions protect actions, not only the buttons in the interface.

The best approach is to start with the biggest risks: homepage, key collections, product pages, cart and sitemap. Then add the browser layer and tune incidents.

After a few days of real data, reduce noise: tune impact levels, mute accepted findings and leave the system focused on what really matters.

• Add the site and choose the correct platform.
• Add HTTP/Page health checks for critical pages.
• Add Sitemap SEO audit for SEO coverage.
• For Shopify, add cart, collection checks and Shopify crawler signature when needed.
• Install JS Agent if real browser signals are needed.
• Review active findings and mute only accepted issues.
• Enable alerts once the signal is clean enough.

This section answers the most important GO4 questions without exposing internal server paths, credentials or installation details.

Detailed in-app documentation explains the settings more deeply for users who already have access.

• Does JS Agent change the site? No — it is passive and read-only.
• Does JS Agent add products to cart? No — it does not add, remove or start checkout.
• Can a site be OK and still have warnings? Yes — operational health and quality are separate layers.
• What is a Shopify crawler signature? A valid Shopify Web Bot Auth signature for a specific domain that helps Shopify recognize GO4 requests.
• Does 502/503 always mean a broken page? No — it is often a temporary edge or upstream problem.
• What should I do with an accepted issue? Mute the specific finding instead of disabling the whole check.
• Is it suitable for more than one site? Yes — GO4 has workspaces, roles, filters and separate audit overview screens.