Replace a Telegram Hidden Link Destination, Keep the Label

To change where a hidden Telegram link leads while keeping the words readers see, pilot a Replace rule in RedFox Auto Forward Telegram that matches the whole anchor, meaning the link’s address and its label together, and writes the whole new anchor. RedFox’s Replace guide shows this pattern for a “specific hidden link”: copy the anchor markup from a raw view of a sample post, paste it as the original and enter the new anchor as the replacement. A rule that matches only the visible words is a different job, so check which one you have before you trust it.

This guide is for an editor or channel manager who already has a working route in RedFox Auto Forward Telegram (@AutoForwardNew_Bot) and republishes posts they are permitted to share. One recurring link in those posts, such as “Register here”, points to the source’s page, and you need the same words to lead to your own current page. It is not about resolving a short URL, stripping formatting or editing buttons; the first section sends those jobs to their own guides.

The previous bot has moved to @AutoForwardNew_Bot. Use this current handle to access RedFox Auto Forward Telegram. RedFox supplies the product; Auto-Bot.io publishes this guide. Documentation was checked on October 27, 2026. The specimens below are an editorial reader-run workflow, not an executed forwarding test, and the featured artwork is a concept illustration, not product UI.

1. Name the job before you write a rule

“Change the link” can mean five different jobs. Choose by the result you need:

If you are not sure which row you are in, look at the delivered post. Linked words inside the message text are this guide’s case. A button under the message is not.

2. Why changing the words may leave the destination alone

Telegram keeps a link’s visible text and its address as separate parts. In the Bot API, a clickable text link is a text_link entity whose url field is “URL that will be opened after user taps on the text”. In HTML style it is written <a href="http://www.example.com/">inline URL</a>, with the address in href and the words between the tags. See the Bot API’s MessageEntity and formatting options.

RedFox’s Replace Content guide draws the same line. Its hidden-link example starts with a post that reads like plain text, explains that one word in it is actually a clickable link, and then shows the markup behind it. The rule that changes that specific link matches the complete <a href="…">word</a> string; the rule that changes a mention matches only the mention text. RedFox’s formatting guide has a second example in the same spirit: its goal is to “change the url of Contract Link to another link”, and it works from the raw content rather than the displayed words. Both examples are RedFox’s own illustrations, and the hidden-link example also changes the label, so keeping the label while changing only the address is this guide’s straightforward application of the same pattern, not a separately documented case. A rule written for the visible words alone does not obviously touch the address. This guide has not run a words-only rule against a linked phrase, so it makes no claim about the outcome. The decoy and neighbor checks in section 6 let you see what your own rule does.

There is also a safe way to read a destination without visiting it. The Bot API documentation says Telegram clients display an alert before opening an inline link, “Open this link?” together with the full URL. Check that your own client does this on a harmless specimen, because the documentation describes bot-sent messages and clients can differ.

3. Prepare one pilot task

• Permission and route: use posts you control or are allowed to redistribute, and send the pilot to a private target. Changing a link in someone else’s post is an editorial decision, not a formatting detail; section 8 covers it.
• Where to work: choose the Web App, iOS app or Android app. Web and the apps provide fuller management than the limited Telegram-bot entrypoint. Active tasks run in RedFox’s cloud, and its FAQ says you do not need to keep your internet on.
• Plan: RedFox’s product site, checked October 27, 2026, lists Replace rules under Diamond. Eligible new users can try Platinum for 5 days with full Platinum features. Check the controls available in your account before choosing a plan for this workflow; the listing alone does not establish the tier for every replacement mode.
• Header setting: RedFox’s Replace guide says the feature will not work if Show Header Forwarder is enabled on the task. Check that setting first; the header display guide explains it.
• Task scope: the Replace form’s Apply For Task field says to leave it blank for all tasks. Name the pilot task instead, and do not use Apply For All Tasks. The wrong-feed guide covers the same scope trap for Discord to Telegram.
• Starting record: write down the task name, source, target, header setting, existing Replace rules and their task associations. Record relevant whitelist, blacklist, sender and message-type conditions, plus other active transformations. Use an isolated, authorized pilot where each specimen is eligible; do not weaken protective rules on a live route just to run a test. Keep competing link transformations, including Process To Raw Text and broad URL replacements, out of that pilot. With the new rule inactive, first confirm the linked specimen arrives with its original addresses. Then activate only the new rule and compare an equivalent fresh specimen under the same conditions.

4. Copy the anchor exactly

You need the link as the system sees it. RedFox’s formatting guide explains why: special formatting such as links can cause mismatches because Replace works on plain-text matching, so it points to the @FindMyIDs_Bot helper to read a message’s raw content.

1. Make a harmless specimen in a source you control. Include two links: “Register here” pointing at a page you are allowed to test, and a second linked phrase such as “resources page” pointing somewhere else.
2. Forward the specimen to the helper, press Start if prompted, and choose Get HTML. The guide says it returns the message’s raw content, with links shown as HTML.
3. Copy the whole anchor for “Register here” from that output.

Send the helper only harmless or public specimens. RedFox’s guide links it, but this guide does not establish who operates it, so never forward private messages, invitation links or anything containing credentials. An illustrative specimen looks like this; your helper’s output may differ in detail:

As readers see it:
Spring workshop: Register here. Slides are on the resources page.

Raw view:
Spring workshop: <a href="https://partner.example/register?ref=ab12">Register here</a>. Slides are on the <a href="https://partner.example/resources">resources page</a>.

Copy from the output instead of retyping. The Bot API requires a literal ampersand in HTML style to be written as &, so a link with several query parameters may show escaped characters. Reproducing them exactly is part of matching.

5. Write the Replace rule

1. Open Replace. On the Web dashboard, choose Replace under Features, then Add New. On mobile, open the Dashboard and tap the Replace icon.
2. Choose the type Basic. It replaces specific words or phrases, the simplest type for one exact string. The guide’s hidden-link example does not name a type, so treat Basic as the first thing to test.
3. Give it a label such as swap-register. The guide asks for fewer than 20 characters, using only letters, numbers, hyphens and underscores, with no spaces.
4. Optional: paste the whole raw specimen into Full Content Original. The guide says this field is for previewing or testing matches.
5. Original Words: the complete anchor you copied.
6. New Words: the same anchor with only the address changed.
7. Apply For Task: your pilot task.
8. Select Create Replace, then open the rule in the list and confirm it is activated for the pilot task and not for others.

Original Words:
<a href="https://partner.example/register?ref=ab12">Register here</a>

New Words:
<a href="https://team.example/register">Register here</a>

Keep the label words identical only if the new page still answers them. If “Register here” would now lead somewhere that is not a registration page, change the words in New Words as well, because the label is the promise the reader acts on.

When the address varies. An exact rule stops matching when a source changes the tracking value in the anchor. RedFox also offers Use Regex for patterns, but its create-and-manage guide warns that it does not provide support for regex usage. Confirm access in your account and get help with the exact pattern if needed. Do not replace the exact rule with an “every URL” pattern: it could change the resources link or another page with a similar address. If you choose a broader pattern, preview representative variants and rerun all the controls below, including a same-prefix address that should remain unchanged.

6. Check it with controls, not one lucky post

The checks below are for you to run; Auto-Bot.io has not executed them. Use fresh, harmless posts in a source you are allowed to test and a private target. Before activating the rule, confirm each specimen is eligible under the pilot’s filters and actually reaches that target. Keep those conditions unchanged, activate only the new rule, and compare equivalent fresh specimens. For each delivered post, record the words that arrived and where each link leads. A missing decoy, variant or ordinary-text post is not an unchanged control; resolve its eligibility or delivery before judging the replacement.

1. Target. Send the exact specimen. Expect the words to be unchanged and “Register here” to lead to the new address. Read the destination from your client’s open-link alert, then cancel, or forward the delivered copy to the helper and read its href.
2. Neighbor. In the same message, the “resources page” link should still lead where it did. A rule should change only its target.
3. Decoy. Send a separate post whose words are also “Register here” but whose address is a different page you own. With an exact anchor rule it should arrive unchanged. If its address changes, inspect the saved pattern, other active rules and the task that produced the copy; a broader pattern is one possible explanation.
4. Variant. Send the same words and domain with a different tracking value. An exact rule is not expected to match. Decide whether that is acceptable and you will update the rule when the source changes, or whether a Regex pattern is worth its risk, then rerun controls 1 to 3.
5. No link. An ordinary text post should be unchanged.
6. Caption. If your feed uses captioned photos, test a captioned specimen separately. The Replace guide does not say whether captions are covered, so treat it as untested until your own result says otherwise.

Change one thing at a time. If a result is unclear, restore the previous setting before trying anything else. Passing these controls says the rule behaved on those specimens; it does not guarantee every future post.

7. If the link did not change

• Nothing changed: check Show Header Forwarder first, then whether the rule shows as activated for this task. Compare Original Words with a fresh raw view character by character, because one changed parameter is enough to stop an exact match. Then look for another active transformation on the task.
• The words changed but the destination did not: check whether Original Words contains only the label or the complete anchor. Compare the saved rule with a fresh raw view, then repeat the one-change comparison.
• Other posts or tasks changed: check Apply For Task and whether Apply For All Tasks was used. Deactivate the rule on tasks that should not have it.
• The decoy changed: inspect the pattern, other active rules and task associations. Test a narrower exact anchor with comparable fresh specimens before attributing the result to a particular rule.
• The delivered message shows angle brackets or markup as text: deactivate the rule, restore your previous state and keep the specimen as a reproduction for support. The guide does not document that outcome.
• The link is a button: use the button URL guide instead.
• Nothing arrives at all: compare fresh eligible specimens with this rule inactive and active. Check task status, access, filters and other transformations before attributing the missing delivery. Do not change several settings at once or assume Replace is unrelated.

8. Replace a link only when the reader would agree with the swap

Being able to rewrite an address does not settle whether you should. Redistribute only content you may share, and respect the source owner’s terms. If you replace a partner’s referral link with your own, follow any disclosure rules that apply to your audience; this guide gives no legal advice. Keep the label truthful for the new page and verify the actual destination, whether through your client’s link preview or the harmless specimen’s raw view. Do not rely on every reader noticing a mismatch.

Keep a short audit note for each swap: the old anchor, the new anchor, the date, the task and who approved it. It will save time when a source changes its link or a reader asks where a link went.

9. Go live and keep checking

• Apply to the live task only after the controls pass. Repeat the target and neighbor checks on the first real post that carries the link.
• Undo with Deactivate For Task, which the guide documents. Delete is described as permanent, so keep the exact Original Words and New Words before you remove anything.
• Verify on fresh posts. Do not assume that changing or removing a rule edits messages that were already delivered.
• Recheck when the source changes. The Replace guide describes no alert when a rule stops matching, so look at the next post that carries the link and compare it with the audit note.

FAQ

Does changing the visible words change where a link goes?

Do not assume it does. Telegram stores the words and the address separately, and RedFox’s own example for changing a hidden link matches the full anchor. Test your rule with the target and decoy controls instead.

Do I need to write HTML?

Mostly you copy it. Take the anchor from the raw view, then edit only the address between the quotation marks and, if needed, the words between the tags.

Will this resolve a shortened link?

No. Choosing your own destination and revealing where a redirect leads are different jobs. For the second, see the Final Redirect Link guide.

Does it work with Show Header Forwarder on?

RedFox’s Replace guide says it does not. Turn the header off on the pilot task, or choose another way to deliver the posts.

Will it correct posts that were already delivered?

Do not rely on that. Check the next fresh post after each change, and handle earlier copies separately.

Pilot one link swap before you touch a live route

Explore RedFox Auto Forward Telegram, choose one pilot task and one harmless specimen, copy its anchor from the raw view, write a single Replace rule and run the six controls. Move the rule to a live task only when the target changes, the neighbor and decoy do not, and the new address is one you are happy for readers to see.