feat(website): SEO on-page improvements for the "meta-harness" query - #12
Closed
juristr wants to merge 4 commits into
Closed
feat(website): SEO on-page improvements for the "meta-harness" query#12juristr wants to merge 4 commits into
juristr wants to merge 4 commits into
Conversation
…definition section, FAQ + FAQPage schema - title/description reframed around the meta-harness optimization layer, keyword-first - decouple hero: visually-hidden keyword <h1>, dot-canvas wordmark now aria-hidden decoration - #what-is H2 becomes "What is a meta-harness?" with snippet-ready definition - add FAQ section with self-contained FAQPage JSON-LD (6 Q&As)
…r, keyword-anchored link + spelling variants
✅ Deploy Preview for nrwl-harnesstools ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
… definition into the answer section - WhatMetaHarnessV3: two senses become real <h3>s (optimization leads, orchestration aside) - revert #what-is to "Meta-harnesses are the missing layer" so the page still earns the definition - move the what-is-a-meta-harness definition into "The answer" section as its opening thesis
Member
Author
|
Superseded by #13: additive content extracted there, realigned to the orchestration positioning (site targets the layer-above sense, not the paper's optimization sense). Title change dropped to avoid a second identity change during Google re-evaluation. See Polygraph session metaharness.tools-SEO-drop-investigation-728945cc for the full rationale. |
juristr
added a commit
that referenced
this pull request
Jul 24, 2026
…cted from #12) (#13) * feat(website): extract SEO content from PR #12, keep current title FAQ section + FAQPage JSON-LD, 'What is a meta-harness?' definition H2, hidden keyword H1 decoupled from dot-canvas wordmark, README reframe, new meta description. Title stays 'Meta-Harness 101' to avoid a second identity change during Google re-evaluation. * feat(website): align extracted SEO content with orchestration positioning Site's subject is the orchestration sense (layer above harnesses: cross-repo coordination, session memory, policy), not the Stanford paper's optimization sense. Rewrite FAQ answers, definition lead, hidden H1, meta description, two-senses section (orchestration first + focus), README back to layer-above wording. Paper disambiguation FAQ now draws the distinction instead of claiming same-idea. * feat(website): add FAQ to nav + section rail * Split definition from capabilities; add harness-optimization loop viz - Answer section now owns the two meanings (orchestration vs optimization), each with its own visualization - New HarnessOptimizationLoop animation: proposer/candidate-harness/experience- filesystem outer loop from the Stanford Meta-Harness paper - Capabilities section refocused on orchestration meta-harnesses - Fix pre-existing unused-const typecheck errors in two kernels * Answer section: alternating rows for the two meanings; viz scaling fixes - Two meanings laid out as text-column + full-size viz rows (capabilities row pattern), orchestration badged as the site's focus - HarnessOptimizationLoop: DOM sizes in cqw so boxes keep world proportions at any width (fixes overlap at column/mobile widths); boxes pinned to world rects so arrows land on their edges; label shift - Capabilities: drop separator line, de-duplicate orchestration-focus copy * Optimization viz: paper-accurate scores, arc + label + background fixes - Scores were four different agents from the paper's TB2 leaderboard posed as one run's candidates; now illustrative unitless scores with an early regression, matching the Appendix A trajectory shape. 'pass rate %' -> 'score', end label no longer claims 'best of 4 candidates' - Log arc lands on the filesystem box's right edge (mirrors read arc) - 'proposes new harness code' label moved clear of the harness box - Outer frame gets the same surface fill treatment as MetaHarnessLayers * fix(website): keep hero subtitle on one line max-w-2xl (672px) too narrow for the longer subtitle at text-3xl; bump to max-w-4xl + text-balance so narrow viewports wrap evenly. * feat(website): singular 'The answer: a meta-harness' heading + rail label * feat(website): FAQ Q1 notes the two senses, site focuses on orchestration * feat(website): FAQ Q2 states broader-scope distinction explicitly
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.
Summary
On-page SEO (P0) to lift metaharness.tools for the query "metaharness" / "meta-harness". SERP recon put us around page 2 (position ~17); the term splits into an optimization-layer sense (Stanford/MIT arXiv paper + GitHub repos, high authority) and an orchestration-layer sense (Databricks Omnigent, MindStudio). We lean into the optimization sense (our actual topic) and aim to own the definitional/question intent the high-authority pages serve poorly.
Changes (all verified in the built HTML):
aria-hiddendecoration); a new visually-hidden<h1>carries the keyword heading. Visual unchanged; screen-reader a11y improves.#what-isH2 becomes the literal query "What is a meta-harness?" with a snippet-extractable optimization definition as the lead paragraph.FaqV3.astro) with a self-contained FAQPage JSON-LD (6 Q&As) built from one array so schema can't drift from copy. Includes the Stanford-paper disambiguation ("same idea, narrower scope") and a spelling-variants Q&A that puts "metaharness / meta harness / meta-harness" into visible body text.Follow-ups (P1/P2) tracked in the Polygraph session description:
<h3>promotion of the two definitions, comparison table,DefinedTerm/citationJSON-LD rewrite,dateModifiedfreshness fix, and off-page internal links from nx.dev withmeta-harnessanchor text.View session information ↗