Broken links and missing assets create two problems at once: visitors hit dead ends, and crawlers waste time following URLs that do not lead to useful content. HTTPS problems can be even more disruptive because they can block access entirely or trigger browser warnings.

Broken internal links

A link that points to a 404, 410 or server error should be fixed at the source. Update it to the correct destination when a replacement exists, or remove it if the referenced resource no longer belongs in the page.

Missing images and assets

A broken image can come from a deleted media file, an incorrect path, a migration mistake or mixed HTTP/HTTPS URLs. Check the actual image URL, not just the page HTML. If the file exists, verify permissions and cache behavior.

HTTPS and redirect consistency

Every important public URL should have a predictable secure destination.

• HTTP should redirect cleanly to HTTPS.
• Avoid unnecessary redirect chains.
• Canonical URLs should use the final HTTPS version.
• Internal links should point directly to the preferred destination when possible.

Quick workflow

1. Scan an important page.
2. Open each reported broken URL directly.
3. Fix the source link or restore the missing resource.
4. Review redirects and HTTPS consistency.
5. Purge caches and run the scan again.

FAQ

Are all redirects bad?

No. A single intentional redirect is normal; long chains add latency and complexity.

Can cached pages hide a fixed broken image?

Yes. Purge page/CDN caches after changing asset URLs.

Should I redirect every deleted page?

Only when there is a genuinely relevant replacement. Otherwise a clear 404 or 410 can be appropriate.

Bottom line

Fix broken paths at the source and keep internal links pointing directly to stable HTTPS destinations. Open Site Health Checker.