diff --git a/about/intro.md b/about/intro.md
index 77798b45..4888c9ed 100644
--- a/about/intro.md
+++ b/about/intro.md
@@ -121,7 +121,7 @@ You can identify pyOpenSci packages that have been peer-reviewed by the green
:::{figure-md} pyos-badge
:class: myclass
-
+
pyOpenSci Peer Review Badge
:::
diff --git a/appendices/package-approval-template.md b/appendices/package-approval-template.md
index 42e12450..61c2e826 100644
--- a/appendices/package-approval-template.md
+++ b/appendices/package-approval-template.md
@@ -9,7 +9,7 @@ There are a few things left to do to wrap up this submission:
- [ ] Activate [Zenodo](https://zenodo.org/) watching the repo if you haven't already done so.
- [ ] Tag and create a release to create a Zenodo version and DOI.
-- [ ] Add the badge for pyOpenSci peer-review to the README.md of . The badge should be `[![pyOpenSci](https://tinyurl.com/y22nb8up)](https://github.com/pyOpenSci/software-review/issues/issue-number)`.
+- [ ] Add the badge for pyOpenSci peer-review to the README.md of . The badge should be `[![pyOpenSci Peer-Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/issue-number)`.
- [ ] Please fill out the [post-review survey](https://forms.gle/BLGVCfUdiJHS5YJY7). All maintainers and reviewers should fill this out.
diff --git a/how-to/author-guide.md b/how-to/author-guide.md
index 42af3ee7..ec04e5c7 100644
--- a/how-to/author-guide.md
+++ b/how-to/author-guide.md
@@ -250,7 +250,7 @@ Once your package is approved, a few things will happen:
1. We will ask you to ensure that your package is being tracked / archived using
Zenodo. You will then want to created a tagged release representing the version of the
package accepted by pyOpenSci.
-1. We will ask you to add the pyOpenSci badge [![pyOpenSci](https://tinyurl.com/y22nb8up)](https://github.com/pyOpenSci/software-review/issues/issue-number) to the
+1. We will ask you to add the pyOpenSci badge [![pyOpenSci Peer Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](https://github.com/pyOpenSci/software-review/issues/issue-number) to the
top of your **README.md** file.
1. We will promote your package on our social media channels!
1. We will invite you to write a blog on our website spotlighting your package. The blogs that our maintainers write are some of the most popular content on the website!
diff --git a/how-to/editors-guide.md b/how-to/editors-guide.md
index 1227d5d8..068a956c 100644
--- a/how-to/editors-guide.md
+++ b/how-to/editors-guide.md
@@ -407,7 +407,7 @@ interested in this option, consider doing the following:
- Go to the repository settings in the "pyOpenSci" GitHub organization and give the author "Admin" access to the repository.
- Ask the author to:
- Change any needed links, such as those for CI badges.
- - Add pyOpenSci badge: `[![pyOpenSci](https://tinyurl.com/y22nb8up)](link-to-issue)`.
+ - Add pyOpenSci badge: `[![pyOpenSci Peer Reviewed](https://pyopensci.org/badges/peer-reviewed.svg)](link-to-issue)`.
- Re-activate CI services:
- For Travis, activating the project in the pyOpenSci account should be sufficient.
- For AppVeyor, tell the author to update the GitHub link in their badge, but do not transfer the project: AppVeyor projects should remain under the authors' account. The badge is `[![AppVeyor Build Status](https://ci.appveyor.com/api/projects/status/github/pyOpenSci/pkgname?branch=main&svg=true)](https://ci.appveyor.com/project/individualaccount/pkgname)`.
diff --git a/index.md b/index.md
index 34256d76..87f193be 100644
--- a/index.md
+++ b/index.md
@@ -115,7 +115,7 @@ programmers and researchers.
:::{figure-md} pyos-badge-home
:class: myclass
-
+
**pyOpenSci Peer Review Badge will appear on the README.md file of packages that have been
reviewed and vetted by us.**