Tekton Growth SEO Fulfillment

Visibility Growth Plan Buildout Tracker

A visual reference for the SEO template reset, showing what exists now, what each month actually executes, who owns it, and what stays approval-gated.

Updated: 2026-06-22 23:08 PT Production templates: 17 Manual trigger only No client tasks generated yet

Current buildout state

The old P2/P4 SEO template sets were retired/frozen and the VGP template structure is live. The key correction: every month needs executable SEO work, not just audits and recommendations.

5

SEO template sets

Foundation Reset, Approval Packets, Execution Packets, Monthly Cadence, Checkpoints.

17

Total SEO templates

Includes the new 30/60/90 execution model.

4

Changed or added

Month 1 updated, plus 30-Day, 60-Day, and 90-Day execution packets.

0

Live client actions

No GBP, site, citation, indexing, or client-facing work was executed during template setup.

Operating rule

Audits and maps are inputs. Each month must create completed work, approved-ready implementation tasks, or explicitly blocked execution items with a clear approval gate.

30 / 60 / 90 executable cadence

The framework now starts with a fast foundation, then moves into buildout, then optimization and trust expansion.

First 30 days

Foundation + Quick Sprint

Clawton: facts/baselines/packetsJakob: approved site execution
  • Lock NAP, services, target city, GBP landing page, access matrix
  • Local Dominator setup or baseline
  • Citation/NAP launch or cleanup queue
  • Technical quick fixes where Tekton controls the site
  • GBP quick optimization packet and approved safe changes
  • First Core 30 homepage/service/internal-link pass
  • Review specificity setup
  • Sprint proof with before/after notes
Days 31-60

Buildout + Implementation

Jakob/Web Designer: implementationClawton: packet/proof support
  • Build or refresh priority Core 30 pages
  • Implement internal link pass
  • Schema, metadata, and indexability fixes
  • Approved GBP service/category/content improvements
  • Citation cleanup or order follow-through
  • Review process improvements
  • First GSC/LD adjustments if enough data exists
  • Log completed URLs, fields, files, and remaining gates
Days 61-90

Optimization + Trust Expansion

Clawton: optimization/trust queueJakob: approved implementation
  • GSC almost-winner optimization
  • Local Dominator weak-zone fixes
  • Support and geo content briefs tied to target pages
  • Citation/NAP verification and cleanup tasks
  • Review specificity and reputation next action
  • Local authority/link/mention opportunities
  • Schema and entity trust checks
  • Next 90-day execution queue

How work should move

This keeps strategy, TaskTracker execution, Jakob implementation, and client-visible progress connected without turning TaskTracker into a pile of audit tasks.

1. Clawton locks factsScope, access, NAP, GBP, site, citations, LD, GSC, GA4, Core 30 gaps.
→
2. TaskTracker creates packets30/60/90 tasks with real subtasks, assignees, gates, due offsets, and proof expectations.
→
3. Jakob executes approved workSite/page/schema/internal-link/technical changes, with proof and held gates separated.
4. Approval gates stay visibleGBP edits, deploys, citation spend, indexing, outreach, and client sends require explicit approval.
→
5. Proof gets loggedBefore/after links, screenshots, fields/files changed, approvals held, and next queued work.
→
6. Portal gets clean milestonesClient sees progress, not internal clutter or raw subtasks.

Production template readback

The templates below are the key buildout pieces currently tracked from the production manifest.

TemplateSetOwnerDueSubtasksStatus
[SEO] {{Client}}: 60-Day Core 30 Buildout SprintSEO Execution Packetsjakobgillow@gmail.com45 days8SOP + subtasks present
[SEO] {{Client}}: Month 1 Foundation SprintSEO Foundation Resetclawton@tektongrowth.com3 days10SOP + subtasks present
[SEO] {{Client}}: 30-Day Quick Sprint ExecutionSEO Foundation Resetjakobgillow@gmail.com10 days8SOP + subtasks present
[SEO] {{Client}}: 90-Day Optimization + Trust Expansion SprintSEO Monthly Cadenceclawton@tektongrowth.com75 days9SOP + subtasks present

Approval gates that do not move automatically

Internal template approval does not authorize downstream platform changes. These stay one-at-a-time approval gates.

GBP profile edits: categories, services, description, URL, address, hours, posts, photos.
Live site deploys, metadata/copy/schema changes, DNS, canonical, sitemap, or indexing actions.
Citation submissions, vendor orders, credit spend, listing claims, outreach, or paid placements.
Local Dominator configuration changes when scan setup was not already approved.
Client-facing sends, reports, requests, approval packets, or public review replies.
Broad rollout across every current client. Pilot first, then decide manual vs triggered behavior.

Next buildout decisions

The framework is now pointed in the right direction. The next step is proving the packets on real clients without flooding the board.

1. Pick pilot clients

Choose 3-5: new/early, messy active, mature/plateaued, Core 30-heavy, citation/NAP-heavy.

2. Run classification

Use SEO State Classification Audit first for existing clients so we do not duplicate completed work.

3. Generate one packet at a time

For each pilot, create the right 30/60/90 execution task and review whether the subtasks are actually usable.

Watch item

The 30-day and 60-day templates route to Jakob by default. The 90-day optimization packet routes to Clawton for strategy/trust queue creation, then any approved implementation should become Jakob-owned execution work.