# How to Use Redirects When Replacing an Article By AI Visibility editorial team AI-assisted article. Two articles answer parts of the same customer question. An editor combines them into one guide, and the web team sends both old addresses to the new page. One address used to explain a deadline that the replacement barely mentions. The redirect works, but a reader following that saved link may still leave without the answer. Choose the destination by comparing what a reader expected from the old article with what the replacement actually provides. Then test the old address, the final page and any section that should open for the reader. The AI Visibility access checklist covers reach. This walkthrough focuses on the editorial decision to replace an article and the technical checks that preserve the reader’s route. AI Visibility site access checklist (/article/can-ai-search-access-your-website-a-practical-checklist/) Decide whether the old article needs a new address Start with the reason for the change. If the article still serves the same purpose and the address is useful, update it in place. If two articles overlap and one replacement can answer both sets of questions, consolidate the material and map both routes. If the old article needs to remain available as a historical record, label its status and link to the current guidance. If the old article is being removed without a relevant replacement, choose a removal response that matches the publishing decision. GOV.UK’s publishing guidance illustrates the distinction between a withdrawal that remains visible and unpublishing with a separate route. GOV.UK withdraw or unpublish guidance (https://guidance.publishing.service.gov.uk/publish-update-retire-content/standard-content-types/withdraw-unpublish-standard/) · Google guide to site moves (https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) Editorial outcome Route for the old address What to check Same article, revised Keep the current URL New information appears on the existing page Permanent equivalent replacement Redirect to the relevant new article Final page answers the old reader’s question Two articles consolidated Map each old route to the appropriate page or section Both intents survive the merge Historical record retained Keep the old page with clear status and a current link Dates and replacement are easy to find Removed without a relevant replacement Return the intended 404 or 410 Current links stop sending readers to the old page Read the old headline, opening and the part people still need. If available and authorised, consult useful internal links, search reports or referral examples. A single old article may answer a question that the new page treats as a subsection. Note the old question and the exact new heading that should serve it. This gives the editor a way to check the replacement before the developer activates the route. If several old pages would land on one destination, review their mappings individually. Consolidation is a good fit when the target genuinely incorporates or replaces their material. Sending every removed article to the homepage can create a poor landing experience and may be treated as a soft 404 by Google. Where a replacement exists, make it the closest useful destination for the person who followed the old link. Google guide to site moves (https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) Try the map on a small editorial example. Suppose a “weekend delivery” article and a “delivery areas” article will both move into a service guide. The weekend article needs an answer about days and cutoff times. The delivery areas article needs a place where the reader can check coverage. A shared destination can work if it keeps both answers findable. The first old route can land near the weekend section while the second lands near coverage. If the proposed guide only has a delivery enquiry form, send the content back for review before approving either redirect. Match the redirect to the publishing decision For a permanent replacement, Google recommends a permanent server-side redirect such as 301 or 308 when possible. For a temporary route, select an appropriate temporary status under your platform’s guidance. Keep the rule tied to the expected old article and direct it to the final destination. A chain through several old URLs adds opportunities for failure and makes it harder to tell which rule needs an update. Google redirects guidance (https://developers.google.com/search/docs/crawling-indexing/301-redirects) · HTTP semantics, RFC 9110 (https://www.rfc-editor.org/rfc/rfc9110) Make the new content available before enabling the redirect. For a single article, record whether old slash or query-string variants should reach the same destination. Preserve parameters only where they have a purpose and fit your privacy and analytics policies. If you want a section to open, use a stable fragment and verify that the target actually has the expected identifier. A fragment selects a location in the browser; the browser does not send it as part of its request for the page. Check the destination as a page and as a reader journey. HTTP semantics, RFC 9110 (https://www.rfc-editor.org/rfc/rfc9110) Use a bounded GET to capture the whole chain. Keep the intermediate Location and the final response. Replace the example address with the exact old article you are responsible for testing. old_url='https://example.com/replace-with-the-old-article' curl --silent --show-error --location --max-redirs 8 --max-time 20 \ --dump-header old-article.headers --output destination.html \ --write-out 'status=%{http_code} final=%{url_effective} redirects=%{num_redirects}\n' \ "$old_url" grep -iE '^(HTTP/|location:|content-type:)' old-article.headers Request the new address directly as well. Confirm the final status, title, relevant content and declared canonical. If the old route sends people to a section, open the original URL in a clean browser and check that the heading exists and is the intended place to start. Test a narrow screen if a sticky header or a different template could conceal the heading. Verify that links on the new page still take the reader to the next action. Follow a real documentation replacement Google Search Central’s update history says it reduced duplication involving its helpful content FAQ and redirected the FAQ. It also says the helpful content system section moved into the archived portion of the ranking systems guide. That public history gives the test a stated editorial context. Google Search documentation update history (https://developers.google.com/search/updates) On 6 November 2026, the former FAQ URL returned a 301 with a Location pointing to the ranking systems guide and its #helpful-content fragment. The destination returned HTTP 200 and declared the guide URL as canonical. A fresh Chrome document contained the matching Helpful content system heading with the fragment identifier. This establishes that the fragment named an existing section in the tested document. The browser check did not measure viewport alignment or how often readers used the route. Former helpful content FAQ (https://developers.google.com/search/help/helpful-content-faq) · Ranking systems guide section (https://developers.google.com/search/docs/appearance/ranking-systems-guide#helpful-content) The same run checked two related routes for context. The older core-updates address redirected once to the current core-updates guide and returned 200. The people-first content guidance returned 200 directly. They remain distinct resources. The observed FAQ destination shows why an editor should preserve the specific reader intent when consolidating. Sending a reader to a broadly related guide or section can change which answer they see first. Current core-updates guide (https://developers.google.com/search/docs/appearance/core-updates) · People-first content guidance (https://developers.google.com/search/docs/fundamentals/creating-helpful-content) Update the places that still point to the old article Change the internal links you control to point to the current address. Check navigation, related-article cards, editorial references and any XML sitemap that lists the retired article. Preserve the redirect for external links and bookmarks. Record which links are outside your control so the publishing owner can distinguish completed updates from channels where the redirect still carries the journey. Google recommends directing internal links to the preferred canonical. Google canonicalization guidance (https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) Public launch communications can help readers find new material while old links are still circulating. What’s On’s coverage of Emirates Woman’s website launch embeds the publication’s official Instagram reel. That illustrates the communication side of a change. The coverage supplies no evidence about how any old article address redirects. For a publication that uses social or newsletters, check the saved article links independently and update the channels the editorial team controls. What’s On coverage with the official Emirates Woman reel (https://whatson.ae/2022/05/luxury-fashion-magazine-emirates-woman-launches-new-website/) Use a separate check for links within the old article if they supply a useful next step. When the replacement merges a step-by-step guide and an FAQ, preserve the practical next action beside the answer that needs it. Confirm that links to supporting documents, related services or forms still point to the correct edition. A technically correct redirect still leaves an editorial gap if the replacement drops the resource that made the original article useful. Check what happens to the article date and claims during the merge. Carry forward a still-valid fact with its source and update information that changed. If the old article described a seasonal offer, show the scope of any historical references in the new copy. The replacement should help a returning reader identify which information applies now. A redirect tells the browser where to go. The opening paragraph, section label and date tell the reader why this is the right place. View the selected official Instagram post (https://www.instagram.com/reel/Cd5WIJCD9sr/) Official Emirates Woman Instagram reel embedded in coverage of its website launch. Verify the reader’s route after release Use an Article replacement record with the old URL, previous question, intended replacement, final heading, expected status and owner. Add the observed response chain, final content and the checks you ran after deployment. If you have authorised logs, look for requests to the old address and check their outcome at the relevant layer. A request to the old path shows it was used. Evidence for the destination is a separate observation unless your records can connect them reliably. For a replacement that will be edited frequently, make the fragment part of the release test. Editors sometimes rename headings or regenerate identifiers during a redesign. Keep a stable anchor when it continues to serve the original reader. If the section moves, update the route and check the old link again. An HTTP status check alone may still pass while the browser can no longer find the target heading. If you have an authorised Search Console property, inspect old and new URLs separately when you need search evidence. The live result and indexed result may refer to different observations. Record the dates and the exact address the platform reports. A successful redirect and browser test can close the immediate delivery check while you wait for updated platform evidence. Google Search Console URL Inspection (https://support.google.com/webmasters/answer/9012289?hl=en) If a staged test succeeds, repeat it against the public route after release. Production redirect rules, caches and application routes can differ from the staging configuration. Save the public response and the browser result together. A rollback plan should identify who can restore the previous route and how they will check that it serves the intended page. Close the editorial task when the old link reaches the intended answer, the new page serves that answer on its own and links you control point to the right place. When an old page still receives meaningful traffic, keep the route in the periodic checks for shared links. That makes the record useful long after the content merge has shipped. AI Visibility is published by Lunasol, which offers GEO and AEO services. The worked example uses public documentation, HTTP and a clean browser observation. About AI Visibility (https://aivisibility.ae/about/)