anchor.diff:  related_applications: [short-url-manager]
   ---
   
  -There is a regular requirement for creating short URLs on behalf of
  -departments, usually for use with for campaign materials. Content
  -designers do this using the [Short URL Manager][short-url-manager] app.
  -Read [more about Short URL Manager][short-url-manager-section] below,
  -including how to remove routes originating from it.
  -
  -There are also processes for [redirecting HRMC manuals][hmrc-manuals-section]
  -and [redirecting from campaign sites][campaign-sites-section].
  -
  -Finally, sometimes there is a need to manually redirect existing URLs to
  -another internal location, either due to an incident, content being
  -archived or because the slug has been changed.
  -
  -## Choosing a redirect strategy
  -
  -Does something exist at the incoming URL already? There's a
  -[simple way of checking][check-route-exists-section].
  -
  -If no route exists, and if you have the time to wait for a content
  -designer to review the proposal, you should just use Short URL Manager.
  -If the route already exists, or if you're in a hurry, you'll need to take
  -a different approach.
  +There are a number of different ways of applying redirects on GOV.UK.
  +Here is a guide for choosing the right one:
  +
  +- Is the redirect a short URL, such as `gov.uk/dfe`?
  +  [Use Short URL Manager][short-url-manager-section].
  +- Are you redirecting a HMRC manual?
  +  Read the [HMRC section][hmrc-manuals-section].
  +- Are you redirecting from a campaign site?
  +  Read the [campaign sites section][campaign-sites-section].
  +
  +That covers the service-specific redirects. We then have several options
  +for applying redirects to most GOV.UK content:
  +
  +- Are you having an incident and need to apply a redirect _urgently_?
  +  You can [apply the redirect directly in Router API][apply-redirect-in-router-api-section]
  +  (though you'll need to do some housekeeping afterwards).
  +- Is the redirect correctly showing in Content Store, but not in Router API?
  +  You may just need to [nudge Content Store into updating Router API][register-redirect-from-content-store-section].
  +- Is the redirect correctly showing in Publishing API, but not in Content Store?
  +  Try [re-presenting the content item downstream][represent-content-item-section].
  +- Does the redirect not exist anywhere yet?
  +  You'll need to [apply a redirect from within the relevant publishing app][apply-redirect-from-publishing-app-section].
  +
  +## Manually apply a redirect from any publishing app
  +[apply-redirect-from-publishing-app-section]: #manually-apply-a-redirect-from-any-publishing-app
   
   The preferred method of creating redirects is to use the publishing app that
  -originally published the content to set up the redirect. This usually
  +originally published the content to set up the redirect. You can find out
  +[what exists at the incoming URL already][check-route-exists-section] (if
  +anything), and [which app owns the route][find-owning-app].
  +
  +Once you've established which app owns the route, you should see if it is
  +possible to set up the redirect from within the app UI itself. This usually
   involves unpublishing the content, whereupon the app gives the option to
   redirect the old route to another route. This approach is preferred as it
   keeps the workflow and publishing history within the app, as well as
  
positive.code: 
  If a route is found, and it has the handler `redirect`, then there is
  already a redirect in place.
  
  ## Redirect using the Short URL Manager
  [short-url-manager-section]: #redirect-using-the-short-url-manager
  
negative.code: Router API.
  
  Not all applications support unpublishing / setting redirects. In these
  cases, you'll need to interact with Publishing API manually - see below.
  
  > Note that this won't work if the thing you're redirecting originates from
  > the Short URL Manager: there's [a rake task][short-url-manager-section-remove-route]
  > for that.
  
  You'll need to get the content ID of the current thing that exists at the
  route you want to redirect from. This is generally just a case of visiting
  the route prefixed with `/api/content` to expose its Content Store
  information.
  
  You may want to log into the Content Store app console in another shell:
  
  `$ gds govuk connect app-console -e production content_store/content-store`
  