When and Why Site Splits?

When it comes to split sites, the goal is to keep things simple and purposeful. A split site is used when a group needs access to multiple versions of their benefits site, whether by benefit year, language, or location/subgroup.

When to Use a Split Site

By Benefit Year

This is the most common split site and is typically created right before open enrollment. It is only needed if the group has a change in benefits, carriers, or plans such as adding or removing options. It allows employees to view their current benefits (prior to the effective date) alongside the upcoming benefits (effective on the new date). Once open enrollment ends, the split site should be removed. Please notify the website team when it is time to remove the split.

By Language

While accessibility features (only available for WordPress Large Groups) have reduced the need for language based splits for new groups, there are still current groups with this kind of split. No new clients or current websites that do not already have a language split, will be getting this type of split due to the accessibility feature that auto-translates if needed. Keep in mind that documents can always be requested in other languages to carriers and posted on the website, even without a language split or translations. Large groups are the only ones that qualify for an Accessibility Plug In. Ask Stephen Guy if that is an option.

By Location or Subgroup

This is the least common split and is used when benefits differ substantially between locations or subgroups. If differences are minimal, such as only the medical carrier varying, a split may not be necessary and the differences can often be handled on individual pages. However, if there are multiple carrier and plan differences across benefits, a location based split helps avoid confusion.

Key Guidelines for Split Sites

  1. Purposeful Timing – Splits are most useful during major changes such as group renewals or open enrollment.
  2. Post Open Enrollment – Remove the split once open enrollment is complete and benefits changes are finalized.
  3. Benefit Driven Decision – Only create a split when there are meaningful differences in offered benefits to avoid unnecessary complexity.

By using split sites strategically and only when necessary, you maintain a clean and efficient user experience while ensuring employees have the right information at the right time.