URL slug strategy sgen — building URLs that hold up over time

How to set a URL slug strategy that survives content changes

A URL slug is the segment of a web address that identifies a specific piece of content. In yourdomain.com/blog/ethiopia-yirgacheffe-2024, the slug is /blog/ethiopia-yirgacheffe-2024. Slugs look like small decisions but they compound fast.

Every link shared in a press release, every Google result pointing at your site, every social media post a reader saves — all of them point at a slug. Change the slug later without a redirect in place and every one of those links breaks instantly, with no warning to you or to the visitor.

This guide covers three connected things: how to choose a slug format that holds up across the life of your site, how to change slugs safely when you need to, and how to use SGEN's Redirects panel to keep old links working through every transition. It also covers one current limitation in SGEN's redirect matching that you need to know before you create your first redirect rule.

This is a workflow guide — not a single-feature reference. It brings together Post-type settings (the URL prefix layer), individual post slug fields (the per-post layer), and Redirects (the safety net) into one coherent plan that you run at launch and revisit whenever your content structure changes.

What is this for?

This guide answers a question every site owner faces: "What should my URLs look like, and what do I do when they change?"

Two layers of URL structure live inside SGEN and each is controlled in a different place.

The prefix layer is set in Post-type settings at /sg-admin/blog/settings. This is where the

/blog in yourdomain.com/blog/.. comes from. Change blog to journal here and every single blog post URL rewrites site-wide the moment you click Save. The prefix is a one-time decision made at launch — or during a deliberate rebrand — and it affects every post of that content type at once.

The per-post layer is set in the URL Slug field inside each post's own editor. This is where

/ethiopia-yirgacheffe-2024 comes from. Each post has its own slug, generated automatically from the post title when the post is first saved, and editable at any time before or after publishing. Changes here affect only the one post — not the whole site.

A slug strategy is the set of rules you agree on for both layers before you publish anything — or as a documented retrofit for a site already in motion. Without an agreed convention, every author makes a different call and the URL structure becomes inconsistent within a few months of launch.

For your business, a craft-roaster brand, the strategy fits on four lines:

• Blog prefix: /blog — one word, clear, no ambiguity.
• Per-post slug format: <origin>-<varietal>-<year> — readable, predictable, search-friendly.
• Examples: /blog/ethiopia-yirgacheffe-2024, /blog/colombia-gesha-2026, /blog/kenya-aa-2025.
• Exception rule: Non-origin posts use <topic>-<format>, e.g. /blog/brewing-guide-pour-over.

Once that convention is written down and shared with everyone who publishes, the URL structure manages itself. New authors know exactly what slug to use. Auditors know exactly what to check. SEO consultants have a predictable URL pattern to work with.

The pill counts below reflect a site mid-audit — 47 published posts following the convention, 6 old slugs already covered by redirects, and 3 posts that were renamed but not yet given redirect rules:

The pending count (3) is the actionable work. It is visible, finite, and clearly scoped — exactly what a good slug audit should surface.

Good use cases

Example 1: Launch-day slug decisions that hold for years.

your business is launching their SGEN site. The marketing team agrees on three rules before touching the keyboard: (1) the blog prefix stays /blog — one word, already familiar to readers; (2) every blog post follows /blog/<origin>-<varietal>-<year>; (3) no per-post slug is left at the auto-generated default before publishing. These three rules mean that every link shared in the launch newsletter, every press mention, and every Google result points at a URL that still works in two years — because the format was decided before publishing, not retrofitted after.

Here is what a post published on that convention looks like on the live site:

The convention pays back on every post published after launch. Each new Ethiopia coffee gets a URL that fits the pattern automatically; no decision required, no redirect needed.

Example 2: Renaming a published post — with a redirect.

your business published an early post at /blog/ethiopia before the naming convention was in place. After the convention was agreed, the post was renamed to /blog/ethiopia-yirgacheffe-2024 to match. Two press mentions still point at the old URL. The fix is a redirect:

The redirect catches every visitor following the old link and sends them to the right post silently. The Hits counter in the Redirects list shows how often the old URL is still being followed, giving the team a signal for when the redirect is no longer earning its place.

Example 3: Changing the post-type prefix site-wide — and covering every gap.

your business decides to rename their blog prefix from /blog to /journal as part of a rebrand. This is a one-field change in Blog → Settings — but it rewrites the URL of every blog post the moment Save is clicked. Every inbound link to /blog/.. becomes a 404 immediately unless a redirect rule catches it.

The safe workflow in order:

mentions, partner sites, newsletter archives, and Google Search Console.

Then add one rule per important individual post: blog/<slug> → /journal/<slug>.

Here is what the Redirects list looks like after that migration — five rules covering the archive root and four high-traffic posts, all active, all accumulating hits as inbound links follow through:

After each redirect rule saves, the confirmation banner timestamps it for multi-admin accountability:

Once redirect rules are in place, open the post in a private browser window and view page source. Every blog post page source should show the new prefix in the canonical link tag and the og:url meta tag. If either still reads the old prefix, the Blog Settings change did not save — re-open the settings form and confirm the slug field shows the new value before continuing.

What NOT to use this for

— created by checking "Is Regex match?" in the Redirects form — save without errors but do not fire on the public site. The Hits counter stays at zero and visitors get a 404. This affects every regex pattern without exception. Use plain, exact URLs for every redirect rule you create. If you have dozens of old posts to cover, add one rule per URL rather than one pattern that covers all of them. For large batches, use the CSV import at /sg-admin/redirects/import_export — it accepts a plain-URL rule per row and processes them all in one upload.

Blog Settings is immediate and site-wide. Every inbound link to the old prefix is a 404 the moment you click Save. If you cannot commit 15–20 minutes of focused work to redirect coverage right after the save, schedule the change for a session when you have uninterrupted time.

The /blog/<origin>-<varietal>-<year> pattern works for your business because all three fields are known before a post is published. A convention like /blog/<author>-<topic>-<date>-<revision> breaks the first time a guest author publishes or a post needs a second revision. Choose a format that uses only fields that are stable and always present.

title when the post is first saved. If the title is "Our New Ethiopia Single-Origin Coffee — In Stock for Spring 2026 — Buy Now and Save," the auto-generated slug will be long and out of convention. Edit the URL Slug field to the canonical form before clicking Publish. Because the post has never been live at the long auto-generated slug, no redirect is needed.

tool in the Redirects panel currently returns an error instead of a preview when a rule matches. It is not reliable on this version. Test redirect rules in a private or incognito browser window — visit the old URL and confirm the new destination loads.

→ /journal/ethiopia-yirgacheffe-2024 costs every visitor an extra round-trip for each hop and costs Google crawl budget. When a prefix migration creates a second generation of redirects, go back and update the older rules to point straight at the current final destination.

without committing to keep the redirect permanently.** Those links cannot be updated retroactively. The redirect covers every click on those old links, but the redirect must remain active indefinitely. Decide whether the SEO benefit of a cleaner slug outweighs the permanent maintenance cost before making the change.

are reserved on every SGEN site. Saving one of these as a blog prefix breaks parts of the admin panel. Pick a real, meaningful word for the content type.

that need their own redirect rules. Treat slug decisions as launch decisions. If you find yourself wanting to change the prefix for the third time in a year, the slug is not the problem — the editorial direction is. Pause, lock the slug in, and revisit only at the next major site refresh.

How this connects to other features

custom-object URL lives here. Any URL slug strategy starts with a decision at this level. See Customize post-type URL slugs for the full workflow including archive title, archive description, posts per page, and default category fields.

after a slug change. Every rename in this guide requires a corresponding redirect rule to be complete. See Manage site redirects for the full setup walkthrough, including the 301-vs-302 decision, priority settings, and CSV import/export for managing rules in bulk.

scale. The URL Slug column shows every post's current slug. After a slug migration, open the Manager and scan for any posts still showing the old prefix. The Issues chip filters to rows with canonical mismatches or missing fields introduced by the migration. See Audit SEO across your site.

own schedule. Submit the updated sitemap to Google Search Console after a migration so Google discovers the new URLs faster and stops indexing the old ones sooner.

prefix after a rename. Update those nav links in Menu Builder as part of the same migration session — ideally in the same 20-minute window as the redirect work.

page URLs needs its trigger condition updated to /journal/* after a prefix change. Check every active code snippet in Custom Codes and update the URL condition before going live.

Before you start

the site.

Search Console's Top Pages report and your newsletter archive. A spreadsheet of the top 20–30 URLs is enough for most sites.

may see a brief 404 while the redirect rules are being added in parallel.

change. Before is safer for posts with significant inbound traffic. Immediately after is acceptable if you have a list ready and can work quickly.

fire on the public site on this version, so all redirect rules must use plain, literal URLs.

• You are signed in as a SGEN Administrator with access to Blog Settings, Redirects, and SEO.
• You have a written slug convention — even one line — agreed with every person who publishes on

Where to go

For post-type prefix changes:

1. Left navigation → Blog → Settings (path: /sg-admin/blog/settings).
2. The identical form exists under Events → Settings for events, and under each custom

object's own Settings page for custom content types.

For per-post slug changes:

1. Left navigation → Blog → All Posts.
2. Click the post title to open the post editor.
3. Find the URL Slug field in the editor sidebar. On some editor layouts it is inside a

collapsed "SEO" or "Settings" panel — scroll the sidebar fully or expand any collapsed sections.

For redirect rules:

1. Left navigation → Redirects → All Redirects (path: /sg-admin/redirects/).
2. Click Add New (top right) to reach the Add New form at /sg-admin/redirects/add_new.
3. For bulk imports, use /sg-admin/redirects/import_export.

Steps

Blog prefix: /blog
Per-post slug: <origin>-<varietal>-<year>
Exception: Non-origin posts → <topic>-<format> e.g. /blog/brewing-guide-pour-over

target,destination,type,is_regex,is_active,priority,stop_processing
blog,/journal,301,0,1,5,1
blog/ethiopia,/journal/ethiopia-yirgacheffe-2024,301,0,1,5,1
blog/ethiopia-yirgacheffe-2024,/journal/ethiopia-yirgacheffe-2024,301,0,1,0,1
blog/colombia-gesha-2026,/journal/colombia-gesha-2026,301,0,1,0,1
blog/kenya-aa-2025,/journal/kenya-aa-2025,301,0,1,0,1
blog/brewing-guide-pour-over,/journal/brewing-guide-pour-over,301,0,1,0,1

What success looks like

What to do if it does not work

old path exactly — no leading slash, no trailing slash, no domain. The target blog/ethiopia matches requests for /blog/ethiopia. A target of /blog/ethiopia (with a leading slash) or blog/ethiopia/ (with a trailing slash) may not match the incoming URL. Edit the rule, adjust the slashes, save again, and test in a private browser window.

The most likely cause is that the post's URL Slug field was not updated — the redirect is in place but the old slug is still active on the post itself. Open the post editor and confirm the URL Slug field now shows the new value. If it does, test in a private window to rule out browser cache on the old slug.

Regex match?" is not enabled on the rule — if it is, that is the cause. Uncheck the box, enter a plain literal URL as the target, and save again. If the box is already unchecked and Hits remain at zero, the old URL may genuinely not be receiving any external traffic. Leave the rule in place and check again after a month before deciding to remove it.

All posts change prefix simultaneously. If specific posts return a 404 despite having a redirect rule, check that the target in the redirect rule exactly matches the old URL path for that post. Also confirm the post's per-post slug was not accidentally changed during the migration — only the prefix should change; the per-post slug carries over unchanged.

sometimes inside a collapsed "SEO" or "Permalink" section. Scroll the sidebar fully and expand any collapsed panels. If you still cannot find it, your user role may not have permission to edit slugs — ask an Administrator to make the change or update your role permissions.

on its own schedule. Reload /sitemap.xml after waiting a few minutes. If old URLs still appear after an hour, re-open Blog Settings and confirm the URL slug field reads the new value — a save that appeared to succeed may have silently reverted. Change the value again and save.

refreshes its index on its own schedule — typically days to weeks after receiving a 301 redirect. Use the URL Inspection tool in Google Search Console to request a priority re-crawl of the most important posts. The redirect rules handle every visitor click during the transition, so there is no traffic loss while the index catches up.

regex redirect rules save but do not fire on the public site. The workaround is the CSV import: prepare one plain-URL row per post, upload at /sg-admin/redirects/import_export, and each row becomes an individual active redirect rule immediately. This is more verbose than a single regex pattern but it is the only approach that reliably sends visitors to the right place right now.