domains / families / marketing / seo-drift

seo-drift

combined

SEO drift monitoring — snapshot a site's SEO state and detect regressions over time. Captures a baseline (rankings/positions, indexed page count, titles & meta descriptions, canonical/robots directives, schema presence, key on-page elements) and on later runs diffs against it to surface what changed: ranking drops, pages that fell out of the index, titles/metas that were accidentally overwritten (a CMS/redeploy classic), canonicals or noindex flipped, schema that disappeared. Use this skill when the user wants to monitor SEO over time, catch regressions after a site change / migration / redeploy, set a baseline, diff against a previous state, or asks "what changed on my site's SEO" or "did my redesign break SEO". Trigger on: "SEO drift", "SEO monitoring", "track SEO over time", "did my site change break SEO", "after migration SEO", "SEO regression", "baseline my SEO", "compare SEO to last month", "my titles changed", "pages fell out of the index". For a one-time full audit use /seo-an… Snapshot a site's SEO state and detect ranking, indexation, metadata, canonical, robots, schema, and on-page regressions over time.

When to use

• baseline or monitor a site's SEO over time;
• check whether a migration, redesign, CMS change, or redeploy damaged SEO;
• compare current search performance and page metadata with a prior snapshot;
• investigate titles, descriptions, canonicals, robots directives, or schema that changed unexpectedly;
• identify rankings or indexed pages that disappeared.

When not to use

• Search Console data can lag and may suppress low-volume queries.
• A live crawl cannot prove that Google has indexed a page or adopted its canonical.
• Position changes can reflect seasonality, SERP composition, location, device mix, or competitors rather than a site regression.
• The skill does not replace server-log analysis, full-crawl tooling, or manual review of a large migration.
• Comparisons are unreliable when URL sets, date windows, locales, or device filters differ without normalization.

Skill page

Conflict

The first copy is a thin pointer that delegates to a WORKFLOW.md file not included in the prompt, so it contains no executable steps. The second copy is a self-contained, detailed procedure. Because the first copy's actual procedure is missing and the second copy adds substantial steps, constraints, and severity rules not present in the first, crowning one would hide the real alternative. The second copy is the only one with actionable content, but the first copy's delegation pattern is a distinct structural choice that should be noted.