Redirect Implementation

A redirect tells the browser to send anyone who visits a specific page to a different URL automatically. This is useful when you retire a page, rename a campaign URL, or want to point traffic from one slug to another without breaking existing links.

You can set one up entirely through the AI chat.

Use a redirect when:

• •You rename or delete a page and want old links to still work
• •A campaign URL has ended and you want to route visitors to your main site or a new campaign
• •You want to consolidate two pages and funnel all traffic to one destination
• •You have an external URL (e.g. a Calendly link) that you want to serve from a short, branded slug

Before asking Flint to set up the redirect, have two things ready:

1. 1.Source path - The Flint page slug that visitors will land on (e.g. /old-campaign). This is the URL you want to redirect *away from*.
2. 2.Destination URL - Where visitors should end up (e.g. /new-campaign or a full URL like https://example.com/landing).

If you are redirecting away from a page that still exists in your project, the redirect will take precedence over the page content — visitors will never see the page itself.

Open the AI chat and describe what you want. You do not need to know any configuration syntax.

Example prompt:

"Add a redirect so that anyone who visits /old-campaign is automatically sent to /new-campaign."

Flint will update the project's routing configuration to add the redirect rule. The change takes effect on your next publish.

Redirects only take effect on your live site after publishing. Click the Publish button in the top right corner of the editor to push the change live.

After publishing, open the source URL in a browser (or an incognito window to avoid cache) to confirm it redirects to the correct destination.

Flint supports two types of URL forwarding:

• •Redirect - The browser is sent to a new URL. The address bar changes. The visitor sees the destination page. Use this for permanent or temporary moves.
• •Rewrite - The content of the destination URL is served at the source path. The address bar stays the same. The visitor does not know they are seeing content from a different URL.

For most use cases — retiring a page, renaming a campaign, or forwarding a branded slug — a redirect is the right choice. If you want to serve content from one URL while keeping a different URL in the address bar, ask for a rewrite instead.

To remove a redirect, open the AI chat and ask Flint to remove it:

"Remove the redirect from /old-campaign."

Flint will delete the rule from the routing configuration. Publish again to make the change live.

If the underlying page still exists in your project, removing the redirect will make that page accessible again at its original URL.

• •Redirect chains: Avoid chaining redirects (A redirects to B which redirects to C). This slows down the browser and can cause loops. Always point the source directly at the final destination.
• •Self-referencing redirects: Do not redirect a page to itself. This creates an infinite loop and the browser will show an error.
• •Publish after every change: Redirect rules are only live after publishing. Changes in the editor are previews only.
• •Test in incognito: Browsers cache redirects aggressively. Always test in an incognito or private window after publishing to see the real behavior.