↑↓ selectEnter openEsc close

    1. Elbuz

    How to manage product and category page addresses (SEO URLs)

    27 min readUpdated

    Elbuz builds a page address (SEO URL) for each product, category, manufacturer and article from its name, in Latin letters, and keeps it after a rename, so pages stay in search.

    When you need this:

    • No address after import — “Update only empty fields” fills in only those.
    • You renamed a product — the address and search links stay.
    • A page moved or a product is gone — a 301 rule leads to the new address, a 410 says the page is gone.
    • Two products share a name — the uniqueness check adds a number; both pages open.

    Where to start: check the address templates in the “URL Generator” window.

    What the address generator does

    A page address is a string like /mishka-logitech-g502-x-plus. In the card the field is labeled “SEO URL”; in literature the same thing is called a or friendly URL.

    Where an address comes from and how to set a template

    There are four sources, and the generator is only one of them.

    1. The generator builds an address from a template when the SEO URL field is empty: when a product or category is created, on import, when the base catalog is updated from price lists, and before export to a website via a .
    2. You typed the address by hand in the card. It is then saved exactly as entered: no transliteration, checks or corrections at all. Whatever you type becomes the address, including Cyrillic, spaces and capital letters. A slash inside such an address makes the page unreachable: the website looks up each part of the path separately.
    3. The price list file had an address column. The value goes into the database as is, the same way as manual input.
    4. A link to the supplier's website. If the product is new, the file has no address of its own, and the link to the supplier's product page is filled in, the path of that link becomes the address — without the domain, ? or #. This is where addresses with a slash inside come from: the supplier's path had several levels.
    Four address sources and the generator's steps
    Created in the appwith an empty SEO URLfieldAddress typed by handin the cardThe price list filehad an SEO URL columnNew product with a linkto the supplier's websiteNo (default)YesWhere the productor category came fromThe generator builds the addressfrom a templateSaved exactly as typed,no transliterationThe path of that linkbecomes the address1. Substitute macros:{PRODUCT_ID}-{PRODUCT_NAME}2. Trim the source textto “Max. URL length”3. Remove charactersfrom the delete list4. Transliterate:Cyrillic → Latin,128-character ceilingAddress in the databaseUniqueness checkon?Identical addressesallowedEvery row in the groupgets 0-ID- added
    • Action or result
    • Decision: the path depends on the answer

    Address templates

    The generator window has four template fields. Default values:

    • “Category URLs” — {CATEGORY_ID}-{CATEGORY_NAME};
    • “Product URLs” — {PRODUCT_ID}-{PRODUCT_NAME};
    • “Manufacturer URLs” — {MANUFACTURER_ID}-{MANUFACTURER_NAME};
    • “Article URL” — {ARTICLE_NAME}.

    These are the defaults — your fields may contain something completely different. The window screenshot above, for example, shows the templates of a specific account, not these. Before starting a run, check what is set in your account.

    For products, besides the ID and name, you can use {PRODUCT_ID_SITE} (the product ID on the website), {PRODUCT_MODEL}, {PRODUCT_SKU}, {PRODUCT_MPN} and {PRODUCT_MANUFACTURER}. {EAN}, the product barcode, also works. Categories and manufacturers have only the “ID + name” pair; articles have ID and name.

    The ID in the template is your insurance against identical addresses. Two products with one name get one address, but IDs never repeat. That is why the default template starts with {PRODUCT_ID}. Without the ID the address is shorter and easier to read, but you must watch for matching names yourself; the app won't prevent them.

    Two more fields control how text turns into an address: “Max. URL length” (50 by default) and “Characters to delete” — a list of characters to drop before transliteration. The second field is empty by default.

    “Transliteration rule” sets how Cyrillic becomes Latin: “Own table” (default) uses the rules from the “URL Transliteration” button; “KMU No. 55 (official Ukrainian)” is the official romanization under Cabinet of Ministers Resolution No. 55 of 27.01.2010, as in passports: «Згорани» → zghorany, «Щербухи» → shcherbukhy. The rule applies to product, category, manufacturer and article addresses the generator creates or updates.

    The “Generator enabled” checkbox turns the whole mechanism on and off. Clear it and the app stops building addresses altogether: new products and categories will have no address, and you will have to type it by hand in every card.

    One address for all languages

    A product has one address for all languages. The “SEO URL” field in the card sits outside the language switcher — unlike the page title and description, which are separate for each language.

    Languages are told apart by a prefix at the start of the path: /ua/mishka-logitech and /en/mishka-logitech are the same page in different languages. The prefix is set in the languages directory, and for the store's main language it is usually empty.

    An address without a prefix is redirected to the one with the current language prefix — but with code 302 (“temporary”), not 301. Search engines don't remember such a move: the address without a prefix stays in their index as a separate page. Campaign tags are carried over: utm_source, utm_medium, utm_campaign, utm_term, utm_content, gclid, yclid and others.

    How a name turns into an address

    The “URL Transliteration” button opens the replacement table: the “Find” column is the character in the name, the “Replace” column is what to replace it with. There are 69 rules: all Cyrillic letters, ґ, the + sign (turns into plus) and about thirty Latin letters with diacritics — Polish, German, French. Hard and soft signs are replaced with nothing.

    URL Transliteration window with search and replacement columns
    1Search column
    2Replacement column
    3Add (plus) button
    1. Search — the character or letter to be replaced.
    2. Replacement — the Latin text used in the URL.
    3. Add — creates a new rule row; not pressed.

    Rules are edited right in the cell, the “+” button adds an empty row, the trash can deletes the selected ones. The list is shared across the whole app: it also applies on export to a website and on import.

    This table is used when the “Transliteration rule” is “Own table”.

    With “KMU No. 55”, letters are replaced under the official rules: «зг» becomes zgh; є, ї, й, ю, я at the start of a word become ye, yi, y, yu, ya, elsewhere ie, i, i, iu, ia; the soft sign and apostrophe are dropped. Switching the rule doesn't change existing addresses while “Update only empty fields” is on.

    Besides table replacement, the app does a few more things to the name, and they are what causes surprises. Here is the same string before and after:

    Product nameAddress
    Ноутбук HP ZBook Ultra G1a 14"noutbuk-hp-zbook-ultra-g1a-14
    Мишка бездротова Logitech G502 X PLUS, чорнаmishka-bezdrotova-logitech-g502-x-plus-chorna
    Кабель USB-C -> HDMI, 2 мkabel-usb-c-hdmi-2-m
    Пам'ять G.Skill Ripjawspam-yat-g-skill-ripjaws
    Щітка для одягу «Їжачок»shhitka-dlya-odyagu-izhachok
    Розетка 220В +перехідникrozetka-220v-plusperekhidnik
    爱心 подарунокpodarunok

    What these seven rows show:

    • everything is converted to lowercase, punctuation and spaces become hyphens, several hyphens in a row collapse into one, leading and trailing ones are removed;
    • the apostrophe is not in the rules table, so it turns into a hyphen and splits the word: «Пам'ять» gives pam-yat;
    • the plus sign sticks to the next word — plusperekhidnik. If it appears in names often, add it to “Characters to delete”;
    • characters that are neither Latin nor in the rules table disappear without a trace — Chinese characters, Greek letters, emoji;
    • tags and entities like & are stripped from the name before transliteration — but in a single pass. If a name arrived double-encoded (Комп'ютерні), only the outer entity is removed, and the rest ends up in the address as junk: kompamp-039-yuterni.

    “Max. URL length” trims the name, not the address. Trimming happens before transliteration, so the finished address has more characters: a Cyrillic letter often becomes two Latin ones, and «щ» even three (shh). Example: at 70, the name «Настільне кріплення для монітора Anda Seat Stealth чорне металеве універсальне» is trimmed to 70 characters, but the address comes out at 72.

    The app cuts strictly by character count, ignoring word boundaries: in the example above the last word was left as univ.

    On top of that there is a hard ceiling no setting can get around: an address is never longer than 128 characters. Set “Max. URL length” to 200 and you still get 128. This is a limit of the conversion function itself.

    What happens to the address when you rename a product

    Nothing. The address stays the same — the one built when the product was created.

    That helps: names get edited all the time — package contents, color, a common style — and if the address were rebuilt each time, the website would drop pages from the index after every edit. All automatic runs (creation, import, base catalog update, export to a website) work in “Empty only” mode: they don't touch a filled-in address.

    The same goes for categories: moving a branch in the tree doesn't change the address — it belongs to the category itself, not to its parents.

    If you do need to rebuild the address for the new name, clear the “SEO URL” field in the card and save. An empty field means “build it again”, and the app builds the address from the current template for this one product. The old one is lost; what to do with it next is covered in the redirects section.

    Product card, SEO tab: SEO URL field and Google search preview
    1SEO URL
    2URL line in the preview
    1. SEO URL — the product address, filled in; do not clear it.
    2. The preview shows the same address as it appears in search results.

    A product copy doesn't inherit the address. The “Duplicate” button builds it again: the copy's ID is added to the original's address, and the original's ID is removed from it. So two identical cards don't clash over the address, even if their names are the same.

    How to separate identical addresses and remove orphaned ones

    The app doesn't prevent two products from having the same address, and neither does the database: there is no unique index on this field.

    A match comes from a template without {PRODUCT_ID} combined with length trimming. As long as the ID is at the start of the template, there can be no match: IDs are unique, and the app trims from the end. Without the ID, “Max. URL length” cuts off exactly the tail that made the name different from its neighbors.

    An example from the demo account: template {PRODUCT_NAME}, “Max. URL length” = 50, six mounts «Настільне кріплення для монітора Anda Seat Stealth …» in different colors and sizes. In all of them the first 50 characters end at “Stealth” — and six products got the address nastilne-kriplennya-dlya-monitora-anda-seat-stealth.

    Only one of the six pages will open. The website looks the address up in a list and uses the last row it finds — the other cards simply don't open at their address. For customers and search bots these pages don't exist, even though the products are in the app, active and look normal.

    There is no way to notice this in the admin panel: the app shows no warning about matching addresses, neither in the card nor in the product list.

    Uniqueness check

    Settings have a “Check SEO link uniqueness” switch: Account → System settings, “Catalog” section, “Data processing rules” group. It is off by default.

    It works only when the generator builds addresses: a run from the window, a new product, an import, saving a card with an empty SEO URL field. It doesn't run in the background and covers only that run's addresses. If one of them already exists in the catalog, it adds the store number and product ID to its start: 0-154686-nastilne-kriplennya-dlya-monitora-anda-seat-stealth.

    Existing duplicates are separated only by a run with “Update only empty fields” cleared. In “empty only” mode, only a new address that matches an existing one gets a number. With the checkbox cleared, every row in the group gets a number, including the indexed one: none of the six addresses above would stay the same.

    The order: list the duplicates and which of them bring search traffic → turn on the check → run regeneration with the checkbox cleared (it rebuilds all other addresses too) → set up redirects from the old addresses.

    How to remove orphaned addresses

    When a product or category is deleted, its address is deleted with it. But a row can get lost in other ways: deletion that bypasses the card, a failure mid-operation, a disabled language, a deleted store. Such rows harm nothing, but they stay in the database forever.

    They are removed by “Database integrity check”: Account → System settings → “System functions”, “General” group. The same check also runs automatically after an import from a file.

    What it does with addresses:

    • deletes addresses of categories, products, manufacturers and articles that are no longer in the catalog;
    • deletes addresses linked to a store or language that doesn't exist;
    • merges full duplicates of one row — if the same item accidentally got two identical records, the older one stays.

    It doesn't touch identical addresses of different products: to the check, these are two different rows. Those are separated by the uniqueness check described above.

    The check also restores generator settings if they were wiped: empty templates are replaced with the default values.

    Before you change addresses

    How to redirect an old address to a new one

    The “URL redirect” button in the generator window opens the list of rules. Each rule is a row: old address, new address and an active switch.

    Rules for product and category addresses are created only by hand: the generator doesn't create them on rename, on regeneration or when the uniqueness check is turned on. Only the blog creates a rule automatically — the “301 Redirect” button on the “Cannibalization” tab in the article interlinking window.

    URL redirect window with an empty grid and column headers
    1Old SEO URL
    2New SEO URL
    3Add (plus) button
    1. Old SEO URL — the address that is redirected.
    2. New SEO URL — the address it redirects to.
    3. Add — adds a redirect rule; not pressed.

    The columns are:

    • “Active” — the website ignores a disabled rule;
    • “Old SEO URL” — what to intercept;
    • “New SEO URL” — where to send visitors; saved in lowercase even if you type capitals;
    • “Note” — free text about why the rule was created; saved with the row;
    • “Response code” — how the website responds to the old address: 301 “Permanent redirect”, 302 “Temporary redirect” or 410 “Page removed permanently”. A new rule is created with code 301;
    • “Date added” and “Date updated” — for reference, read-only.

    The “+” button adds an empty row at the top of the list, which you then fill in right in the cells. Enter just the address, without the domain or language prefix — as it appears in the card's SEO URL field: nastilne-kriplennya-dlya-monitora-anda-seat-stealth, not https://your-site/ua/nastilne-kriplennya-dlya-monitora-anda-seat-stealth.

    The website checks the rules before looking for the page: first the whole path, then each part of it separately, until the first match. On a match, it responds with the rule's code: 301 (“moved permanently”) or 302 (“temporary”) to the new address. The language prefix is kept: you write a rule once and it works for all languages.

    What the website does with the address a customer opens: the language prefix is checked first, redirect rules come before the page lookup, and the bottom branch shows why only one of several identical addresses opens
    YesNoYes, code 410Yes, code 301 or 302NoNoYes, for one itemYes, for severalA customer opensan address on the websiteThe language has a prefix,but the address doesn't start with it?302 to the same addresswith the language prefixIs there an active “URL redirect”rule for the whole pathor one of its parts?“Not found” page —removed permanentlyRedirect to the“New SEO URL” with that codeIs every part of the pathamong the SEO URLs?“Not found” pageIts page opensThe one foundlast opens
    • Action or result
    • Decision: the path depends on the answer

    Test redirects in an incognito window. The website applies a saved rule starting with the next time the address is opened. But a browser that has received a 301 even once remembers it and keeps going to the new address on its own. So in that same browser a removed rule still “works” for a while.

    Code 410 works differently from the other two. There is no redirect: the website shows a “not found” page and tells the search engine the page won't come back — unlike a regular 404, which reads as “couldn't find it right now”. The new address isn't used, so leave it empty.

    The is updated too: addresses with an active redirect are left out of it, so the search engine isn't offered pages that will be redirected anyway. This applies to all page types: categories, products, articles, news and filter landing pages.

    A rule intercepts any part of an address, not only a full match. Put a word in “Old SEO URL” that appears as a separate part of live links, and all those pages start redirecting. Before saving, make sure the old address isn't used elsewhere: open it on the website — there should be no live page.

    Redirects work only on the Elbuz storefront. If the catalog goes to your own website via a tunnel, the addresses are sent there, but the redirect rules are not: they aren't part of the export. For an external website, set up redirects with the website's own tools. In an Elbuz CMS store, the “Redirects” module does this: How to set up 301 redirects and get rid of 404 errors.

    How to rebuild addresses for the whole catalog

    The “Update URL in base catalog” button goes through the whole catalog at once: categories, products, manufacturers, articles. What it does depends on the “Update only empty fields” checkbox.

    • Checkbox checked (the default every time you open the window) — the app fills in only missing addresses. It doesn't rebuild existing ones: this is the same mode all automatic runs use.
    • Checkbox cleared — the app rebuilds all catalog addresses from the current templates.

    The uniqueness check, if turned on, works in both modes — in “empty only” mode, only for newly built addresses.

    A run with the checkbox cleared can't be undone. The app keeps no address history, there is no undo, and no redirects from the old addresses are created.

    The nightly database backup for the last week (“Account” → “System settings” → “Other settings” → “Restore DB backup”) is not a rollback: it takes the whole database back a day, along with orders, stock and edits.

    In practice this means every catalog page the search engine knew stops opening at its old address, and the new address is a new page with no history for it.

    Regeneration with the checkbox cleared is needed when:

    • the website isn't live yet and there are no rankings to lose;
    • you changed the address template and want to apply it to existing products;
    • addresses came from a price list in a form you don't like.

    Before you start, check the templates and “Max. URL length”: the run applies whatever is in the fields right now.

    During the run you'll see the message “Processing data, please wait...”, and the “Update URL in base catalog” button is disabled until the server responds. Then one of two things happens:

    • if the server responded without an error, you'll see “Base catalog update completed”. The app doesn't say how many addresses changed, so check the result in the catalog. This message doesn't mean every step succeeded: if a query inside the run failed with a database error, the error is only written to the system log, the run goes on, and “completed” still appears at the end;
    • if the generator is disabled, the server returned an HTTP error or the connection dropped, you'll see “Base catalog update failed. Check whether the SEO URL generator is enabled.” The text is the same for all three causes: if your generator is enabled, the cause is something else.

    Before the run, export the product list to a file: product grid menu “Export products to XLSX file” → “All products”. The file contains only the columns currently turned on in the grid, so first turn on “Product SEO URL”. This is your copy of the old addresses: the old one in the file, the new one in the app.

    Spot-check a few rows by opening them on the website. The grid column shows not the row the page opens by, but its service copy in the products table. After a manual SEO URL edit in the card the copy lags behind, so the file may hold an outdated address — and the redirect would come from the wrong one.

    If a run breaks off or takes a long time

    Addresses are not written one by one. First the app builds all new addresses in a separate working table: it fills in the templates, trims the length, removes characters, transliterates. Catalog addresses don't change at this stage, except in two cases at the very start of the run, in both modes:

    • placeholder product addresses like product-name or product-id are deleted;
    • if the template contains a name ({PRODUCT_NAME}, {CATEGORY_NAME}, etc.), addresses consisting only of an ID (154686 or 154686-) are cleared.

    Then the results are transferred to the catalog in separate queries, one after another:

    1. existing addresses are overwritten in one query (in “Update only empty fields” mode, only empty ones);
    2. addresses for items that had none are added in one query;
    3. if the uniqueness check is on, the store number and the item's ID (product, category, manufacturer or article) are added to identical addresses;
    4. the copy of addresses shown in the product grid's “Product SEO URL” column is updated.
    A run from the click to the final message: the “Update only empty fields” checkbox only decides which items go into the working table; after that, both modes follow the same path
    NoYesChecked: only items withoutan address go to theworking tableCleared: all categories,products,manufacturers, articles goto the working tableYesNoClicked “Update URLin base catalog”“Generator enabled”?“Generator is disabled!” —the run didn't startPlaceholders are deleted; ID-onlyaddressesare cleared if the template has aname“Update only empty fields”?Template, trimming to “Max. URLlength”,“Characters to delete”, transliterationWrite to catalog: overwrite existing,add missingUniqueness checkon?Matching addresses from this runget the store number and item IDThe “Product SEO URL”column is updated“Base catalog updatecompleted”
    • Action or result
    • Decision: the path depends on the answer

    The run has no overall rollback: a break between steps leaves whatever was already written.

    • If the run broke off before the transfer, catalog addresses are the old ones, except for the cleared ID-only addresses.
    • If it broke off after the first step, existing addresses are already new, but items without an address may stay without one, duplicates aren't separated, and the product grid column shows old values.

    A repeat run builds addresses again from templates and names rather than resuming; the working table is recreated at the start of every run. “Update only empty fields” mode fills in addresses the broken run didn't manage to add or had cleared. A repeat won't bring old addresses back: they are already overwritten, and the regeneration warning applies.

    How many rows per run, and can you close the window

    • There is no ceiling. A run takes all categories, products, manufacturers and articles in the catalog in one pass, without batches and without a row limit.
    • This is not a background task. The run is a single request to the server while the window waits for the response; it doesn't appear in the task queue or the operation log. The final message comes only to this window: if you close it earlier, you won't see either “completed” or “failed”, and you'll have to check the result in the catalog.
    • Two runs by one user go one after the other. A second generator run — from another tab, during an import or when saving a card with an empty SEO URL — waits for the first to finish, but no longer than ten minutes. Then it starts anyway and recreates the working table in the middle of the first run. So don't overlap a long run on a large catalog with another one.

    Scenarios

    The website isn't live yet, and you want short addresses without an ID

    What to set up. In the “URL Generator” window, enter {PRODUCT_NAME} in “Product URLs”, check “Max. URL length”, clear the “Update only empty fields” checkbox and click “Update URL in base catalog”. So that products whose names start the same way don't get one address, turn on the uniqueness check in system settings beforehand.

    What you get. Addresses of all categories, products, manufacturers and articles are rebuilt from the current templates. Where an address still matches another one, the uniqueness check adds the store number and item ID to the start — for every row in that group.

    What won't happen. The app won't create redirects from the old addresses to the new ones, and the previous addresses won't be saved anywhere. On a website that isn't live yet this doesn't matter; on a live one, see bulk regeneration.

    After an import some products have no address, and the rest must not be touched

    What to set up. Leave the “Update only empty fields” checkbox checked — that is how it is every time you open the window — and click “Update URL in base catalog”.

    What you get. Only items with no address or an empty one get an address. Products with a placeholder address like product-name also get a new address in the same run. If the template contains a name, the app also treats ID-only addresses (154686, 154686-) as empty and builds them again.

    What won't happen. Filled-in addresses stay as they were, even if the template has changed since.

    You renamed one product and want the address to match the new name

    What to set up. In the product card, clear the “SEO URL” field and save. Then in “URL redirect” add a row: old address — the one that was in the field, new address — the one that appeared, “Response code” — 301.

    What you get. The generator builds an address from the current template for this product only. Customers and search engines arriving at the old address end up at the new one.

    What won't happen. Other products don't change. The app doesn't remember the old address, so write it down before clearing the field. Without a row in “URL redirect”, the old address will return “not found”.

    A product is discontinued for good, with no replacement

    What to set up. In “URL redirect”, add a row, enter the product address without the domain or language prefix in “Old SEO URL”, and select 410 “Page removed permanently” in “Response code”. Leave the new address empty.

    What you get. At this address the website shows a “not found” page and tells the search engine the page won't come back. The rule applies to all website languages.

    What won't happen. There is no redirect anywhere. If the same piece of address appears as part of other links, the rule intercepts them too — check this before saving.

    What to do when the result isn't what you expected

    Common problems
    What you seeWhyWhat to do
    “Generator is disabled!” You clicked “Update URL in base catalog” with the “Generator enabled” checkbox cleared Check the box and try again. If the window has no such checkbox at all, your access group hasn't been granted the right to it (who has access)
    “Base catalog update failed. Check whether the SEO URL generator is enabled.” The checkbox is checked on screen, but the generator is disabled in the saved settings; or the server returned an error or the connection dropped mid-run Clear and check “Generator enabled” again, click outside the field and try again. If the error persists, run with “Update only empty fields” checked: it fills in addresses that didn't get written (if a run breaks off)
    You renamed a product, but the address stayed the same That's by design: the app doesn't rebuild a filled-in address If you need a new one, clear the “SEO URL” field in the card and save (about renaming)
    The product page returns 404, although the product is in the catalog and active The SEO URL field is empty, or the address went to another product, or it contains a slash or another character the app didn't build Open the card and look at the “SEO URL” field; if it's empty, fill it in or run the generator in “empty only” mode (about identical addresses)
    The address opens the wrong product Several products have the same address; the website shows the last of them Change the address in the duplicate cards by hand, or turn on the uniqueness check and run the generator with “Update only empty fields” cleared (about identical addresses)
    The address is cut off mid-word “Max. URL length” kicked in: it trims the source name by character count, ignoring word boundaries Increase the value or shorten the name itself; keep the 128-character ceiling in mind (about transliteration)
    A word disappeared from the address, or two words merged into one The name had characters with no transliteration rule: Chinese characters and emoji disappear, the plus sign turns into plus and sticks to the next word Add the rule you need in “URL Transliteration” or add the character to “Characters to delete” (about transliteration)
    After a catalog update, pages dropped out of search A generator run with “Update only empty fields” cleared overwrote all addresses and created no redirects Set up rules from the old addresses to the new ones in “URL redirect”; take the old addresses from the file you exported earlier (about redirects)
    The page returns “410 Gone” A rule with code 410 — “removed permanently” — is set up for this address Find the row in “URL redirect”: if 410 was set by mistake, set 301 and enter the new address, or clear “Active”

    FAQ

    Can the generator create SEO URLs for filter attribute values, like /noutbuky/ram-16gb?

    No: the generator has templates only for categories, products, manufacturers and articles, and filter pages are built by the website's filter module. If you need a separate “Laptops 16 GB” page, create a category and fill it using a parity category rule by attribute.

    Does the app create redirects from the old address to the new one?

    No, for products and categories rules are created by hand in “URL redirect”. So before changing addresses, export the old ones to an file with the “Product SEO URL” column (redirects).

    A product is discontinued for good — what should I set for its address?

    A rule with code 410 “Page removed permanently” and no new address. If the product was replaced by another one, a 301 to the replacement's page is better: customers and search engines land on a live product (redirects).

    Why do two products have the same address?

    {PRODUCT_ID} was removed from the template, and “Max. URL length” trimmed the names down to a shared beginning. Only one of these pages opens. Addresses are separated by the uniqueness check during a generator run (identical addresses).

    How long can an address be?

    No longer than 128 characters, and there is no way around this ceiling. “Max. URL length” trims the name before transliteration, so the finished address comes out a bit longer than that value (transliteration).

    Can I change product addresses in bulk?

    No: the “Product SEO URL” column in the product list is read-only. Only regeneration from a template changes addresses in bulk. For categories, the “SEO URL” column in the “Category list” table can be edited in the cell.

    Will redirects be sent to my own website?

    No. The tunnel sends addresses, but redirect rules work only on the Elbuz storefront. For an external website, set up redirects with the website's own tools.

    I click “Update URL” and it says “Base catalog update failed” — what's wrong?

    The generator is disabled in the saved settings, the server returned an error, or the run broke off. What to do is in troubleshooting; what's left after a break is in “If a run breaks off”.

    Where to find it and who has access

    Menu
    Directories → Base product catalog → URL Generator
    Address of one product
    product card, “SEO” section, “SEO URL” field
    Address of one category
    category card or the “SEO URL” column in the “Category list” table
    Other entry points
    the “URL Transliteration” and “URL redirect” buttons in the generator window
    Access right
    the “URL Generator” window; the buttons and “Generator enabled” have separate rights
    Prepare
    a filled-in catalog: addresses are built from product and category names

    The generator has no desktop shortcut, and the transliteration and redirect windows have no menu items of their own.

    Left menu: Directories, Base product catalog expanded with the URL Generator item
    1URL Generator
    1. URL Generator — opens the SEO URL generator window.

    The window has no “Save” button: as soon as you leave a field, the form is sent to the server automatically. The “Update only empty fields” checkbox is the exception: it is not saved at all and is checked again every time you open the window.

    SEO URL generator window with the three top buttons, both checkboxes and the template fields
    1Update URL in base catalog
    2Update only empty fields
    3Product URLs
    4Max. URL length
    1. Update URL in base catalog — mass run over all addresses; not pressed here.
    2. Update only empty fields — keeps existing addresses unchanged; must stay checked.
    3. Product URLs — template of macros for product addresses.
    4. Max. URL length — limit on the generated address length.

    Rights inside the window are granted to an access group separately:

    • Button “Update URL in base catalog” — without it, the regeneration button, “URL Transliteration” and “URL redirect” disappear;
    • Flag: generator enabled — controls only the “Generator enabled” switch. “Update only empty fields” is always visible;
    • Advanced tab: SEO URL — a right of the categories window: without it, the category card has no SEO URL field, even if the generator is open to you.

    Templates, “Max. URL length” and “Characters to delete” are not protected by a separate right: access to the window means access to addresses across the whole catalog.

    Related topics

    • If you need to fix the address of one product — product card: where the “SEO URL” field is and what happens on save.
    • If you are moving catalog branches or looking for categories without an address — category tree: moving doesn't change the address, and the category table has a “Without SEO URL” filter.
    • If the catalog goes to your own website — export via tunnel: what exactly is sent there.

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free