To fix the 'Locale not detected' error, ensure the locale matches a configured help center locale.
This error occurs when the search crawler can't detect a locale or the detected locale doesn't match any help center locales. Check that thelang
attribute in the<html>
tag, the HTTP Content-Language header, and the<meta>
tag match a locale from your help center. For more information, seeUnderstanding search crawler locales.
To verify domain ownership for Zendesk's search crawler, ensure your homepage is publicly accessible and the verification tag is correctly placed. The search crawler checks domain ownership each time it runs, which can take up to 24 hours. If…
If your sitemap cannot be processed, ensure the sitemap URL is correct and publicly accessible. The search crawler uses the sitemap defined during setup each time it runs. If it can't process the sitemap, you'll receive an email notification. To…
The 'Title not detected' error means the search crawler couldn't find a title for a record. To resolve this, ensure the affected page has a<title>
,<h1>
, or textual content in the<body>
tag. The crawler uses these elements to determine the…
To fix the 'Body not found' error, ensure the affected page is properly marked with the<body>
tag. This error indicates that the search crawler couldn't detect the body of a page. Verify that the<body>
tag is correctly implemented on the page…
If you encounter an HTTP status code error, check the page's accessibility and update the sitemap. Common errors include 404 (Page not found), 403 (Forbidden), and 5xx (Server error). Ensure the sitemap is current and all URLs point to existing,…
To resolve the 'Invalid URL domain' error, ensure the page's domain matches the configured domain. This error occurs when a URL in the sitemap is not on the domain set during crawler setup. Verify that the domain of the page triggering the error…
The 'Undetermined' error may be due to exceeding the external records limit or JavaScript redirects. This error can occur if you've exceeded the 50,000 external records limit or if the page uses JavaScript location redirects. To resolve, delete…