> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/reference-and-help/redirects.md). # Redirects Send old paths to new URLs, accept suggested redirects for deleted or renamed pages, and use the 404 Task. The built-in Redirects module keeps old links working after you delete or rename a page. Open **WP AI Manager > Integrations > Redirects**. If the module is off, turn it on under **Settings > Modules**. ## Add a redirect 1. Select **Add Redirect**. 2. Enter the **Source path**, for example `/old-services/`. 3. Enter a **Target URL**, or a **Target post ID**. 4. Choose the **Status code**: **301 Permanent** for a page that has moved for good, **302 Temporary** otherwise. 5. Optional: **Match regardless of ?query** so `/old-services/?ref=x` also redirects. 6. Select **Add redirect**. Edit or delete a redirect from **Active redirects**. A deleted redirect can be restored from History. ## Suggested redirects When a page is deleted or its slug changes, its old URL appears under **Suggested redirects**, labelled **deleted** or **renamed**. Select **Add redirect** to send it to the right place before visitors and search engines hit a 404. ## Fix broken links with a Task The **Fix broken links and 404s** Playbook (Guided or Automate) finds internal links that point to missing pages and proposes redirects for review. It needs the Redirects module. Proposals are applied only after you select them and choose **Apply selected**. It can be scheduled; scheduled runs always wait for review. In Chat you can also ask: "Review broken links and propose redirects". This works on any site, with or without Elementor. --- # 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.3techagency.com/documentation/reference-and-help/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.