Personalization, SEO, speed, and website questions

You can personalize an existing page without replacing your website builder or forms. These answers cover what changes, what stays on your website, and what to check before going live.

Do I need to rebuild my website?

No. Campaigns change existing page elements through the installed RightMessage snippet. You keep your builder, hosting, and usual website publishing process.

You'll need control over snippet installation and the content you want to target. Start with Change copy, images, links, and page sections.

Can I keep my existing forms?

Yes. You can personalize a headline or surrounding copy without replacing the form. Avoid replacing a whole container with interactive form markup unless you also test validation and submission.

To recognize contacts from form submissions, check your visitor identification, consent, and email-platform syncing setup. Keeping the form doesn't set those up automatically.

Can RightMessage create new page sections?

No. Build the section in your website first, then use the campaign editor to change its content or visibility. The editor targets existing elements rather than building page layouts. RightMessage can also build a whole landing page for you to host with us instead, on any plan; see hosted pages.

Can I show a different testimonial to each audience?

Yes. Create the testimonial blocks on your website, then change their copy or visibility for each audience. Keep a useful default and test visitors who match more than one audience.

Use approved quotations that apply to the audience. Don't invent customer quotes for personalized content.

Can UTM information change my landing-page headline?

Yes. In the campaign editor, choose Add audiences, then Visitors from a link, and enter the parameter and value your ad's link carries, such as utm_campaign is spring_sale. RightMessage creates the segment for you. You can also add a UTM or query condition to a segment yourself, then target that segment in a campaign audience. RightMessage uses the value you specify. It doesn't infer a visitor's demographics from it.

See add an audience from a link, UTM conditions, and match a landing page to an ad click.

Do I need a different URL for every audience?

No. Different audiences can see different content at the same URL. Their matching rules determine which changes apply.

You may still want a separate URL for a permanent page in search or your navigation.

Does RightMessage remember someone when they visit another page?

It depends on the condition you're using. Current-page query conditions need the parameter on the current URL. Other query lookups can use its latest stored occurrence. Saved answers and identified contact data have their own behavior.

Check the condition reference for the data you use. Don't assume every value lasts forever or that any cross-domain link carries a visitor's identity.

Will search engines always see the default content?

No, that isn't guaranteed. Your website owns the original source content. What a crawler sees after that depends on its JavaScript support, available visitor context, and rendering.

Keep your source page useful and inspect representative rendered pages in your search tools. Don't make audience-only copy your sole indexable explanation. Personalization doesn't guarantee better search rankings.

Do I still need separate search landing pages?

Yes, when a search intent needs its own lasting URL and complete, relevant content. Personalization adapts an existing page to known visitor context. It doesn't create a separate indexable page for every audience.

How much does RightMessage affect page speed?

The effect depends on your page, device, network, targeting, and integrations. The snippet loads asynchronously, but requests, rule checks, and page updates still take time. There isn't a fixed loading time or a promise of zero impact.

Measure your actual page before and after changing your setup. If a headline flickers, use temporary cloaking on that element rather than hiding the whole page.

Can blockers or security tools prevent personalization?

Yes. Browser extensions, consent controls, content-security policies, and network failures can block scripts or requests. Inspect the browser where the problem happens, even if your own browser works.

If only the campaign editor shows a challenge or a copy of your page, follow editor loading diagnostics. Don't bypass form security based on a public project identifier.

What do I need to check after a website redesign?

Check the snippet, domain and page rules, CSS selectors, and Smart Match targets. Reinstall the snippet if needed. A class change can break a selector even when the URL stays the same.

Retest personalization after a redesign walks you through it. You can use campaigns on stable pages now, but recheck pages that are about to be rebuilt before relying on them.

Why does a matching UTM visitor still see the original page?

The campaign may be unpublished, disabled, assigned to holdback, or unable to find the element it should change. If the audience or the Original page is in an A/B test, the visitor may be seeing Control or another version, and with Wait for consent before tracking on, tests show Control until they accept cookies. Other audience conditions and later overlapping changes can also affect what appears.

Use personalization troubleshooting to inspect that browser. Check the visitor's actual holdback assignment rather than assuming the campaign's percentage explains this visit.