Skip to content

Update Matomo geolocation FAQ link - #1674

Merged
oschwald merged 1 commit into
mainfrom
wstorey/fix-link
Jun 9, 2026
Merged

Update Matomo geolocation FAQ link#1674
oschwald merged 1 commit into
mainfrom
wstorey/fix-link

Conversation

@horgh

@horgh horgh commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

The check-links CI job failed on a broken link in content/geoip/docs/databases.md:

[301] https://matomo.org/faq/setting-up-accurate-visitors-geolocation/ | Rejected status code: 301 Moved Permanently

Matomo now serves this FAQ under a how-to/ path and 301-redirects the old URL. Updated the link to the new location:

  • Before: https://matomo.org/faq/setting-up-accurate-visitors-geolocation/ → 301
  • After: https://matomo.org/faq/how-to/setting-up-accurate-visitors-geolocation/ → 200

Verified locally with lychee (✅ OK) and prettier/cspell pass.

🤖 Generated with Claude Code

The link checker failed because matomo.org now serves this FAQ under a
how-to/ path and 301-redirects the old URL. Update to the new location.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying dev-site with  Cloudflare Pages  Cloudflare Pages

Latest commit: 95206de
Status: ✅  Deploy successful!
Preview URL: https://2089b7d7.dev-site-4ua.pages.dev
Branch Preview URL: https://wstorey-fix-link.dev-site-4ua.pages.dev

View logs

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the URL for the Piwik/Matomo analytics integration link in the databases documentation. The review feedback correctly points out that the link text is in all caps, which is inconsistent with the rest of the table, and suggests updating it to standard casing for consistency.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

| ------------------------------ | ----------------------- | ----------------------------------------------------------------------------------------------------------- |
| Ad-serving | Revive Adserver | [Geotargeting with Revive Adserver](https://www.revive-adserver.com/faq/geotargeting-with-revive-adserver/) |
| Analytics | Piwik/Matomo | [GEO LOCATE YOUR VISITORS](https://matomo.org/faq/setting-up-accurate-visitors-geolocation/) |
| Analytics | Piwik/Matomo | [GEO LOCATE YOUR VISITORS](https://matomo.org/faq/how-to/setting-up-accurate-visitors-geolocation/) |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The link text [GEO LOCATE YOUR VISITORS] is in all caps, which is inconsistent with the sentence/title casing used for all other links in this table (e.g., [Geotargeting with Revive Adserver], [IP lookups enrichment]). Please update the link text to use standard casing, such as [Geolocate your visitors], to maintain consistency in formatting and style across the documentation.

Suggested change
| Analytics | Piwik/Matomo | [GEO LOCATE YOUR VISITORS](https://matomo.org/faq/how-to/setting-up-accurate-visitors-geolocation/) |
| Analytics | Piwik/Matomo | [Geolocate your visitors](https://matomo.org/faq/how-to/setting-up-accurate-visitors-geolocation/) |
References
  1. Consistency in terminology, formatting, and style. (link)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pre-existing, so I'll leave it

@oschwald
oschwald merged commit aa0e729 into main Jun 9, 2026
10 checks passed
@oschwald
oschwald deleted the wstorey/fix-link branch June 9, 2026 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants