# Bug: Write.as navigation links incorrectly use vanity domain

**URL:** <https://discuss.write.as/t/bug-write-as-navigation-links-incorrectly-use-vanity-domain/20422>\
**Category:** Bugs\
**Created:** [January 28, 2026, 6:43pm UTC](https://discuss.write.as/t/bug-write-as-navigation-links-incorrectly-use-vanity-domain/20422 "2026-01-28T18:43:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnkarahalis](https://discuss.write.as/user_avatar/discuss.write.as/johnkarahalis/32/5508_2.png) [@johnkarahalis](https://discuss.write.as/u/johnkarahalis)\
**Post date:** [January 28, 2026, 6:43pm UTC](https://discuss.write.as/t/bug-write-as-navigation-links-incorrectly-use-vanity-domain/20422/1 "2026-01-28T18:43:57Z")

</div>

Using a broken link checker, I found that certain vanity domain URLs which 404 accidentally link to Write.as product pages but _using the vanity URL_.

For example, take this URL:

[https://blog.johnkarahalis.com/tag:SoftwareDev](https://blog.johnkarahalis.com/tag:SoftwareDev)

That URL is _itself_ 404, and it attempts to link to `blog.johnkarahalis.com/pricing`, `blog.johnkarahalis.com/start`, etc.).

 ![Screenshot from 2026-01-28 13-50-20](https://discuss.write.as/uploads/default/original/2X/f/fc4991bcbc4232efe2e182eaa149d08a9a2ce550.png)

It should be linking to `write.as/pricing`, `write.as/start`, etc.

Given that it only seems to happen on pages which themselves 404, I don’t think it’s a huge deal, but I wanted to mention it.

(Truthfully, I don’t know why the broken link checker ever visited `.../tag:SoftwareDev`, because I don’t link to that myself, from with the blog, but that’s another question altogether.)

---

<div class="post-metadata">

**Author:** ![harmonpa214](https://discuss.write.as/user_avatar/discuss.write.as/harmonpa214/32/5655_2.png) [@harmonpa214](https://discuss.write.as/u/harmonpa214)\
**Post date:** [January 30, 2026, 11:58am UTC](https://discuss.write.as/t/bug-write-as-navigation-links-incorrectly-use-vanity-domain/20422/2 "2026-01-30T11:58:58Z")

</div>

Thanks for noticing this! That’ll be something we can look into and hopefully fix within the coming months.

Thanks,  
Peter
