Home | Connectors | OpenText Content Metadata Service | OpenText Content Metadata Service - Wix Integration and Automation
Flow: OpenText Content Metadata Service ? Wix
Use OpenText Content Metadata Service as the system of record for standardized content metadata such as content type, region, product line, campaign, and approval status. Wix can consume this metadata to automatically organize and publish website pages, landing pages, and content blocks with consistent tagging and structure. This reduces manual site administration and ensures web content aligns with enterprise governance standards.
Business value: Faster publishing, better content consistency, and improved search and content governance across digital properties.
Flow: Wix ? OpenText Content Metadata Service
When marketing teams upload website assets in Wix, such as images, PDFs, or downloadable brochures, the asset metadata can be sent to OpenText Content Metadata Service for classification and standardization. This helps enforce enterprise metadata rules, making assets easier to search, reuse, and audit across the broader content ecosystem.
Business value: Better asset discoverability, reduced duplication, and stronger compliance with metadata standards.
Flow: Bi-directional
Marketing teams can create campaign landing pages in Wix while OpenText Content Metadata Service maintains the authoritative metadata for campaign name, owner, launch date, region, and approval state. Wix can display only approved content based on metadata status, while updates made in Wix can be reflected back into OpenText for governance and reporting. This supports controlled campaign launches across multiple business units.
Business value: Improved approval control, reduced launch risk, and clearer accountability for campaign assets.
Flow: OpenText Content Metadata Service ? Wix
For organizations using Wix to present product information, OpenText Content Metadata Service can provide standardized metadata for product descriptions, categories, specifications, and regional variants. Wix can use this metadata to keep product pages aligned with enterprise content models, ensuring that updates made centrally are reflected on the website without manual re-entry.
Business value: Consistent product messaging, fewer content errors, and lower maintenance effort for web teams.
Flow: OpenText Content Metadata Service ? Wix
OpenText Content Metadata Service can supply metadata such as audience segment, geography, language, or business unit to support personalized website experiences in Wix. Wix can use this metadata to determine which content variants, banners, or calls to action should be displayed for specific visitor groups or site sections. This is especially useful for global organizations managing multiple local market sites.
Business value: More relevant user experiences, improved conversion rates, and easier management of multi-region content.
Flow: OpenText Content Metadata Service ? Wix
By pushing standardized metadata into Wix, organizations can improve internal site search, page categorization, and content filtering. Metadata such as topic, industry, service line, and publication date can be used to structure website navigation and search results, helping visitors find relevant information faster.
Business value: Better site usability, improved content findability, and stronger customer self-service.
Flow: Bi-directional
OpenText Content Metadata Service can manage lifecycle metadata such as draft, review, approved, expired, and archived, while Wix handles the live presentation layer. When content reaches an expiration date or is marked obsolete in OpenText, Wix can automatically remove or replace the corresponding page or asset. This is useful for regulated industries or fast-changing marketing content.
Business value: Reduced risk of outdated content, improved compliance, and less manual cleanup.
Flow: OpenText Content Metadata Service ? Wix
Content teams can define reusable metadata models in OpenText and expose approved content for use in Wix website builds. This allows web, marketing, and communications teams to reuse the same content definitions across repositories instead of creating separate versions for each channel. It supports a more scalable content operations model across the enterprise.
Business value: Higher content reuse, faster site updates, and more consistent messaging across channels.