Tekton Growth SEO Fulfillment

AI SEO Mastery → Visibility Growth Plan Canonical Templates

Source-based operating doc. The old detailed SEO templates have been folded into the seven canonical VGP TaskTracker templates so the team has one operating flow, not a second process layer.

Updated: 2026-06-23 PTSource: AI SEO Mastery digest + Core 30 Skool lessonsCanonical set: Visibility Growth Plan - 90 Day SEOInternal operating doc

The process in one screen

Local SEO starts by making Google understand the business, then making the website mirror and support the GBP, then using rank maps, GSC, reviews, citations, and authority signals to decide what to build next.

Days 0-3: Intake + Fact Lock

Lock source truth before making claims, pages, metadata, schema, GBP edits, citations, reports, or execution tasks.

Days 4-7: GBP + Service Truth Cleanup

Clean the GBP category/service model and build the service truth map before site planning. Draft exact GBP changes, but keep live edits approval-gated.

Days 8-14: Core 30 Audit + First Sprint Packet

Map current site against Core 30 architecture, technical blockers, and service truth, then convert gaps into the first approved Jakob execution sprint.

Days 15-30: Foundation Sprint Execution

Execute the approved Month 1 quick sprint: baseline setup, citation/NAP launch or cleanup queue, technical fixes, first Core 30 page work, schema/internal links, review process, and proof log.

Days 31-60: Core 30 Buildout

Turn Month 1 maps into Jakob-owned implementation: category/service/location/trust pages, internal linking, schema/metadata, citation follow-through, review process, and first GSC/LD adjustments.

Days 61-90: Optimization + Trust Expansion

Use early signals to optimize pages and expand trust: GSC almost-winners, Local Dominator weak zones, review specificity, citations/NAP, local authority, schema/entity trust, and AI visibility checks.

Monthly SEO Opportunity Review

Recurring decision loop: Demand → Visibility → Clicks → Leads → Next action. Produces 3-5 prioritized tasks or approval-gated recommendations, not a generic checklist.

What changed

  • The five detailed SEO support sets are now detail-library history, not active competing workflows.
  • The useful details from those sets are folded directly into these VGP subtasks.
  • The canonical operating set stays manual-trigger only until Nick/Jakob decide otherwise.

Key correction

Core 30 is not a vague “30 assets” idea. The source defines a page architecture: GBP landing page, GBP category pages, GBP service pages, location page(s), About/Contact, then topical/geographic support after rank-map review.

Canonical VGP Template 1

VGP - Days 0-3: Intake + Fact Lock

Lock source truth before making claims, pages, metadata, schema, GBP edits, citations, reports, or execution tasks.

13 folded subtasksDue +3 daysvisibility-growth-planseophase:fact-lockinternal-onlyapproval-gated
Folded-in detail modules
SEO State Classification AuditLocal Rank Tracking Setup + Baseline
If this is an existing client, run SEO State Classification first: Needs Foundation Reset, Foundation Done/Core 30 Weak, Core 30 Built/Needs Optimization, or Mature/Needs Deep Re-Audit.
Confirm client identity: business name, website, phone, address, service areas, market, industry, primary offer, high-margin services, excluded services, and target city.
Confirm access matrix for GBP, website/CMS, GA4, GSC, Bing Webmaster, Local Dominator, BrightLocal/citations, Drive, Cosmo/onboarding docs, and note exact missing-access workaround.
Lock canonical NAP, service area, target cities, GBP landing page, primary/secondary service categories, and real proof sources before writing or changing anything.
Pull owned GBP facts where available: primary category, secondary categories, services, description, hours, service areas, business info fields, profile links, photos baseline, review count/rating, newest reviews.
Crawl the site and capture URLs, status codes, titles, H1s, metas, canonicals, schema, internal links, sitemap, robots, redirects, mobile/rendering notes, and llms.txt if present.
Capture homepage/GBP landing page content as the Core 30 audit input.
Export Screaming Frog Internal URLs CSV and All Links CSV for the Core 30 content audit workflow.
Set up or verify Local Dominator baseline inputs: map-pack/local intent, GBP/proximity reality, keyword set, grid center, grid size, cadence, latest runs, share links/screenshots, average rank, top-3 percentage, and weak zones.
Capture citation/entity footprint: Google, Bing Places, Apple Maps, Facebook, Yelp, BBB, GPS/navigation, niche/local directories, duplicates, old addresses, and NAP mismatches.
Pull GSC/GA4/Bing baseline where available: pages, queries, clicks, impressions, CTR, positions, traffic quality, and leads/conversion proof.
Build proof inventory: real services, photos, completed jobs, reviews, team, licenses, warranties, process, offers, constraints, local proof, and unsupported claims to avoid.
End with exit state: Executed, Ready for approval, Needs access, Blocked, and Next action.
Canonical VGP Template 2

VGP - Days 4-7: GBP + Service Truth Cleanup

Clean the GBP category/service model and build the service truth map before site planning. Draft exact GBP changes, but keep live edits approval-gated.

12 folded subtasksDue +7 daysvisibility-growth-planseogbpphase:service-truthapproval-gated
Folded-in detail modules
GBP Optimization Approval PacketReview Specificity Plan
Run GBP risk audit and classify changes by risk. Business name, address, categories, landing page URL, and unsupported services/categories require explicit approval.
Confirm primary GBP category matches the highest-value accurate broad service identity.
Identify 3-5 strong secondary categories where appropriate. Do not add every possible category.
Research competitor GBP categories for legitimate missing options, but only keep categories that match real services.
Create service cleanup matrix: keep, consolidate, needs proof, remove/do not emphasize, needs site support.
Build Service Truth Map: category cluster, parent service, child service, revenue priority, conversion priority, proof available, existing URL, needed URL, tracked keyword.
Audit GBP fields: description, hours, holiday hours, service areas, appointment links, products/services where relevant, profile links, automated calls, and other applicable boxes.
Draft GBP description and service/category edits around true primary service identity, categories, city/area, proof, and trust. No hype or invented guarantees.
Build GBP landing alignment plan: title/H1/body/schema/internal-link changes needed so the landing page supports primary category, city, categories, and services.
Create owner-led review specificity process focused on service/location/job-type language, not generic review begging or scripted policy-risky language.
Bundle exact proposed GBP changes with before/after values, risk notes, and rollback notes into an approval packet.
Do not save GBP edits until Nick/Jakob approves the exact payload. If approved, perform one controlled save and post-change QA.
Canonical VGP Template 3

VGP - Days 8-14: Core 30 Audit + First Sprint Packet

Map current site against Core 30 architecture, technical blockers, and service truth, then convert gaps into the first approved Jakob execution sprint.

12 folded subtasksDue +14 daysvisibility-growth-plancore30seophase:core30-auditapproval-gated
Folded-in detail modules
Core 30 Gap MapTechnical SEO Audit + Implementation Packet
Decide single-location vs multi-location structure. Single-location: homepage is GBP landing page. Multi-location: homepage separate, each location gets its own GBP landing page.
Audit homepage, GBP services/categories, Internal URLs CSV, and All Links CSV against Core 30 structure.
Map GBP landing page target: primary category + city, natural title/H1, category blocks, trust proof, and links to category/service pages.
Map category pages for real GBP categories, usually 3-5 and up to 10 where justified.
Map service pages for real GBP services and money terms. Prioritize the 11+ source-recommended service pages and 20-30 service pages only where justified by proof and scope.
Map Locations, About, and Contact trust pages. Avoid doorway-style location spam.
Run technical SEO packet: indexability, canonicals, robots, redirects, sitemap inclusion, broken links, duplicate metadata, title/H1 mismatches, schema validity, mobile/rendering, speed blockers.
Identify homepage mention/link gaps, category-to-service internal link gaps, service-to-category/up/across link gaps, and nav/footer-only link weakness. Body links matter.
Pick first 10-15 priority actions and 2-3 high-margin services for homepage links and separate tracking.
Create page briefs with URL, title/meta, H1, H2/H3, trust elements, FAQs, schema notes, CTA, internal links, proof needed, and approval gate.
Create Jakob execution packet with exact URLs, page targets, file/repo/CMS notes, internal links, schema notes, and approval gates.
Do not deploy, index, submit recrawls, or make live site changes until approval is recorded.
Canonical VGP Template 4

VGP - Days 15-30: Foundation Sprint Execution

Execute the approved Month 1 quick sprint: baseline setup, citation/NAP launch or cleanup queue, technical fixes, first Core 30 page work, schema/internal links, review process, and proof log.

13 folded subtasksDue +30 daysvisibility-growth-plancore30seophase:foundation-sprintclient-visibleapproval-gated
Folded-in detail modules
30-Day Quick Sprint ExecutionCore 30 Page Build/Refresh
Set up or fix Local Dominator baseline/cadence if approved, then record baseline links/screenshots and settings.
Launch approved citation/NAP campaign or build cleanup queue. If NAP is not confirmed, hold citation launch.
Implement approved technical quick fixes where Tekton controls the site: indexability, canonicals, sitemap/robots, redirects, broken links, duplicate metadata, schema errors, mobile/rendering blockers.
Apply approved safe GBP changes only if the exact payload was approved. Log before/after and post-change QA.
Implement approved homepage/GBP landing-page alignment: title, H1, body sections, category blocks, high-margin service links, trust proof, and local relevance.
Build or repair first approved Core 30 page: confirm target/page type, outline first, draft section-by-section, fact-check, add local proof, CTA, internal links, and schema notes.
Build or repair approved primary category, top secondary category, and top money service pages from the sprint packet.
Add or validate approved conservative LocalBusiness, Organization, PostalAddress, OpeningHours, Service, and FAQ schema only where valid and supported.
Fix body internal links: homepage to categories/services, categories to child services, services back/up/across. Nav/footer alone does not count.
Create review-specificity prompt/action item for the owner without faking, incentivizing, or over-scripting reviews.
QA desktop/mobile, links, schema validation, titles/H1s, screenshots, and generated/captured output.
Log live URLs, files/fields changed, publication dates, before/after notes, proof screenshots/links, and held approval items.
Do not submit indexing, trigger recrawls, or send client-facing updates until separately approved.
Canonical VGP Template 5

VGP - Days 31-60: Core 30 Buildout

Turn Month 1 maps into Jakob-owned implementation: category/service/location/trust pages, internal linking, schema/metadata, citation follow-through, review process, and first GSC/LD adjustments.

11 folded subtasksDue +60 daysvisibility-growth-plancore30seophase:core30-buildoutclient-visibleapproval-gated
Folded-in detail modules
60-Day Core 30 Buildout SprintCore 30 Page Build/Refresh
Select Month 2 priority actions from Month 1 proof, Service Truth Map, Core 30 gap map, Local Dominator baseline, and approval state.
Build or refresh remaining approved category pages tied to real GBP categories and service proof.
Build or refresh priority service pages tied to GBP/service truth map, high-margin services, and tracked keywords.
Create or repair Locations, About, and Contact trust pages where needed. Avoid doorway spam and unsupported location claims.
For every page build/refresh: confirm source facts, outline, draft, fact-check, add local proof, add contextual internal links, QA, log publish date, and schedule 2-4 week impact check.
Implement approved internal linking pass: homepage/category/service/support paths, anchors, hubs where needed, and body links over nav/footer-only links.
Implement approved schema/metadata/indexability fixes from the technical packet.
Follow through on citation/NAP launch or cleanup queue and log live/pending/submitted/failed/rejected/duplicate/needs-claim state.
Implement approved review-specificity process improvement and owner-response cleanup where applicable.
Review GSC crawl/index/impression signals and Local Dominator movement once enough time has passed.
Log completed URLs/fields/files, proof, remaining approvals, blocked items, and next gate.
Canonical VGP Template 6

VGP - Days 61-90: Optimization + Trust Expansion

Use early signals to optimize pages and expand trust: GSC almost-winners, Local Dominator weak zones, review specificity, citations/NAP, local authority, schema/entity trust, and AI visibility checks.

12 folded subtasksDue +90 daysvisibility-growth-planseophase:optimization-trustclient-visibleapproval-gated
Folded-in detail modules
GSC Almost-Winner OptimizationCitation/NAP Month 4 VerificationReview Specificity PlanLocal Authority Opportunity ReviewQuarterly AI/Entity Trust CheckSupporting + Geo Content Planner
Run 2-4 week post-publication rank review against original Local Dominator settings: top-3 percentage, average rank, geographic coverage, and weak zones.
Classify weak zones as proximity, topical relevance, geographic relevance, trust/link, or GBP/category/service issue.
Pull GSC/Bing almost-winners: positions 4-20, especially 11-20, high impressions/low CTR, question/long-tail/buyer queries, and query/page mismatches.
Draft approved metadata, content expansion, FAQ/PAA, internal-link, and support-content updates for almost-winner pages.
Create topical support briefs when service/topic relevance is weak. Supporting pages must reinforce target service/category pages.
Create geo support briefs only when rank maps justify geographic relevance work. Use credible landmarks/neighborhoods and avoid doorway spam.
Prepare the Month 4 citation/NAP verification checkpoint if a campaign was launched, and only spot-check live/pending/failed/duplicate listings early when drift, rejection, or launch proof requires it.
Run review specificity plan: count/rating/velocity, service/location/job-type language, owner responses, negative review triage, platform diversity, and next review action item.
Run local authority opportunity review: Chamber, BBB, Yelp, local orgs, sponsorships, media, events, schools, government/vendor lists, manufacturer/dealer directories, niche contractor directories.
Run AI/entity trust check: Bing Places, Apple Maps, Yelp/BBB/top citations, SameAs/entity consistency, schema, review language, local/community mentions, AI referrals/Bing where available, neutral AI recommendation tests.
Bundle citation, schema, review, AI visibility, mention/link, and almost-winner work into approval-gated execution packets.
Convert findings into 3-5 prioritized next-action tasks with owners, source evidence, and gates. Do not dump a generic backlog.
Canonical VGP Template 7

VGP - Monthly SEO Opportunity Review

Recurring decision loop: Demand → Visibility → Clicks → Leads → Next action. Produces 3-5 prioritized tasks or approval-gated recommendations, not a generic checklist.

15 folded subtasksDue +30 daysvisibility-growth-planseophase:monthly-cadenceclient-visibleapproval-gated
Folded-in detail modules
Monthly Growth CadenceGSC Almost-Winner OptimizationLocal Authority Opportunity ReviewReview Specificity Plan
Review carryover tasks, blockers, prior-month proof, and duplicate open TaskTracker work before creating anything new.
Crawl priority site pages and check technical/indexability blockers that outrank content expansion.
Pull Local Dominator current runs and compare against baseline/prior month by keyword, grid, average rank, top-3 percentage, and weak zones.
Pull GSC/GA4/Bing where available: queries, pages, clicks, impressions, CTR, positions, traffic quality, leads, and conversion proof.
Review Core 30/page impact: published URLs, crawl/index signals, titles/H1s, internal links, page movement, and gaps still blocking topical/local authority.
Review supporting content needs using PAA/customer questions, GSC, SERP examples, heatmap weak zones, credible landmarks/neighborhoods, and existing internal links.
Review GBP state: categories, services, description, photos/posts where applicable, review themes, landing-page alignment, and approval-gated change opportunities.
Review reviews: count/rating/velocity, service/location specificity, owner responses, negative review triage, and next review action item.
Review citations/NAP if checkpoint is due or drift is suspected: campaign status, duplicates, failed/pending listings, Bing/Apple/Yelp/BBB/niche directories.
Review authority opportunities: local organizations, sponsorships, media, chamber/BBB, manufacturer/dealer directories, and legitimate local mentions.
Run quarterly AI/entity trust checks when due: Bing, Apple Maps, SameAs/entity consistency, schema, trusted mentions, AI referrals, and neutral AI visibility tests.
Build SEO Opportunity Map: service, location, page/GBP asset, demand, visibility, clicks, leads, source evidence, next action, owner, and approval gate.
Create or draft only 3-5 prioritized execution/approval tasks with source evidence. Routine tasks can be created; strategic or live-impact actions stay approval-gated.
Prepare client-visible progress summary only after facts, completed work, and approval-sensitive language are verified.
Post monthly work log: Executed, Ready for approval, Needs access, Blocked, and Next action.

Operating rules

Do

  • Use GBP/category/service truth before page planning.
  • Build Core 30 before broad blog/topic maps.
  • Use Local Dominator and GSC to decide geographic vs topical expansion.
  • Keep TaskTracker as execution checklists and approval gates.
  • Document source data, decisions, proof, and exit state.
  • Assign website/SEO implementation to Jakob by default.

Do not

  • Do not create pages from every GBP service automatically.
  • Do not invent guarantees, services, locations, reviews, or schema claims.
  • Do not make live GBP/category/address/site/indexing/citation/client-facing changes without approval.
  • Do not treat local SEO like broad topical-map SEO first.
  • Do not publish raw AI content without fact-checking and local proof.
  • Do not run the old detailed sets as separate active workflows.

Source references

Primary local files used for this operating doc:

Internal Tekton SEO operations doc. This describes the process and task structure only. It does not authorize live client, GBP, website, citation, indexing, or external changes.