Link maintenance is the work of keeping a site's published routes understandable and dependable as its content changes. A renamed guide, retired service or duplicated campaign page can leave different systems describing different versions of the same destination. Start with a URL inventory and a clear decision for each route. This workflow helps a small team maintain those decisions; it does not guarantee search visibility.
Build an inventory with a purpose
Collect URLs from your publishing system, navigation, sitemap and campaign records. Include important destinations linked from your bio page, even when another service hosts them. For each entry, record its purpose, owner, current address, intended public status and last manual check. Separate a page's job from its headline so a renamed article remains recognizable in the record.
Add the response status and final destination when you inspect a URL. A browser may quietly follow several redirects, so seeing a page load does not tell you whether the original route still works cleanly. Prioritize booking, checkout, contact and heavily referenced resources before rarely used archive pages. Keep an explanation beside each planned change so another editor can understand it later.
Choose the preferred URL for duplicate content
A tracking parameter or alternate route may expose substantially the same content at several addresses. Identify the preferred public version, then inspect the page's canonical declaration and the URLs used in navigation. Google's canonicalization documentation describes redirects and canonical annotations as signals; Google ultimately selects the canonical. A declaration is not an instruction that guarantees selection.
Record why a duplicate exists before removing it. A campaign route might still be used in printed material or an email sequence. Ask the site maintainer to make the technical change, then update links you control to the preferred destination. Do not apply the same canonical to distinct articles simply because they cover related subjects; review whether their actual content serves the same task.
Distinguish a move from a removal
For a permanently moved resource, map the old address to its direct replacement. Avoid sending every retired URL to the homepage, where a visitor must restart their search. If there is no meaningful replacement, decide whether the material should remain as an honest archive or be removed. A redirect should express a real relationship between the old promise and the new destination.
Check the server response as well as the visible message. Google's HTTP status guidance explains how error responses affect crawling and indexing, and notes that a successful response alone does not guarantee indexing. A missing-page message served with a success status deserves investigation. Give visitors a useful way back to relevant content without disguising an unavailable resource.
Keep sitemap dates tied to real changes
Compare the sitemap against the inventory after a publication, move or removal. Check that its addresses represent the versions you intend to publish. Google's sitemap guidance says lastmod values should reflect significant page changes and be consistently accurate. Do not refresh every date merely because a build ran or the calendar changed.
Write down which event updates that value in your publishing process. Replacing a substantial section and fixing a template footer are different events. If your system cannot supply a trustworthy modification date, have its maintainer review the implementation instead of manufacturing recent dates to make the site look active.
Review crawl controls separately
Check robots rules and page indexing directives when a public resource appears inaccessible to search. Google's robots.txt introduction explains that blocking crawling is not a reliable way to keep a URL out of search results. Treat access control for private material as a separate requirement, rather than relying on a crawler instruction.
Finish each maintenance pass with a short change log: the URL, observed problem, chosen action, owner and verification date. Revisit changed routes from a phone and from an existing published link. Use the bio-page overview when checking your public entry point, and assign a fresh review whenever a destination's owner changes.