← SEO & Growth CopilotCONTENT HISTORY
WHAT CHANGED
Update to SEO & Growth Copilot
Snapshot Nov 3, 2026 · 18:49 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save SEO & Growth Copilot and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Investigate organic traffic or conversion changes and prioritize competing hypotheses.",
"included_files": [],
"name": "diagnose-organic-traffic",
"skill_md_contents": "---\nname: diagnose-organic-traffic\ndescription: Investigate organic traffic or conversion changes and prioritize competing hypotheses.\n---\n\n# Diagnose Organic Traffic\n\n## Trigger and scope\nInvestigate organic traffic or conversion changes and prioritize competing hypotheses. Do not activate this workflow for unrelated broad marketing requests. Use actual site, data, source or repository evidence supplied or accessible in the current host. Never imply access to a tool or account that is absent.\n\n## Required procedure\nConfirm source of metrics, comparison windows, instrumentation changes and key events. Decompose impression, CTR and landing-page conversion contributions and cohort differences. Test demand, SERP presentation, indexing, navigation, UX and measurement hypotheses.\n\n## References\n- Read `../../references/traffic-diagnostics.md` when relevant.\n- Read `../../references/gsc-analysis.md` when relevant.\n- Inspect original material under `../../references/original/` when specialized detail is needed; current official guidance takes precedence on conflicts.\n\n## Deliverable\nObserved drivers versus hypotheses, ranked checks, monitoring strategy.\n\n## Acceptance and safety gates\nDo not label coincidence as causation or guess competitor traffic. Every high-impact finding needs an evidence label, source URL/data range, estimated effect as a hypothesis, and clear verification step. Do not fabricate Search Console access, test executions, indexing status, or rankings. Distinguish intended changes from deployed changes and read-only checks from live edits. Get explicit approval before publishing, changing production metadata/robots/redirects, or touching external accounts.\n"
}SHA-256 of public snapshot: 921e0f6da7f3a5d695c653d1a26a2d40319c8eb0361aea8c46902ed5081e4016