Is Yext a native CMS Max integration?

No native Yext connector was found in the current CMS Max repository. Entities, listings, reviews, APIs, webhooks, and content delivery require a scoped implementation with explicit source-of-truth decisions.

What does CMS Max manage in this workflow?

CMS Max manages the public website, search-facing content, navigation, page experience, forms or commerce journeys used in scope, and the governed connection point. Yext remains responsible for yext entities, publishers, listings, reviews, search, analytics, apis, webhooks, and provider account operations.

What should we prepare before connecting Yext?

Prepare the provider account, administrator and technical contacts, target audiences, locations, business facts, entities, listings, reviews, publishers, and local performance records, required fields, consent requirements, existing tags or embeds, test records, analytics plan, support path, and success measures.

Does this automatically synchronize locations, business facts, entities, listings, reviews, publishers, and local performance records?

No. Locations, listings, reviews, publishers, and analytics are not synchronized automatically. A custom project must define each field owner, direction, identifier, version, conflict rule, and reconciliation process.

How should privacy and consent be handled?

Document the data sent to Yext, its purpose, lawful basis, customer notices, consent state, retention, deletion, access, suppression, and regional requirements. Legal approval remains the site owner's responsibility.

What must pass before launch?

Test valid and invalid journeys, duplicate actions, missing fields, mobile and keyboard use, consent states, provider errors, analytics, authoritative records, support, monitoring, and rollback with representative production-like data.