<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[SalvageGrid]]></title><description><![CDATA[Field notes on website moves and content recovery. Learn to review a redirect map, test old URLs and verify the destination a reader actually reaches.]]></description><link>https://salvagegrid.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 20:03:42 GMT</lastBuildDate><atom:link href="https://salvagegrid.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How to tell whether a permanent redirect saved the right page]]></title><description><![CDATA[The cheapest redirect to write is often the least helpful to the reader. Imagine a studio with three old links in circulation for its bulletin, workshop…]]></description><link>https://salvagegrid.hashnode.dev/how-to-tell-whether-a-permanent-redirect-saved-the-right-page</link><guid isPermaLink="true">https://salvagegrid.hashnode.dev/how-to-tell-whether-a-permanent-redirect-saved-the-right-page</guid><category><![CDATA[Web Development]]></category><category><![CDATA[http]]></category><dc:creator><![CDATA[John Bedford]]></dc:creator><pubDate>Sun, 22 Nov 2026 11:21:21 GMT</pubDate><content:encoded><![CDATA[<p>The cheapest redirect to write is often the least helpful to the reader. Imagine a studio with three old links in circulation for its bulletin, workshop bookings and contact page. Sending all three to the homepage would make a redirect checker show movement. Only a person who knows what each link promised can say whether its new destination makes sense.</p>
<p>Use a two-column map to start. Put the exact old path on the left and the most relevant final page on the right. Keep a short note about the reader’s intent beside any disputed match. If a new page does not answer the same question, leave that row open for review. This is especially useful on restored websites where some old content survives and the new owner has chosen to retire the rest.</p>
<p>In the Fieldwork Studio demonstration, the old bulletin path is /studio-bulletin/ and the new path is /launch-notes/. We requested the old address without automatically following it and saw a 301 response. We then requested its destination, got a 200 response and checked that it contained the launch notes. That last read is worth doing even on a very small site. A successful response code can belong to a generic homepage or an empty template.</p>
<p>Before applying a batch, inspect the destination column for any page that is itself due to move. Follow one old address through to its final page and write down each step. If several old links lead to one new page, have the client confirm that the page covers each of the original purposes. Make a copy of the accepted map before applying it so that a later editor can see what was intended.</p>
<p>After release, pick an old link still used in an email, a brochure or a customer bookmark. Open it as a reader would and repeat the check. SalvageGrid’s site-move service gives an agency a place to review the map and check the result. Bring an old address you genuinely need to keep working.</p>
<p><a href="https://hostandrank.com/fieldwork-studio">Inspect the Fieldwork Studio demonstration</a></p>
<p><a href="https://hostandrank.com/journal/ref/salvagegrid-01">Open the SalvageGrid site move checker</a></p>
]]></content:encoded></item></channel></rss>