DocsReferenceTroubleshooting

Troubleshooting. When something looks wrong.

The most common problems and what to do about them. Still stuck? E-mail support@searchsentinel.app.

On this page

The page returns 403 or "Crawler Blocked"

A firewall, bot protection or CDN is blocking the checks. Copy the user agent from the "Crawler Blocked" notice on the URL detail page and allowlist it. See The Search Sentinel crawler.

Changes are logged but no alert arrives

  • Check which channels are on in the URL's Alert settings. New URLs copy the alert settings of the project's other URLs, so if those send nothing, the new URL sends nothing either. In a project without alert settings, a new URL alerts only your login e-mail and the default webhooks from your account. Use Bulk Edit Alerts in the project settings to set all URLs at once.
  • Check that the trigger for that kind of change is on in Alert Triggers.
  • Throttling may have held it back: by default there is at least 60 minutes between two alerts for a URL, and changes in between are not sent.
  • Changes of elements turned off in the project's What To Track Setup are not logged at all.
  • Open Show Alert History: it shows per channel whether the alert was sent, or the error that came back. Use Send Test Alert to test the channels.
  • For e-mail, check your spam folder and that alerts@searchsentinel.app is allowed.

A snippet shows "Not Found" but it is on the page

  • Matching is exact and case-sensitive. Copy the pattern from the page source, including quotes.
  • The snippet may be added by JavaScript, for example through Google Tag Manager. Checks read the HTML without running scripts. Look for something that is in the HTML source, like the GTM container ID.
  • Click the status to open the page's HTML with matches highlighted.

No Core Web Vitals data

CrUX only has data for pages and sites with enough Chrome traffic. Without URL-level data Search Sentinel shows origin data; without either it shows "No CrUX data available". New data arrives weekly after Google's Monday release. Alerts are evaluated per metric for URL-level data, never for origin-level data. FCP and TTFB alerts are off until you switch them on in the project's CrUX thresholds.

Search Console data stops three days ago

That is normal: Search Console data arrives with a delay of about three days. If data stops for longer, click Reconnect under Settings → GSC.

A URL is not checked any more

  • The URL or project may be paused. Look for the Paused label.
  • The checks of your billing period may be used up. Scheduled checks are skipped until the period resets or you buy a credit pack. See the meters on Billing & usage.
  • Your trial may have ended.

"This URL is already monitored in another project"

A URL can be in one project per account, and on team plans in one project per team; the message names the project when a teammate already monitors it. Remove it from the other project first, or keep monitoring it there.

The robots.txt check says "Blocked"

Googlebot may not crawl the URL according to the current robots.txt. Open Robots & XML to see the rule and line number that matched.