Skip to main content
Sign in

Map custom meta tags to searchable fields in Fusion

  • Updated

Goal

Enable search functionality using values from a custom HTML meta tag while excluding the tag from the visible page source for SEO or compliance purposes.

 

Environment

Fusion 5
 

Guide

Replace the keywords meta tag with a custom name

In the page source HTML, replace the existing <meta name="keywords" ...> tag with a custom tag name. For example:

<!-- Before -->
<meta name="keywords" content="keyword1, keyword2, keyword3">

<!-- After -->
<meta name="abcxyz" content="keyword1, keyword2, keyword3">

This ensures the sensitive or deprecated tag name does not appear in the public page source, while still allowing Fusion to ingest the data.

 

Update the "Map To Page Model" stage in the index pipeline

  1. Navigate to Index Pipelines in the Fusion UI.

  2. Open the pipeline that processes the content containing your new meta tag. 

  3. Locate the Map To Page Model stage.

  4. Update the field mapping to refer to the new tag name. For example:

{
  "input": "abcxyz",
  "output": "keywords"
}

This maps the value of the custom abcxyz meta tag to the keywords field in Fusion’s data model.

  1. Save the pipeline configuration and reindex the affected documents.

 

Validate the result

  • Use Fusion's Index Workbench or Solr query to verify that the values from the renamed meta tag are correctly indexed under the keywords field.

  • Confirm that the keywords field is searchable and behaves as expected during queries.

 

Optional: Confirm SEO impact

Although Fusion indexing is unaffected by the change, confirm with your SEO team whether replacing the keywords meta tag satisfies their compliance requirements. Modern search engines generally do not rely on the keywords tag for ranking, but internal policies may differ.

Powered by Zendesk