Store owner field guide / Product pages

Product page down or unreachable? Troubleshoot 404 errors and store outages.

Start with the exact public product URL, compare it with the rest of your storefront, and use the response as a clue. A page that responds is not proof that the product is in stock or that checkout and payment work.

The key distinction

Reachability tells you whether a saved public URL responded. It does not tell you what the page contains or whether a shopper can complete a purchase.

01 / Work through these checks

What to do when a product page is down or unreachable

  1. Verify the exact public URL

    Open the full product-page address that shoppers should use. Compare it with the URL saved in your monitor and the published link in your store platform. Check the product path and spelling; an editor or preview address is not the same as the public product URL.

  2. Store offline or one product page down? Compare public pages

    If those pages open but this product page does not, focus on this listing and its URL. If several pages fail too, the problem may affect a wider part of the storefront or domain. This comparison narrows the scope; it does not identify a root cause by itself.

  3. Read the response as a clue, not a diagnosis

    An HTTP response, a DNS error, and a connection timeout point to different parts of the request. Use the result to decide what to check next:

    HTTP 404 — page not found
    The address returned a not-found response. The product may have been removed intentionally, or its public URL may have changed. Check the product in your store platform and confirm its current published URL before treating the 404 as an outage.
    HTTP 5xx — server error
    The server returned an error while handling the request. Check your store platform’s status information and contact its support team or your host if the error continues.
    DNS lookup failure
    The domain name could not be resolved for that request. Recheck the spelling and domain, then ask your domain provider, store platform, or host to review a persistent DNS problem.
    Timeout or connection failure
    No usable response arrived in time, or the connection could not be made. Retry from another browser, device, or network; if it keeps failing, share the result with your store platform or host.

  4. Retry from another browser, device, or network

    Try a private browser window, another device, or a different connection such as mobile data. If the page works there, investigate the original browser or network. If the same failure follows the URL across attempts, keep the result and contact your store platform or host.

  5. Escalate persistent host or domain failures

    Send your store platform or host the exact public URL, when you checked it, the HTTP status or failure reason shown, and whether the home page and another product page worked. That gives support a clear starting point for investigating the listing, server, or domain.

02 / The reachability signal

What SnagSparrow checks—and what it cannot tell you

SnagSparrow checks each saved public product-page URL once when it is first saved, then daily, and whenever you start an on-demand check. It records the reachability result, the HTTP status when available, and a failure reason. It sends incident and recovery alerts to the email on your account.

These are checks of individual URLs. SnagSparrow does not monitor whole-store uptime, so a result for one product page does not describe every page in your store.

A responding product page can still be sold out. SnagSparrow does not read page content, confirm stock, or monitor inventory. It cannot tell whether the page is blank or contains a “sold out” or “back in stock” message.

Page reachability also does not verify the cart, checkout, or payment flow. A page can respond while a shopper is unable to complete a purchase; SnagSparrow does not monitor checkout or payment.

03 / Investigate the cause

Alerts report a result; they do not repair the page

SnagSparrow reports reachability results and sends alerts, but it does not automatically diagnose the cause, repair a page, or fix a product listing. Use the URL and response details to investigate in your store platform, or contact the platform or host when a failure persists.