SEO Content Engine · Dependency Map

What each phase actually reads, and why

Seven phases run in order, brand foundation through article images. Each box shows only the inputs that phase consumes directly, not everything downstream inherits. Nodes are colored by kind so an engine file and a tool never look alike, and each carries a badge for how much of it is read.

Node kinds

Engine file a repo file the engine produced

Tool an MCP, service, or CLI

External input the live web / research

Gate must exist, not read as content

full reads the whole file part reads only named sections gate presence required, content not consumed out produced by the phase, not read

I build AI-powered SEO content systems for early-stage B2B SaaS: full-scale SEO, semantic topical maps, content briefs, content writing, and end-to-end content automation. This map is a sanitized view of the architecture; client names and proprietary methodology are abstracted.

LinkedIn Book a 30-min call salehin.riad96@gmail.com See the full system map