I build on Optimizely. And I switch the testing on.
Cypher builds, migrates and optimizes websites on Optimizely. It plans content types and reusable blocks your editors control, sets up audience-based personalization and A/B tests in the platform, checks each one before a visitor sees it, and verifies every page for content parity, visual parity and accessibility before you sign off.
What I do on Optimizely
Optimizely brings content management and experimentation together, which is exactly why so many teams only use half of it. I build the site and switch on the other half: the audiences, the variants and the tests you bought it for.
- New sites and redesigns, built from reusable blocks
- Migrations onto Optimizely from another platform
- Personalization by audience, set up and verified
- A/B/n tests configured with one goal each
- Speed, accessibility and SEO work, with the evidence
Blocks your editors can reuse
Pages are built from blocks with the fields and options your team needs, so a marketer can put together a campaign page without a developer. Every block is written up in a component catalog, with where it’s used.
Where Optimizely projects usually go wrong
- Blocks copied instead of reused. Ten versions of the same promo block means ten places to fix; one block with settings is easier for everyone.
- Audiences nobody defined. Personalization needs agreed audiences first: who they are, how the site recognizes them, and what each should see.
- Tests without a goal. Every test needs one primary metric decided before it starts, or nobody can call the result.
- Flicker on page-level tests. Tests that change the page in the browser can flash the original first, so how each variant loads gets checked.
- Content structure carried over as is. A migration is the moment to fix content types that grew by accident.
What I check before you sign off
- Content parity of 98% or better against the pages being replaced
- Visual parity at three breakpoints
- Accessibility and performance on every representative page
- Every old URL redirected to its new home, and tested
- Each test’s goal, audience and traffic split, verified before it starts
What you own at the end
Your code in your repository, your Optimizely setup documented, audiences and tests your team can run, an editor guide, a component catalog, the evidence for every page, and a known-gaps report.
Go deeper on Optimizely
Questions people ask
Can you set up our A/B tests in Optimizely?
Yes. Tests are configured in the platform with one goal each, checked before they start, and handed over with a note on how to read the results.
Do you build personalization for different audiences?
Yes. Audiences are agreed first, then the variants are built and each one is verified before a visitor sees it. Who sees what is one of the few decisions that’s yours.
Can you migrate us onto Optimizely?
That’s the migration playbook: every page inventoried, content moved and checked for parity, every old URL redirected, and visual parity checked at three breakpoints.