Customizing and redirecting article URLs

Emovart builds article URLs from your Notion page titles (see Achieving pretty URL links for your site). Redirect links add a layer on top of that: any number of alternative paths that permanently redirect to an article's canonical URL. Use them for marketing-friendly short links, or to catch traffic still pointing at an old address.

How to add a redirect link

1. Open Settings → Help Centers, select your site, and go to the Links section.
2. Find the article you want and click Add redirect.
3. Enter the alias path — anything you like, such as /refunds, or an old platform path like /en/articles/4182-refund-policy.
4. Save. Requests to the alias now answer with a permanent (301) redirect to the article's canonical URL.

How do I copy my new redirect link?

Hover over any alias in the list and click the copy icon — you get the full URL, including your custom domain, on the clipboard and ready to paste into chats, emails, or your app.

Migrating from another knowledge base (Intercom, Zendesk, etc.)

Redirect links really shine when you move an existing help center onto Emovart without losing search rankings or breaking the thousands of links already out in the wild.

The migration challenge

Your old platform's URLs follow a structure Emovart doesn't naturally produce — Intercom uses /en/articles/12345-article-title, Zendesk uses /hc/en-us/articles/12345-Article-Title, and so on. Those addresses are indexed by Google and embedded in emails, chat macros, and your app. If they start returning 404s after the switch, you lose all of that equity.

Step-by-step migration process

Here's the four-step playbook we recommend:

1. Prepare your custom domain (don't switch yet!)

Build your Emovart site completely while the old help center is still live: import content into Notion, connect it, and test everything on the default your-slug.emovart.studio address. Add your custom domain in the console, but leave your DNS pointing at the old platform until the redirects are in place.

2. Map your old URLs to new articles

Export the list of your old article URLs — most platforms provide a sitemap or CSV export. For each one, the path is the alias you'll create. Take an old Intercom-style link:

https://help.example.com/en/articles/4182-how-to-request-a-refund

The same article's new canonical URL on Emovart:

https://help.example.com/billing/how-to-request-a-refund

The alias to add to that article in the console is simply the old path:

/en/articles/4182-how-to-request-a-refund

For larger help centers, keep the mapping in a plain list and work through it methodically:

/en/articles/4182-how-to-request-a-refund  ->  /billing/how-to-request-a-refund
/en/articles/4190-changing-your-plan       ->  /billing/changing-your-plan
/en/articles/4201-inviting-teammates      ->  /account/inviting-teammates

3. Complete the domain switch

Once every old path has an alias, point your DNS at Emovart by changing the CNAME as described in Connecting a custom domain. From that moment, old links hit your Emovart site and are 301-redirected to the matching new articles.

4. Verify the migration

Spot-check a sample of old URLs from different sections of the old help center — each should land on the right article after a single permanent redirect. Then keep an eye on Google Search Console over the following weeks: indexed pages should transfer to the new URLs without a traffic dip.

Pro tips

• 301 redirects pass SEO value, so your rankings follow the content to its new home.
• Map your top 20 articles first — analytics will show they carry the overwhelming share of traffic.
• Keep the old platform's export around for a few months in case a missed URL surfaces.

Common migration scenarios

• Intercom: paths look like /en/articles/<id>-<slug> — add one alias per article.
• Zendesk: paths look like /hc/<locale>/articles/<id>-<slug> — remember every locale you actually published.
• Restructuring within Emovart: staying on the platform but reorganizing collections? Add aliases for the old paths before you rename anything.