Content Hub

SEO and social publishing metadata with Content Hub 1.x


Content Hub 1.x will reach end-of-life on September 30, 2024. Acquia recommends you to upgrade to Content Hub 3.x. For more information, see Upgrading from Content Hub 1.x to 3.x.

If your purpose for using Acquia Content Hub is syndicating blog or editorial content, you’ll want to use the Metatag module to maintain the Search Engine Optimization (SEO) of both original and syndicated content. Metatag can help preserve canonical URL data across platforms.

The Metatag module

If you use Acquia Content Hub to syndicate blog content, you’ll want the metadata on your syndicated content to indicate the original source (canonical URL) to preserve SEO. Installing the Metatag module on both the publishing and subscribing websites allows metadata from the publishing website to be transferred to the hub, and then to the subscribing websites.

You must set the canonical URL in the Metatag module. This will enable your syndicated content to keep its original source information.

Options exist to vary deployment and Metatag module settings on subscribing websites for more complex architectures.

Preventing evaluation of tokens

Acquia Content Hub provides the ability to denylist tokens when there are properties that you do not want submitted to the publishing hub.

As an administrator, complete the following steps:

  1. Navigate to Configuration > Acquia Content Hub Connector > Settings.
  2. In the Properties List field, enter the tokens you want to exclude. Each token must be on a separate line.
  3. Click Save configuration when finished.

Social metadata with Acquia Content Hub and the Metatag module

Users interested in good social metadata can use the Metatag module to create more efficient workflows. Using the module allows the publishing website to invest additional effort in social media display by editing Open Graph and Twitter Cards metadata in the publishing website, which adds value to syndicating websites.

Subscribing websites and the Metatag module

Options exist to vary deployment and Metatag module settings on subscribing websites for more complex architectures through token overrides.