Your first working redirect: plan, domain and link

This route gets you to a verified first redirect: a visitor opens your incoming URL and KEHR sends them to the intended page. The linked guides show the detailed forms; this article gives you the order of steps and the final checks.

This scenario uses a domain handled by a KEHR plan. To protect an existing PHP website, start with PHP site protection; that integration does not require moving the website to a redirect server.

1. Prepare your plan and domain#

1. Follow the plan selection guide and choose a package with the features you need. In Plans, check that it is “Active” and note the number after #.
2. Connect your domain and assign it to that plan. If DNS is not ready, first follow the guides for the server IP and DNS records.
3. Refresh the page and check that your domain appears in the correct plan's information. An https:// link requires working HTTPS on that domain; an added domain alone is insufficient.

Registering a domain name and assigning it to a plan are separate actions. Start with one domain and one plan. If a plan already serves visitors, check the effect on its existing links before reassigning a domain or changing shared settings.

2. Create one destination#

1. Open the complete destination URL directly in your browser and check that the page works.
2. Follow the template guide to create one template with one Offer Page URL, a recognizable comment, and a delay of 0.
3. Check the saved card and note its template number. For example, plan #101 and template #501 are different numbers.

Offer Page is the destination, such as https://example.org/landing. The incoming URL you give visitors is different, such as https://example.com/promo. All URLs and numbers in this example are synthetic.

3. Assign a template to your incoming link#

1. In Plans, open “Settings” for the correct plan number, then “Incoming traffic”.
2. Follow the streams guide to add one link on your domain, select your template, and leave “Delete after first visit” off. This makes the link reusable for testing.
3. Refresh the page and check the full incoming address and template number in the saved row.
4. On the “Settings” tab, check the redirect method. For a simple new setup, “302 redirect (server-side)” is an option that does not require a visitor to click a button. The method applies across the plan.

If your plan does not support streams, follow the default action guide. Traffic rules and visitor checks can change the result even for an existing stream. If you already have filtering rules, first check which rule matches your test visit; do not delete working rules for this example.

4. Check the complete route#

1. In a new tab, open the exact incoming URL, including the path saved in your stream. The domain root is a different link and can produce a different result.
2. Compare the page that opens with your intended destination. “By button” requires a click. If you need UTM or other parameters, check them using the settings guide.
3. In Plans, open “Statistics” for this plan. Find the visit by domain and time; statistics use UTC. Expand its row and read the result and reason.

“Redirect link issued” confirms that KEHR issued a URL, not that the destination fully loaded or a purchase occurred. This setup is successful when the correct page actually opens in your browser and the saved domain, stream, and template match your tested URL.

If the result differs#

• The URL does not open: check its spelling, DNS, and HTTPS before changing rules.
• A different page opens: compare the incoming path, template number, matching rule, and default action.
• Access is restricted or a check does not finish: use the result and reason in the history; a stream setting does not disable visitor checks.
• No history row appears: check the plan, domain, period, and UTC, then refresh statistics a little later.

For help, give support the plan number, domain, full incoming URL, template number, time with its time zone, and a screenshot of the result. Do not include connection secrets or API keys.