Skip to main content

Troublesbleshooting Instant Redirect Pages

This article explains how to diagnose and fix common issues with Instant Redirect Pages in Kyrios so short URLs and paths reliably redirect to the intended destination.

Updated over 3 months ago

Who this is for / When to use

This guide is for Kyrios users who have created URL redirects for funnels, websites, or external links and find that the redirect does not work, goes to the wrong destination, or behaves inconsistently.


Why an Instant Redirect page does not work after setup

An Instant Redirect page fails when the domain, path, or destination is misconfigured or when the target page is unpublished or unavailable.

To resolve this:

  1. Go to Settings → Domains → URL Redirects.

  2. Open the redirect and confirm the Domain is correct.

  3. Verify the Path exactly matches what you are typing in the browser (for example, /zoom).

  4. Confirm the Redirect Type and Target URL / Funnel Step are correctly selected.

  5. Save the redirect and test it by visiting yourdomain.com/your-path in a browser.


Why the redirect goes to the wrong URL

A redirect sends users to the wrong destination when the target URL, funnel, or step selection is incorrect.

Fix this by:

  1. Opening Settings → Domains → URL Redirects.

  2. Editing the redirect rule.

  3. Confirming the Target URL is typed correctly with no extra spaces.

  4. If redirecting to a funnel, ensure the correct Funnel and Step are selected.

  5. Click Add Redirect or Save and test again.


Why the redirect works sometimes but not always

Intermittent redirect behavior is usually caused by browser caching or incomplete DNS propagation for custom domains.

To fix this:

  1. Clear your browser cache or test in an incognito window.

  2. Test the redirect on another browser or device.

  3. If using a custom domain, allow DNS changes up to 24 hours to fully propagate.


Why the redirect returns a 404 error

A 404 error occurs when the redirect path does not exist or the destination page is not published.

Steps to resolve:

  1. Confirm the Path begins with a forward slash (example: /zoom).

  2. Make sure the destination funnel step or website page is published and live.

  3. Verify the domain connected to the funnel or page matches the redirect domain.


Redirecting to external links like Zoom or Google

Instant Redirect Pages can send visitors to external websites when the redirect type is set to URL.

To set this up correctly:

  1. Go to Settings → Domains → URL Redirects.

  2. Click Add a Redirect.

  3. Select the correct Domain.

  4. Enter the Path (example: /zoom).

  5. Set Redirect Type to URL.

  6. Paste the full external link (including https://) into Target URL.


Redirecting to a funnel step

A funnel redirect sends traffic to a specific step inside an existing funnel that is connected to the same domain.

To ensure it works:

  1. Select Redirect Type: Funnel.

  2. Choose the correct Funnel.

  3. Select the correct Step.

  4. Confirm the funnel is published and assigned to the same domain.


Why redirects stop working after a domain migration

Redirects break after a domain migration when old domains are not mapped correctly or redirects were not updated.

To fix this:

  1. Confirm the new domain is fully connected in Settings → Domains.

  2. Update existing redirects to use the new domain.

  3. Test each redirect path individually.


REGEX redirects not working for all paths

REGEX redirects fail when the pattern syntax is incorrect or the source domain is not properly selected.

How to fix:

  1. Double-check the REGEX pattern syntax.

  2. Ensure the redirect is configured to apply to all paths.

  3. Confirm the source domain is correct.


Common issues and fixes

  • Problem: Redirect does nothing when visited
    Fix: Confirm the domain is selected and the redirect is saved successfully.

  • Problem: Redirect works on desktop but not mobile
    Fix: Clear cache and confirm the destination page is mobile responsive.

  • Problem: Funnel redirect loads blank page
    Fix: Ensure the funnel step is published and connected to the correct domain.

Did this answer your question?