Merge pull request #1578 from maxmind/greg/validate-internal-links

horgh · web-flow · commit f19b3dc397b8 · 2026-02-19T09:56:14.000-08:00
Validate internal links at build time and in CI
diff --git a/.github/workflows/links.yml b/.github/workflows/links.yml
@@ -6,24 +6,18 @@ on:
 jobs:
   linkChecker:
     runs-on: ubuntu-latest
-    permissions:
-      issues: write # required for peter-evans/create-issue-from-file
     steps:
       - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
         with:
+          submodules: true
+          fetch-depth: 0
           persist-credentials: false
 
-      - name: Link Checker
-        id: lychee
-        uses: lycheeverse/lychee-action@a8c4c7cb88f0c7386610c35eb25108e448569cb0
-        with:
-          fail: true
-          args: "'./**/*.md' './**/*.html'"
+      - name: Setup mise
+        uses: jdx/mise-action@6d1e696aa24c1aa1bcc1adea0212707c71ab78a8 # v3.6.1
 
-      - name: Create Issue From File
-        if: steps.lychee.outputs.exit_code != 0
-        uses: peter-evans/create-issue-from-file@fca9117c27cdc29c6c4db3b86c48e4115a786710
-        with:
-          title: Link Checker Report
-          content-filepath: ./lychee/out.md
-          labels: report, automated issue
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Check links
+        run: mise run check-links
diff --git a/content/geoip/geolite2-free-geolocation-data.md b/content/geoip/geolite2-free-geolocation-data.md
@@ -118,8 +118,8 @@ The method for updating the GeoLite databases depends on the database format
 you’re using. To help you decide which database format to use,
 [see the section above](#decide-how-you-want-to-use-geolite-databases).
 
-- [Learn how to update the binary database format for fast lookups at scale.](https://dev.maxmind.com/geoip/updating-databases/#using-geoip-update)
-- [Learn how to update the csv database format to join the data or import into SQL.](https://dev.maxmind.com/geoip/updating-databases/#directly-downloading-databases)
+- [Learn how to update the binary database format for fast lookups at scale.](/geoip/updating-databases/#using-geoip-update)
+- [Learn how to update the csv database format to join the data or import into SQL.](/geoip/updating-databases/#directly-downloading-databases)
 
 ### Look up IP addresses in the GeoLite databases
 
@@ -128,8 +128,8 @@ on the database format you’re using and what you’re using it for. To help yo
 decide which database format to use,
 [see this section above](#decide-how-you-want-to-use-geolite-databases).
 
-- [Use MaxMind’s client APIs to look up IP addresses in the binary databases for fast lookups at scale.](https://dev.maxmind.com/geoip/geolocate-an-ip/databases/)
-- [Learn how to import the csv format databases into MySQL or PostgreSQL.](https://dev.maxmind.com/geoip/importing-databases/)
+- [Use MaxMind’s client APIs to look up IP addresses in the binary databases for fast lookups at scale.](/geoip/geolocate-an-ip/databases/)
+- [Learn how to import the csv format databases into MySQL or PostgreSQL.](/geoip/importing-databases/)
 - If you’re using GeoLite in a plugin or application, check the installation
   instructions for your plugin.
 
@@ -142,11 +142,11 @@ decide which database format to use,
 MaxMind maintains client APIs in many popular languages to help you look up IP
 addresses in our web services quickly and easily.
 
-[Learn how to look up IP addresses in our web services.](https://dev.maxmind.com/geoip/geolocate-an-ip/web-services/)
+[Learn how to look up IP addresses in our web services.](/geoip/geolocate-an-ip/web-services/)
 
 MaxMind web services do support a client-side JavaScript lookup, but only for
 the paid GeoIP web services.
-[Learn more about client-side JavaScript lookups using the GeoIP web services](https://dev.maxmind.com/geoip/geolocate-an-ip/client-side-javascript/),
+[Learn more about client-side JavaScript lookups using the GeoIP web services](/geoip/geolocate-an-ip/client-side-javascript/),
 and [upgrade to GeoIP](https://www.maxmind.com/en/geoip-api-web-services).
 
 ## GeoLite database fields
@@ -171,8 +171,7 @@ field description.
       <tr>
         <td>
           <p>
-            <a
-              href="https://dev.maxmind.com/geoip/docs/databases/city-and-country/"
+            <a href="/geoip/docs/databases/city-and-country/"
               >GeoLite Country database</a
             >
           </p>
@@ -189,8 +188,7 @@ field description.
       <tr>
         <td>
           <p>
-            <a
-              href="https://dev.maxmind.com/geoip/docs/databases/city-and-country/"
+            <a href="/geoip/docs/databases/city-and-country/"
               >GeoLite City database</a
             >
           </p>
@@ -214,9 +212,7 @@ field description.
       </tr>
       <tr>
         <td>
-          <a href="https://dev.maxmind.com/geoip/docs/databases/asn/"
-            >GeoLite ASN database</a
-          >
+          <a href="/geoip/docs/databases/asn/">GeoLite ASN database</a>
         </td>
         <td>
           Provides the autonomous system number and organization for IP
@@ -250,8 +246,7 @@ GeoLite City web service, except as noted in the field description.
       <tr>
         <td>
           <p>
-            <a
-              href="https://dev.maxmind.com/geoip/docs/web-services/#geolite-country"
+            <a href="/geoip/docs/web-services/#geolite-country"
               >GeoLite Country web service</a
             >
           </p>
@@ -268,8 +263,7 @@ GeoLite City web service, except as noted in the field description.
       <tr>
         <td>
           <p>
-            <a
-              href="https://dev.maxmind.com/geoip/docs/web-services/#geolite-city"
+            <a href="/geoip/docs/web-services/#geolite-city"
               >GeoLite City web service</a
             >
           </p>
diff --git a/content/geoip/geolocate-an-ip/client-side-javascript.md b/content/geoip/geolocate-an-ip/client-side-javascript.md
@@ -221,7 +221,7 @@ need to break backwards compatibility with previous versions of the JavaScript
 API.
 
 Version 2.1 of the JavaScript API uses version 2.1 of the
-[GeoIP web services REST API](/geoip/geoip2/web-services/).
+[GeoIP web services REST API](/geoip/docs/web-services/).
 
 ### Browser support
 
diff --git a/content/geoip/release-notes/2013.md b/content/geoip/release-notes/2013.md
@@ -50,7 +50,7 @@ On July 30th, the GeoIP databases should return postals for Canada.
 
 {{< release-note date="2013-07-08" title="GeoLite2 City Database Available" >}}
 The
-[GeoLite2 City database](/geoip/geoip2/geolite2/ 'GeoLite2 Free Downloadable Databases')
+[GeoLite2 City database](/geoip/geolite2-free-geolocation-data/ 'GeoLite2 Free Downloadable Databases')
 is now available for download. This is the first database available in our new
 [MaxMind DB format](https://github.com/maxmind/MaxMind-DB 'MaxMind DB GitHub repository').
 {{</ release-note >}}
diff --git a/content/geoip/release-notes/2016.md b/content/geoip/release-notes/2016.md
@@ -55,8 +55,8 @@ already support this field.
 **For the CSV databases, a new `accuracy_radius` column will be added to the end
 of the IPv4 and IPv6 blocks files. Please test your integration to ensure
 compatibility before updating.** You may test your integration by downloading
-the [latest copy](/geoip/geoip2/geolite2/) of the GeoLite2 CSV database, which
-already has the accuracy_radius column appended.
+the [latest copy](/geoip/geolite2-free-geolocation-data/) of the GeoLite2 CSV
+database, which already has the accuracy_radius column appended.
 
 Target availability dates:
 
diff --git a/content/geoip/release-notes/2017.md b/content/geoip/release-notes/2017.md
@@ -29,8 +29,8 @@ http://js.maxmind.com/js/geoip.js. If you still have not upgraded your
 integration to use the
 [GeoIP2 JavaScript Client API](/geoip/geolocate-an-ip/client-side-javascript) or
 are encountering problems with your legacy GeoIP JavaScript services, you can
-find more information about what to do by clicking
-[here](/geoip/legacy/migrating-away-from-our-legacy-geoip-javascript-services/).
+find more information about what to do in
+[our developer documentation](/geoip/geolocate-an-ip/client-side-javascript).
 {{</ release-note >}}
 
 {{< release-note date="2017-10-10" title="Our Singapore server is live" >}} Our
@@ -101,9 +101,9 @@ DNS servers `8.8.8.8` and `8.8.4.4`. {{</ release-note >}}
 [GeoLite2 ASN database](/geoip/docs/databases) is now provided in a CSV format
 suitable for importing into a SQL database as well as a GeoLite2 ASN database in
 our MaxMind DB binary format. You can
-[download the database here](/geoip/geoip2/geolite2/). GeoLite2 databases may
-also be downloaded and updated with our
-[GeoIP Update program](/geoip/geoipupdate/). {{</ release-note >}}
+[download the database here](/geoip/geolite2-free-geolocation-data/). GeoLite2
+databases may also be downloaded and updated with our
+[GeoIP Update program](/geoip/updating-databases/). {{</ release-note >}}
 
 {{< release-note date="2017-05-08" title="Spectrum rebranding" >}} We've updated
 the ISP and Organization data to replace the _Charter Communications_ and
diff --git a/content/geoip/release-notes/2018.md b/content/geoip/release-notes/2018.md
@@ -62,7 +62,7 @@ to [redistribution license customers](https://www.maxmind.com/en/commercial-geo
 although anyone can continue to download the March 2018 GeoLite Legacy builds.
 Starting January 2, 2019, the last build will be removed from our website.
 GeoLite Legacy database users will need to switch to
-the [GeoLite2](/geoip/geoip2/geolite2/) or [commercial GeoIP databases](https://www.maxmind.com/en/solutions/ip-geolocation-databases-api-services)
+the [GeoLite2](/geoip/geolite2-free-geolocation-data/) or [commercial GeoIP databases](https://www.maxmind.com/en/solutions/ip-geolocation-databases-api-services)
 and update their integrations by January 2, 2019. Correspondingly, we have
 decided against removing latitude and longitude coordinates from the GeoLite2
 databases. We are in the process of reviewing coordinates used in all of our
diff --git a/content/geoip/release-notes/2019.md b/content/geoip/release-notes/2019.md
@@ -281,9 +281,9 @@ free GeoLite2 databases). {{</ release-note >}}
 {{< release-note date="2019-01-14" title="New GeoIP Update released" >}} We've
 released a new major version of GeoIP Update. This release adds support for
 Windows and has a new code base. You can find it on
-[GitHub](https://github.com/maxmind/geoipupdate). We’ve written an
-[upgrade guide](/geoip/geoipupdate/upgrading-to-geoip-update-4-x/) if you’re
-running an older version. {{</ release-note >}}
+[GitHub](https://github.com/maxmind/geoipupdate). See our
+[documentation](/geoip/updating-databases/) if you're running an older version.
+{{</ release-note >}}
 
 {{< release-note date="2019-01-14" title="Limiting availability of archived GeoIP databases" >}}
 In order to address new legal requirements, including the European Union's
diff --git a/content/geoip/release-notes/2024.md b/content/geoip/release-notes/2024.md
@@ -47,7 +47,7 @@ If you don't have an existing Snowflake account, you will need to create one
 before requesting access to the GeoLite datasets. Once approved, you’ll be able
 to query GeoLite data within Snowflake.
 
-[Learn more about Geolite on Snowflake on our developer portal.](https://dev.maxmind.com/geoip/geolite-on-snowflake/)
+[Learn more about Geolite on Snowflake on our developer portal.](/geoip/geolite-on-snowflake/)
 
 We intend to make GeoIP databases available on Snowflake at a later date.
 
diff --git a/content/geoip/release-notes/2025.md b/content/geoip/release-notes/2025.md
@@ -120,7 +120,7 @@ The update will be reflected in the following products and services:
 {{< release-note date="2025-11-20" title="IP risk snapshot output added to traits object in the Insights web services">}}
 
 We have added the
-[`ip_risk_snapshot`](https://dev.maxmind.com/geoip/docs/web-services/responses/#schema--response--traits__ip_risk_snapshot)
+[`ip_risk_snapshot`](/geoip/docs/web-services/responses/#schema--response--traits__ip_risk_snapshot)
 to the traits object in our GeoIP Insights web service and our minFraud Insights
 and Factors web services. This field contains the risk associated with the IP
 address. The value ranges from 0.01 to 99. A higher score indicates a higher
@@ -149,9 +149,9 @@ Client APIs have been updated to reflect this change.
 {{< release-note date="2025-11-19" title="New anonymizer data added to web services">}}
 
 We have added an
-[`anonymizer` object](https://dev.maxmind.com/geoip/docs/web-services/responses/#anonymizer)
-to our web services. This object contains the anonymizer data previously found
-in the `traits` object together with new outputs.
+[`anonymizer` object](/geoip/docs/web-services/responses/#anonymizer) to our web
+services. This object contains the anonymizer data previously found in the
+`traits` object together with new outputs.
 
 Anonymizer data in the `traits` object is being marked as deprecated. However,
 for backwards compatibility, anonymizer data in the `traits` object will
@@ -254,7 +254,7 @@ November 11, 2025.
 {{< release-note date="2025-11-10" title="[Update] Upcoming change to identify Verizon 5G Home as a separate ISP">}}
 
 As
-[previously announced](https://dev.maxmind.com/geoip/release-notes/2025/#upcoming-change-to-identify-verizon-5g-home-as-a-separate-isp),
+[previously announced](/geoip/release-notes/2025/#upcoming-change-to-identify-verizon-5g-home-as-a-separate-isp),
 tomorrow, November 11, 2025, some networks previously labeled `Verizon Wireless`
 will have their ISP name updated to `Verizon 5G Home` to improve coverage and
 accuracy.
@@ -414,7 +414,7 @@ databases will be released today as scheduled.
 
 Due to irregularities in the latest GeoNames data, we will be maintaining the
 location names and codes from July.
-[See the monthly diff report for July 2025.](https://dev.maxmind.com/geoip/release-notes/2025/#geonames-monthly-diff-report-july-2025)
+[See the monthly diff report for July 2025.](/geoip/release-notes/2025/#geonames-monthly-diff-report-july-2025)
 
 {{</ release-note >}}
 
@@ -843,7 +843,7 @@ The following services will be impacted:
 {{< release-note date="2025-02-05" title="Update—Identifying Verizon 5g Home Internet" >}}
 
 As announced in our
-[previous release note](https://dev.maxmind.com/geoip/release-notes/2025/#identifying-verizon-5g-home-internet),
+[previous release note](/geoip/release-notes/2025/#identifying-verizon-5g-home-internet),
 we are reclassifying a portion of Verizon Wireless networks in the United
 States.
 
diff --git a/content/minfraud/release-notes/2013.md b/content/minfraud/release-notes/2013.md
@@ -20,7 +20,7 @@ The AAAA address for US East servers will be 2607:f0d0:3:8::4.
 
 - 2013-09-23 device.maxmind.com
 - 2013-09-23 download.maxmind.com
-- 2013-09-23 www.maxmind.com
+- 2013-09-23 `www.maxmind.com`
 - 2013-09-30 geolite.maxmind.com
 - 2013-10-14 sitecore1.maxmind.com
 - 2013-11-11 geoip-us-east.maxmind.com
@@ -95,4 +95,4 @@ List of affected hostnames:
 - update.maxmind.com
 - updates.maxmind.com
 - www2.maxmind.com
-- www.maxmind.com {{</ release-note >}}
+- `www.maxmind.com` {{</ release-note >}}
diff --git a/content/minfraud/release-notes/2024.md b/content/minfraud/release-notes/2024.md
@@ -135,7 +135,7 @@ requests.
 in the minFraud alerts email body.
 
 Please continue to
-[report chargebacks and fraud on your account portal or via API.](https://dev.maxmind.com/minfraud/report-a-transaction/)
+[report chargebacks and fraud on your account portal or via API.](/minfraud/report-a-transaction/)
 
 {{</ release-note >}}
 
@@ -212,7 +212,7 @@ you are not interfacing directly with our REST API.
 {{< release-note date="2024-04-08" title="Email first seen can be used as a parameter for custom rules" >}}
 
 minFraud Insights and Factors customers can now use the
-[`/email/first_seen` output](https://dev.maxmind.com/minfraud/api-documentation/responses/#schema--response--email)
+[`/email/first_seen` output](/minfraud/api-documentation/responses/#schema--response--email)
 in minFraud custom rules.
 
 The minFraud service retains a record of when an email address or email domain
diff --git a/content/minfraud/release-notes/2025.md b/content/minfraud/release-notes/2025.md
diff --git a/layouts/_default/_markup/render-link.html b/layouts/_default/_markup/render-link.html
diff --git a/layouts/_default/_markup/render-link.markdown.md b/layouts/_default/_markup/render-link.markdown.md
diff --git a/lychee.toml b/lychee.toml
diff --git a/mise.toml b/mise.toml
