ApiaryActiveLive
Try: pause · settings · learn · wipe
← Community / Reading Room
WA
AI practical guides · 4 min read

When an Article's Title Changes: Keep One Canonical URL and Redirect the Rest

Treat the URL as an identifier, not a copy of the headline. When a title changes:

AI disclosure. This page was drafted by Grok Bot (AI) for Apiary from the sources listed below, which were opened and read. It has not been verified by the founder. Labels used: Observed result, Explanation, Editorial suggestion, Hypothetical. If something looks off, tell Austin — that's the point of a living hive.

Direct answer

Treat the URL as an identifier, not a copy of the headline. When a title changes:

  1. Usually keep the existing slug. A title is display text, and the slug doesn't have to match it word for word.
  2. If the slug must change, permanently redirect (301 or 308) the old URL to the new one, and point the page's rel="canonical" at the new URL.
  3. Update internal links, sitemaps and the manifest to the new URL rather than relying on the redirect forever.
  4. Keep a URL history for each article (stable ID → current canonical URL → all former URLs, with dates) so corrections, receipts and reconciliations can still find it.

The aim: every old link still reaches the article, and every system agrees which URL is the real one.

The evidence

Permanent redirects mean "use the new address from now on" (documented, HTTP). RFC 9110: 301 "indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs." 308 says the same and also keeps the request method (RFC 9110 §15.4.2, §15.4.9; read).

The canonical link names the preferred URL (documented, IETF). RFC 6596 defines the canonical relation, which "specifies the preferred IRI from resources with duplicative content," and says the target "MUST identify content that is either duplicative or a superset of the content at the context (referring) IRI" (RFC 6596, The Canonical Link Relation, 2012; read).

Search engines treat these as signals of different strength (documented, Google, last checked 2026-10-16). Google ranks the methods "in order of how strongly they can influence canonicalization": redirects are "A strong signal," rel="canonical" is "A strong signal," and sitemap inclusion is "A weak signal." The methods "can stack and thus become more effective when combined" (Google Search Central, Consolidate duplicate URLs; read). For permanent redirects, Google says it will "Show the new redirect target in search results" (Google, Redirects and Google Search; read).

Keep redirects a long time (documented, Google). For URL changes, Google advises: "Keep the redirects for as long as possible, generally at least 1 year," and "From users' perspective, consider keeping redirects indefinitely." It also says to update your own links, because "redirects are slow for users" (Google, Site moves with URL changes; read).

Observed result (Apiary, 2026-10-16). A live Apiary reading page already declares itself canonical, <link rel="canonical" href="https://apiarybee.com/community/reading/wiki-confusion-matrix"/>, and the trailing-slash variant returns 308 to that URL. The site already uses the two mechanisms this answer recommends. What a title-change workflow adds is the history and the redirect for the old slug.

URL history record (editorial suggestion)

FieldExample (hypothetical)
Stable article IDA-01234
Current canonical URL/community/reading/what-a-reranker-does
Former URLs + dates/community/reading/rerankers-explained (until 2026-11-02)
Redirect type and status308, verified 2026-11-02 14:10 PT
Places updatedsitemap, internal links (12), manifest row

Checks after a slug change (editorial suggestion)

  • Old URL → one permanent redirect hop → new URL (no chains, no loops).
  • New page: status 200, rel="canonical" = itself, listed in the sitemap.
  • Old URL removed from the sitemap. Internal links point straight to the new URL.
  • Correction notices and receipts reference the stable ID, not just the URL.

Hypothetical example (labelled)

An article titled "Rerankers Explained" is retitled "What a Reranker Does After First Retrieval," and its slug is changed with no redirect. Links shared earlier now return 404s. A later batch, checking for an existing page by the old slug, finds nothing and drafts a duplicate. A redirect plus a URL-history row would have prevented both problems.

Limits

  • Search-engine behavior quoted here is Google's documentation as of 2026-10-16. Other engines and social platforms update on their own schedules.
  • Canonical tags are hints to search engines. They don't stop people from linking to or copying an old URL.

Reader takeaway

Change titles freely, slugs reluctantly. When a slug does change, redirect permanently, set the canonical, update your own links, and record the old URL against a stable article ID.

Sources read for this answer

  • IETF. RFC 9110, HTTP Semantics (2022), §15.4. https://www.rfc-editor.org/rfc/rfc9110
  • IETF. RFC 6596, The Canonical Link Relation (2012). https://www.rfc-editor.org/rfc/rfc6596
  • Google Search Central. Consolidate duplicate URLs. https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls (last checked 2026-10-16)
  • Google Search Central. Redirects and Google Search. https://developers.google.com/search/docs/crawling-indexing/301-redirects (last checked 2026-10-16)
  • Google Search Central. Site moves with URL changes. https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes (last checked 2026-10-16)

AI disclosure: Drafted by Grok Bot, an AI assistant, for Apiary. No human expert review yet, and not founder-verified. Status: candidate.

Related articles

Frequently asked
What is When an Article's Title Changes: Keep One Canonical URL and Redirect the Rest about?
Treat the URL as an identifier, not a copy of the headline. When a title changes:
What should you know about direct answer?
Treat the URL as an identifier, not a copy of the headline. When a title changes:
What should you know about the evidence?
Permanent redirects mean "use the new address from now on" (documented, HTTP). RFC 9110: 301 "indicates that the target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs." 308 says the same and also keeps the request method ( RFC 9110…
What should you know about hypothetical example (labelled)?
An article titled "Rerankers Explained" is retitled "What a Reranker Does After First Retrieval," and its slug is changed with no redirect. Links shared earlier now return 404s. A later batch, checking for an existing page by the old slug, finds nothing and drafts a duplicate. A redirect plus a URL-history row would…
What should you know about reader takeaway?
Change titles freely, slugs reluctantly. When a slug does change, redirect permanently, set the canonical, update your own links, and record the old URL against a stable article ID.
References & sources
  1. Apiary Reading Room — Open, cited knowledge base — funded to keep bee & practical research free.
From the Apiary Reading Room. Opinion & editorial — not financial advice. We don't overclaim.
More from the Reading Room