When a blog changes URLs, categories, domains, or article structure, old internal links can quietly send readers to redirects, irrelevant pages, or nowhere at all. This review workflow shows how to find affected links, verify redirect and canonical behavior, update navigation and anchor text, and maintain a repeatable internal link change log.
Overview
Internal links are part of your blog’s navigation system. They help readers move from one article to another and give search engines context about how pages relate. A site change can weaken that system even when every new URL appears to work in a browser.
For example, a link may still resolve through a redirect, but it may point to an outdated category, use anchor text that no longer matches the destination, or create a longer path than necessary. A deleted article may leave broken links in older posts, landing pages, menus, author archives, and related-content blocks.
The goal of blog link maintenance is not to replace every URL blindly. It is to decide what each old link should do now, update the links that matter, and record the decision so the same issue does not have to be investigated again. A useful process combines a URL export, a crawl or link report, manual checks for high-value pages, and a short change log.
If you are building a broader system, use this internal linking workflow for a blog alongside the migration-specific checks below.
What to track
Start by creating a list of URLs affected by the site change. Include old and new article URLs, category and tag paths, the previous and current domain if applicable, merged articles, deleted pages, and any changed pagination or archive paths. Exporting this list from the CMS, redirect manager, sitemap history, or migration spreadsheet is usually more reliable than relying on memory.
Next, identify where those URLs are used internally. A crawler or CMS search can locate links in article body copy, navigation, footer menus, breadcrumbs, author pages, category pages, related-post modules, image links, and calls to action. Track at least these fields:
- Source URL: the page containing the internal link.
- Linked URL: the old or current destination found in the source.
- HTTP result: whether the link returns a successful page, redirect, error, or unexpected destination.
- Final URL: the destination after redirects are followed.
- Canonical target: the preferred URL declared by the destination page, when available.
- Anchor text: the visible wording of the link and whether it still describes the destination.
- Link location: body copy, navigation, related content, breadcrumb, or another component.
- Action and owner: update, retain, remove, replace, or investigate, plus the person responsible.
Prioritize links from important or frequently visited pages first. A link in the main navigation, a popular evergreen article, or a conversion path generally deserves earlier attention than an isolated link in an old archive. For a content-focused review, a keyword extractor can also help identify whether new anchor wording reflects the topic of the destination, but use editorial judgment rather than forcing keywords into every link.
Decision table for common site changes
| Change | Recommended internal-link action | Verification |
|---|---|---|
| URL changed, page remains the same | Update internal links to the new direct URL. Keep a redirect from the old URL when external or bookmarked traffic may still use it. | Confirm the new URL loads directly and its canonical target is consistent. |
| Category renamed | Update category links, breadcrumbs, menus, and relevant copy. Check whether the category’s purpose or content scope also changed. | Review the new archive and confirm that links do not lead to an empty or unrelated listing. |
| Article deleted | Remove the link or replace it with the closest useful page. Do not redirect every deleted article to the homepage by default. | Read the surrounding sentence to ensure it still makes sense after removal or replacement. |
| Articles merged | Link to the surviving, more complete article and revise anchor text. Redirect the retired article if it has a meaningful replacement. | Check that the surviving page covers the intent promised by the old link. |
| Domain moved | Convert internal links to the new domain and check absolute URLs in templates, feeds, structured content, and downloadable resources. | Confirm no important internal links still resolve to the old domain or create redirect chains. |
Cadence and checkpoints
Run the first review immediately after a migration, redesign, URL change, or content consolidation project. Do not wait for a routine crawl if the site structure has changed. A practical post-change workflow has four passes.
- Export and compare: compare the old URL inventory with the new one. Mark added, removed, renamed, merged, and unchanged pages.
- Crawl internal links: find broken links, redirecting links, redirect chains, links to non-preferred URLs, and unexpected cross-domain destinations.
- Review high-value templates: check menus, breadcrumbs, category pages, related-post modules, footer links, and any reusable component that can multiply one error across the site.
- Re-crawl after edits: verify that updates were published and that the final destination, canonical target, and visible anchor text are correct.
After the initial repair, schedule a lightweight monthly or quarterly review. Monthly checks suit sites that publish frequently or change categories often. Quarterly checks may be sufficient for a stable blog. Also review links after a platform update, navigation redesign, domain migration, batch URL edit, or article merge project.
Use your Search Console or analytics reports as supporting evidence, not as a complete link inventory. Those systems can help surface pages with declining visibility, unexpected redirects, or visits to old URLs, while a crawler or CMS export shows where internal links are actually placed.
How to interpret changes
A redirect is not automatically a problem. If an old URL has a clear, relevant replacement, a single redirect can preserve a useful path for visitors who follow an old link. However, internal links should normally point directly to the current destination so readers and crawlers do not need an unnecessary extra request.
Investigate redirect chains, loops, and redirects that end on an unrelated page. A redirect to a category, homepage, or generic article may be a poor replacement when the original page had a specific purpose. Treat an unexpected canonical target similarly: determine whether the page was intentionally consolidated or whether the canonical setting is inconsistent with the link structure.
Broken links require context. Replace a deleted article with another page only when the new page answers the same question or supports the same claim. If no suitable replacement exists, remove the link and edit the sentence so it remains complete. For merged content, update both the destination and the anchor text; wording such as “read the original setup guide” may be misleading when the destination is now a broader reference article.
When many links fail at once, look for a shared cause before editing individual posts. A changed URL pattern, plugin setting, category base, or reusable template may have created the problem. Fixing the source system first can prevent the same error from returning.
Internal link change log template
Keep a simple record in a spreadsheet, project tracker, or repository. The log should be easy to update during every migration and easy for another editor to understand later.
Date | Source URL | Old link | New link | Link location | Reason | Redirect checked | Canonical checked | Status | Reviewer
YYYY-MM-DD | /article-a | /old-guide | /new-guide | Body copy | URL changed | Yes | Yes | Published | Initials
Add a migration or project name when several changes are happening at once. For complex work, include the old and new anchor text, a ticket number, and the date of the next verification crawl.
When to revisit
Revisit this process on a monthly or quarterly cadence, depending on publishing volume and site complexity. Schedule an immediate review when you change URL patterns, rename categories, merge or delete articles, redesign navigation, move domains, change CMS platforms, or introduce a new related-content component.
At each review, begin with the change log and the current URL export rather than repeating the entire investigation from scratch. Filter for unresolved items, recently changed URLs, and links that still return redirects or errors. Then sample important pages manually to confirm that the link is useful in context, not merely technically valid.
- Export current URLs and compare them with the previous review.
- Run a crawl or CMS link search for changed and redirected destinations.
- Repair broken, indirect, irrelevant, or outdated links.
- Check navigation, breadcrumbs, related posts, and high-value articles.
- Re-crawl, record the result, and assign a date for the next review.
A consistent log turns internal link maintenance into a manageable publishing workflow. It also makes future migrations safer: editors can see why a link was retained, replaced, or removed, while developers and content owners share the same before-and-after record.
For related publishing checks, pair this process with a blog post SEO audit checklist and a content performance review. Together, they help you maintain both the technical paths between articles and the usefulness of the content those paths connect.