# Redirects (/docs/core/maintenance/redirects)



# Redirects [#redirects]

When you rename or move a page, its old URL should still work, since other sites and search engines may link to it. Redirects handle that, but editing nginx config by hand is error-prone. Atlas gives you a simple table instead.

<ThemeImage name="redirects" alt="The redirects manager" />

## How it works [#how-it-works]

Atlas reads and writes the redirects file set by `redirectsFile` in [atlas.json](/docs/core/getting-started/the-workspace), which is `nginx/redirects.conf` for the Coolify docs. You add a redirect by giving the old path and the new one, and Atlas writes the matching nginx rule.

<ThemeImage name="redirect-modal" alt="The add redirect dialog" />

To find an existing rule in a long file, search by either path.

## Lossless editing [#lossless-editing]

Your redirects file often has more than just simple rules: comments, custom blocks, and rules Atlas does not manage. Atlas preserves all of that **byte for byte**. It only touches the redirects you edit through the table, and leaves everything else exactly as it was.

<Callout type="info">
  Add a redirect whenever you change a page's slug. Pair this with [Doctor](/docs/core/maintenance/doctor), which flags internal links that still point at the old path.
</Callout>

## Next steps [#next-steps]

<Cards>
  <Card title="Review and commit changes" href="/docs/core/git/changes" />

  <Card title="Run the preview server" href="/docs/core/git/preview-server" />
</Cards>
