Native CMS Max trust content

Customer Reviews Built Into CMS Max

Collect first-party testimonials, review every submission, and publish approved trust content without a third-party widget.

The CMS Max Reviews feature uses the native Testimonials package to create a public submission workflow, notify administrators, hold content for review, and place approved testimonials across the website with list or compact layouts and supported structured data.

  • Native submissions
  • Approval workflow
  • Admin notifications
  • Flexible display
  • Review schema
CMS Max Reviewswith CMS Max
Customer journey
CMS Max Testimonials and Reviews feature artwork
Reviews are stored and managed in CMS Max, so the website team controls the submission, moderation, display, and retention workflow.
01Collect
02Review + approve
03Publish + measure

Conversion architecture

A connection earns its place when customers and operators can trust it.

Define the business outcome, data boundary, customer expectation, operating owner, failure path, and measurement plan before installing the technology.

Make the request clear

Explain how submitted names, ratings, location details, testimonial copy, and dates may be reviewed, edited, displayed, retained, or removed.

Moderate consistently

Use a written policy for relevance, authenticity, privacy, prohibited content, corrections, approval, hiding, archiving, and disputes.

Use reviews as evidence

Place approved testimonials near the relevant offer and support them with concrete product, service, policy, and customer-experience information.

Current CMS Max capabilities

What the implemented workflow supports.

Availability depends on the plugin or approved embed being active, required provider accounts, current provider features, accurate configuration, consent, source data, plan limits, and tenant setup.

01 / Collection

Public testimonial form

Add the native submission form to a page or modal, customize its button and success behavior, and keep the visitor in the CMS Max website experience.

02 / Moderation

Pending review before publication

Submitted testimonials can remain unapproved until an administrator reviews the name, content, rating, location, and publication decision.

03 / Notifications

Alert designated administrators

Configure one or more administrator email recipients so the team knows when a new testimonial is waiting for review.

04 / Display

List and compact layouts

Place approved testimonials through the CMS Max widget and shortcode system, choose list or compact presentation, and control sort, limit, pagination, and minimum rating.

05 / Details

Configurable date and location output

Choose whether public testimonial views show the submission date, reviewer city, and reviewer state while supported rating output remains part of the review record.

06 / SEO

Supported review structured data

CMS Max can build Review and rating data for approved testimonial collections within the configured business-schema context. Search engines still control eligibility and presentation.

Customer-to-operation flow

Make the handoffs visible from intent to outcome.

Every stage needs clear inputs, an observable result, an exception path, and a named owner.

01

Request

Invite an authentic customer to share feedback.

02

Submit

Capture the testimonial in the native form.

03

Review

Check relevance, privacy, accuracy, and policy.

04

Publish

Approve and place it in the right context.

05

Maintain

Correct, hide, archive, and refresh as needed.

Implementation sequence

Move from account access to production confidence.

Use representative content, users, devices, permissions, failures, and provider states before relying on the workflow.

01. Write the review policy

Define eligibility, disclosure, incentives, privacy, approval criteria, prohibited content, editing, response, correction, removal, and retention.

02. Install and configure Reviews

Activate the Testimonials plugin, set administrator notification recipients, and review date, city, and state display settings.

03. Place the submission experience

Add the testimonial form to a page or modal, choose button text, success message or redirect, and link the privacy and review policy.

04. Design publication views

Choose list or compact presentation, sorting, pagination, limits, minimum rating, surrounding context, and accessibility.

05. Test moderation end to end

Submit realistic ratings, long text, location values, duplicates, private information, unacceptable content, and mobile inputs; verify notifications and approval.

06. Govern the library

Review pending items, document edits, respond to disputes, archive stale or invalid content, verify schema, and keep testimonials aligned with current offers.

Operational ownership

Know which system and team controls each outcome.

Clear ownership makes privacy, security, support, changes, billing, measurement, and incident recovery faster.

CMS Max
Stores testimonial records and provides the submission, administration, moderation state, display components, notifications, and supported schema generation.
Website team
Owns placement, surrounding claims, design, accessibility, links, conversion measurement, and keeping testimonials relevant to current offers.
Merchant
Owns review policy, authenticity standards, incentives, privacy, approval, edits, disputes, retention, legal compliance, and customer communication.
Search engines
Independently decide whether structured data is eligible, trusted, indexed, or shown. Valid markup does not guarantee review stars or any rich result.

Documentation and related resources

Confirm the current provider requirements.

Provider interfaces, plans, policies, APIs, scripts, and supported features can change. Use official documentation and the live account during implementation.

Integration FAQ

Resolve the practical questions before launch.

Turn each answer into configured rules, representative tests, monitoring, and written ownership.

Are CMS Max Reviews stored in a third-party widget?

No. The Reviews feature uses the native CMS Max Testimonials package for submission, records, approval state, display, notifications, and supported schema output.

Can reviews be held before they appear publicly?

Yes. The workflow supports pending and approved states so administrators can review a submission before it is included in public testimonial lists.

How can approved reviews be displayed?

Use the CMS Max testimonial list widget or shortcode with list or compact layouts and controls for sorting, limit, pagination, and minimum rating.

Can administrators receive a new-review email?

Yes. Configure one or more administrator email recipients. A dashboard notification also warns when the plugin is active but notification recipients are missing.

Which reviewer details can be shown?

The current plugin settings include controls for showing the date, city, and state. Testimonial records also support name, review content, rating, and location data used by the display and schema workflows.

Do approved reviews guarantee stars in Google?

No. CMS Max can emit supported structured data, but search-engine guidelines, content, business context, trust signals, technical quality, and independent eligibility systems control rich-result presentation.

Connect with purpose

Build a customer workflow the business can operate after launch.

Bring the use case, account, data, consent requirements, owners, content, test plan, failure handling, and success measures. CMS Max will help map the supported path.

Building Relationships with Web Developers and Marketing Agencies that want better results

The world's fastest and most SEO friendly website code.