What Changed in the New Sparkforge Blog

By Sparkforge Support Team ·Last reviewed May 3, 2026

The new Sparkforge Blog simplifies URLs (no more /b/ or /c/ segments), auto-updates the XML sitemap, supports canonical tags for SEO, and opens posts on their own pages. Old blogs keep working but should be migrated.

The Sparkforge Blog was rebuilt to fix the URL structure, SEO gaps, and editor limitations of the previous version. Here's what changed and how to move existing content over.

1. Simpler URLs

The /b/ and /c/ segments are gone. URLs now follow a clean structure based on whether you're using a domain or a subdomain.

If your domain is abc.com

  • Blog home: abc.com/blog (you set the slug — usually /blog)
  • Post: abc.com/post/post-name
  • Category: abc.com/blog/category/category-name
  • Tag: abc.com/blog/tag/tag-name
  • Author: abc.com/blog/author/author-name

If a page already exists at the slug, Sparkforge appends a unique parameter so you don't get a collision.

If your subdomain is blog.abc.com

  • Blog home: blog.abc.com (no slug needed — set Blog Home as the default page in the domain editor)
  • Post: blog.abc.com/post/post-name
  • Category: blog.abc.com/category/category-name
  • Tag: blog.abc.com/tag/tag-name
  • Author: blog.abc.com/author/author-name

2. Automatic XML sitemap

Publish a post and the sitemap updates itself. No more manually editing sitemap.xml or robots.txt every time you ship content.

3. Posts open on their own page

Each blog post opens as its own page rather than overlaying the blog home. That gives you room to add a subscribe form, comment area, or any custom section per post.

4. Canonical tags for SEO

The new blog supports canonical URLs, which tell Google which version of a page to index and where to consolidate ranking signals when content shows up in multiple places.

5. Layout and design control

You can choose layouts, control what shows on each card in the blog list, and style the home and post pages independently.

What happens to old blogs

Old blogs (the ones that lived inside Funnels and Websites) keep working and you can keep posting to them. But they have the URL, canonical, and sitemap gaps the new blog fixes. All old posts roll into a Default Blog. New sub-accounts created after this release start on the new blog automatically.

Move from old blog to new blog

  1. Go to Sites > Blogs.
  2. Open the Default Blog (your migrated old posts live here).
  3. Select the checkbox next to the posts you want to move.
  4. Click Move Blog.
  5. Confirm the move.

Heads up: the old URL of each moved post will break and a new URL will be assigned. Plan redirects accordingly.

Update funnel or website embeds

If you embedded a blog list element in a funnel or website, edit it to point at the new blog and republish the funnel or page.

Frequently Asked Questions

Will my old blog URLs still work after I migrate?
No. Moving a post to the new blog assigns it a new URL. Plan redirects for any URLs you've shared, linked to, or that have inbound traffic.
Do I have to migrate to the new blog?
Old blogs keep working, but they're missing the URL cleanup, canonical tags, and auto sitemap. Migration is recommended if SEO matters to you.
Where do my old posts go?
Existing posts roll into a Default Blog under Sites > Blogs. From there you select and move them to a new blog.
Do I still have to manage robots.txt and sitemap.xml manually?
No. The new blog auto-updates the XML sitemap each time you publish a post.
What about new sub-accounts?
Sub-accounts created after this release start on the new blog by default — no migration needed.

Was this article helpful?