<?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[HostAndRank]]></title><description><![CDATA[Practical WordPress and static hosting handovers for agencies. Follow real redirect, maintenance and enquiry checks and see what each result proves.]]></description><link>https://hostandrank.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 15:41:48 GMT</lastBuildDate><atom:link href="https://hostandrank.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[What to test before handing a WordPress site back to its owner]]></title><description><![CDATA[Ask two people to open the same website after a handover and they can give you two honest, conflicting answers. The site owner uses a bookmark saved years…]]></description><link>https://hostandrank.hashnode.dev/what-to-test-before-handing-a-wordpress-site-back-to-its-owner</link><guid isPermaLink="true">https://hostandrank.hashnode.dev/what-to-test-before-handing-a-wordpress-site-back-to-its-owner</guid><category><![CDATA[WordPress]]></category><category><![CDATA[Web Hosting]]></category><dc:creator><![CDATA[John Bedford]]></dc:creator><pubDate>Sun, 22 Nov 2026 11:21:21 GMT</pubDate><content:encoded><![CDATA[<p>Ask two people to open the same website after a handover and they can give you two honest, conflicting answers. The site owner uses a bookmark saved years ago. The agency types the new address into a clean browser. A green homepage tells you very little about the first person’s experience. A useful handover starts with the addresses and tasks a client already relies on.</p>
<p>Fieldwork Studio is our demonstration WordPress site. Its old bulletin lived at /studio-bulletin/ and its replacement is /launch-notes/. We followed the old address, recorded the permanent redirect and then opened the destination. The old page returned 301 and the destination returned 200. That sequence matters. A redirect can send a reader to an error page just as easily as it can send them to the right story. We also read the destination to confirm that the launch notes were actually there.</p>
<p>Use that pattern for the client’s most important journey. For an agency it might start with an old project page that still appears on printed material. For a local business it might start with an opening-hours link in a customer’s phone. Write down the original address, expected destination and what you should see. Include at least one inner page. Share that short list with the person who knows the business before declaring the move complete.</p>
<p>Then follow a task past the browser. Send one agreed test enquiry with an identifiable subject. Record separately when the form accepts the message and when the intended inbox receives it. Ask the recipient to check the reference, especially if the inbox forwards mail elsewhere. A success screen alone cannot establish delivery.</p>
<p>Finish with a maintenance example the client can find later. In Fieldwork, the Classic Widgets update had an approval, a backup and a post-update check. Give the owner the route to that record along with their WordPress sign-in. When the next update arrives, they can make a decision with the previous one in front of them. If you are comparing hosting for that kind of handover, start with the plan and its client workspace.</p>
<p><a href="https://hostandrank.com/fieldwork-studio">Inspect the Fieldwork Studio demonstration</a></p>
<p><a href="https://hostandrank.com/journal/ref/hostandrank-01">Compare client hosting plans</a></p>
]]></content:encoded></item></channel></rss>