---
name: fit-every-new-piece-into-the-tree-structure
description: "Help each new page lead readers to the next useful step."
category: SEO & Content Architecture
stage: —
definitive_article: /seo-tree
status: complete
---

# Fit every new piece into the tree structure

Help each new page lead readers to the next useful step. This guide finds the right home for a new story or method on your site. Start with what the page helps someone do and your current site map.

**The path:** Reader purpose → Existing topic owner → Page role and parent → Checked links

**Start when:** A new or substantially revised piece has real source material and needs a role and link plan before release.

## Inputs

- The actual draft/source material, [Goals, Content, Targeting: the result, source material and people served](https://blitzmetrics.com/gct-business-strategy/), proposed title and current publication scope.
- [Map actual content roles](https://local-service-spotlight.github.io/task-library/?task=map-content-hierarchically-root-trunk-branches-leaves#task-map-content-hierarchically-root-trunk-branches-leaves) and the current topic, method and offer URLs; [Improve the existing owning page](https://local-service-spotlight.github.io/task-library/?task=enhance-existing-articles-before-creating-new-ones#task-enhance-existing-articles-before-creating-new-ones) decision when a possible duplicate exists.
- Current WordPress content type/taxonomy rules or the actual non-WordPress source; relevant proof and media rights.

## Steps

1. State the reader’s task or question and the evidence this piece supplies. Compare that purpose with the current map before choosing a URL. A generic subject label such as “marketing” does not tell you whether the piece is a recipe, a topic explanation or a dated story.
2. Find the maintained page that owns the same method or topic. If the new draft repeats its job, prepare an enhancement to that page. If it adds a distinct case, execution or event, identify its specific contribution and keep the main method on its existing hub.
3. Assign the actual page role: entity home, topic or method hub, service offer, task recipe, supporting story or utility page. Choose one primary parent for a supporting piece where appropriate, while retaining useful cross-topic links. Do not declare every branch a task recipe or force legal/contact pages into a content branch.
4. Write the upward link in a sentence that tells the reader why the parent helps. Where relevant, add the real service destination and the practical how-to route. Apply [entity linking, choosing the right home for a named person or topic](https://blitzmetrics.com/entity-linking/) to named people, companies and concepts so a provider help page does not replace our own explanation without a source or action reason.
5. Use existing supported categories and tags according to the site’s approved taxonomy. A category may support a branch without being the branch page itself. Preserve current Page/Post/builder ownership; do not force every definitive page into a new post or invent term assignments for unsupported content types.
6. Prepare the receiving hub’s useful link back to the new evidence, with a short account of what it proves. The new page’s outgoing parent link alone does not make it discoverable from the site. Verify both directions where the relationship genuinely benefits readers.
7. Check the draft’s plain opening, authentic lead visual, link text and target identity, then save its role and links in the inventory. Pass the exact revision to the authorized publisher. After release, verify the normal URL and update the dated map; a planned branch remains planned until it exists.

## Definition of done (QA checklist)

Quality assurance (QA) means checking the actual result against its agreed requirements. Follow the [Article Guidelines](https://localservicespotlight.com/article-guidelines/).

- [ ] The new piece has a clear role, unique purpose and verified parent or an explicit approved gap.
- [ ] Links use actual maintained destinations; a supporting story has a relevant incoming path.
- [ ] Existing URL, type, builder and taxonomy rules are preserved; no planned content is drawn as published.
- [ ] The exact output, source revision, reviewer evidence and remaining owner action are saved.
- [ ] For any reader-facing output, the short grade-five opening states the reader’s useful outcome and supporting method or proof. The body delivers that promise; a useful authentic visual appears in the first screen. Retain exact text and quoted reviewer evidence.

## Example(s)

**Fictional teaching example. This is not a client result or proof of a completed run.**

A fictional landscaper records a real patio build. The new case page supports the existing patio service and the installation method, but the site already has a main patio guide. The case links to both useful destinations, and the guide adds a short evidence link back. The map gains a leaf, not a duplicate main guide.

## Handoff and Content Factory context

[Place the accepted links](https://local-service-spotlight.github.io/task-library/?task=step-4-create-links-with-proper-anchor-text-and-placement#task-step-4-create-links-with-proper-anchor-text-and-placement) receives the exact source-to-target rows. [Publish the checked site directory](https://local-service-spotlight.github.io/task-library/?task=publish-seo-tree-site-directory#task-publish-seo-tree-site-directory) receives the checked role and published URL after release; an unresolved owning topic goes to the content owner.

This task supports the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Identity, proof, access or coordination can support several stages. Use the real inputs and receiving owner above; this task does not create unrelated transcripts, clips or ads merely because the diagram has four stages.

## Start with an agent

Give the [AI worker](https://blitzmetrics.com/build-agents/) this recipe, the real inputs, desired result and actions already authorized. Ask for the saved output, sources, checks and next owner. A [skill is a written recipe](https://localservicespotlight.com/plugin/); loading one does not prove account access or perform the task. Use the [installation guide](https://localservicespotlight.com/install/) if reusable setup is needed. A ZIP is a source snapshot, not an access grant or automatic update.

Use the app’s actual supported tools and verified file/account access. Keep a missing human verification step with its real owner. Recurring work needs its own configured job, trigger, timezone and observed result; this guide creates no schedule. Before any media playback, mute the player and set its volume to zero. If silence cannot be verified first, use captions, frames, metadata or another silent check.

## Record the real execution

Open the run record when work begins. Keep one execution ID, starting recipe revision, real inputs and current state. Write the [meta article, the record of this execution](https://blitzmetrics.com/meta-article-prompt/) with actual steps, results, checks, failures and next owner. Writing is required; public release follows existing authority. Link it to this recipe and the [Task Library](https://local-service-spotlight.github.io/task-library/).

Reuse the same execution ID for internal checks, revisions, retries and meta writing. A blocked run stays open with its dependency and owner, without an invented finish time. Dated public examples and distinct verified execution counts remain separate. Propose the smallest source-backed recipe improvement when the actual evidence reveals a defect.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** —
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Save this task’s actual output, source, date and checks where the receiving owner can read them. Follow the Inputs and Handoff sections for its next step.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- [Maintained source guide](https://blitzmetrics.com/seo-tree/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=fit-every-new-piece-into-the-tree-structure#task-fit-every-new-piece-into-the-tree-structure)
- [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Definitive article and task recipe standard](https://blitzmetrics.com/definitive-article-guide/)
- [How recipes and run records fit together](https://localservicespotlight.com/meta-articles/)

## Review and evidence still needed

The inherited contributor status is `complete`. It is preserved, not promoted by this rewrite. That label alone does not prove document readiness, account access, an actual execution or a client result.

The fictional example teaches the method and does not fill a real-run evidence gap. A named semantic reviewer must check the actual opening, full method, sources and handoff. Check the useful opening visual in the normal rendered guide at the current required desktop and mobile sizes, including 1280 × 800 and 390 × 844. Source readability checks do not prove public presentation or task execution.