---
name: publish-seo-tree-site-directory
description: "Help readers see what your site covers and where to go next."
category: SEO & Content Architecture
stage: Post
definitive_article: https://blitzmetrics.com/seo-tree-site-directory/
status: needs-work
---

# Publish an SEO Tree site directory

Help readers see what your site covers and where to go next. This guide builds a linked map of your real pages and proof. Start with your checked page list and the home page that names the person or business.

**The path:** Checked hierarchy → Clickable map + text list → Source and visual checks → Public directory

**Start when:** The site’s checked hierarchy is ready for a public directory on its own domain.

## Inputs

- [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) with actual URL roles, entity home, topic/offer branches and supporting pages.
- Current source/builder, any existing directory URL, approved publishing scope and public-safe identity evidence.
- The [SEO Tree, the map that links a site’s proof to its main topics and offers](https://blitzmetrics.com/seo-tree-site-directory/) method, current [Article Guidelines](https://localservicespotlight.com/article-guidelines/) and real node/label data rather than decorative example leaves.

## Steps

1. Inspect the existing site directory and the source that owns it. Improve the current canonical route where it already serves this job. Choose a new directory path only when needed and agreed; do not rename a live method article or change the site’s routing just to force a preferred slug.
2. Use the verified entity home as trunk, actual major topics and offers as branches, and relevant existing content as leaves. Identify off-site roots from genuine identity or proof sources. An appearance, a profile and praise are distinct evidence types; the map must not imply endorsements that those sources do not contain.
3. Check each selected branch against the current site’s own navigation and content. Link its actual owning URL and describe what a visitor can learn or do there. Keep task recipes separate from topic hubs and historical stories. Missing or duplicate owners become explicit repair items before they are presented as resolved.
4. Build a useful clickable visual and matching visible text outline from the same data. Use clear groups, labels and real anchors that work with a keyboard. Show the actual scoped breadth; if the lead view is simplified, label its coverage and give a direct path to the complete directory.
5. Write a short grade-five opening that explains why this specific map helps the reader and how to use it. Put meaningful map content in the first desktop and mobile screen, followed by concise role explanations and real links. Preserve authentic relevant media and avoid a full-screen decorative title card.
6. Check every node’s destination, the text/visual agreement, public-safe source facts and the rendered page. Unknown destinations stay held or clearly labeled. Search-friendly markup can clarify visible facts but does not guarantee indexing, rankings or a search feature. Keep client metrics and private evidence out of public hidden data as well as visible copy.
7. Publish through the existing authorized source rail and verify the ordinary anonymous URL at the current required sizes. Save the source revision, date, checked links and remaining gaps. Use the directory for future page-placement decisions and send measured offer-link questions to the Money Tree task.

## 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 directory preserves its real source and route and represents the scoped published structure honestly.
- [ ] Clickable visual, text outline and actual destinations match, with meaningful first-screen content.
- [ ] Proof types and public/private boundaries remain truthful; normal public readback is recorded.
- [ ] 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 firm has three actual topic guides and ten case stories. The opening map shows all three topics and points to the full linked outline below. A social profile is labeled as identity proof, not a testimonial. One missing story URL is held for repair instead of drawn as a working leaf, and the publisher checks both mobile and desktop.

## Handoff and Content Factory context

[Place future content in the tree](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) uses the accepted directory. [Build the measured Money Tree](https://local-service-spotlight.github.io/task-library/?task=build-money-tree-site-diagram#task-build-money-tree-site-diagram) receives the actual offer branches when measured supporting counts are required; the site owner receives the dated release receipt.

The source places this task in Post within the [Content Factory: Produce, Process, Post and Promote](https://blitzmetrics.com/content-factory/). Produce captures real sources, Process makes the selected useful assets, Post releases approved work, and Promote distributes proven work. The actual handoff above determines what this task must supply.

## 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:** Post
- **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:** Draft URL or WP post ID, slug, author user ID, featured-image media ID. Promote reads the live URL, not the draft.

## 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-site-directory/)
- [This task in the Task Library](https://local-service-spotlight.github.io/task-library/?task=publish-seo-tree-site-directory#task-publish-seo-tree-site-directory)
- [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/)

### Primary method references

- [Google’s structured data introduction](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data)

## Review and evidence still needed

The inherited contributor status is `needs-work`. 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.