> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/redirects.md). # Redirects Keep old links working when you move to Pylon or reorganize your knowledge base. ## Page redirects Use page redirects to send old URLs, such as links from your previous help center, to pages in your Pylon knowledge base. Redirects are permanent (301), so search engines transfer the old page's ranking to the new one. To create a redirect: 1. In your knowledge base, go to **Settings > Page redirects**. 2. Click **Create Redirect**. 3. Under **Redirect to**, choose the **Homepage**, an article, or a collection. 4. Enter the **Original URL** as a relative path, for example `/hc/en-us/articles/360012345678-reset-password`. 5. Optionally choose a **Language** to open the destination in that translation. Click **Export to CSV** to download all of your redirects. Knowledge base admins can manage redirects. To create redirects in bulk, use the [Knowledge Base API](/pylon-docs/developer/api/api-reference/knowledge-base.md). ## Migrating from Zendesk Zendesk Help Center URLs start with `/hc/{locale}/articles/`. Create a page redirect for each old article URL you want to keep, since Zendesk article IDs don't match Pylon's. Any `/hc/{locale}/articles/...` URL without a matching redirect is sent to the same path under `/articles/` on your knowledge base. ## Stable article URLs Article URLs include a numeric ID followed by the slug, for example `/articles/1234567890-reset-your-password`. Pylon finds the article by its ID, so links keep working after you rename an article or change its slug. Old URLs load the article and point search engines to the current URL. You don't need a redirect when you rename an article or move it to another collection. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.usepylon.com/pylon-docs/knowledge-base/redirects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.