URL Redirects
You automatically send visitors who land on an old address to the new one. That way old links don't break and your search engine value moves to the new…
Where to find: Left menu → Content → URL Redirects Who it's for: Anyone who changes the address of a product or page, or who doesn't want old links to return a 404 In short: You automatically send visitors who land on an old address to the new one. That way old links don't break and your search engine value moves to the new address.
What is it for?
You changed a product's name, so its address changed too. But that old address is registered on Google, your customer bookmarked it, and maybe it was shared in a blog post. Everyone who visits the old address gets a "page not found" (404) error.
A redirect quietly moves that visitor to the new address. The visitor notices nothing and lands directly on the right page.
When you change product, category and blog addresses from the panel, the system creates the redirect itself — you don't have to do anything manually. These appear in the list with an Automatic label.
301 or 302?
| Type | What does it mean? | When is it used? |
|---|---|---|
| 301 Permanent | "This page has moved here for good." | For permanent moves. Search engine value is transferred to the new address. This is the default and the right choice in most cases. |
| 302 Temporary | "This page is being shown from here for now." | For short-term campaigns and temporary redirects. |
If you're not sure, choose 301.
The list screen
| Column | What does it show? |
|---|---|
| Source path | The old address the visitor entered. |
| Target | The new address they'll be sent to. If it's outside your site, it's marked with a separate icon. |
| Redirect type | 301 Permanent or 302 Temporary. |
| Hits | How many times this redirect has been used. Hover over it to see the last time it was used. |
| Source | How the record was created: Manual, Import or Automatic. |
| Status | Active (working) or Inactive (stopped). |
The Hits counter is not instant; it updates with roughly a 5 minute delay.
The search box at the top searches on the path. You can select rows and use Bulk Actions to Activate, Deactivate or delete them all at once.
Adding a new redirect (step by step)
- Click the New redirect button.
- Type the old address in the Source path field. Example:
/eski-urun - Type the new address in the Target field. Example:
/yeni-urun - Choose a Redirect type (the default is 301 — Permanent).
- If you like, write a Note (to remember why you added it).
- Make sure the Status switch is on.
- Click the Add button.
Fields
| Field | Required? | Description |
|---|---|---|
| Source path | Yes | Must be an address inside your site (starts with /). |
| Target | Yes | Can be a path inside your site (/yeni-urun) or a full address (https://...). |
| Redirect type | Yes | 301 or 302. |
| Note | No | Up to 500 characters. Just for you. |
| Status | Yes | If you turn it off, the redirect won't work. |
Warnings that appear as you type
As you type the source path, the system checks it live and lets you know:
"It will be saved as: ..." — Your address is simplified before it's saved. For example, even if you type /Eski-Urun/, it is stored as /eski-urun.
"A redirect already exists for this source path." — You can't create a second record for the same address; edit the existing one.
"'{name}' is currently published at this address." — Careful! There is a real page at the address you entered (a product, category, blog post, etc.). If you add a redirect, that page will no longer be reachable.
"This address is one of the store's system pages." — You're trying to redirect one of the system's own pages, such as /cart or /login. If you do, that page will become unreachable.
These warnings don't block you, they only inform you. You can go ahead and save — but be sure you know what you're doing.
How addresses are simplified
To guarantee a match, the system standardises the source address:
| Rule | Example |
|---|---|
| Everything is converted to lowercase | /Eski-Urun → /eski-urun |
A trailing / is removed | /eski-urun/ → /eski-urun |
A leading / is added if missing | eski-urun → /eski-urun |
| Everything after the question mark is dropped | /eski-urun?renk=kirmizi → /eski-urun |
The last one matters most: parameters after a question mark are ignored. /urun?renk=kirmizi and /urun count as the same address; you can't create separate redirects for the two.
Good news: the parameters in the visitor's address are kept and carried over, as long as the target has no parameters of its own.
Chain and loop protection
The system stops redirects from tangling with each other.
Chain flattening: If A → B exists and you add B → C, the system automatically turns the old one into A → C. You'll see this message: "The target was the source of another redirect; the chain has been flattened and connected to the final address."
This is a good thing: the visitor reaches the target in a single step instead of two — faster, and healthier for search engines.
Loop prevention: If you try to create an endless circle such as A → B and B → A, the record is rejected: "This redirect would create a loop; it can't be saved."
Bulk adding with CSV
If you have many redirects, you can import them in bulk instead of entering them one by one.
- Click the Import button.
- Write one redirect per line in the text box:
/eski-urun,/yeni-urun,301 /eski-kategori,/yeni-kategori,302 - Choose the default Redirect type (if a line has a third value, that one wins).
- If you want existing records to be overwritten, turn on the Overwrite existing source paths switch.
- Click the Import button.
| Rule | Value |
|---|---|
| Separator | Comma , · semicolon ; · tab |
| Per import | Up to 500 lines |
| Comment line | Lines starting with # are skipped |
| Header line | Headers such as source,target are recognised automatically and skipped |
When it finishes you'll see a summary: "{n} added · {n} updated · {n} failed". Failed lines are listed separately.
There is no export feature. You can't download your redirects to a file.
Automatic redirects
When you change the address of a product, category or blog post, the system creates a 301 redirect from the old address to the new one on its own. These records appear in the list as Source: Automatic.
So you don't need to be afraid of changing a product's name or address — old links won't break.
You can also edit, deactivate or delete these records manually.
When do changes go live?
The change you make takes effect on your store within a few minutes (it's not instant, because of caching).
If it doesn't work right away while you're testing, wait a few minutes, clear your browser cache and try again.
Frequently asked questions
Can I turn it off instead of deleting it? Yes. Turn off the Status switch; the record stops working but isn't deleted. You can turn it back on later.
Can I redirect to another website? Yes. Type the full address starting with https:// in the Target field.
The redirect points to the page itself. The source and target can't be the same; the system doesn't allow it. Make sure they don't become identical after simplification.
Can I search in the note field? In practice the search box works on paths; you can't search your notes.
Can I export in bulk? No, there is no export.
Related pages
- Content — Overview — Overview of the Content section.
- Blog Posts — List — Blog posts and their addresses.
- Legal Pages (Agreements) — Agreement pages.
Was this page helpful?
Legal Pages (Agreements)
You create the legal pages required for e-commerce by selecting from ready-made templates. The page description: "Manage your legal pages."
Forms — Overview
With a drag-and-drop tool you design your own forms (contact, survey, pre-order application...); customers fill them out, and responses are collected…