We’ve migrated our documentation to a new site, which means some URLs have changed.
Audience

How Do I Exclude Pages and Articles from Piano Content Recommendations?

Exclude a Page from All Modules via Meta Tag (Recommended)

Add the following meta tag in the page's <head>:

<meta name="cXenseParse:recs:recommendable" content="false"/>

What It Does

Marks the page as not recommendable, preventing it from appearing in recommendation results across all modules after the page is recrawled.

Important: You Must Recrawl the Page

The tag is applied when Piano re-parses the page. If the page was previously crawled as recommendable, it may continue to appear until a refetch updates its content profile.

Recrawl via the Insight UI (Schedule Refetch)

  1. Go to InsightContentPage statistics.

  2. Enter the page URL and open its details.

  3. Go to Page Administration.

  4. Select Schedule refetch.

If you have many URLs, you can also provide a list (or a path/wildcard, when applicable) to Piano Support to assist with a bulk refetch.

Exclude a Page from a Specific Module via Collection Query

If you only need to exclude a page from one module (not globally), use an advanced collection query filter.

In the module editor:

  1. Select a ModuleEdit Module

  2. Select Collection

  3. Open Advanced settingsCollection Query

  4. Add an exclusion filter using one of the following formats:

Exclude by URL:

not query(url:"<article_url>")

Exclude by article ID:

not query(articleid:"<article_id>")

This method is module-specific. The same page can still appear in other modules unless you exclude it there too. Use page-level meta tags when you need consistent exclusion across all widgets.

Unpublished or Removed Content

If content has been unpublished or should be fully removed from the recommendation system, delete its content profile using the /document/delete API endpoint. This helps ensure retired URLs don't continue to surface in recommendations.

Excluding Section Fronts and Non-Article Pages

For section front pages (and similar hub pages), configure the page class as frontpage so they are not treated as recommendable content.

Troubleshooting: The Page Still Appears in Recommendations

Check the following:

  • Was the page recrawled after adding the meta tag? The tag will not take effect until the next refetch/recrawl.

  • Is the meta tag syntactically correct and in the <head>? Confirm the rendered HTML includes:

    <meta name="cXenseParse:recs:recommendable" content="false"/>

  • Are you excluding at the right level? If you used a collection query, it only affects that one module.

  • Is the page accessible to the crawler? If the crawler can't retrieve the page content, it may not process updated markup.

If problems persist, gather the affected URL(s), the module(s) where it appears, and a screenshot of the recommendation placement for further investigation.

Last updated: