Every alert type and how to fix it

Find the “Issue:” line of your alert below. A few different causes share the same Issue line, such as “Page returned an HTTP error”, so also compare the “Expected:” and “Observed:” lines. Each entry shows the exact wording of the lines that change, what it means, the usual causes and what to do. The first thing to try is always the same: open the page yourself in a private browser window.

If a change was intentional, you do not need to wait for it to clear. In the dashboard, open the page and choose Change what’s checked to approve the new wording, or This is intended: stop warning me about this. See Using the dashboard.

Page returned an HTTP error

Issue: Page returned an HTTP error
Severity: HIGH
Expected: HTTP < 400
Observed: 404
Suggested action: Check this page and its hosting.

The server answered, but with an error number. The number in “Observed” tells you what to do:

  • 404 or 410 (not found / gone): the page was deleted, unpublished, renamed or its address changed. Restore it, or restore the old address, or add a redirect from the old address to the new page. On WordPress check Pages, Trash and Drafts first.
  • 500 (server error): something on the site crashed. Common causes are a plugin or theme update, a full disk or a database problem. Check your host’s error log, deactivate the last plugin you changed, or restore a backup.
  • 502, 503 or 504 (gateway or unavailable): the host or its caching layer could not answer. Often temporary during maintenance or a traffic spike. If it lasts, contact your host.
  • 401, 403 or 429: PageNora does not raise an alert for these. A page that refuses automated visitors, needs a login or is rate limiting is shown as “unknown”, never as broken. See Troubleshooting.

When it is fixed: you will get a recovery email after two healthy checks.

The site cannot be reached

Issue: Page returned an HTTP error
Severity: HIGH
Expected: Site reachable
Observed: Cannot connect: the server refused the connection
Suggested action: Check that the site is online, its domain and DNS are correct, and its HTTPS certificate is valid.

The Issue line is the same as above, but “Expected: Site reachable” and “Observed: Cannot connect” tell you it is this case. PageNora could not even open a connection. The reason after “Cannot connect:” is one of these:

  • the server refused the connection: your web server is not running or a firewall closed it. Restart the site at your host or contact them.
  • the domain name does not resolve: your domain’s DNS is broken or the domain expired. Check that the domain is renewed and its DNS records still point to your host.
  • the connection timed out: the server did not answer in time. The host may be down or overloaded.
  • the HTTPS certificate or secure connection failed: the certificate expired, does not match the domain or is badly installed. Renew it or ask your host to reissue it.

PageNora first checks that its own internet connection works. If it cannot reach the internet it stays “unknown” and says nothing, so an outage on our side never becomes a false alarm about your site.

The site’s robots.txt returns a server error

Issue: Page returned an HTTP error
Observed: robots.txt returns HTTP 503 (server error); the page was not requested

PageNora reads your robots.txt first, as polite crawlers do. If that file itself fails with a server error, your site is struggling, so PageNora reports it. Fix the server error (see HTTP 500 and 503 above). If your robots.txt simply does not exist (404), that is fine and checks go ahead.

Expected page content is missing

Issue: Expected page content is missing
Severity: HIGH
Expected: (555) 010-4477
Observed: Expected text absent
Suggested action: Check the selected content or CTA. Presence does not verify form submission.

A phrase you asked us to watch (a phone number, a button label, a price) is no longer in the page’s text. Open the page and look. Common causes: someone edited the wording, a page builder or plugin update changed the layout, the text became an image or is now loaded by JavaScript after the page opens (PageNora reads the page as delivered by the server and does not run JavaScript). If the new wording is intentional, choose Change what’s checked on that page and enter the new phrase.

An important link is missing

Issue: An important link is missing
Severity: HIGH
Expected: /book/
Observed: Expected link absent
Suggested action: Restore the intended link or approve an updated baseline.

The page no longer contains a link to the address in “Expected”, for example your Book now button. Check that the button still exists and still points there (it may now point to a new address, or the menu was rebuilt). If the link intentionally moved, choose Change what’s checked and enter the new address.

An important link leads to a missing or failing page

Issue: An important link leads to a missing or failing page
Severity: HIGH
Expected: /book/
Observed: Critical link returns HTTP 404
Suggested action: Restore the target page or correct this link.

(for a server error the lines read:)
Observed: Critical link returns HTTP 503 (server error)
Suggested action: The destination page is failing on its server. Check that page, its plugins or booking service, and its hosting.

The link is still on your page, but the page it leads to on your own website fails. The “Observed” line says how: HTTP 404 or 410 means the page is gone, and HTTP 500, 502, 503 or 504 (server error) means the page exists but is crashing on its server, for example a booking or form plugin on your own site that is failing. This is the broken-booking-button case. For a missing page: restore it, change the link to the right address, or add a redirect. For a server error: check that page, its plugins and your host. A link that goes to another company’s website is checked only for being present on your page: PageNora does not follow it, so it cannot tell you that company’s service is down. If the destination only refuses automated visitors (403, 429) or cannot be reached from our side, PageNora shows “unknown” and does not alert.

Page title changed

Issue: Page title changed
Severity: MEDIUM
Expected: Book an appointment | Example Clinic
Observed: Home | Example Clinic
Suggested action: Review the change against the approved baseline.

The page’s title (the text on the browser tab and in search results) is different from the one you approved. A different title can mean the wrong page is being served, a template or SEO plugin changed, or someone retitled it. Fix it in your page settings or SEO plugin. If the new title is deliberate, choose Change what’s checked and approve the new title.

Search description changed

Issue: Search description changed
Severity: MEDIUM
Expected: Book physio appointments online.
Observed: 
Suggested action: Review the change against the approved baseline.

The meta description (the grey text under a search result) changed or disappeared; a blank “Observed” means it is gone. Check the page’s SEO settings or your SEO plugin and restore it, or approve the new wording under Change what’s checked if the change was intended.

Canonical address changed

Issue: Canonical address changed
Severity: MEDIUM
Expected: https://www.example-clinic.com/book
Observed: https://staging.example-clinic.com/book
Suggested action: Review the change against the approved baseline.

The canonical tag tells search engines which address is the “official” one for this page. If it points somewhere else (a staging copy, another page, a different domain) search engines may stop showing your real page. Typical cause: a staging site was copied over, or an SEO plugin setting changed. Restore the correct canonical in your SEO settings.

Page is marked noindex

Issue: Page is marked noindex
Severity: HIGH
Expected: indexable
Observed: max-image-preview:large noindex
Suggested action: Review the robots directive.

The page tells search engines not to show it. If this is a page that should bring in visitors, that is serious and silent. Typical causes: “Discourage search engines from indexing this site” is ticked (WordPress: Settings, Reading), a page-level “hide from search” setting is on, or a developer left a site-wide noindex after launch. See Platform guides for where the setting lives. Remove it, then wait for the recovery email.

Form problems

Issue: Page expectation changed
Severity: HIGH
Expected: fields: email, message, name, phone
Observed: Missing fields: phone
Suggested action: Restore the missing fields. Forms added by JavaScript or an embedded widget may not appear in the page source; PageNora does not submit forms.

Three versions exist, all about whether the form is still on the page:

  • Missing fields: a field you listed is gone (for example the phone field). Restore it in your form plugin.
  • No matching form found on the page: the whole form is gone, or it now loads in a way PageNora cannot see (an embedded widget loaded by JavaScript). Restore the form.
  • The form has no submit button: the button was removed or renamed in a way the page code no longer shows as a submit button.

Important limit: PageNora checks that the form is present. It does not submit it, so it cannot tell whether messages are actually delivered to you. Send yourself a test message from time to time. If your form is an embedded third-party widget (a booking widget, for example), watch the link or text around it instead.

Page response exceeded your limit

Issue: Page response exceeded your limit
Severity: MEDIUM
Expected: The page answers in under 5000 ms
Observed: It took 7342 ms
Suggested action: Review hosting response latency.

The page took longer than the limit you chose (in milliseconds; 7342 is about 7.3 seconds). One slow check is not reported; it has to repeat. Common causes: busy or cheap hosting, no caching, a heavy plugin. Try a caching plugin, remove unused plugins and ask your host about the plan. (PageNora measures how fast your server sends the page, not how long a browser takes to show images, so an oversized image is not the cause of this alert.)

HTTPS certificate is nearing expiry

Issue: HTTPS certificate is nearing expiry
Severity: MEDIUM
Expected: At least 14 days left on the HTTPS certificate
Observed: 9 days left
Suggested action: Renew the HTTPS certificate before expiry.

The certificate that secures your site has about 9 days left (you chose to be told at 14). If it expires, visitors see a scary browser warning. Most hosts renew free certificates automatically; if yours has not, ask your host to reissue it, or renew it in your hosting panel.

Recovery confirmed

The matching “resolved” email uses the same Issue line with Status: resolved and Observed: Recovery reconfirmed. It appears after two healthy checks. See Reading an alert.