Repository navigation
Record the apex flip in infra notes - #18
Merged
Merged
Conversation
Fills the placeholder date and replaces "by Nima" with what actually happened: the flip is a per-project domain setting reachable only through the API, and the ordering matters — setting the new redirect before clearing the old one points the two hosts at each other. Also states the failure it fixed, since "contradicting the canonicals" undersold it: every sitemap URL was redirecting away from itself onto a page whose canonical pointed back at the redirector.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
Records the apex flip that went live on 2026-08-20. Documentation only — no
code or config changes.
docs/infra.mdhad been written ahead of the flip with a placeholder date and"by Nima", and it described the old state as merely "contradicting the code's
canonicals". Two corrections:
What the old state actually was.
sitemap.xmlfed Google the apex, the apex308'd to
www, andwwwserved a page whose canonical pointed back at the apex.Every submitted URL redirected away from itself onto a page pointing back at the
redirector, which Google resolves by discarding the canonical. That is a
different and worse failure than a host-preference mismatch, and it was live for
the whole window after the PR #16 SEO work shipped.
How to redo or revert it. The direction is a per-project domain setting and
vercel domainshas no subcommand for it — it is API-only. Clearing the oldredirect must come before adding the new one, or the two hosts point at each
other in the gap between calls. DNS is not involved and does not need touching.
Verified live before writing this: apex 200,
www308 → apex with the pathpreserved, all 7 sitemap URLs resolving in 0 redirect hops, and canonical /
og:url/ JSON-LD@idall matching the host that serves them.