Shopify blog in a subfolder: what actually works

01What Shopify allows, and what it does not

Shopify's own blog always lives under /blogs/, for example /blogs/news/your-article. You can change the blog handle and the article handle, but not the /blogs/ segment ^[6]. Shopify cannot host pages from WordPress or another CMS itself. To show them in a folder on your store domain, something in front of the storefront has to route that one folder to another origin and leave every other path to Shopify.

If all you want is a short link to share, a URL redirect from /blog to /blogs/news is enough. It changes the entry link, not the article URLs. Before you move content out of Shopify at all, check what the built-in blog can and cannot do. Many stores need better templates, not a second system.

02Choose by the URL you need and the risk you can own

What an app proxy means in practice

Shopify's documentation sets these limits ^[1]:

• The subpath is at most 30 characters.
• Each app has one proxy route.
• Store staff can change the prefix and subpath after installation.
• Cookie and Set-Cookie are stripped.

The consequences for a content folder:

• WordPress logins, comments and previews do not work through the proxy.
• Every canonical tag and sitemap entry must use the public proxied URL, never the origin address.

What CDN routing means in practice

In the documented Shopify mode, the shop's custom domain is proxied by your CDN zone and then passed to Shopify ^[2]. A path rule for the content folder sends those requests to your CMS; every other request continues to Shopify. You become responsible for those rules. If nobody on the team can read and maintain them, an app proxy or a subdomain is the more honest choice.

If the second system is WordPress, Shopify and WordPress together also covers the plugin route and migration. If you are considering rebuilding the storefront too, compare headless Shopify with a separate content system first.

03Name the folder so it cannot collide with Shopify

This is where most do-it-yourself attempts fail first. Edge path rules commonly use a trailing wildcard that matches any suffix ^[3].

The collision

A rule written as yourstore.com/blog* matches all of these:

• /blog and /blog/…, which is what you intended;
• /blogs/news/…, Shopify's own blog;
• /blog-sale, which could be a product or page handle.

Your CMS then answers for URLs it does not own, and those pages either break or are duplicated.

The fix

• Pick a name that is not a prefix of a Shopify path. Avoid anything that begins like /blogs, /products, /collections, /pages, /cart, /account, /search, /checkout, /apps or /a. /academy/, /guides/ or /learn/ are safer than /blog/.
• Write two exact rules: /academy and /academy/*. Never use /academy*.
• Decide on lowercase. Route patterns are case-sensitive ^[3], so /Academy/ will not reach your CMS. Redirect case variants to the lowercase URL.

If you must use the word "blog", keep it a separate segment (/blog plus /blog/*) and re-test /blogs/news after every routing change.

Three settings that must stay untouched

• Checkout. In the documented mode we use, edge scripts do not run on /checkout ^[2]. Design the content system so it never needs to.
• Certificate renewal. Shopify renews your certificate through /.well-known/acme-challenge/. A blanket "force HTTPS" setting at the edge can block it ^[2]. Exclude that path from any HTTPS redirect.
• Domain verification. Confirm the domain still shows as connected in Shopify after the change.

04How ShopXN.net runs this in production

ShopXN.net is a Shopify store selling travel eSIMs. Its travel reference library, in English and Chinese, lives in a folder on the same domain and is served from a separate content origin through CDN routing.

We checked the response headers on October 14, 2026:

• Storefront paths such as /products/ return powered-by: Shopify.
• Library pages return no Shopify headers and their own X-Robots-Tag: index, follow.

The routing rules, written as behavior

Two more decisions complete the setup:

• Tags point to the public folder. Each page declares its own public URL as canonical, and the English and Chinese versions reference each other with hreflang.
• The library has its own sitemap. The store's robots.txt lists it as a second Sitemap: line, added through robots.txt.liquid ^[4].

What the folder did not do

On October 9, 2026 we inspected 99 of the library's URLs in Search Console:

Sharing the store's hostname gave us control over routing and navigation. It did not make Google crawl new pages faster. New pages still have to earn crawling through internal links and usefulness. Plan links from pages that are already indexed into the new folder, and read the folder's progress one page at a time in Search Console.

05Launch checks and the result you should see

06Move existing /blogs/ articles without losing them

Shopify's URL redirects are meant for addresses that no longer resolve ^[6]. A redirect from a native article that is still published will not fire.

1. Publish in the new folder. Confirm the new URL returns 200 and declares itself canonical.
2. Unpublish the Shopify article. Its old URL now returns 404.
3. Add the redirect. Redirect the old /blogs/… URL to the new address.
4. Update links you control. Fix theme links, navigation and product descriptions, so you do not rely on the redirect forever.
5. Move a small batch first. Confirm the redirects in Search Console before moving the rest.

Worked example: moving 60 articles in batches of 10 means six rounds. If each round is checked after a week of crawling, the move takes about six weeks rather than one afternoon. In return, a template or redirect mistake affects 10 URLs instead of 60.

07Plan the rollback before launch

If you delete the routing rule, the folder falls back to Shopify, which has no such pages, and every article becomes a 404. Decide in advance:

• Short outage: keep a minimal rule that returns 503 with Retry-After for the folder.
• Abandoning the setup: move the articles back into the native blog and redirect each folder URL to its new address.

A 503 for a few hours is recoverable. Weeks of 404s are not.

08Copy this routing brief and fill in the brackets

Public folder: https://[yourstore.com]/[academy]/
Exact rules: /[academy] and /[academy]/* (no trailing-wildcard rule like /[academy]*)
Content origin: [origin hostname], must answer noindex, nofollow when requested directly
Allowed methods: GET, HEAD. Everything else: 405
Unpublished paths: 404 + noindex, without contacting the origin
Origin errors: pass status through + noindex
Cookies: remove Set-Cookie from content responses
Never match: /products, /collections, /cart, /checkout, /account, /blogs, /pages, /search
HTTPS: do not redirect or block /.well-known/acme-challenge/
Sitemap: /[academy]/sitemap.xml, listed in robots.txt.liquid as a second Sitemap: line
Canonical and hreflang: public folder URLs only
Rollback: 503 + Retry-After rule ready, owner: [name]
Acceptance: the eight launch checks, with results recorded on [date]

09Questions

Sources and what still needs a direct check

1. Shopify, About app proxies and dynamic data. Prefixes, subpath limits, stripped headers. Checked October 14, 2026.
2. A CDN provider's published Shopify custom-domain setup guide and its June 3, 2025 change note. Proxy mode, the HTTPS setting warning and blocked edge scripts on /checkout. Checked October 14, 2026.
3. The same provider's route pattern reference. Trailing wildcards and case sensitivity. Checked October 14, 2026.
4. Shopify, Customize robots.txt. Extra sitemap URLs. ShopXN.net's live robots.txt and Shopify-generated sitemap.xml, observed October 14, 2026.
5. Google Search Central public statements that subdomains and subdirectories are both handled, as reported in industry coverage. No dedicated Search Central page compares the two.
6. Shopify Help Center, URL redirects, and Shopify Community replies on the fixed /blogs/ segment.
7. Shopify Community threads on reverse proxies for /blog (2024–2025). Merchant reports, not policy.

Still to check yourself

• Your CDN provider's current Shopify instructions. Settings and restrictions change.
• Whether any app, theme feature or marketing tool already uses the folder name you picked.
• Whether your Shopify plan or contract has terms about proxies in front of the store.

The ShopXN.net observations come from our own production headers and Search Console checks. The routing table is a simplified description, not a drop-in configuration. If you want the routing designed and implemented for you, see our content hub service and architecture page, or request an assessment. For a broader baseline, use the technical SEO audit checklist. If the content needs several languages, read the international SEO guide before naming folders.