--- title: Troubleshooting Web source issues slug: n1ab5310 canonical_url: https://docs.coveo.com/en/n1ab5310/ collection: index-content source_format: adoc --- # Troubleshooting Web source issues This article provides troubleshooting best practices and lists common issues when [indexing](https://docs.coveo.com/en/204/) content with the Web source. ## Important: Troubleshooting fundamentals Though the information provided in the [Common issues](#common-issues) section will often help you identify and resolve a problem, keep the following in mind: * A given set of symptoms can be caused by different underlying issues. * When you expand a content update activity in the **Activity** panel or [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page, the error code and messages displayed may only be general indicators of the problem. * Coveo only halts an indexing operation and displays an error when specific conditions are met. Consequently, finding the root cause of an issue may require more granular information, which only update logs can deliver. To download an update log . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click the desired resource, and then click **Activity** in the Action bar. . In the **Activity** panel that opens, click the desired activity, and then click **Download logs** in the Action bar. The downloaded file is named after the unique operation ID representing the selected activity. To locate issue root causes in logs . Open the log file in a text file viewer. . Look for `WARN`,`ERROR`, and `FATAL` messages. ![Indexing activity logs with a warning message | Coveo](https://docs.coveo.com/en/assets/images/index-content/warn-message-in-logs.png) > **Tip** > > Use a log file viewer that supports highlighting by log level to make these messages more noticeable. . If necessary, review `NOTICE` and `INFO` messages. They sometimes reveal a configuration that you overlooked and that may be causing the issue. ![Indexing activity logs with an info message | Coveo](https://docs.coveo.com/en/assets/images/index-content/info-message-in-logs.png) ## Common issues Issues are divided into categories. Click a category description below to reach the related section. * [Missing items](#missing-items) * [Extra or unwanted items](#extra-or-unwanted-items) * [Unexpected or missing content inside items](#unexpected-or-missing-content-inside-items) * [Unexpected item field values](#unexpected-item-field-values) * [Indexing is slow](#indexing-is-slow) * [Indexed content isn't up to date](#indexed-content-is-not-up-to-date) ### Missing items #### User agent blocklisting > **Context and symptoms** > > * No items or a limited number of items are indexed. > > * Other symptoms may vary. > For example: > > ** The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may display a `WEB_FORBIDDEN_ERROR` code. > > ** The activity [download logs](#important-troubleshooting-fundamentals) may show a NOTICE message in the following format: > > ```text CDN/Caching Detection: Provider = '', Host = '', Detected Header: '' = '', Reference header: . Please consult https://docs.coveo.com/en/1831/index-content/ip-addresses-to-allowlist to allowlist the IP addresses by the CDN/Caching provider if needed. ``` > > This message indicates that the source has detected that pages at `` are served by the `` CDN/Caching provider, which may interfere with requests from the Coveo crawler. > > .Likely cause and resolution >
Details > > **Cause** > > Your web server or CDN/Caching provider may be blocking requests from the Coveo crawler based on its user agent. > > This can happen, for example, if you're using the `mod_rewrite` module on an Apache server or the `URL Rewrite` module on an IIS server. > The source automatically detects the following CDN and caching providers, which can also interfere with requests from the Coveo crawler: Akamai, Amazon CloudFront, Cloudflare, Fastly, Incapsula (Imperva), and Varnish. > > **Resolution** > > . Chrome and other web browsers allow you to emulate web requests by [overriding the default user agent string](https://developer.chrome.com/docs/devtools/device-mode/override-user-agent). > Use this feature to test whether your web server or CDN/Caching provider restricts, filters, or otherwise handles requests differently based on the Coveo crawler user agent string (that is, `Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko) (compatible; Coveobot/2.0;+http://www.coveo.com/bot.html)`). > > . If applicable, update your web server, CDN/Caching provider, or Web source configuration to allow or properly handle requests. > > .. (Recommended) Update your web server or CDN/Caching provider configuration so that requests from the Coveo crawler user agent are allowed and processed as expected. > > .. On the **Advanced settings** subtab of your source configuration, set the [user agent string](https://docs.coveo.com/en/malf0160#user-agent-string) to a value that your web server accepts and processes without restriction. > > . [Rebuild](https://docs.coveo.com/en/3390#refresh-rescan-or-rebuild-sources) your source. > >
#### IP blocklisting > **Context and symptoms** > > * No items or a limited number of items are indexed. > > * Other symptoms may vary. > For example: > > ** The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may display a `WEB_FORBIDDEN_ERROR` or a `No such host is known` message. > > ** The activity [download logs](#important-troubleshooting-fundamentals) may show a NOTICE message in the following format: > > ```text CDN/Caching Detection: Provider = '', Host = '', Detected Header: '' = '', Reference header: . Please consult https://docs.coveo.com/en/1831/index-content/ip-addresses-to-allowlist to allowlist the IP addresses by the CDN/Caching provider if needed. ``` > > This message indicates that the source has detected that pages at `` are served by the `` CDN/Caching provider, which commonly interferes with requests from the Coveo crawler. > > ** An HTTP request may simply time out with no error. > > .Likely cause and resolution >
Details > > **Cause** > > Your infrastructure may be restricting, filtering, or otherwise preventing inbound requests from [Coveo Platform](https://docs.coveo.com/en/186/) IP addresses. > The source automatically detects the following CDN and caching providers, which can interfere with requests from the Coveo crawler: Akamai, Amazon CloudFront, Cloudflare, Fastly, Incapsula (Imperva), and Varnish. > > **Resolution** > > Configure your infrastructure to allow and properly handle inbound requests from the [Coveo Platform](https://docs.coveo.com/en/186/). > If the [download logs](#important-troubleshooting-fundamentals) are showing a CDN/Caching detection message, you may need to [allow requests from Coveo Platform IP addresses](https://docs.coveo.com/en/1831/) at the CDN/Caching provider level. > > Alternatively, consider installing the [Coveo Crawling Module](https://docs.coveo.com/en/3260/) on your infrastructure to push [items](https://docs.coveo.com/en/210/) to the [Coveo Platform](https://docs.coveo.com/en/186/) instead. > >
#### RespectUrlCasing setting issue > **Context and symptoms** > > * Missing items have URLs that contain uppercase characters. > All indexed items have URLs that only contain lowercase characters. > > * Other symptoms may vary. > For example, the [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may display an authentication issue (for example, a `WEB_FORBIDDEN_ERROR` error code). > > * The `RespectUrlCasing` JSON parameter is set to `false`. > > .Likely cause and resolution >
Details > > **Cause** > > With `RespectUrlCasing` set to `false`, the Web source crawler lowercases a URL it discovers, and then requests the lowercased URL from the server. > If the web server is case sensitive, it doesn't recognize the requested URL and doesn't serve the request. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click the source, and then click **Edit configuration with JSON** in the **More** menu. > Then, set [`RespectUrlCasing`](https://docs.coveo.com/en/mc1f0219#respecturlcasing-boolean) to `true`. > >
#### Crawling rules issue > **Context and symptoms** > > The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) doesn't show all the items you wanted to index. > > .Likely cause and resolution >
Details > > **Cause** > > Your current **Crawling rules** exclusions and inclusions are filtering out the items you wanted to index. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, review your source's [exclusions and inclusions](https://docs.coveo.com/en/malf0160#exclusions-and-inclusions). > > To be indexed, a page: > > * Must not match any exclusion rule, AND > > * It must match at least one inclusion rule (for example, by selecting the **Include all non-excluded pages** option). > >
#### Starting URL exclusion > **Context and symptoms** > > * The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) doesn't show all items you want to index. > > * One of your **Starting URLs** isn't indexed. > > * The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may show a `WEB_NO_DOCUMENT_INDEXED_DUE_TO_FILTERS` error code. > > .Likely cause and resolution >
Details > > **Cause** > > Your current **Crawling rules** exclusions and inclusions are filtering out that **starting URL**. > Consequently, the crawler can't index the items that are reachable via that **starting URL**. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, adjust your source's [exclusions and inclusions](https://docs.coveo.com/en/malf0160#exclusions-and-inclusions) to ensure the **starting URL** and all items accessible through it aren't filtered out. > > To be indexed, a page: > > * must not match any exclusion rule, AND > > * it must match at least one inclusion rule (for example, by selecting the **Include all non-excluded pages** option). > >
#### 301 Moved Permanently redirect > **Context and symptoms** > > * The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may show a `NO_DOCUMENT_INDEXED` error code. > > * Your **Starting URL** doesn't include a `www` segment (for example, `+https://abc.com+`). > > * When trying to access that starting URL manually in a browser, you're automatically redirected to a page that includes the `www` segment (for example, `+https://www.abc.com+`). > > .Likely cause and resolution >
Details > > **Cause** > > By default, the Web source only indexes items that are _internal_ to the site. > The Web source is considering the page it's redirected to (for example, `+https://www.abc.com+`) as _external_ to the website (for example, `+https://abc.com+`). > This internal/external validation is unrelated to exclusion and inclusion rules. > > **Resolution** > > If you're only getting started with a new Web source, you might simply want to delete the source, start fresh with a new one, and include the `www` segment in the **Starting URL**. > Otherwise, you can proceed as follows: > > . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click the source, and then click **More** > **Edit configuration with JSON** in the Action bar. > > . In the **JSON configuration** field, under the `parameters` property, add the following code block: > > ```text "IndexSubdomains": { "sensitive": false, "value": "true" }, ``` > > The **JSON configuration** field should now look as follows: > > ![Adding the IndexSubdomains parameter | Coveo](:https://docs.coveo.com/en/assets/images/index-content/adding-index-subdomains.png) > > . Click **Save** to exit the **Edit configuration with JSON** panel. > > . If necessary, make adjustments to your [exclusions and inclusions](https://docs.coveo.com/en/malf0160#exclusions-and-inclusions) to ensure the redirection URLs (for example, `+https://www.abc.com/something+`) aren't filtered out. > You might also need to add exclusion or inclusion rules to filter out unwanted subdomain items. > > . Rebuild your source. > >
#### Orphan pages > **Context and symptoms** > > * The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) doesn't show all items you want to index. > > * All of your **Starting URLs** are indexed. > > .Likely cause and resolution >
Details > > **Cause** > > The missing items may be orphan pages. > > **Resolution** > > * Add links to these items in your website so that the Web source crawler and other search engines may reach them, OR > > * On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, open your source. > Add [**Starting URLs**](https://docs.coveo.com/en/malf0160#starting-urls) for your orphan pages. > If necessary, make adjustments to your [exclusions and inclusions](https://docs.coveo.com/en/malf0160#exclusions-and-inclusions) to ensure the added **Starting URLs** aren't filtered out. > >
#### Missing or invalid basic authentication configuration > **Context and symptoms** > > * A page isn't indexed. > > * The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may show a `WEB_AUTHENTICATION_ERROR` error code. > > * When trying to access that page manually in a browser, you're prompted for credentials in a pop-up window. > > .Likely cause and resolution >
Details > > **Cause** > > Accessing the page content requires basic authentication. > > **Resolution** > > * Request the authentication credentials from the web server administrator. > Then, on the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, configure [**Basic authentication**](https://docs.coveo.com/en/malf0160#basic-authentication) on the source. > > * If you're using a password manager (for example, LastPass), it may replace the previously recorded username and password with different ones as you edit the source. > Check your password manager options and ensure that it respects the `autocomplete="off"` attribute. > >
#### Missing or invalid form authentication configuration > **Context and symptoms** > > * A page isn't indexed. > > * The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) page may show a `WEB_AUTHENTICATION_ERROR` error code. > > * When trying to access that page manually in a browser, a login page is displayed instead. > > .Likely cause and resolution >
Details > > **Cause** > > Accessing the page requires form authentication. > > **Resolution** > > * Request the authentication credentials from the web server administrator. > Then, on the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, configure [**Form authentication**](https://docs.coveo.com/en/malf0160#form-authentication) on the source. > > * If you're using a password manager (for example, LastPass), it may replace the previously recorded username and password with different ones as you edit the source. > Check your password manager options and ensure that it respects the `autocomplete="off"` attribute. > >
#### Authentication status validation issue > **Context and symptoms** > > * A page isn't indexed. > > * Accessing that page requires form authentication. > > * When trying to access that page manually in a browser, the form authentication **Login page address** page is displayed. > Typing in the credentials and submitting the login page brings up the page to be indexed. > > .Likely cause and resolution >
Details > > **Cause** > > The authentication **Validation method** might not be configured properly. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, make sure your source's [**Validation method**](https://docs.coveo.com/en/malf0160#validation-method) and the associated value are adequate. > >
#### Redirection to login page issue > **Context and symptoms** > > * A page isn't indexed. > > * Accessing that page requires form authentication and your source configuration **Validation method** is `Redirection to URL`. > > * When trying to access that page manually in a browser, the form authentication **Login page address** page _isn't_ displayed. > > .Likely cause and resolution >
Details > > **Cause** > > The `Redirection to URL` **Validation method** doesn't work in your use case. > Consequently, the Web source crawler doesn't know it must authenticate before accessing the page to index. > > **Resolution** > > * On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, choose another [**Validation method**](https://docs.coveo.com/en/malf0160#validation-method) for your source. > Select a method based on the way the web server responds when you manually try to access the page to index (when unauthenticated). > > * If no reliable validation method can be found, try enabling the form authentication [**Force authentication**](https://docs.coveo.com/en/malf0160#force-authentication) option. > >
#### Content freshness issue > **Context and symptoms** > > Items recently added to the site are still not appearing in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)). > > .Likely cause and resolution >
Details > > **Cause and Resolution** > > See [Indexed content is not up to date](#indexed-content-is-not-up-to-date). > >
### Extra or unwanted items #### Query parameters > **Context and symptoms** > > * The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) shows duplicate items. > > * Duplicate item URIs only differ in their query string parameter values. > > Example: > > ![Two items in the Content Browser with identical URIs except for query string parameter values](:https://docs.coveo.com/en/assets/images/index-content/two-items-with-different-query-string-param-values.png) > > .Likely cause and resolution >
Details > > **Cause** > > You're currently not specifying that the query string parameter should be ignored. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, open your source. > On the **Advanced settings** tab, add the parameter to the [**Query parameters to ignore**](https://docs.coveo.com/en/malf0160#query-parameters-to-ignore) list. > > Example: > > ![Adding a parameter to the Query parameters to ignore list](:https://docs.coveo.com/en/assets/images/index-content/adding-param-to-query-parameters-to-ignore.png) > >
#### Multiple URL variants > **Context and symptoms** > > * The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) shows duplicate items. > > * Duplicate item URIs only differ in their casing. > > * The `RespectUrlCasing` JSON parameter is set to `true`. > > .Likely cause and resolution >
Details > > **Cause** > > The Web source crawler discovers multiple variants of the same page, each with different URL casings. > > **Resolution** > > If the web server is case insensitive, make the Web source crawler ignore URL casing. > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click the source, and then click **Edit configuration with JSON** in the **More** menu. > Then, set [`RespectUrlCasing`](https://docs.coveo.com/en/mc1f0219#respecturlcasing-boolean) to `false`. > > [IMPORTANT] > >
> Don't set `RespectUrlCasing` to `false` if the web server is case sensitive. > If you do, items with uppercase characters in their URL won't be indexed. #### ===== #### Missing filtering > **Context and symptoms** > > The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) shows items you don't want to index. > > .Likely cause and resolution >
Details > > **Cause** > > Your current **Crawling rules** exclusions and inclusions don't filter out the unwanted items. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, open your source and configure [exclusions and inclusions](https://docs.coveo.com/en/malf0160#exclusions-and-inclusions) to filter out the unwanted items. > > To _be_ indexed, a page: > > * must not match any exclusion rule, AND > > * it must match at least one inclusion rule (for example, by selecting the **Include all non-excluded pages** option). > >
#### Content freshness issue > **Context and symptoms** > > Items recently deleted from the website are still appearing in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)). > > .Likely cause and resolution >
Details > > **Cause and Resolution** > > See [Indexed content is not up to date](#indexed-content-is-not-up-to-date). > >
### Unexpected or missing content inside items #### Indexing by reference > **Context and symptoms** > > * When viewing source items in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), item **Description** areas are empty. > > * If you then click a specific item, and then click **Properties**, the **Quick view** tab isn't displayed. > > ![Indexing by reference results details panel | Coveo](:https://docs.coveo.com/en/assets/images/index-content/indexing-by-reference-results.png) > > .Likely cause and resolution >
Details > > **Cause** > > You may be indexing by reference. > When indexing by reference, the body of the web page (used for the Quick view) isn't retrieved and no excerpt (used for the item description) is generated. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click the source, and then click **Edit configuration with JSON** in the **More** menu. > If HTML documents are currently indexed by `Reference`, change that value to `Retrieve`. > > ![JSON configuration indexing HTML by retrieve example | Coveo](:https://docs.coveo.com/en/assets/images/index-content/indexing-html-by-retrieve.png) > >
#### Broken images in the Quick view > **Context and symptoms** > > When [accessing the Quick view of an item](https://docs.coveo.com/en/1712#access-the-quick-view-tab), images are broken. > > ![Broken image in the Quick view](:https://docs.coveo.com/en/assets/images/index-content/quick-view-images-broken.png) > > .Likely cause and resolution >
Details > > **Cause** > > The connector retrieves web page HTML as is and doesn't retrieve the images referenced in the HTML. > The Content Browser [Quick view](https://docs.coveo.com/en/1712#quick-view-tab) displays this HTML without any alteration. > This means it doesn't replace relative paths, such as ``, with the corresponding absolute paths, such as ``. > As a result, when web pages contain images that are referenced using relative paths, the images can't be displayed in the Content Browser Quick view. > > Images that require authentication to be viewed also appear broken when browsing the web page item Quick view in the Content Browser. > > **Resolution** > > None. > This is a known limitation of the Content Browser Quick view. > > The Quick view is intended to provide a preview of the item content, not a full rendering of the web page. > To view the full web page, users can open the original document by clicking the item `clickable URI` link in the search results. > >
#### YouTube player not available in the Quickview component > **Context and symptoms** > > In the Quickview component of a Coveo JavaScript Search Framework search result, the YouTube player isn't available. > You notice the following symptoms: > > * The YouTube video [iframe](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe) shows the following error message: > > ``` Try watching this video on www.youtube.com, or enable JavaScript if it is disabled in your browser. ``` > > * In the browser console, the following message appears: > > ``` Blocked script execution in '' because the document's frame is sandboxed and the 'allow-scripts' permission is not set. ``` > > .Likely cause and resolution >
Details > > **Cause** > > For security reasons, the only way to view a YouTube video in the YouTube player within a Coveo JavaScript Search Framework result template is by: > > * Indexing items with the YouTube source. > > * Using the [CoveoYouTubeThumbnail component](https://coveo.github.io/search-ui/components/youtubethumbnail.html). > (Note: The [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)) Quick view doesn't meet this requirement.) > > **Resolution** > > . Index YouTube videos with the [YouTube source](https://docs.coveo.com/en/1637/). > > . In your Coveo JavaScript Search Framework search interface, use the [CoveoYouTubeThumbnail component](https://coveo.github.io/search-ui/components/youtubethumbnail.html) to show a relevant image of the result video content. > Clicking the thumbnail starts the video. > > The following is a sample implementation: > > ```html
``` > >
#### Copy protection on PDF > **Context and symptoms** > > When viewing a PDF item in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), you notice the following: > > * There's no description. > > * The Quick view shows the following: > > ![Copy protected PDF | Coveo](:https://docs.coveo.com/en/assets/images/index-content/copy-protected-pdf.png) > > .Likely cause and resolution >
Details > > **Cause** > > The PDF is password-protected. > > ![Document security on document in file system | Coveo](:https://docs.coveo.com/en/assets/images/index-content/document-security-on-pwd-protected-pdf.png) > > Therefore, the source can't retrieve the document binary content it needs to generate the description and the Quick view. > > **Resolution** > > . If acceptable, remove the password protection on the PDF in the file system. > > . [Rebuild](https://docs.coveo.com/en/3390#refresh-rescan-or-rebuild-sources) your source. > >
#### Web scraping issue > **Context and symptoms** > > * When [accessing the Quick view of an item](https://docs.coveo.com/en/1712#access-the-quick-view-tab), sections of the actual web page are missing. > > * You have one or multiple web scraping configurations configured on your source. > > .Likely cause and resolution >
Details > > **Cause** > > A web scraping configuration may be removing the missing sections. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, review your source's [web scraping configurations](https://docs.coveo.com/en/malf0160#web-scraping-subtab): > > * Check that web scraping configurations appear in an order that makes sense. > In [single-match mode](https://docs.coveo.com/en/mc1f3573#single-match-vs-multi-match), the first matching configuration is applied to the page, and the following are ignored. > > * In the [**Configuration info**](https://docs.coveo.com/en/mc1f3573#configuration-info) settings of the applied web scraping configuration, try changing or adding a rule to exclude your page. > > * In the [**Elements to exclude**](https://docs.coveo.com/en/mc1f3573#elements-to-exclude) tab of the applied web scraping configuration, try making your selector more restrictive to avoid removing sections from your page. > >
#### Web scraping exclusions not applied > **Context and symptoms** > > * The [Quick view of items](https://docs.coveo.com/en/1712#access-the-quick-view-tab) shows sections such as headers and footers that your web scraping configuration should exclude. > > * The [download logs](#important-troubleshooting-fundamentals) may show a NOTICE message in the following format: > > ```text NOTICE Did not crawl the links on page ''. Reason: 'The content type 'application/octet-stream' is not set up as parsable (check parameters: "ParsableContentTypes", "ParsableContentTypesSuffixes")'. ``` > > .Likely cause and resolution >
Details > > **Cause** > > The web server or CDN is returning pages with an unexpected `Content-Type` response header value or isn't including the `Content-Type` header at all. > > **Resolution** > > * Ensure that the `Content-Type` header is included when pages are served. > > * If the `Content-Type` response header value is `application/octet-stream`, configure your source to consider that content type as parsable. > > .. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **Edit configuration with JSON** in the **More** menu. > > .. In the **Parameters** tab, [add the following parameter](https://docs.coveo.com/en/mc1f0219#configuring-listed-and-unlisted-parameters): > > ```json "ParsableContentTypes": { "sensitive": false, "value": "[\"text/html\",\"application/xml\",\"application/xhtml+xml\",\"application/octet-stream\"]" } ``` > > .. Click **Save and rebuild source**. > >
#### Missing dynamic content > **Context and symptoms** > > * When [accessing the Quick view of an item](https://docs.coveo.com/en/1712#access-the-quick-view-tab), sections of the actual web page are missing. > > * Your web page contains dynamically rendered content (for example, responses to JavaScript API calls). > > .Likely cause and resolution >
Details > > **Cause** > > The source may be crawling your page before all its dynamic content is rendered. > > **Resolution** > > On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, open your source. > In the [**Advanced settings**](https://docs.coveo.com/en/malf0160#advanced-settings-subtab) subtab, make sure [**Execute JavaScript on pages**](https://docs.coveo.com/en/malf0160#execute-javascript-on-pages) is enabled. > Increase the **Time the crawler waits before considering a page as fully rendered** value, if necessary. > >
#### HTML pages indexed as txt items > **Context and symptoms** > > When accessing the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), pages are appearing under the `txt` file type, instead of `html`. > > .Likely cause and resolution >
Details > > **Cause** > > The web page, at the moment it's crawled, isn't valid HTML. > If the page includes dynamic content, it might not be fully rendered when the crawler processes it. > > **Resolution** > > . If the page includes dynamic content, make sure it's fully rendered when the crawler processes it. > > .. On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, open your source configuration. > > .. In the [**Advanced settings**](https://docs.coveo.com/en/malf0160#advanced-settings-subtab) subtab, make sure [Execute JavaScript on pages](https://docs.coveo.com/en/malf0160#execute-javascript-on-pages) is enabled. > > .. Set or increase the **Time the crawler waits before considering a page as fully rendered** value (for example, 300 milliseconds). > > .. Save and rebuild your source. > > . Fix the HTML of web pages still indexed as `txt`. > > .. Use an [HTML markup validator](https://validator.w3.org/) to identify the most significant issues with the page. > > .. Fix these markup issues. > > .. [Rebuild](https://docs.coveo.com/en/3390#refresh-rescan-or-rebuild-sources) your source. > >
#### Login page content instead of proper page content > **Context and symptoms** > > * When [accessing the Quick view of an item](https://docs.coveo.com/en/1712#access-the-quick-view-tab), you notice that a login page content appears instead of the content of the page specified by the URI. > This symptom will likely repeat itself over many items. > > * When trying to access the page to index manually in a browser, you're redirected to that login page. > > .Likely cause and resolution >
Details > > **Cause** > > The page to index is protected and form authentication isn't properly set up. > > **Resolution** > > . Request the login page authentication credentials from the web server administrator. > > . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, configure [form authentication](https://docs.coveo.com/en/malf0160#form-authentication) for your source. > Use the provided username and password and set the **Login page address** to the login page URL. > > . Set the [**Validation method**](https://docs.coveo.com/en/malf0160#validation-method) to `Redirection to URL` and the **Value** to the login page URL. > > . [Rebuild](https://docs.coveo.com/en/3390#refresh-rescan-or-rebuild-sources) your source. > > . Validate that the item now contains the [proper content](https://docs.coveo.com/en/1712#access-the-quick-view-tab). > >
#### Indexing pipeline extension > **Context and symptoms** > > * When [accessing the Quick view of an item](https://docs.coveo.com/en/1712#access-the-quick-view-tab), sections of the actual web page are missing. > > * The [**Extensions**](https://platform.cloud.coveo.com/admin/#/orgid/content/extensions/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/extensions/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/extensions/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/extensions/)) page shows you have one or several [indexing pipeline extensions (IPEs)](https://docs.coveo.com/en/206/) in your [Coveo organization](https://docs.coveo.com/en/185/). > > .Likely cause and resolution >
Details > > **Cause** > > An [indexing pipeline extension (IPE)](https://docs.coveo.com/en/206/) may be removing the missing sections. > > **Resolution** > > [Review the logs](https://docs.coveo.com/en/1645#inspect-impacted-item-logs) for the items affected by the extensions. > Make necessary adjustments to the extension script or [conditions](https://docs.coveo.com/en/64/). > >
### Unexpected item field values #### Inexistent field > **Context and symptoms** > > * When inspecting an item in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), the expected field name doesn't appear. > > * On the [**Fields**](https://platform.cloud.coveo.com/admin/#/orgid/content/fields/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/fields/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/fields/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/fields/)) page, the expected field doesn't appear. > > .Likely cause and resolution >
Details > > **Cause** > > The field doesn't exist. > You need to create the field and the field [mapping](https://docs.coveo.com/en/217/). > > **Resolution** > > . On the [**Fields**](https://platform.cloud.coveo.com/admin/#/orgid/content/fields/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/fields/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/fields/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/fields/)) page, at the upper right, click **Add field**. > > . Follow instructions in the [Add a field](https://docs.coveo.com/en/1833#add-a-field) article to configure your field. > > . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **More** > **View and map metadata**. > > . Choose the [metadata](https://docs.coveo.com/en/218/) you want to use to populate the field. > > . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **Mappings** in the Action bar. > > . Follow instructions in the [Manage mappings](https://docs.coveo.com/en/1640#manage-mappings) section to configure your mapping. > >
#### Field mapping issue > **Context and symptoms** > > * When inspecting items that should have values for the field in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), the expected field name doesn't appear in any item. > > * On the [**Fields**](https://platform.cloud.coveo.com/admin/#/orgid/content/fields/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/fields/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/fields/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/fields/)) page, the expected field appears. > > .Likely cause and resolution >
Details > > **Cause** > > There may be a field [mapping](https://docs.coveo.com/en/217/) issue. > > **Resolution** > > . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **More** > **View and map metadata**. > > . Make sure the metadata that should be used to populate your field appears. > If the metadata _is_ being used to populate a field, it will be shown as `Indexed`. > If you see two entries under the same metadata name, take note of the indexed and not indexed metadata `Origin` values for the final step in this procedure. > > . On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, click your source, and then click **Mappings** in the Action bar. > > . Make sure the mapping rule for the field references the right metadata name. > > . Add or edit the `Origin` value in the [field mapping rule](https://docs.coveo.com/en/1839/) (for example, `%[description:crawler]`). > >
#### Metadata extraction issue > **Context and symptoms** > > * When inspecting an item in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), the expected field name doesn't appear. > > * When inspecting other items from the source in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)), the field appears with values in some or all of them. > > .Likely cause and resolution >
Details > > **Cause** > > There may be a metadata extraction issue specifically for that item. > > **Resolution** > > Search for reasons why the metadata extraction process wouldn't be working on your specific item. > For example, if you're using a web scraping configuration, go to the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, and then validate the following in your source configuration: > > * Your item matches the [**Configuration info**](https://docs.coveo.com/en/mc1f3573#configuration-info) rules you set for that web scraping configuration. > Also remember that only the first matching web scraping configuration is applied to the page in [single-match mode](https://docs.coveo.com/en/mc1f3573#single-match-vs-multi-match). > > * Your [CSS or XPath selector](https://docs.coveo.com/en/mc1f3573#metadata-to-extract) works for that specific item. > >
#### Title field value selection > **Context and symptoms** > > The item `title` field value isn't ideal. > > .Likely cause and resolution >
Details > > **Cause** > > Coveo has a `title` field selection process to ensure all indexed items have titles. > This process may not return ideal titles in your use case. > > **Resolution** > > Coveo automatically extracts several pieces of metadata that you can use as item titles. > See [Item title selection](https://docs.coveo.com/en/1839#item-title-selection) mapping rule options to control the value selection process. > [Edit the `title` field mappings](https://docs.coveo.com/en/1640#manage-mappings) on your source. > >
#### Metadata origin selection > **Context and symptoms** > > * The indexed item has a value for the given field, but that value isn't the expected one. > > * On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, when you click the source and then click **More** > **View and map metadata**, you see two entries under the same metadata name. > > Example: > > ![metadata value conflict](:https://docs.coveo.com/en/assets/images/index-content/view-metadata-conflicts.png) > > .Likely cause and resolution >
Details > > **Cause** > > There's a metadata origin selection issue. > > For example, you've configured a web scraping configuration to extract a `description` metadata. > The Web source may also be [automatically extracting](https://docs.coveo.com/en/malf0160#source-key-characteristics) `description` metadata from the page `` tags. > > When values for the same metadata name are extracted in the [crawling stage](https://docs.coveo.com/en/2684#crawling) and in the [processing (or _converter_) stage](https://docs.coveo.com/en/2684#processing) of the [Coveo indexing pipeline](https://docs.coveo.com/en/184/), the latter value is used by default to populate the mapped field. > > Example: > > ![item field value](:https://docs.coveo.com/en/assets/images/index-content/metadata-conflict-field-value.png) > > **Resolution** > > * Use a unique metadata name and create a dedicated field for the custom metadata you're extracting, OR > > * Access the [**Edit mappings**](https://docs.coveo.com/en/1640#navigating-the-edit-mappings-panel) panel. > Specify the `origin` value in the [field mapping rule](https://docs.coveo.com/en/1839/) (for example, `%[description:crawler]`) to populate the field with the custom metadata you're extracting. > >
#### Overwritten crawler metadata > **Context and symptoms** > > * The indexed item has a value for the given field. > > * On the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, when you click the source and then click **More** > **View and map metadata**, you see an entry under the metadata name you chose under the `Crawler` origin. > > * You specified the `origin` value in the field mapping rule (for example, `%[description:crawler]`), but the field value isn't the expected one. > > .Likely cause and resolution >
Details > > **Cause** > > There's a metadata conflict. > > You can have two configurations extracting values for the same metadata name at the crawling stage. > When this happens, one value overwrites the other and you only see one `Crawler` origin entry for that metadata name on the **View and map metadata** subpage. > > **Resolution** > > Change the metadata name in your configuration to make it unique and adjust your [field mapping rule](https://docs.coveo.com/en/1839/) accordingly. > >
### Indexing is slow #### Source scope > **Context and symptoms** > > Indexing the source items is taking a long time. > > .Likely cause and resolution >
Details > > **Cause** > > The Web source may be crawling and indexing a very high number of items, and maybe even unwanted items. > This may be due to a number of reasons (for example, high number of starting URLs, too broad crawling rule [exclusions and inclusions](https://docs.coveo.com/en/malf0160#exclusions-and-inclusions)). > > **Resolution** > > * See [Extra or unwanted items](#extra-or-unwanted-items). > > * Consider breaking up the Web source into multiple sources. > This helps performance-wise and it simplifies source configurations and troubleshooting, OR > > * Consider using one or multiple [Sitemap sources](https://docs.coveo.com/en/1967/) instead. > >
#### Crawl delay > **Context and symptoms** > > Indexing the source items is taking a long time. > > .Likely cause and resolution >
Details > > **Cause** > > The **Time the crawler waits between requests to your server** may be unnecessarily high. > > **Resolution** > > [Provide proof of website ownership](https://docs.coveo.com/en/malf0160#proof-of-website-ownership). > Then, on the [**Sources**](https://platform.cloud.coveo.com/admin/#/orgid/content/sources/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/sources/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/sources/)) page, open your source. > On the **Advanced settings** tab, reduce the [**Time the crawler waits between requests to your server**](https://docs.coveo.com/en/malf0160#time-the-crawler-waits-between-requests-to-your-server) value. > >
#### ExpandBeforeFiltering setting > **Context and symptoms** > > Indexing the source items is taking a long time. > > .Likely cause and resolution >
Details > > **Cause** > > The source may be configured with `ExpandBeforeFiltering` set to `true`. > > **Resolution** > > Consider [editing the source JSON configuration](https://docs.coveo.com/en/1685#access-the-edit-configuration-with-json-panel) and setting [`ExpandBeforeFiltering`](https://docs.coveo.com/en/mc1f0219#expandbeforefiltering-boolean) to `false`. > >
### Indexed content is not up to date #### Source rescan schedule > **Context and symptoms** > > Recent changes to site items aren't reflected in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)). > > .Likely cause and resolution >
Details > > **Cause** > > * Your source [rescan schedule](https://docs.coveo.com/en/1933#schedule-a-source-update) may be disabled, OR > > * The time interval between consecutive rescans might be too long. > > **Resolution** > > Make sure the [rescan schedule](https://docs.coveo.com/en/1933#schedule-a-source-update) is enabled and that its recurrence settings are adequate. > >
#### Caching > **Context and symptoms** > > * Changes to existing items made prior to the last content update operation aren't reflected in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)). > > * The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) shows that schedule-triggered [rescan](https://docs.coveo.com/en/2711/) activities _are_ taking place. > > * The activity [download logs](#important-troubleshooting-fundamentals) may show a NOTICE message in the following format: > > ```text CDN/Caching Detection: Provider = 'Varnish', ... Please consult https://docs.coveo.com/en/1831/index-content/ip-addresses-to-allowlist to allowlist the IP addresses by the CDN/Caching provider if needed. ``` > > This message indicates that the source has detected that pages from the host are served by Varnish, which is a caching provider. > > .Likely cause and resolution >
Details > > **Cause** > > Your infrastructure may be serving a cached and outdated version of the web page. > These issues can occur if you use a caching provider such as Varnish, which is known to interfere with requests from the Coveo crawler. > > **Resolution** > > Ensure your infrastructure serves up-to-date web pages to the Coveo crawler. > For example: > > * Add middleware that detects the Coveo crawler and rewrites the request to the same URL with a fixed cache-busting query parameter (for example, `?__coveo=1`) so the crawler receives a fresh HTML variant of the page. > > * Configure your caching provider to [allow inbound requests](https://docs.coveo.com/en/1831/) from the [Coveo Platform](https://docs.coveo.com/en/186/). > >
#### Number of items limit reached > **Context and symptoms** > > * Recent updates to web pages and newly added pages aren't reflected in the [**Content Browser**](https://platform.cloud.coveo.com/admin/#/orgid/content/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/browser/)). > > * The [**Activity Browser**](https://platform.cloud.coveo.com/admin/#/orgid/activity/browser/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/activity/browser/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/activity/browser/)) shows schedule-triggered {rescan} activities are failing with a `DOCUMENT_LIMIT_EXCEEDED` error code. > > * On the [**System Performance**](https://platform.cloud.coveo.com/admin/#/orgid/organization/system-performance/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/organization/system-performance/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/organization/system-performance/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/organization/system-performance/)) page, the **Index size** section shows that your index contains more than twice as many items as your license allows. > > .Likely cause and resolution >
Details > > **Cause** > > Indexing is blocked because you've reached the 200% license item usage threshold. > > **Resolution** > > * If possible, delete unused sources to bring the item count below the 200% threshold. > Then, see the [July 20, 2023 Coveo Platform update](https://docs.coveo.com/en/o4hf8088#check-your-number-of-indexed-items) for suggestions on how to reduce your item count even more. > > * To reassess your needs and discuss your options, contact your Coveo Customer Success Manager. > >