Skip to content

Blog

Shopify blog categories and tags

Published

How Shopify handles categories and tags on the blog

Shopify has no native 'category' field on blog posts. Categories are emulated via blog containers — you can create multiple blogs per store at /blogs/[blog-handle]/, e.g. /blogs/guides, /blogs/journal, /blogs/news. Tags are first-class — every post can have multiple tags, and each tag generates an archive URL at /blogs/[blog-handle]/tagged/[tag]/. Tag archives are crawlable and indexable by default. The risk is thin-content archive pages when tagging is loose; the discipline is a closed tag taxonomy.

The platform mechanic: blog containers are top-level architecture (decided once, rarely changed), tags are post-level metadata (set per post). Shopify's SEO overview1 treats both as editable resources, and the optimize-site doc2 calls for a 'logical hierarchy of categories' that the blog-container mechanism is built to deliver.

Blog containers — Shopify's category mechanism

A Shopify store can have multiple blog containers. Online Store > Blog posts > Manage blogs lets you create them. Each container has its own handle, its own archive page (at /blogs/[handle]/), its own RSS feed, and its own routing. The default blog is named 'News' with handle 'news'. Most stores need one or two blogs; some need three. Skip the temptation to create five or six — fragmentation produces thin archives.

The mental model: blog containers are top-level categories. /blogs/guides is for evergreen how-to content. /blogs/journal is for brand-voice editorial. /blogs/news is for time-sensitive announcements. Posts go in exactly one container — there's no cross-posting. A skincare brand might run /blogs/ingredients (ingredient explainers), /blogs/protocols (routine guides), and /blogs/news (launches). Three containers, ~30 posts in each, each container with its own category authority.

Tags and the /tagged/ URL pattern

Every Shopify blog post can have any number of tags. Each tag generates an archive URL at /blogs/[blog-handle]/tagged/[tag]/. The archive page lists every post tagged with that tag, scoped to the blog container. Tags are typed via the post editor as a comma-separated list. The URL slug for the tag is auto-generated from the tag text — 'Ceramides' becomes /tagged/ceramides, 'Hyaluronic Acid' becomes /tagged/hyaluronic-acid.

The rule that compounds: maintain a closed tag taxonomy. Decide your 12-25 tags in a spreadsheet before writing posts. Every post draws two or three tags from the closed list. Never let writers invent new tags ad hoc — that's how a Shopify blog ends up with 87 tags, 60 of which have one post each, every one of which generates a thin archive page.

The thin-archive trap

A tag archive page with one or two posts is thin content by Google's standards. A blog with 60 such archives signals low overall quality. The trap is structural: tagging a post with a new ad-hoc tag feels frictionless, and the consequence (a thin /tagged/[new-tag]/ archive page) doesn't surface for months. By the time a manual audit catches it, you have 40-60 thin archives dragging the blog's overall ranking down.

Shopify's keywords doc3 sets the 250-word body minimum on standard pages and 500 words on blog posts. Tag archive pages don't have a body field — they're just lists of posts with the tag. Two posts in a list is below any reasonable thin-content threshold. The signal is real, and it accumulates across the blog.

Two paths forward. (1) Maintain a closed taxonomy and never breach it — every tag has at least 5 posts within 6 months or it gets retired. (2) Noindex tag archives via robots.txt.liquid4 or theme.liquid template conditions. The first approach is preferred because tag archives are useful for users and AI shopping engines when they're not thin. The second is the safety net.

The tag-pruning audit — quarterly cadence

Walk this every quarter on every Shopify blog you operate. (1) List the tags. (2) Count posts per tag. (3) Mark every tag with fewer than 5 posts as a prune candidate. (4) For each prune candidate, either redistribute its posts to an existing tag or accept the redirect. (5) Delete the tag (which clears it from the assigned posts). (6) Set up a 301 redirect from the now-defunct /tagged/[tag]/ URL to the parent /blogs/[blog-handle]/ archive.

  1. List the tags. Shopify has no tag export for blog posts: open any post in Content > Blog posts and click View all tags5, or print {{ blog.all_tags | join: ', ' }} in a temporary theme template6.
  2. Count posts per tag. Tags with ≥5 posts: keep. Tags with 1-4 posts: prune candidate.
  3. For each prune candidate: pick the closest tag in the kept set and re-tag those posts.
  4. Delete the original tag from each post. (Shopify doesn't auto-delete tags from the system; once unused, they disappear from listings.)
  5. Set up a 301 redirect at Online Store > Navigation > URL Redirects from the old /tagged/[old-tag]/ to /blogs/[blog-handle]/ or to the new tag's URL.
  6. Verify with Google Search Console — confirm the old tag URL drops out of the index within 4-8 weeks.

Single most useful one-time intervention on most Shopify blogs we audit: collapsing a 60-tag mess into a 14-tag closed taxonomy. Thin-content signal clears within 8-12 weeks, and the kept tags rise into the index with stronger per-archive authority.