What is link reclamation?
Repair the intended reference
- Confirm the old reference
Open the referring page and verify the actual destination.
- Inspect the destination
Identify a broken, moved, incorrect, or intentionally removed resource.
- Equivalent replacement
Use a relevant redirect or ask the publisher to correct the destination.
- No suitable replacement
Keep an honest missing-resource outcome instead of sending every old link to the homepage.
Lost references and broken destinations
Google’s link guidance supports usable destinations and clear context. Its redirect documentation explains ways to move resources and indicate the intended new destination. These principles apply when a real old reference should lead to an equivalent current page. Reclamation can involve a redirect on your site or a polite correction by the referring publisher.
A link disappearing from an index is not proof that the publisher removed it, so verify the live page before requesting changes.
An illustrative repair after a website move
Verify the old reference and relevant replacement
Confirm what changed in the live route. Inspect the referring page, old address, and final destination rather than treating an index alert as proof of removal. Decide whether you control the correction or need an editor’s help. A relevant destination should preserve the original information task.
- Open the source page and confirm whether the reference is missing, incorrect, or simply absent from a report.
- Check the old destination’s response and find the genuinely equivalent current resource.
- Implement an appropriate redirect when you control the move, or request a factual correction.
- Retest the full route and update internal links to the final destination.
Start with our website SEO checker. The website SEO checker can assist with an initial site-side review. Source-page corrections and full redirect-chain verification require direct checks of the referring link and destination responses.
Respect editorial decisions and avoid irrelevant redirects
An editor can remove a reference for valid reasons, and the business is not entitled to its restoration. Avoid unrelated redirects or chain-heavy fixes. Restoring a route improves access; its effects on rankings, traffic, and customer inquiries require separate observation.
Keep a URL map when moving important resources. It helps the business repair links in published articles, past estimates, and customer messages without redirecting everything to a generic page.
What are you trying to reclaim?
Reclamation tries to restore the useful route or reference that previously existed. First establish what was lost and why it mattered to the reader. A removed citation and an inaccessible destination are different problems. The appropriate action depends on who controls the failure and whether the original information still deserves a place in the source passage.
- A publisher can retain its anchor while your website removes the destination.
In that case, the existing reference has not necessarily been lost at the source. Repairing your own route may restore access without requiring the publisher to edit its article.
- The publisher can also remove the anchor while leaving the business name in the text.
That may reflect an editorial decision rather than a technical error. Verify the change before asking for restoration, and explain the practical purpose the reference would serve today.
- A wrong destination presents another case.
A reference might point to a similarly named company or to an unrelated page on your site. The correction concerns accurate identification or task completion. It should not be framed as an entitlement to additional ranking credit.
- The backlink record helps locate an existing external reference, but it does not prove the publisher intended that reference to remain indefinitely.
Reclamation requires a current editorial justification as well as evidence of the prior implementation.
How do you confirm whether a link was genuinely lost?
Confirm loss by inspecting the live source and comparing it with reliable earlier evidence. A reporting platform may stop showing a link for reasons unrelated to a publisher edit. Record the collection methods and dates. If earlier evidence is unavailable, describe the current observation rather than confidently reconstructing a change that you cannot establish.
- Open the source URL from the report.
Search the page for the business name and inspect the surrounding passage. A redesigned article may move its references into a different component. The reference could still exist even if the visible layout has changed substantially.
- Inspect the anchor rather than relying only on its displayed wording.
A publisher might change the text while preserving the destination. An image link can also identify the resource differently from the sentence that previously contained the reference.
- Compare screenshots or saved markup if your organization has them.
A previous export is evidence of what a tool observed, not always a complete view of the page. Explain that distinction when the earlier record is less direct than the current browser inspection.
- Google’s Links report documentation states that the report is a sample and can contain historical references.
It groups data rather than exposing every live anchor individually. Do not interpret absence from that report as proof that the publisher removed a link.
- A third-party platform can have its own discovery and recrawl limits.
Read its field definitions before comparing status changes. A link marked lost may reflect an inaccessible source request or a revised collection result. Confirm what the label means before translating it into an outreach claim.
- If the source page itself has moved, look for the publisher’s current version.
The citation may have moved with the article. Record the new source separately, then evaluate whether any actual correction remains necessary.
How can Search Console help locate a reference?
Search Console can supply candidate source pages for links to a destination you own. Use its reports to narrow the investigation, then inspect the source directly. The report’s grouping and historical coverage limit what it establishes. It is a research aid for locating references, rather than a live certificate that every listed link still works as displayed.
- Open Links and select the relevant externally linked destination.
Through Top linked pages, choose the page and then the linking site to reach available source URLs. Alternatively, start from Top linking sites and narrow to the relevant destination. Google’s documentation describes both routes.
- Save the source URL you intend to investigate.
Keep the report’s target information alongside it, but compare that information with the actual href on the source page. A reported target can reflect a redirect or canonical grouping rather than the exact address the publisher originally used.
- Use an export when it supports a repeatable investigation.
Preserve the collection date and identify the report used. Do not mix a recent observation with an older sample while presenting the combined file as a single current snapshot.
- Inspect any apparent destination mismatch manually.
The report can help identify where to look, but a successful browser route and the surrounding sentence establish the practical reading experience. The record should explain those observations separately.
- A backlink audit can combine these candidates with other relevant evidence.
Its scope should remain explicit. A list assembled from available tools does not become a complete inventory of every publisher reference merely because several sources were combined.
- Prioritize references that point to important information the business still maintains.
This is a practical resource decision rather than a claim that certain sources supply a known amount of ranking credit. The priority should be explainable through the actual customer or reader task.
What should you inspect on your own website first?
Inspect the old destination and the resource that should replace it before contacting the publisher. If your website caused the failure, fixing that route can restore several references at once. Check the response and the final content together. A successful request to the wrong page does not preserve the original purpose of the external citation.
- Open the old URL in a browser and note whether the address changes.
Use the Network panel if you need to understand the response or redirect route. Inspect the main document request separately from images or scripts that may fail without making the page unavailable.
- Search your current site for the resource’s topic and distinctive title.
A redesign may have changed the folder or naming convention while preserving the information. Compare the current page with the task promised by the source passage before treating it as an equivalent replacement.
- Check whether the content still belongs online.
A guide that contains withdrawn advice may need revision before its route is restored. Reclamation should not revive inaccurate material simply because historical references point to it.
- If the resource was accidentally deleted, restoring it can be appropriate where the information remains accurate and useful.
Confirm the publication decision with the content owner. Do not silently recreate a retired document without understanding why it was removed.
- For an evergreen resource, the subject may remain useful while individual details change.
Update those details before restoring access. The label evergreen does not remove the need to check factual accuracy after a move or deletion.
- Finally, review the destination’s own onward links.
A repaired landing page that directs readers to another missing document still leaves the task incomplete. Test the specific route the external citation expects readers to follow.
When is a redirect the appropriate repair?
A redirect is appropriate when the old address has genuinely moved to a relevant replacement and you control the route. Choose the implementation according to the intended move. Verify the final page’s purpose before applying the rule. Redirecting every missing resource to a generic commercial page can hide the error without restoring what readers came to find.
- Google’s redirect guidance distinguishes permanent and temporary moves.
A permanent resource move normally calls for a permanent redirect, while a temporary location has a different meaning. The decision starts with the actual move rather than a preference for a label in an audit report.
- Prepare an old-to-new URL map that records the resource purpose.
A title match is an initial clue, not sufficient proof of equivalence. Verify that the replacement still supplies the cited instructions or evidence before approving the mapping.
- Consider a hypothetical roofing preparation guide moved into a new learning section.
The new version covers the same preparation task and corrects outdated details. Mapping the old address to that guide preserves the reason a neighborhood publication cited it.
- Contrast that with a discontinued rebate page redirected to a quote form.
The old reference may have promised eligibility information that no longer exists. A quote form does not fulfill that promise. The better action can be to explain the discontinuation and ask the publisher to revise the passage.
- Test for unintended chains or loops.
A rule can point to another address that itself redirects, particularly after several redesigns. Document the complete route and simplify it where appropriate so the implementation reflects the current intended destination clearly.
Why is a canonical declaration not the same repair?
A canonical declaration identifies a preferred representative among suitable duplicate or similar URLs. It does not function as a browser redirect that sends a reader from a broken address to a working replacement. Choose the remedy according to the actual problem. A citation that leads to a missing page needs an accessible route, not an unrelated canonical assertion.
| Point to consider | Explanation and application |
|---|---|
| Google’s canonicalization guidance describes signals used to select a representative URL. | That selection is separate from the browser’s destination when someone clicks a publisher’s link. Confusing the two can leave the reader route broken while the site reports a preferred URL elsewhere. |
| If both old and new pages remain accessible with similar content, evaluate whether duplication or an intended move is the real issue. | The publishing plan should determine whether the old version remains useful. Do not apply a canonical declaration solely because external links use an inconvenient address. |
| If the old URL returns an error, an element on the new page does not make the old response usable. | The developer needs to inspect the route itself. A content editor may be able to update a page setting but lack access to the necessary redirect configuration. |
| The canonical-tag decision should preserve a coherent set of signals. | It is not a way to tell visitors that an unrelated page is equivalent. Keep the content relationship explicit and verify what the old address actually serves. |
| Where uncertainty remains, ask the implementer to demonstrate the intended route in a browser. | A successful configuration save is not sufficient validation. The repair is complete only when the relevant address behaves as intended and the destination satisfies the reading task. |
| Keep canonical observations in the technical record if they affect the investigation. | Separate them from the outreach request. A publisher generally needs the accurate destination and a concise reason to update it, rather than an unexplained account of your site’s representative-URL settings. |
How do you handle a publisher’s wrong destination?
Handle a wrong destination as a factual correction supported by the source context. Identify the affected reference and provide the address that actually fulfills its purpose. Explain your affiliation and leave the publisher control over the wording. The request should correct the reader route rather than use an error to demand unrelated promotional changes or extra references.
- A publisher may accidentally link a business name to another company with a similar name.
Provide the official website and enough identifying context to establish the error. Do not turn that correction into a request to add claims about service quality or market position.
- A publisher can also link the right company to the wrong page.
A sentence promising a maintenance checklist should not lead to a recruitment page. Explain the mismatch and identify the current resource that provides the promised information.
- Check the replacement address immediately before sending it.
An outdated internal note can introduce another error. The business should not ask an editor to change a working reference to an unverified destination merely because that destination appeared in its outreach template.
- The anchor-text wording needs to match the corrected destination.
If the original words describe information the new page does not contain, the passage may need a change too. Let the editor choose accurate wording rather than insist on a commercial keyword phrase.
- Include the exact source page and location of the reference.
An editor responsible for many pages should not need to search the entire website for the business name. A specific section or sentence makes the correction easier to review.
- If the publisher chooses another accurate source, that can still resolve the issue.
The company is entitled to request factual accuracy, not to dictate every editorial destination. Record the actual correction without claiming that every repair must point to your preferred page.
What if the publisher deliberately removed the link?
A deliberate removal requires an editorial conversation rather than a technical repair demand. Ask whether the resource became unsuitable or whether the publication changed its linking practice. Review the concern before proposing restoration. The publisher may have a valid reason to retain the text without a link or to choose a different reference that better serves current readers.
- Read the revised passage first.
It may no longer discuss the subject your resource answered. Restoring the old anchor without changing the surrounding text could create a less coherent article than the editor’s revised version.
- If the editor explains that the resource was outdated, investigate the specific issue.
Correct the information because it affects readers, then show what changed. Do not ask for restoration based only on a newly changed date at the top of the page.
- A content-decay review can help when changed requirements or products undermined the old explanation.
The repair must address the substantive problem. The fact that a resource was previously cited does not establish that it remains an appropriate current reference.
- If the publisher has a general policy of limiting commercial links, respect that decision.
A useful mention can remain without a clickable reference. Do not repeatedly contact different employees in an attempt to bypass the publication’s stated position.
- For a previously paid placement, inspect the agreement and qualification rather than treating removal as an independent editorial mistake.
The commercial obligations need their own review. A contractual disagreement is not resolved by demanding an ordinary-link classification.
- The dofollow-link label should remain separate from the reason for restoration.
A reference can be useful with appropriate qualification. Reclamation does not justify asking a publisher to remove a qualification warranted by the actual relationship.
How do you prevent future losses during a website move?
Prevent avoidable losses by mapping important existing resources before changing their addresses. Preserve the reading task and test the actual routes after implementation. Update links you control directly. External editors can help with corrections, but your migration should not depend on every publisher responding before visitors can reach the information that your old URLs promised.
- Build the map from the current website and relevant external-reference evidence.
Include important downloadable documents as well as HTML pages. A redesign can preserve visible page content while inadvertently deleting a file that customer articles still cite.
- Assign responsibility for deciding each replacement.
A developer can implement a route, but the content owner needs to confirm whether the new resource fulfills the old purpose. A migration spreadsheet should not treat every deleted page as equivalent to the nearest service category.
- Review internal linking during the move.
Links within your own site should use the intended current destinations where practical. Relying on redirects for every navigation step can conceal outdated templates and complicate later maintenance.
- Test representative external entry points, including exact older addresses from published references.
Starting every test at the homepage misses the routes reclamation is meant to preserve. The relevant test begins where the visitor’s actual citation begins.
- Check downloads and fragment references separately.
A guide may still load while an anchor to a specific section stops working. The page-level route is then intact, but readers can lose the precise location the publisher intended to cite.
How do you prioritize and verify reclamation work?
Prioritize work according to the importance of the information and the clarity of the repair. Fix site-controlled errors before requesting changes from publishers where that resolves the route. Verify each completed action in the live environment. Report the restored access and any remaining limits, rather than assigning a speculative search value to every corrected reference or redirect.
| Point to consider | Explanation and application |
|---|---|
| A current preparation guide cited from a relevant article can merit prompt attention because readers still need its information. | A historical mention of a discontinued product may need a different response. The priority should reflect current usefulness, not just the number of references in an export. |
| Keep an action record with the source URL and old destination, the verified problem, and the proposed repair. | Identify who controls the change. This prevents repeated outreach when a developer’s route correction is the actual unresolved dependency. |
| After implementation, follow the source reference to its final destination. | Check the page’s content and any necessary onward steps. A redirect returning a successful response is incomplete evidence if the visitor still cannot access the cited document. |
| Inspect the live publisher edit when an editor confirms a correction. | An email acknowledgment can precede publication, and a CMS edit can contain an unintended address. Preserve the observed outcome and date rather than marking the case complete solely from the reply. |
| The link-building service should separate verified repairs from new editorial suggestions in its reporting. | Those activities solve different problems. A reclaimed route does not establish a new publisher endorsement, and a new mention does not prove an old failure was repaired. |
| A brand mention without a link may need no action when identification is already clear. | Keep those observations separate from confirmed broken references. This prevents a useful repair program from becoming an indiscriminate campaign to make every appearance of the business name clickable. |
| Close cases with a precise outcome. | Record a functioning redirect, a corrected publisher anchor, or an editorial decision to remove obsolete advice. A refusal can also close the case when no factual error remains. Reclamation is successful when the appropriate issue is resolved, not when every historical link is restored regardless of context. |
Related terms
Compare: Broken link building, Backlink audit, Unlinked brand mentions. Return to the Link building glossary.
Questions about Link reclamation
Can a permanent redirect repair an old link to an equivalent moved page?
Yes. A suitable permanent redirect can route visitors and search engines to the replacement. Verify the final destination and relevance.
Redirects and Google Search ↗Does a canonical tag send a visitor to the replacement page?
No. Canonicalization signals a preferred representative; it is not the browser navigation performed by a redirect.
How to Specify a Canonical with rel="canonical" and Other Methods ↗Does Search Console’s Links report list every external link?
No. Its link reporting is not a complete ledger. Confirm individual references on the referring page before claiming a link was lost.
Links report - Search Console Help ↗Should every deleted page redirect to the homepage?
No. Use a relevant replacement when one exists. An irrelevant destination can fail the original reader task and be interpreted as a soft 404.
Redirects and Google Search ↗Continue learning
Connect this to your website
- link-building service →
Prioritize verified lost references whose repair restores a relevant route for the original reader.
Sources
SEO Link Best Practices for Google ↗Accessed October 8, 2026Redirects and Google Search ↗Accessed October 8, 2026How to Specify a Canonical with rel="canonical" and Other Methods ↗Accessed October 8, 2026Links report - Search Console Help ↗Accessed October 8, 2026Published . Definitions and examples link to their supporting sources. Our SEO methodology →
