In short. Change the slug in the editor's Post URL field, commit the value, and check the public address and any links to the previous URL.
Definition: As of October 2026, Ghost's Post URL field changes a post's slug, the readable text used to identify the post in its web address. The field is in the editor's post settings; committing the edited value saves the URL change.
Key facts
- Ghost's post settings documentation says the default post URL comes from the post title and supports customization.
- Ghost's released editor tests cover saving a manually edited slug for both a draft and an already published post.
- Ghost's routing documentation defines the default post address pattern as
/{slug}/, with the slug supplied by the editor.
Where is the post URL field?
Ghost's Preparing posts for publishing places Post URL in the post settings menu within the editor. The existing title supplies the default value. A custom value replaces the slug used for that post.
The same documentation recommends a short slug that stays on topic, with hyphens separating words. Ghost's routing guide gives this example of a slug:
my-great-post
How is the URL change saved?
In Ghost's released URL field component, pressing Enter removes focus from the field and commits the value. Clicking outside the field also commits it. After replacing the slug, leaving the field therefore submits the edit.
Ghost's slug saving tests verify that a manual slug edit saves independently for drafts and published posts. The published-post test also checks that the post retains its published status.
For remaining unsaved edits on a published post, Ghost's editor header code provides the Update action and an Updated success label. The action is disabled while saving or when there are no pending edits. After saving, opening View post from the URL field provides a check of the public address.
What happens to the full address and old links?
Ghost's routing guide explains that collection settings determine the URL pattern around the slug. Its blog example uses /blog/{slug}/, so editing the slug changes the post-specific part within that pattern. Changing a shared prefix such as /blog/ involves the collection's permalink configuration in routes.yaml.
An address change also calls for checking links to the previous address. Ghost's redirects documentation describes redirect rules for sending old URLs to new ones after permalink changes. A redirect sends a request for one address to another; Ghost supports permanent redirects through a redirects.yaml file. Checking the old address after the edit establishes whether a redirect needs to be configured.
Related terms
- How do I change collection URL patterns in Ghost?
- How do I upload a redirects.yaml file in Ghost?
- How do I set a custom canonical URL in Ghost?
FAQ
Can I change a published post's URL?
Yes. Ghost's released saving tests verify a manual slug change on a published post while retaining its published status. Check your old address afterwards to assess the redirect needed.
Should I paste a complete URL into Post URL?
Enter the post's slug. Ghost's routing documentation shows how the editor's slug fits into the publication's permalink pattern, such as /{slug}/ or /blog/{slug}/.
Sources
- Ghost, "Preparing posts for publishing", updated 3 January 2024
- Ghost, "URL field component", released source
- Ghost, "Editor slug saving tests", released source
- Ghost, "Editor header actions", released source
- Ghost, "URLs & Dynamic Routing", undated
- Ghost, "Redirects", updated 11 November 2024
Check how a page reads to answer engines. Open the GEO score analyzer