playbooks

home / skills / gtmagents / gtm-agents / publishing-process

publishing-process skill

/plugins/seo-workflow-orchestration/skills/publishing-process

This skill coordinates multi-team SEO content launches, ensuring QA, approvals, and analytics before go-live and post launch validation.

npx playbooks add skill gtmagents/gtm-agents --skill publishing-process

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.3 KB
---
name: publishing-process
description: Use to orchestrate approvals, QA, and go-live steps for SEO content +
  technical launches.
---

# SEO Publishing Process Skill

## When to Use
- Coordinating multi-team releases (writers, designers, web, legal).
- Ensuring SEO assets meet quality, accessibility, and analytics requirements before launch.
- Running retros after missed deadlines or publishing defects.

## Framework
1. **Pre-flight Checklist** – briefs approved, assets uploaded, localization complete, legal sign-off captured.
2. **CMS/Code QA** – metadata, schema markup, internal links, CWV budgets, responsive design.
3. **Analytics & Tracking** – UTMs, event triggers, conversion modules, A/B test configs.
4. **Launch Controls** – staging reviews, smoke tests, rollback plan, comms schedule.
5. **Post-launch Validation** – indexation check, monitoring alerts, performance baseline snapshot.

## Templates
- Publishing runbook (steps, owner, evidence link, status).
- QA checklist (content, technical, analytics, accessibility).
- Launch log capturing timestamps, environments, and approvals.

## Tips
- Timebox approvals with clear SLAs to keep calendars on track.
- Automate checklist reminders via project tools or Git hooks.
- Pair with `deploy-optimizations` to keep evidence attached to each task.

---

Overview

This skill orchestrates approvals, QA, and go-live steps for SEO content and technical launches. It centralizes pre-flight checks, CMS and code validation, analytics verification, launch controls, and post-launch validation. The goal is to reduce release friction, catch SEO regressions, and ensure measurable launches with clear ownership and evidence.

How this skill works

The skill runs a defined publishing framework: a pre-flight checklist confirms briefs, assets, localization, and legal sign-offs. It performs CMS and code QA on metadata, schema, links, and performance budgets, then verifies analytics, UTM tags, and A/B test configs. Launch controls automate staging reviews, smoke tests, and rollback readiness, and post-launch validation captures indexation, monitoring alerts, and performance baselines.

When to use it

  • Coordinating multi-team releases involving writers, designers, web engineers, and legal
  • Before pushing SEO-critical pages or sitewide technical updates to production
  • When you need repeatable, auditable publishing runbooks for compliance or governance
  • To run a root-cause retrospective after missed deadlines or publishing defects
  • When launching localized content or large-scale content migrations

Best practices

  • Timebox approvals with explicit SLAs to prevent calendar bottlenecks
  • Attach evidence links (screenshots, validation reports) to each checklist item
  • Automate reminders and status updates through project tools or CI hooks
  • Use staging smoke tests and a documented rollback plan for every release
  • Capture a performance baseline and alert thresholds immediately post-launch

Example use cases

  • Publishing a pillar SEO page with cross-team sign-offs and tracking implementation
  • Rolling out a site redesign that requires metadata and schema verification
  • Launching a localized campaign where translations, hreflang, and analytics must be validated
  • Coordinating a technical SEO fix release with staged rollout and rollback controls
  • Running a post-mortem after an indexation or traffic drop to map failures to process gaps

FAQ

What artifacts should be attached to the publishing runbook?

Attach the brief, proof of uploaded assets, localization evidence, legal sign-off, CMS screenshots, analytics config export, and smoke test results.

How do I limit approval delays?

Set clear SLAs for each approver, automate reminders, and escalate overdue items to a designated owner.