Know when your website, SEO signals or Shopify selling path has a problem — before customers notice.

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

The goal is practical visibility: not only that something is wrong, but what is wrong, which URL is affected, whether it is critical, whether it has been accepted or muted, and how it changed over time.

• Useful for Shopify stores, SEO teams, agencies, support teams and website owners.
• Separates critical operational problems from quality warnings.
• Keeps history and evidence for every check execution.
• Provides a clear active-issue workflow instead of relying on manual spot checks.

Most website and store problems do not look dramatic at first: one empty collection, a noindex URL in the sitemap, a broken canonical, a slow page, temporary bot protection or a cart path that stops working correctly.

GO4 reduces the time between a problem appearing and the team reacting. That protects revenue, SEO visibility, advertising spend and customer trust.

• Fewer missed issues after theme, app, SEO or collection changes.
• Faster response for critical pages and checkout-related problems.
• Clearer communication between owner, developer, SEO and marketing teams.
• Less noise through accepted finding mutes and separate quality vs downtime layers.

The dashboard shows the overall state of monitored websites, recent checks and open incidents. It is the place to see whether something needs immediate attention.

GO4 separates operational health from quality warnings. An SEO issue does not look like full downtime, and a real critical failure does not get buried among lower-priority warnings.

• Global site filter for working with multiple projects quickly.
• Critical checks, quality warnings and incidents are shown as separate layers.
• Recent runs provide context about what happened most recently.
• Useful for daily review by owners, operators or support teams.

Sitemap SEO audit discovers URLs from sitemap sources and builds a persistent inventory. It then audits pages for important SEO signals and displays Findings, URLs, Sources and Progress in separate views.

This is especially useful for larger sites where manually checking every important URL is slow and where noindex, missing title/meta, canonical issues or H1 signals can easily be missed.

• Discovers URLs from sitemaps and tracks audit progress.
• Shows active and muted issues per URL.
• Includes server diagnostics, live server HTML preview and rendered browser diagnostics.
• Supports server vs browser comparison for harder SEO cases.
• Useful for stores, blogs, landing pages and large catalogue structures.

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.
• Collections, Findings, Progress and Overview tabs for each check.
• Collection audit overview across all sitemap-mode collection checks.
• Removed sitemap collections can have their active findings cleaned up after complete discovery.

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

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 the status.
• Rendered browser diagnostics use a controlled local browser worker.
• Server vs browser comparison shows whether the browser confirms or changes the warning.

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 System diagnostics without creating false cascades of SEO or collection errors.

• Host cooldown protection after 429, bot challenge, temporary 5xx and network errors.
• Max fetches per host / process for safer large batch checks.
• Deferred checks keep the previous real status unless strict behavior is enabled.
• Owners can see cron/worker diagnostics, active cooldowns and historical cooldown records in System.

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

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

• Browser-side title, meta description, canonical, robots/noindex and page type signals.
• Performance timing: total load, TTFB, DOM ready and load event.
• JavaScript errors and resource load errors when the browser exposes details.
• Safe read-only /cart.js check for Shopify sites.
• Ingestion guard stops events for disabled sites, inactive workspaces or disabled JS Agent collection.

For Shopify stores, GO4 adds checks aimed at real storefront risks: cart behavior, products, collections, collection sitemaps, SEO signals and browser-side cart endpoint 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+ indication at the Shopify endpoint cap.

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 resolved.

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.
• 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 simulation and collection audit.
• 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.

Protected technical documentation, when needed, should remain available only to admins and owners.

• 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 — uptime and quality are separate layers.
• Why are cooldowns used? They protect the system and monitored hosts from too many requests during temporary problems.
• 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.