Skip to main content
Contributor ⭐️⭐️⭐️
November 30, 2022
Discovery

Get public URL before publishing

Related products:CC Moderation
  • November 30, 2022
  • 25 replies
  • 263 views

It would be fantastic to have a production ready URL before publishing content live. The current preview, includes preview and a few other things that means you can’t reference the URL in other content until pushing the content live. This post provides a workaround, but that is prone to manual error, typos, and a bunch of other issues. Please provide a better way to do this. 

25 replies

すもも
Contributor ⭐️⭐️⭐️
March 11, 2026
I just started using this recently and was surprised that this feature wasn't available!In our company, we need to provide topic URLs to other departments in advance.Manually changing URLs is very dangerous.This is an old post, but I would appreciate your consideration.
すもも
Erik_
Contributor ⭐️⭐️⭐️⭐️⭐️
March 12, 2026

See this recent post for some good news :)

 

The shortest answer is doing -George Herbert
すもも
Contributor ⭐️⭐️⭐️
March 17, 2026

 

@Erik_ Thanks for letting me know. I'm really looking forward to the update.

すもも
Larry
Helper ⭐️⭐️
March 20, 2026
The following idea has been merged into this idea:

All the votes have been transferred into this idea.
Larry Imgrund || Senior Product Manager & Community Nerd
Larry
Helper ⭐️⭐️
March 20, 2026
OpenDiscovery
Larry Imgrund || Senior Product Manager & Community Nerd
Larry
Helper ⭐️⭐️
March 20, 2026

Thanks for this idea and to everyone who's contributed here.

This is being tracked alongside a related idea and we're moving it into discovery as part of broader content workflow improvements. The ability to get a stable, production-ready URL before publishing is a clear need for teams coordinating community content with external campaigns and deployments. We'll keep this thread updated as we learn more.

Larry Imgrund || Senior Product Manager & Community Nerd
danielwal_coco
Contributor ⭐️⭐️⭐️⭐️
April 2, 2026

Exactly! I have to provide our development, Marketing, and Product teams with REAL URLs during the development cycle. Which means, I can’t use Drafts and must create hidden Categories so the articles aren't where they are supposed to be and must be moved post-release (which changes the URL, but if one uses a shortened URL with JUST the Topic ID, it works...) but it’s a PAIN.

Larry
Helper ⭐️⭐️
April 6, 2026

Exactly! I have to provide our development, Marketing, and Product teams with REAL URLs during the development cycle. Which means, I can’t use Drafts and must create hidden Categories so the articles aren't where they are supposed to be and must be moved post-release (which changes the URL, but if one uses a shortened URL with JUST the Topic ID, it works...) but it’s a PAIN.

@danielwal_coco  Completely understand, I’m investigating as part of the broader content workflow improvements we are planning this year. I will do my best to try and deliver this one earlier if possible given the pains communicated by everyone on this idea.

Larry Imgrund || Senior Product Manager & Community Nerd
danielwal_coco
Contributor ⭐️⭐️⭐️⭐️
June 8, 2026

Exactly! I have to provide our development, Marketing, and Product teams with REAL URLs during the development cycle. Which means, I can’t use Drafts and must create hidden Categories so the articles aren't where they are supposed to be and must be moved post-release (which changes the URL, but if one uses a shortened URL with JUST the Topic ID, it works...) but it’s a PAIN.

@danielwal_coco  Completely understand, I’m investigating as part of the broader content workflow improvements we are planning this year. I will do my best to try and deliver this one earlier if possible given the pains communicated by everyone on this idea.

One other thing, when creating a new article, it’s Topic ID (for Insided’s backend) should be the same Topic ID that the front end uses.

Larry
Helper ⭐️⭐️
June 8, 2026

One other thing, when creating a new article, it’s Topic ID (for Insided’s backend) should be the same Topic ID that the front end uses.

Great callout, agreed, we need to make this consistent between surfaces (backend and frontend)

Larry Imgrund || Senior Product Manager & Community Nerd