diff --git a/.github/workflows/markdown-linter.yml b/.github/workflows/markdown-linter.yml
new file mode 100644
index 00000000..dcfd5d9b
--- /dev/null
+++ b/.github/workflows/markdown-linter.yml
@@ -0,0 +1,15 @@
+# This is a basic workflow to help you get started with Actions
+
+name: Check Markdown Links
+
+on: push
+
+jobs:
+  markdown-link-check:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@master
+    - uses: gaurav-nelson/github-action-markdown-link-check@v1
+      with:
+        folder-path: _posts
+        config-file: mlc_config.json
diff --git a/_posts/2020-12-16-github-codeql-pr.md b/_posts/2020-12-16-github-codeql-pr.md
index 151ca0d3..f2f2afef 100644
--- a/_posts/2020-12-16-github-codeql-pr.md
+++ b/_posts/2020-12-16-github-codeql-pr.md
@@ -13,7 +13,7 @@ image:
 
 ## Overview
 
-After virtually attending GitHub Universe last week and watching the [GitHub Advanced Security round-up](https://githubuniverse.com/GitHub-Advanced-Security-round-up/) and [Catching vulnerabilities early with GitHub](https://githubuniverse.com/Catching-vulnerabilities-early-with-GitHub/) sessions, it got me thinking: How do I block a pull request from being merged if the scans detect issues? I didn't think the [GitHub Docs](https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository#understanding-the-pull-request-checks) were incredibly straight forward on how this works.
+After virtually attending GitHub Universe last week and watching the [GitHub Advanced Security round-up](https://www.youtube.com/watch?v=T_-Tn81b4lc) and [Catching vulnerabilities early with GitHub](https://www.youtube.com/watch?v=l2epzyytPGE) sessions, it got me thinking: How do I block a pull request from being merged if the scans detect issues? I didn't think the [GitHub Docs](https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository#understanding-the-pull-request-checks) were incredibly straight forward on how this works.
 
 I knew how to configure a branch protection rule in GitHub that enforces things such as a GitHub Action or Azure DevOps stage completes successfully, but what about code scanning? How configurable is it?
 
diff --git a/_posts/2021-01-25-trac-to-github.md b/_posts/2021-01-25-trac-to-github.md
index 44281858..4ed27734 100644
--- a/_posts/2021-01-25-trac-to-github.md
+++ b/_posts/2021-01-25-trac-to-github.md
@@ -14,7 +14,7 @@ We were working with a client who was migrating off of their old Trac server, an
 
 ## Tools
 
-There are plenty of tools out there on GitHub ([svigerske/trac-to-github](https://github.com/svigerske/trac-to-github), [robertoschwald/migrate-trac-issues-to-github](https://github.com/robertoschwald/migrate-trac-issues-to-github), [hershwg/github-migrate-trac-tickets](https://github.com/hershwg/github-migrate-trac-tickets)... some of them require [XML-RPC](https://trac-hacks.org/wiki/XmlRpcPlugin), which I had a heck of a time installing on my Apache Trac webserver, so I wasn't able to test those.
+There are plenty of tools out there on GitHub ([svigerske/trac-to-github](https://github.com/svigerske/trac-to-github), [robertoschwald/migrate-trac-issues-to-github](https://web.archive.org/web/20200912010021/https://github.com/robertoschwald/migrate-trac-issues-to-github), [hershwg/github-migrate-trac-tickets](https://github.com/hershwg/github-migrate-trac-tickets)... some of them require [XML-RPC](https://trac-hacks.org/wiki/XmlRpcPlugin), which I had a heck of a time installing on my Apache Trac webserver, so I wasn't able to test those.
 
 The two I have tested are:
 
diff --git a/mlc_config.json b/mlc_config.json
new file mode 100644
index 00000000..529dcce0
--- /dev/null
+++ b/mlc_config.json
@@ -0,0 +1,8 @@
+{
+	"replacementPatterns": [
+		{
+			"pattern": "^/",
+			"replacement": "https://josh-ops.com/"
+		}
+	]
+}
\ No newline at end of file