fix: point docs site_url at the brand domain for correct canonicals - #175
Merged
capotej merged 1 commit intoSep 2, 2026
Merged
Conversation
2 tasks
BoldBlackBot
force-pushed
the
fix/docs-canonical-brand-domain
branch
from
August 30, 2026 21:31
3609801 to
5c025b0
Compare
capotej
approved these changes
Sep 2, 2026
The docs are mirrored onto harness.boldblack.ai/docs/ by the harness-site Amplify build, but zensical.toml site_url still named the GitHub Pages origin, so every mirrored page carried a cross-domain canonical to boldblackai.github.io and the sitemap listed cross-origin URLs. Google Search Console flags every /docs/* page as a duplicate for this reason. Set site_url to https://harness.boldblack.ai/docs/ so canonicals and sitemap locs are self-referencing on the serving domain; link the README docs pointer at the brand domain too. Relative links are unchanged (zensical emits them relative by design), so the tree stays relocatable and the Pages deploy keeps working. Requires the harness-site fetch-docs sitemap-loc rewrite (PR boldblackai#20) to be merged and deployed first: after this change the upstream sitemap lists brand-domain URLs, which the mirror must rewrite back to the Pages origin it fetches from. Co-Authored-By: Enrique Canals <84596+EnriqueCanals@users.noreply.github.com>
BoldBlackBot
force-pushed
the
fix/docs-canonical-brand-domain
branch
from
September 2, 2026 02:38
5c025b0 to
40f8f42
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
zensical.toml:site_urlhttps://boldblackai.github.io/harness/→https://harness.boldblack.ai/docs/.README.md: docs link →https://harness.boldblack.ai/docs/.Why
Google Search Console flags every
harness.boldblack.ai/docs/*page ("Duplicate, Google chose different canonical"). All 12 mirrored docs pages declare a cross-domain canonical toboldblackai.github.io/harness/, and/docs/sitemap.xml(submitted via robots.txt) lists cross-origin URLs.site_urlis the single knob that drives both canonicals and sitemap locs; pointing it at the serving domain makes them self-referencing. Same fix already shipped for dispatch (create-dispatch #43).Relative links stay relative (zensical design; relocatability), so the GitHub Pages deploy and the Amplify mirror keep working. Verified locally:
zensical build --cleanwith the new site_url emits all 12 locs + canonicals on the brand domain, no other diffs.Deployment order
Merge + Amplify-deploy boldblackai/harness-site#20 (fetch-docs sitemap-loc rewrite) first. After this PR merges and Pages redeploys, upstream sitemap locs carry the brand domain; the mirror rewrites them back to the Pages origin it fetches from.
Test plan
zensical build --clean: sitemap = 12 brand-domain locs;site/index.htmlcanonical =https://harness.boldblack.ai/docs/.curl -s https://harness.boldblack.ai/docs/ | grep canonical→ brand domain.