CMS

Manage Large Multi-Site Experiences Without Repeating the Same Work

What’s New

Managing the same content across dozens of brand, property, dealer or location websites creates more than operational overhead. It can result in inconsistent information across an organization's digital presence, particularly when updates must be repeated manually across every site.

CMS now allows centrally governed pages to be created and managed from a parent site and distributed across selected child sites in a single workflow. Teams can determine whether pages should arrive as drafts for local review or be published directly. Centrally controlled components remain governed from the parent, while child sites can retain their own local content and flexibility.

Why It Matters

As search moves from retrieving individual pages toward AI systems synthesizing information into answers and recommendations, consistency across the digital estate becomes increasingly important.

Centralized governance helps enterprises maintain a clearer, more authoritative information layer across their websites while reducing repetitive publishing work. One publish can replace a separate page build for every child site, with the operational saving increasing as the number of sites grows.

This helps brands preserve corporate standards and compliance while still allowing the local relevance that search engines and AI experiences need to answer location-specific questions accurately.

Make Multilingual Content Updates Faster and Easier to Trust

What’s New

Keeping translated websites current can become increasingly difficult as the number of languages, pages and content changes grows.

CMS now provides faster AI translation synchronization together with progress tracking, giving teams greater visibility into what is being translated and when processing is complete. The release is intended to reduce translation turnaround time and make synchronization easier to monitor.

The sprint demonstration showed translation synchronization that previously took several minutes completing in seconds in some scenarios, while users can now monitor progress and retry when processing is interrupted.

Why It Matters

AI search is global as well as conversational. Brands need their information to remain accurate and current across languages, not simply on their primary-language site.

Reducing the operational cost of keeping localized experiences synchronized helps organizations maintain stronger information consistency across markets. It also reduces the risk that search engines or AI systems encounter outdated information in one language while receiving newer information in another.

Reduce Mistakes When Managing Large Sets of Content Records

What’s New

Selecting and reordering large numbers of content records could previously become difficult to follow, particularly when editors were working across long lists.

CMS now makes selected records easier to identify and provides clearer guidance when reordering could affect content across multiple pages. This addresses a usability issue identified through customer feedback.

Why It Matters

AI search readiness ultimately depends on the quality of the underlying content being published.

Giving teams clearer control over high-volume content operations reduces unintended changes and makes it easier to maintain the accuracy and consistency of the information that search engines and AI systems consume.

The improvement is small at the interaction level, but meaningful at scale because it reduces friction in the workflows responsible for maintaining the brand's digital knowledge layer.

Schema Manager

See Website Schema Health Without Hunting for Problems Page by Page

What’s New

As schema implementations grow, teams need more than confirmation that markup exists. They need to quickly understand how much of the website is covered, where issues exist, and where action is required.

Schema Manager now provides a more consolidated health view showing URL utilization, schema implementation coverage, indexing status, coverage gaps, errors, and opportunities where schema has not yet been implemented.

Errors and recommended actions are surfaced more directly, with users able to move from the dashboard into the relevant tagging workflow and supporting guidance.

Why It Matters

A schema program becomes difficult to manage when teams have to inspect individual pages simply to understand its overall health.

Bringing coverage, indexing, errors, and opportunities together makes problems easier to identify and shortens the path from detection to action. This gives teams a clearer understanding of whether structured data is actually being deployed effectively across the website.

Local

Make AI Presence More Explainable at the Local Level

What’s New

Local AI Presence previously provided an overall visibility score without showing customers the prompts contributing to that result.

The dashboard now exposes the prompt list being tracked, allowing users to understand which questions contribute to their AI presence and where visibility is stronger or weaker. The capability is currently in beta.

Why It Matters

AI visibility scores have limited value if brands cannot understand the questions behind them.

Prompt-level transparency moves local AI measurement closer to actionable intelligence. It helps businesses understand not just whether their locations appear in AI answers, but the types of customer needs and questions for which those locations are being discovered.

That creates the foundation for connecting AI presence back to content, local information and future optimization recommendations.