Repository navigation
Add evidence-backed search analysis and SEO action workflows - #4
Merged
Merged
Conversation
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.
Search diagnostics now use observed query × page relationships and comparable history instead of inferring associations from separate GSC aggregates. GA acquisition reports, saved SEO research and bounded page evidence feed reviewable SEO actions shared by the dashboard and MCP.
Adds four scoped MCP tools, immutable evidence history, idempotent refresh, SEO-specific baselines and migration 0030. Existing GEO collection and draft review remain available; CMS publishing and weekly reporting are outside this change.
Validation: lint and TypeScript checks; 1,279 workspace unit tests and 61 database/MCP integration tests; 183 SEO workbench tests; 3 focused browser stories; full isolated browser draft/review/implementation flow, API contract and worker checks; production build. The existing local database was backed up and migrated with unchanged existing row counts and encrypted credentials; repeat migration is a no-op. No live Google refresh or paid research call was used for acceptance.