Cloudflare Redirect Rules: 301 Redirects Without Server Access

Why Cloudflare can redirect on its own

Cloudflare sits between the visitor and your website. Once your domain's DNS points to it, every request reaches Cloudflare first, so it can answer with a redirect itself and the request never touches your hosting. For a business owner in Tashkent or any other city this is practical: a site builder often cannot set response codes, shared hosting may be limited, and a developer is not always on call.

Redirects matter for SEO. When a URL changes, search engines need to understand that the new page replaces the old one, and links from Instagram, Telegram, directories and ads should not end in a 404. A permanent redirect with a 301 or 308 status code sends exactly that signal.

What to prepare before you start

Cloudflare rules only affect traffic that passes through Cloudflare. Check three things first:

• your registrar lists Cloudflare's name servers for the domain;
• the DNS tab has a record for the hostname you want to redirect;
• that record is proxied, shown as an orange cloud rather than a grey one.

Tasks that redirect rules solve

If the cloud is grey, the request goes straight to your server and the rule never runs. This is the most common reason for the complaint “I set it up and nothing happens”.

Typical cases where a Cloudflare-level redirect makes sense:

• merging the www and non-www versions of the site;
• forcing http to https;
• moving individual pages after a redesign;
• pointing an old domain to a new one after a rebrand;
• sending spare domains, such as .uz and .com versions or common misspellings, to the main site.

How a redirect rule is built

A rule has a condition, a destination URL, a status code and a few options. The condition usually matches the hostname or the path. To merge mirrors, you say: if the host equals the www version, redirect to the main domain with a 301. Cloudflare renames and reshuffles its dashboard sections from time to time. Page Rules used to be the standard tool, and now there are dedicated redirect rules and bulk redirect lists, so follow the current Cloudflare documentation for exact steps. The logic stays the same.

Two details decide whether the result is good. The first is path preservation: a visitor should land on the same page at the new address, not on the home page. The second is keeping the query string, otherwise UTM tags from your Meta Ads or Google Ads campaigns disappear and analytics loses the traffic source.

For a migration with hundreds of URLs, a bulk list is easier: a table of old addresses and new addresses. Build it by matching pages by meaning. Sending everything to the home page is treated by search engines as a weak signal.

Domains without hosting, loops and server conflicts

An extra domain does not need hosting at all. Add it to Cloudflare, create a proxied DNS record (a placeholder works) and add a rule pointing to your main site. It is a tidy way to deal with domains bought “just in case”.

The classic problem is the “too many redirects” error. It usually comes from the Flexible SSL mode: the visitor arrives over https, Cloudflare talks to your server over http, the server answers with a redirect to https, and the cycle repeats. Fix it by installing a valid certificate on the server and choosing Full (strict) mode, or by removing the forced https redirect from the server and keeping it only in Cloudflare.

To stop redirects from stacking into chains, keep a few habits:

• choose one place for each type of redirect;
• keep mirrors and https in Cloudflare, and page-level moves in the CMS;
• never duplicate the same rule on the server and in Cloudflare;
• write down what is configured where, so you do not have to dig for it in six months.

Caching and verification

Both Cloudflare and browsers can cache redirects. If you changed a rule and still see the old behaviour, purge the cache in the dashboard and test in a private window.

Test several URLs with curl -I or an online header checker. You want a 301 status, the expected address in the Location header, a single hop with no chain, and a final page that returns 200. Open a URL with UTM tags as well, plus the pages your ads point to. If the site accepts payments through Click or Payme, make sure the return URLs after payment are not caught by a rule.

Cloudflare or the server: which is better

If you have server access and do not use Cloudflare for anything else, keeping redirects on the server is simpler, because there are fewer places where something can break. Cloudflare wins when hosting is restricted, you manage many domains, or you need to redirect traffic quickly without a developer.

Redirects are only one part of technical SEO. After a move you should also check the sitemap, canonical URLs and indexing. If you need help with a migration or with SEO optimisation in Uzbekistan, the markdev team can go through your task with you and suggest a careful plan that protects your rankings.