Shopify blog URL structure: understand the path before changing it

For the standard hosted storefront, an article address follows the pattern ‘/blogs/blog-handle/article-handle.’ A blog landing page stops after the blog handle. Shopify’s Liquid article documentation describes the article URL and includes examples of this nested path.

The blog handle and article handle have different roles. Changing the individual article handle does not rename the blog. Likewise, adding a ‘Care’ tag organizes related posts; it is not the same action as changing the article’s address. The category guide explains that organizing choice separately.

For a new article, use a concise description of its actual topic with hyphens between words. Avoid a handle tied to a temporary promotion when the article is meant to remain useful after the promotion ends. The address should remain recognizable when someone sees it outside the blog feed.

When you have a researched primary keyword, its hyphenated form is a useful planned handle. Keep the H1, one relevant H2, first sentence, and page title aligned with that phrase too. Record those decisions in the content brief before the article enters the publishing queue.

For an article, open Content → Blog posts, select the post, and edit the URL handle in its search engine listing. For a blog, open Manage blogs, choose the blog, and edit that blog’s listing. Shopify documents article listing fields and blog details separately.

Before saving, compare the full current path with the proposed path. A change from ‘/blogs/guides/post-a’ to ‘/blogs/guides/post-b’ is an article rename. A change involving the blog segment has a broader organizing context. Write down exactly which URLs need checking instead of assuming every change has the same effect.

A working address can remain useful even when you improve an article’s title. Consider a rename when the current handle is misleading, contains an error, or no longer describes the page’s purpose. Cosmetic preferences alone are a weak reason to introduce a migration task.

• Record the current address and why the proposed one describes the same page more accurately.
• Find internal links, navigation entries, and scheduled references that use the old address.
• Review the redirect option offered when editing the handle; verify the result after saving.
• Keep a dated old-to-new mapping so the team can investigate later link problems.

Shopify’s redirect guidance explains that its URL redirects apply to broken source URLs, rather than overriding a still-valid page. Do not assume that entering a redirect will make a live destination disappear or change the platform’s standard route design.

1. Open the new address in a fresh browser view and confirm the intended article loads.
2. Open the old address and check that it reaches the expected replacement when a redirect is needed.
3. Follow links from the blog archive, related articles, and store navigation.
4. Check the article’s title, image, and content so a working URL does not conceal the wrong destination.
5. Update the page inventory and save the migration note with the publication record.

Use a content inventory to keep the current URL and editorial owner together. Then review contextual links with the internal linking workflow. A successful check means readers can still reach the intended explanation, not simply that the new path looks tidy.