Create a Broken-Link and Redirect Audit for Marketing Websites

Overview

A repeatable audit for finding broken destinations, fixing redirects, and protecting campaign journeys after pages or offers change.

Why link maintenance affects more than SEO

A broken link is a broken promise in a customer journey. A person clicks a campaign email, directory listing, QR code, blog recommendation, or paid ad and reaches an error page or an unrelated destination. The immediate result may be frustration; the business may also lose an enquiry, waste paid traffic, or leave outdated information circulating.

Link audits should therefore combine technical checks with business context. A crawler can identify a 404 response, but it cannot always decide whether the best replacement is a new product page, a category page, a support article, or no redirect at all. The person reviewing the issue needs to know what the original link was intended to help the visitor do.

Build an inventory of high-value links first

Begin with destinations used in revenue or service workflows: active paid campaigns, email templates, booking links, contact forms, top organic landing pages, business profile links, printed QR codes, and partner referrals. Then include internal navigation, older articles, downloadable files, and archived campaign pages. Prioritising high-value routes gives a small team a manageable first pass.

Record the source URL, destination URL, placement, channel, owner, expected user task, last checked date, response status, and proposed action. For links inside content, record the page title and the nearby anchor text. For QR codes and print assets, record where the code appears and whether reprinting is possible. A destination inventory makes future audits faster because the team is not starting from zero.

Run technical checks and interpret results

Use a reputable crawler or link checker to test internal links and important external destinations. Review HTTP response codes, redirect chains, loops, timeouts, and links to insecure or unexpected domains. A 200 response does not guarantee a good destination: the page might load successfully while showing a discontinued offer, an empty template, or a misleading message.

Treat temporary failures cautiously. Rate limits, bot protection, transient server errors, and network timeouts can create false alarms. Recheck uncertain results at a different time or with a browser before changing production links. Avoid aggressive crawling that overloads a small website; use sensible request limits and follow the site's access rules.

Review redirects as a journey, not only a status code. A chain from an old URL through several intermediate pages adds fragility and can slow the visitor. Where appropriate, update the source link to the final destination and reduce unnecessary hops. Do not redirect every removed page to the homepage; an irrelevant redirect can confuse users and may be treated as a soft error by search engines.

Choose the right fix for each failure

If a page has a true replacement with the same intent, use a direct permanent redirect where the move is permanent and update internal links. If the page was removed and has no meaningful substitute, a clear not-found page may be better than sending visitors somewhere unrelated. If an external partner controls the destination, contact the owner or replace the link with a verified alternative.

For campaign pages, check dates, prices, eligibility, forms, and tracking parameters before redirecting. A replacement page that looks similar but no longer accepts the offer can still break the customer promise. Preserve useful query parameters when needed, but test the destination to ensure parameters do not expose sensitive data or cause unexpected behaviour.

Record the decision and its rationale. 'Fixed' is not enough when another person later asks why a page was redirected or retired. A short note such as 'old seasonal offer ended; current service page is not equivalent, so removed link and added an explanatory archive notice' is more useful than a status-only update.

Validate after changes and establish a cadence

After deployment, test the original URL, final destination, mobile layout, form submission, analytics event, and any conversion confirmation. Check representative links from the actual source placement, especially email clients, social profiles, and QR codes. A successful desktop browser test may miss a redirect issue in a mobile app or a parameter-dependent error.

Set a cadence based on risk. Review active campaign links before launch, important service and contact links monthly, and the broader site on a quarterly schedule or after a migration. Any major redesign, URL structure change, product retirement, or CMS migration should trigger an additional audit.

Track meaningful outcomes: high-priority broken links found, time to repair, redirects simplified, campaign journeys retested, and repeat failures by template or team. A falling number of repeat failures may show that publishing controls are improving. Raw link counts alone are less useful because a large site naturally contains more links.

Practical audit checklist

• Export high-value destinations and record the user task each link supports.
• Run a controlled crawl and group findings by severity, source page, and failure type.
• Manually verify ambiguous errors and check whether the replacement preserves intent.
• Fix internal source links, use relevant direct redirects, and avoid irrelevant homepage redirects.
• Retest mobile, forms, analytics, campaign parameters, and printed QR destinations where possible.
• Log the owner, decision, verification date, and next review trigger.

Worked example: an outdated service URL

A local repair company retires a seasonal inspection offer. A link checker finds old links from a blog, a paid ad, and a partner directory. The blog can be updated directly to the current inspection page, while the expired ad is paused because its price and promise are no longer valid. The partner directory is corrected by contacting its owner. The team tests the new page on a phone, submits the enquiry form, and confirms that the source campaign remains identifiable in analytics. Rather than redirecting every old URL to the homepage, it maps each source to a relevant outcome and records the decision. This prevents a technically tidy redirect from preserving a misleading offer.

Implementation note

Add a simple severity scale to the link register. A broken checkout, booking, or contact path should be handled before a low-traffic reference in an old article. Include the date a fix was verified and the person who tested it. When a template change creates many broken links, repair the template or publishing process before fixing each page separately. This reduces repeated work and helps the team distinguish a one-off stale destination from a systemic release problem.

Key Takeaways

• Prioritise links by customer and business impact, not only by the number of errors.
• A technically successful redirect can still be a poor user experience.
• Retest the whole conversion path after changing destinations.

Conclusion and Next Steps

Start with links that support enquiries, bookings, purchases, and active campaigns. Fix the underlying source as well as the destination, and record the result so the same failure does not return unnoticed. Make pre-launch link checks part of the publishing process.

References and Further Reading

• Google Search Central — Redirects and Google Search- Google Search Central — HTTP status codes and network errors- W3C — Web Accessibility Initiative