---
title: "Swimburger - Blog - Documentation"
description: "Swimburger.net is a blog about .NET, cloud, web development, and whatever comes across Swimburger's plate. Swimburger.net is run by Niels Swimberghe."
canonical: "https://swimburger.net/blog/documentation"
---

[

<picture><img class="blog-post-card__image" src="/cdn-cgi/image/width=250,format=auto,quality=90,height=250,fit=cover,gravity=0.5x0.5/media/1uilg00p/thumbnail-optimized.png" srcset="/cdn-cgi/image/width=250,format=auto,quality=90,height=250,fit=cover,gravity=0.5x0.5/media/1uilg00p/thumbnail-optimized.png 250w, /cdn-cgi/image/width=375,format=auto,quality=90,height=375,fit=cover,gravity=0.5x0.5/media/1uilg00p/thumbnail-optimized.png 375w, /cdn-cgi/image/width=500,format=auto,quality=90,height=500,fit=cover,gravity=0.5x0.5/media/1uilg00p/thumbnail-optimized.png 500w" sizes="250px" width="250" height="250" alt="PowerShell logo" decoding="async" loading="lazy" style="background-color:#2D2D2D"></picture>

## PowerShell Script: Scan documentation for broken links

10/2/2020 - PowerShell

A lot of documentation will link to other locations on the web using URL's. Unfortunately, many URL's change over time. Additionally, it's easy to make typos or fat finger resulting in incorrect URL's. Here's a small PowerShell script you can run on your documentation repositories and will tell you which URL's are not resolving in a proper redirect or HTTP StatusCode 200



](/blog/powershell/powershell-script-scan-documentation-for-broken-links)