Skip to content
Tekton Wiki

Operations

Website / SEO Request Triage

Platform
Operations
Owner
Website / SEO Specialist
Assignee
Jakob
Supports
CSM, Operations
Needs review — This SOP contains our content but has not been verified by Nick. Treat as a working draft until marked Live.

Website / SEO Request Triage

Section titled “Website / SEO Request Triage”

What

Section titled “What”

Use this SOP when a website or SEO request reaches Jakob and needs to be clarified before work starts. The goal is to turn a vague request into a scoped production task with a clear definition of done.

Who owns it

Section titled “Who owns it”

Primary owner: Website / SEO Specialist Current assignee: Jakob Supporting owner: CSM for client context and client follow-up

Steps

Section titled “Steps”
  1. Confirm the client, site, affected URL, source of the request, and requested outcome.
  2. Check whether the request is website implementation, technical SEO, content/SEO strategy, tracking, access, launch, or client communication.
  3. Identify blockers before touching production work: missing access, missing copy, missing images, unclear scope, client approval, DNS, indexing, or billing risk.
  4. Write the definition of done in the TaskTracker task or operating thread.
  5. If the request affects DNS, live indexing, redirects, canonical strategy, ads, billing, client sends, or package scope, stop and route for approval before implementation.

Definition of done

Section titled “Definition of done”

The request is triaged when the task has a clear client/site, affected route, production owner, approval status, blocked/unblocked state, and measurable finish line.