How do I recover broken backlinks after a site migration?

Create a URL-by-URL redirect map for valuable links to your former site. Send each moved page directly to its closest replacement, verify the final page and language, and update high-value references with the publisher when possible.

What causes the problem?

During a German-market migration, backlinks can point to a retired .de subdomain, an earlier German-language directory, or an old PDF path. A language selector, redirect chain, or generic brand homepage can make a technically successful request unhelpful to the original reader.

Step-by-step tutorial

  1. Start with evidence from the old site

    Download external-link target data from the old Search Console property and preserve the legacy sitemap. Add key referral URLs from approved analytics, regional associations, and partner documentation.

  2. Map by reader intent and language

    Record the old URL, link context, expected language, and closest current page. Ask the German editorial owner to review destinations with high business or reference value.

  3. Add permanent redirects for moved pages

    For a durable move, implement a server-side 301 or 308 directly to the replacement. Preserve a proper 404 or 410 for permanently removed content with no suitable equivalent.

  4. Verify the response and the page

    Load each important old URL and record its full redirect path, final status, content, and language. Align internal links and sitemap entries with preferred new URLs before asking partners to update their citations.

  5. Follow up on the references that matter

    Give each publisher the exact source paragraph and the new URL. When requesting an update from a German publisher, make it easy for them to check the replacement against the original topic.

Worked example

Reproducible test scenario using a placeholder host. Suppose a German trade body links to example.com/de/lieferanten-handbuch.pdf. The replacement is example.com/de/publikationen/lieferantenhandbuch. Your check should record one permanent redirect, a 200 response at the new address, German-language content, and continued access to the cited handbook edition.

Ten practical questions

What migration URLs should a Germany launch team test first?

Start with referral destinations used in German-language directories, partner documents, and association pages. An older guide can warrant priority if readers still depend on it.

Should old German links redirect to an English corporate site?

Map them to an appropriate German replacement when available. Review the original wording and choose a destination that serves the reader’s task. A generic language selector adds an unnecessary step.

How do we handle links to a previous handbook edition?

Retain the cited edition where it is still needed for reference and mark its date. If replacing the file, make past editions available or state exactly which parts changed.

Why did the old URL begin working and then fail again?

Check whether CDN rules, case normalization, or localization redirects run in different orders in staging and production. Re-test the exact source link with a clean browser session.

What if the retired URL has a fragment identifying a section?

Inspect the section referenced by the source and preserve a meaningful matching anchor on the new page when possible. Test the full link in a browser because fragments are handled by the browser.

What belongs in the redirect handoff spreadsheet?

Record the old URL, referring page, replacement, rationale, expected language, initial and final status, date, and owner. Include a release-test column for pages with live customer journeys.

How can we avoid losing source context on consolidated pages?

Add an identifiable subsection covering the original purpose and retain any relevant downloadable material. Validate the fit against each high-value source before mapping all old URLs to the combined page.

When do we contact a German publisher?

Start with links that remain actionable for customers, procurement staff, or members. Provide the exact page, old address, and new destination so an editor can verify it in a minute.

How long should we maintain the previous domain’s redirects?

Google generally recommends keeping them for at least a year. Renew legacy domain and certificate access for as long as users and sources still rely on those addresses.

How do we know a referral path is restored?

Open the external page, follow the live link, and verify the content and final response. Report link repairs separately from referral volumes and search visibility trends.

Frequently asked questions

Can I cover the main repairs without a paid tool?

Use Search Console, legacy URL inventories, and the browser network panel with authorized access to the relevant properties.

Should the XML sitemap list both old and new URLs forever?

Use the current sitemap to list preferred new destinations. Legacy redirects and a temporary migration workflow can be maintained independently.

Does a permanent redirect guarantee that traffic returns?

Traffic can change for many reasons. A permanent redirect restores the intended route when properly implemented, while search engines and readers act on their own timelines.

Scope and sources

Search Console data is sampled. A test records the redirect and page state for that request. It cannot establish complete link coverage, recover a removed publisher page, or predict rankings.

Next steps

How can I evaluate a backlink offer before paying for it? →

Explore SEO and GEO services for Germany →