Problem
Teams were spending roughly a week per website deciding which pages to create, how to group them by topic and how those pages should link together.
PHASAKORN TRAKLANG · SEO LEAD
I turn search data, technical detail and business pressure into systems teams can understand and ship.
Automation · PROJECT BUILD
SEO Cluster System — Content Planning Automation
Reported workflow improvement: planning time reduced from about 1 week per website to about 1 hour. The report library covers 15 website datasets and turns thousands of pages into a clear, implementation-ready content plan.
The brief
Who it is for
Teams that need a repeatable workflow and a clear next action
What Peach designed and owned
System framing, SEO logic, implementation planning and the handoff to a team that can operate it.
Stack and operating context
Python, deterministic SEO engine, AI-assisted analysis, CSV/HTML/Excel/CMS exports
Interactive workflow
From signal to a decision someone can ship.
01Capture the evidence
02Set the priority
03Assign the owner
04Recheck the change
05Record the outcome
Build evidence
Evidence map
Source inputs, diagnostic rules, human review gates and report outputs form a documented sequence; no client interface is represented as live data.
Architecture / data flow
Python, deterministic SEO engine, AI-assisted analysis, CSV/HTML/Excel/CMS exports connect through a capture → model → ship → verify loop.
Verified scale or capability
Reported workflow improvement: planning time reduced from about 1 week per website to about 1 hour. The report library covers 15 website datasets and turns thousands of pages into a clear, implementation-ready content plan.
Review boundary
Human approval remains required before an automated recommendation becomes published or assigned work.
Decision boundaries
Human review
Automation surfaces context and options; a person approves the priority, owner and implementation decision.
Evidence boundary
Only verified, permitted evidence is published as an outcome. Capability descriptions remain clearly labelled as capability.
Limitations
This page describes the build and operating model. It does not claim client performance, adoption or revenue impact without a separately published source and permission.
What this proves about Peach
Reported workflow improvement: planning time reduced from about 1 week per website to about 1 hour. The report library covers 15 website datasets and turns thousands of pages into a clear, implementation-ready content plan. It also shows how I turn ambiguity into a system the team can continue operating.
Next project