If you are using the HtmlContentInBodyWithRequestsProcessor, this text is most likely indexed in the content of your page.

Since the September release (4.0.402), Coveo for Sitecore has two new parameters that you can set to ignore parts of your HTML content by adding the StartCommentText and EndCommentText nodes in your configuration:

<processor type="Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor, Coveo.SearchProviderBase">
    <StartCommentText>BEGIN NOINDEX</StartCommentText>
    <EndCommentText>END NOINDEX</EndCommentText> 
</processor>

You can then add the nodes like so in your HTML page:

<!-- BEGIN NOINDEX -->
<p>This section will not be indexed.</p>
<!-- END NOINDEX -->
<p>This section will be indexed.</p> 

For more information, refer to this page.

This processor is an implementation of the CleanHtmlContentInBodyProcessor coded by our Coveo for Sitecore guru @jflheureux. If you are using an earlier version, you can add this processor to your code and reference it in your configuration after the HtmlContentInBodyWithRequestsProcessor.

Another solution would be to add conditional rendering for this page section. Coveo for Sitecore uses the Coveo Sitecore Search Provider user agent. It could be detected and used to hide the sections you don't want to be indexed.

A third solution would be to define a special device and layout combination for that user agent, but it requires to duplicate the layouts and controls, and is quite harder to maintain than the other two solutions.

Hope this helps :)

If you are using the HtmlContentInBodyWithRequestsProcessor, this text is most likely indexed in the content of your page.

Since the September release (4.0.402), Coveo for Sitecore has two new parameters that you can set to ignore parts of your HTML content by adding the StartCommentText and EndCommentText nodes in your configuration:

<processor type="Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor, Coveo.SearchProviderBase">
    <StartCommentText>BEGIN NOINDEX</StartCommentText>
    <EndCommentText>END NOINDEX</EndCommentText> 
</processor>

You can then add the nodes like so in your HTML page:

<!-- BEGIN NOINDEX -->
<p>This section will not be indexed.</p>
<!-- END NOINDEX -->
<p>This section will be indexed.</p> 

For more information, refer to this page.

This processor is an implementation of the CleanHtmlContentInBodyProcessor coded by our Coveo for Sitecore guru @jflheureux. If you are using an earlier version, you can add this processor to your code and reference it in your configuration after the HtmlContentInBodyWithRequestsProcessor.

Another solution would be to add conditional rendering for this page section. Coveo for Sitecore uses the Coveo Sitecore Search Provider user agent. It could be detected and used to hide the sections you don't want to be indexed.

A third solution would be to define a special device and layout combination for that user agent, but it requires to duplicate the layouts and controls, and is quite harder to maintain than the other two solutions.

Hope this helps :)

If you are using the HtmlContentInBodyWithRequestsProcessor, this text is most likely indexed in the content of your page.

Since the September release (4.0.402), Coveo for Sitecore has two new parameters that you can set to ignore parts of your HTML content by adding the StartCommentText and EndCommentText nodes in your configuration:

<processor type="Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor, Coveo.SearchProviderBase">
    <StartCommentText>BEGIN NOINDEX</StartCommentText>
    <EndCommentText>END NOINDEX</EndCommentText> 
</processor>

You can then add the nodes like so in your HTML page:

<!-- BEGIN NOINDEX -->
<p>This section will not be indexed.</p>
<!-- END NOINDEX -->
<p>This section will be indexed.</p> 

For more information, refer to this page.

This processor is an implementation of the CleanHtmlContentInBodyProcessor coded by our Coveo for Sitecore guru @jflheureux. If you are using an earlier version, you can add this processor to your code and reference it in your configuration instead of the HtmlContentInBodyWithRequestsProcessor

Another solution would be to add conditional rendering for this page section. Coveo for Sitecore uses the Coveo Sitecore Search Provider user agent. It could be detected and used to hide the sections you don't want to be indexed.

A third solution would be to define a special device and layout combination for that user agent, but it requires to duplicate the layouts and controls, and is quite harder to maintain than the other two solutions.

Hope this helps :)

If you are using the HtmlContentInBodyWithRequestsProcessor, this text is most likely indexed in the content of your page.

Since the September release (4.0.402), Coveo for Sitecore has two new parameters that you can set to ignore parts of your HTML content by adding the StartCommentText and EndCommentText nodes in your configuration:

<processor type="Coveo.SearchProvider.Processors.HtmlContentInBodyWithRequestsProcessor, Coveo.SearchProviderBase">
    <StartCommentText>BEGIN NOINDEX</StartCommentText>
    <EndCommentText>END NOINDEX</EndCommentText> 
</processor>

You can then add the nodes like so in your HTML page:

<!-- BEGIN NOINDEX -->
<p>This section will not be indexed.</p>
<!-- END NOINDEX -->
<p>This section will be indexed.</p> 

For more information, refer to this page.

This processor is an implementation of the CleanHtmlContentInBodyProcessor coded by our Coveo for Sitecore guru @jflheureux. If you are using an earlier version, you can add this processor to your code and reference it in your configuration after the HtmlContentInBodyWithRequestsProcessor.

Another solution would be to add conditional rendering for this page section. Coveo for Sitecore uses the Coveo Sitecore Search Provider user agent. It could be detected and used to hide the sections you don't want to be indexed.

A third solution would be to define a special device and layout combination for that user agent, but it requires to duplicate the layouts and controls, and is quite harder to maintain than the other two solutions.

Hope this helps :)