Trace the link from source to destination
Open the page containing the link and confirm what it promises. Follow its destination and note the final URL, observed response and content. A link can return a successful response yet still land on the wrong service. Conversely, a redirect can be entirely intentional. For a phone or email action, test the appropriate behavior separately; those actions are not ordinary webpage destinations that a source crawler can evaluate in the same way.
Prioritize shared navigation and contact paths
A broken link repeated in a header or footer can affect many pages. Repairing its shared source is usually more useful than editing individual copies. Next check service cards, location pages and links in active content. For example, if a quote page moved from /estimate/ to /contact/, update the shared call to action and verify the new page. Keep the destination aligned with what the button says it will do.
- Check the header, footer and main service links.
- Inspect important forms and downloadable documents.
- Retest any shared component after changing it.
Choose a repair based on intent
Update a link when the correct current destination already exists. Restore a page when it was removed accidentally and still serves a real purpose. Use a redirect when an old URL has a relevant replacement and visitors may still arrive there. Remove a link when the referenced resource is genuinely retired without a suitable alternative. Avoid redirecting every error to the homepage; that can leave the user's original question unanswered.
Distinguish repeatable failures from uncertainty
Timeouts, access restrictions and temporary server problems may prevent a reliable destination check. An unknown result is not evidence that the link passed. Repeat the check where appropriate and inspect the actual browser behavior before changing infrastructure or removing a resource. A public audit also has a bounded sample and cannot certify every external destination or JavaScript action. ColbySEO's report identifies the URLs and evidence it actually collected.
Verify the live repair, then save the result
After publishing, follow the link again from its original page. Confirm the correct final destination and make sure the repair is live outside your editor preview. If you changed a shared menu, check more than one route. Run the free website report for a new public sample and keep the saved PDF with your repair notes. When requesting help, share the source URL, failing destination and intended customer task so the issue can be scoped clearly.
Common questions
Is every redirect a broken link?
No. Redirects can preserve access after a URL change. Inspect whether the final destination is relevant and works, and update internal links to the intended current URL where practical.
Should a deleted service page always redirect to the homepage?
No. Choose a relevant replacement if one exists. If the page is truly gone without an equivalent, an appropriate removal response can be clearer than an unrelated destination.
Will the report find every broken link?
No. The public crawl checks a limited sample, up to 60 public pages, and some destinations cannot be assessed conclusively. Review coverage and manually test important customer actions.