Content Hub & Internal Link Planner

Choose a bounded website problem and a useful hub

Begin with a visitor task the website should resolve. Loom House chooses preparing for a first weaving class. Its hub introduces the experience and directs readers toward loom selection, materials and booking arrangements. Everything about weaving would be difficult to finish. A bounded task helps the editor decide whether each supporting page belongs and what a reader should be able to do afterward.

Gather the inventory yourself from editorial records, your content management system or a separate manual review. The planner accepts the dataset you prepare; it does not discover pages, fetch entered addresses, connect accounts or call a website API. One project holds one to twenty-four pages and up to ninety-six explicit link records. Use that space for a coherent working set rather than treating the maximum as a recommended website architecture.

Choose a hub that provides the starting explanation. Loom House selects First class guide, not its booking form, because the form completes a transaction rather than introducing the subject. You can leave the hub unset while deciding. Reachability then remains unknown instead of failed. Deleting a selected hub does not authorize the planner to choose a replacement.

The all-platform setting and the nine contexts identify the project only: Instagram, TikTok, YouTube, Facebook, LinkedIn, Threads, X, Snapchat and Reddit. They do not change the link algorithm, inspect a feed or generate platform-specific website requirements. A question first heard in a social conversation can inform a page, but the map still represents owned website resources. Keep the conversation source in your editorial notes rather than mistaking the context selector for imported evidence.

Give each page one explainable editorial responsibility

Create a record for each resource with a recognizable title, URL when known, intent, stage and useful notes. Write intent as a task rather than a topic: Choose between the available beginner looms is clearer than Looms. For the preparation page, use Arrive with the required materials. These statements help a reviewer notice two pages making the same promise even when their titles sound different or their proposed addresses look unrelated.

Use idea, draft and published to describe your own editorial assessment. An idea can have a title and intent before it has an address. A draft might have a proposed path without being publicly available. Published means you marked it that way; the planner does not request the URL to confirm publication. Changing a stage does not publish content, alter a content management system or automatically change any link state. Those are separate decisions.

Keep notes operational: Owner: Priya; check whether rental materials are included. Notes allow three hundred characters across no more than eight logical lines. Titles allow one hundred characters and intents one hundred sixty. These limits encourage a compact handoff, not a quality score. Keep longer research and approval histories in your existing editorial records, identified by a short reference.

Missing titles, URLs or intents remain visible as incomplete information, but they do not prevent saving a structurally valid draft or exporting it. That distinction matters during early planning: an unfinished resource should not need an invented address to survive the session. Give page identifiers stable, simple ASCII values if preparing JSON yourself. The identifier connects records; the title explains them. Renaming a page should not require rebuilding its identity from scratch.

Set the origin and understand address identity

Enter an absolute HTTP or HTTPS origin for the website, such as https://loom.example. An origin contains the scheme, host and any nondefault port, not a section path, query or fragment; a root slash is allowed. Credentials do not belong there. The original origin text is retained while its parsed origin provides the comparison base. Use a separate project for another origin rather than assuming related subdomains are interchangeable.

A page URL may be blank, a root-relative path such as /classes/first-visit/, or an absolute HTTP(S) address on that same origin. Protocol-relative values beginning with two slashes are not accepted. Entering any address keeps it as plain project text; the editor never opens it. Review the address in your ordinary website workflow when you need to establish what exists, where a redirect goes or which version the organization intends to maintain.

URL comparison uses the native URL parser, including its host, default-port and dot-path normalization, then ignores the fragment. Thus two records for /classes/first-visit/#materials and /classes/first-visit/#arrival identify the same page for duplicate review. The planner preserves path case, trailing slashes, query parameters and their order. It does not remove tracking parameters or infer that two different-looking addresses are aliases for the same content.

Treat duplicate normalized URLs as a finding to investigate, not a rejected project. Loom House might accidentally create separate records for arrival instructions and materials when both are sections of one guide. Combine the records if one page truly owns both jobs, or clarify the intended split. Conversely, a lack of duplicate findings does not prove unique content. Two distinct URLs can still contain the same explanation, and canonical or redirect decisions require separate website inspection.

Record directed links without blurring their states

Choose a source page, a destination page and the intended anchor wording. First class guide to Materials checklist describes a different journey from Materials checklist back to First class guide. Both directions may be useful, but each requires its own record. Self-links and duplicate directed pairs are not allowed; a reverse pair is allowed. The map represents page-to-page relationships rather than every occurrence of a repeated link within a source page.

Planned means the relationship is intended. Observed means you have recorded an observation. Both means the same directed relationship is planned and user-recorded as observed. It is not a stronger verification tier. Empty evidence is allowed in every state, so an observed label alone cannot establish who checked the page, when they checked it or which paragraph they saw. Add enough context to support the decision without implying that the tool independently verified it.

Loom House writes Checked 23 Oct, published guide, materials paragraph, wording matches checklist. Evidence holds two hundred characters; reference a work ticket for longer explanations. Anchor text has a separate one-hundred-twenty-character field. Keep check details separate from reader-facing wording. An instruction such as add after introduction belongs in a planned record’s evidence or the work ticket.

Use Plan hub round-trips only when that arrangement serves the reader. The action deliberately plans hub-to-support and support-to-hub relationships for every other entered page, within the link cap. Existing observations and evidence are preserved; an observed relationship becomes both rather than being duplicated. The operation is atomic, so it does not leave a partial batch if capacity prevents completion. Review the resulting anchors and editorial reasons before treating the generated plan as ready to implement.

Read the map and findings within the entered scope

Use the graph for the shape of entered relationships, then the matrix and checklist for details. Nodes show numbers and short title excerpts; tables and exports retain full titles and URLs. Arrow direction matters. Left-to-right or top-to-bottom layout changes presentation, not meaning. Selecting a node selects its page; the page list provides an equivalent control without using the canvas.

In the matrix, P means planned, O means observed and B means both; a dash means no entered relationship for that directed pair. A dash does not say the live website lacks the link. The graph also distinguishes states with visual treatments. Compare a source row against its intended next steps rather than scanning for the greatest number of filled cells. A dense matrix can still send a visitor toward irrelevant or unfinished resources.

The counts separate planned-only links from observed links, with both included in observed and also reported separately. Incoming and outgoing observed counts therefore include both-state relationships. All-link counts include every entered state. A page isolated across all entered relationships is different from a published non-hub page with no recorded observed incoming link. The former has no mapped connection; the latter may have plans or outgoing links that do not resolve its recorded incoming gap.

With a hub selected, observed reachability follows directed observed and both-state paths from that hub, excluding the hub itself from the finding list. A link pointing back toward the hub does not establish a route outward from it. Without a hub, that review is unavailable rather than failed. Every isolation, incoming-link and reachability finding concerns this dataset only. None establishes a site-wide orphan, a search indexing problem or a numerical SEO health score.

Resolve overlap through question ownership and next steps

Review pages with the same normalized intent together. Comparison applies Unicode NFC normalization, trimming, whitespace collapse and lowercase conversion. It does not infer synonyms or evaluate the complete articles. Prepare for your first class and Arrive ready for a beginner session can express similar responsibilities without entering the same review group. Read the promises yourself. Likewise, an identical intent is a prompt for discussion, not proof of keyword cannibalization or a prediction of ranking competition.

Loom House has What to bring and First visit checklist, both promising Prepare for a first class. Compare the material. If the checklist repeats the guide, one page may be clearer. If one explains choosing materials and the other gives a printable arrival sequence, revise the intents to distinguish those outcomes. Two social posts introducing different angles do not necessarily justify two pages.

Choose links at moments where another resource resolves the next question. A paragraph explaining loom sizes could point to the selection guide with wording such as Compare beginner loom sizes. The booking page might point back to preparation instructions after the session details. These are editorial proposals, not automatically installed links. Avoid adding every possible cross-link merely to remove an isolated-node finding; the explanation surrounding the link should justify the destination.

Prioritize work by reader consequence and publishing dependency. A preparation guide promising an unavailable materials checklist needs a decision before publication: finish the destination, revise the promise or defer the link. An optional project-gallery detour can wait. The planner offers stage and relationship information for that conversation, not a priority formula. Record the chosen next action in notes or a work ticket so an editor can distinguish an intentional omission from an overlooked task.

Turn the plan into a controlled publishing handoff

Assign implementation through the website’s normal editing process. Identify the source passage, destination, proposed wording and person responsible. Check destination readiness before changing the source: Loom House completes its materials checklist before revising the first-class introduction. Nothing entered here edits a website or publishes a social post. Someone still needs to implement and inspect the decisions.

After publication, inspect the actual source outside the planner. Read the sentence, follow the destination and check that the resulting page fulfills the promise. Record the scope and date of that manual check. Move a planned relationship to both when you want to retain its planning status alongside the observation, or use observed for a recorded relationship without that planned status. The tool does not make this decision from the page stage or a successful export.

Maintain separate dated JSON snapshots for meaningful handoffs. If a source changes later, an old observation remains a historical entry until you review it. The evidence field is not an append-only audit trail and there is no automatic freshness clock. If the relationship is removed, revise or remove its current record and keep the earlier snapshot when history matters. Do not use both to mean formerly present; it specifically combines planned and recorded observed status.

Review dependencies before deleting a page because linked records are affected. Moving pages changes review order, not live navigation. After duplicating a record, replace carried-over wording and inspect duplicate URL findings. Agree on the current file and owner when handing off. Independent copies can diverge; the planner is not a shared database that automatically merges colleagues’ changes.

Save the editable dataset and choose the right export

Save editable JSON deliberately before leaving. There is no autosave or project storage. Version-one JSON must match the exact schema, including required fields and supported enum values, with no unknown properties; the UTF-8 input limit is one MiB. Missing editorial details can remain blank when structurally valid. Importing JSON restores a compatible project, not an arbitrary website export, CSV inventory or social-platform archive. Keep your original editorial research outside this compact file.

Export Pages CSV for page records and Links CSV for directed relationships. Both quote all fields, use a byte-order mark and CRLF line endings, and neutralize spreadsheet-formula injection. JSON retains exact original values for precise round-tripping. Version one has no CSV import: colleagues can review the spreadsheet files, but the planner cannot reconstruct a project from them.

Choose the PNG for an abbreviated map, not a full inventory. Its longest edge is bounded at 4096 pixels, and readable viewing size depends on the actual project and display. The PDF report includes the map, complete page inventory, explicit link records, evidence and contextual next steps, within forty MiB and fifty pages. It is rasterized review material; CSV and JSON preserve selectable text and data for other handoff needs.

Use Copy checklist for a compact task handoff, then confirm the clipboard action succeeded before relying on it. Private fields are rendered as text or on the local canvas rather than executed as HTML or fetched as remote images. Ordinary existing site analytics remain, but entered fields are not included in them. Keep project files in an appropriate location for their contents, especially when notes contain unpublished plans, and reopen the saved JSON when the next review begins.

Questions about planning content and internal links