Link repairs: mapping and verification
A link-and-redirect task needs a clear mapping from the current address to the intended destination. Replacing every missing page with the homepage is not a meaningful repair when visitors were looking for a particular service or document.
What to prepare
- Identify up to ten pages to review; the task includes up to ten fixes or supported redirects in total.
- Supply intended replacements for missing or changed destinations.
- Identify any domain move or wider migration, which is outside this task.
Delivery and review
Separate a bad link from an old address
A link inside a page can be corrected in the editor. Redirecting an address people already know requires the platform’s supported redirect controls. Explain which case applies and preserve examples of the original URL, including any meaningful path.
Choose the closest genuine replacement
Match the old purpose to a relevant current page where one exists. An external supplier’s missing page cannot be repaired by changing their server. You may instead remove or replace your own link after agreeing an appropriate destination.
Test the agreed mapping
Open the old links and confirm the final page is the intended one. The handover records the agreed changes and loop checks. Large redirect migrations, lost-ranking recovery and domain moves are not included simply because several URLs are affected.
What to check
- Each repaired link reaches the agreed destination.
- Supported redirects do not send visitors around a loop.
- The change record identifies what was corrected and any unresolved external dependency.
Sources and further reading
Use the current product description and agreed terms for the scope of your order. Existing customers keep their original agreements.