fix(site): correct v1.0.0 copy and add the missing SEO surface - #32
Merged
Conversation
Two problems, found while tracing where search traffic actually lands. The site still described v0.1.0 It advertised six agents and seven phases, and the agent roster listed every role as claude-sonnet-4.6 — including QA Sealed and Lead Engineer, the exact same-family pairing that v1.0.0 exists to eliminate. The landing page was demonstrating the bug as though it were the design. Now: eight agents, eight phases, and the real cross-family assignments from config.yml, with Arch Critic and Red Team added. Seal plurality is shown as two independent authors, and the QA Validator card notes that its identity is deliberately unconstrained because it executes rather than authors. No SEO surface at all robots.txt and sitemap.xml both 404'd, there was no canonical link, and there were no Open Graph or Twitter tags — so every link to this site, in Slack, on social, anywhere, rendered as a bare URL with no title or description. For a project whose measured bottleneck is distribution rather than conversion, that is the worst place to be losing traffic. Added robots.ts and sitemap.ts as static routes, plus canonical, Open Graph, Twitter card, keywords and metadataBase. The description also carried the same stale six-agent claim and has been corrected. Verified from the build output: robots.txt and sitemap.xml resolve, canonical and og tags are present, no stale counts remain, and npm audit is clean. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9cb0b232-bb14-47a5-a150-00e71bdddcae
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
1 participant
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.
Found while tracing where search traffic actually lands. Two problems.
The site still described v0.1.0
It advertised six agents / seven phases, and the agent roster listed every role as
claude-sonnet-4.6— including QA Sealed and Lead Engineer, the exact same-family pairing that v1.0.0 exists to eliminate.The landing page was demonstrating the bug as though it were the design.
Now: 8 agents, 8 phases, real cross-family assignments read from
config.yml, with Arch Critic and Red Team added. Seal plurality shows both independent authors, and the QA Validator card notes its identity is deliberately unconstrained because it executes rather than authors.There was no SEO surface at all
robots.txtsitemap.xmlThe Open Graph gap is the expensive one: every link to this site — Slack, social, anywhere — rendered as a bare URL with no title or description. For a project whose measured bottleneck is distribution rather than conversion, that is the worst possible place to be losing traffic.
The meta description also carried the same stale six-agent claim.
Verified from build output
robots.txtandsitemap.xmlresolve as static routes, canonical + og + twitter tags present, zero stale counts remain,npm auditclean.