## 1. Mandate, Audience, and Definition of Done **Outcome.** If this plan works, bottom-of-funnel B2B buyers who are 2–4 weeks from choosing a project management tool find competitor-neutral, decision-useful content in organic search and are routed from it to the pricing and comparison pages. Organic search traffic to those pages rises by 50% over the baseline, measured across the next two quarters. The plan schedules and gates the content; it does not claim that any traffic, ranking, or lead result has occurred or will occur. **Stakeholders.** | Role | Holder | Status | |---|---|---| | Writers | Two in-house writers (Writer 1, Writer 2); one freelancer | Roles supplied; names not supplied | | Editor | Not supplied | Must be named before any Section 12 approval (R9) | | Distribution owner (internal linking, on-page updates, search-tooling reads) | Not supplied | Must be named (R9) | | Metric owner (owns the +50% number) | Not supplied | Must be named (R9) | | Legal reviewer (required by the hard constraint) | Not supplied | Must be named (R9, R10) | | Page owner for pricing and comparison pages | Not supplied | Must be named (R8, R9) | **Requirements table.** | ID | Requirement | Source | |---|---|---| | R1 | Grow organic search traffic to pricing and comparison pages by 50%, judged over the next two quarters | Supplied | | R2 | Serve bottom-of-funnel B2B buyers actively comparing project management tools, 2–4 weeks from a purchase decision | Supplied | | R3 | Cover a 6-month horizon with weekly publishing | Supplied | | R4 | No direct product comparisons naming specific competitors without legal review | Supplied (hard constraint) | | R5 | Execute with two in-house writers plus one freelancer | Supplied (background) | | R6 | Build on the 40 existing blog posts; audit first, and update or consolidate rather than duplicate | Supplied (background) | | R7 | Baseline organic traffic and the measurement definition for the 50% target are not supplied | Gap revealed by inputs | | R8 | Which URLs count as "pricing and comparison pages", and who may edit them, is not supplied | Gap revealed by inputs | | R9 | Named holders for editor, distribution owner, metric owner, legal reviewer, and page owner are not supplied | Gap revealed by inputs | | R10 | Legal review turnaround, and what counts as a "direct product comparison", are not supplied; whether existing comparison pages already comply with R4 is unknown | Gap revealed by inputs | | R11 | Share of each writer's time available for this plan is not supplied | Gap revealed by inputs | | R12 | The 6-month horizon and the two-quarter judging window are effectively the same period, leaving little room for ranking lag on late-published pieces | Gap revealed by inputs | **Explicit exclusions.** This plan does not authorize: any named-competitor comparison (feature, price, or performance) absent recorded legal review; any invented search volume, ranking, or traffic figure; any published statistic without a cited source; paid promotion spend; formats or channels outside Section 5; topics outside Section 4; or new pieces that duplicate an existing post. **Solution shape.** - Data-driven (owned by the metric owner and distribution owner): baseline, query and SERP review, prioritization of refreshes versus new pieces, test pass/fail reads. - Editorial judgment (owned by the editor and writers): angle, criteria framing, voice, internal-link placement, page copy. - Legal judgment (owned by the legal reviewer): what counts as a direct product comparison, and clearance of anything naming a competitor. **Completion criteria** (each externally checkable): - **Measurement (R7, R8):** a dated baseline snapshot for the defined page set exists from real analytics, signed off by the metric owner. - **Goal (R1):** measured organic traffic to the page set at the end of the second quarter is compared to that baseline, and the result (met or gap) is reported from real data. - **Publishing (R3, R5):** each published piece has a live URL and publication date, logged against its calendar slot; missed slots are listed. - **Constraint (R4, R10):** zero published pieces contain a competitor-naming comparison without a recorded legal sign-off, verified by pre-publication check records and a post-publication site scan. - **Inventory (R6):** each of the 40 existing posts has a recorded disposition, and no calendar title duplicates an existing post. - **Roles and capacity (R9, R11):** named holders exist for all roles, and a capacity log shows actual hours per piece. - **Validation (R12):** every resourcing-critical Section 7 item is resolved by a real content test, or reported as a named blocker. A calendar spreadsheet alone is NOT completion (→ Section 13). ## 2. Editorial Instructions ``` Execute this plan against real search and audience data, not a simulation of it. Review existing content inventory and past performance first. Update or consolidate an existing piece instead of duplicating it under a new title. Resolve every <VALIDATE> item using current search/keyword data or a small content test — not internal guesswork. Produce actual published pieces and a tracked distribution effort; do not stop at a calendar. Run the content test defined in Section 9, read the actual results, and adjust the pillar mix or cadence before committing the full calendar. Stop producing an unchanged underperforming format; report a concrete blocker when progress needs resourcing, legal sign-off, or data outside your authority. Do not publish a piece with an unverified statistic, a missing required disclaimer, or a claim contradicting a stated hard constraint. Continue low-cost drafting and research while a resourcing-critical validation is pending. Commit a full publishing cadence or distribution spend only within approved authority. Report progress using actual publishing and traffic data, and clearly separate drafted, tested, and fully committed status. Operational defaults (editorial calendar tool, internal review cadence, byline conventions) may be chosen and documented autonomously. Do not autonomously invent traffic or ranking results, or commit resourcing beyond an approved pilot. ``` In particular: do not assume that competitor-neutral, criteria-based content can capture enough comparison-stage search demand to deliver a 50% traffic increase — `<VALIDATE: criteria-demand-share>` is a validation item, not an editorial default. ## 3. Audience and Topic Assumption Ledger **Supplied inputs** | Assumption ID | Claim | Source | Confidence | Consequence if wrong | |---|---|---|---|---| | A1 | The audience is bottom-of-funnel B2B buyers actively comparing project management tools, 2–4 weeks from a decision | Supplied | High (as stated) | Pillars would target the wrong journey stage | | A2 | The goal is +50% organic search traffic to pricing and comparison pages, judged over two quarters | Supplied | High (as stated) | Effort would be measured against the wrong outcome | | A3 | The horizon is 6 months with weekly publishing | Supplied | High (as stated) | Cadence math in Section 5 fails | | A4 | 40 existing posts exist; the team is 2 in-house writers plus 1 freelancer | Supplied | High (as stated) | Refresh-first strategy and effort estimates fail | | A5 | No direct product comparisons naming specific competitors without legal review | Supplied (hard constraint) | High (immovable) | Legal exposure; content withdrawn | **Claims about audience search intent and journey stage** | Assumption ID | Claim | Source | Confidence | Consequence if wrong | |---|---|---|---|---| | A6 | Buyers at this stage search with evaluation modifiers (pricing, cost, alternatives, "best for [team type]", how to choose, migration) and land on pricing and comparison pages from those queries | Unverified — `<VALIDATE: bofu-query-patterns>` (routine) | Low | Pillars P1–P4 target queries the audience does not use | | A7 | Competitor-neutral, criteria-based content can capture enough comparison-stage search demand to move pricing and comparison page traffic by 50%, given A5 rules out competitor-named pages | Unverified — `<VALIDATE: criteria-demand-share>` (resourcing-critical) | Low | If most comparison-stage demand is competitor-named ("X vs Y"), the compliant pillar set is too small to reach the goal | **Claims about topic demand** | Assumption ID | Claim | Source | Confidence | Consequence if wrong | |---|---|---|---|---| | A8 | Pricing and cost queries for project management software have enough demand and a winnable results page to matter | Unverified — `<VALIDATE: pricing-query-demand>` (routine) | Low | P2 yields little traffic; fallback pillar weakens | | A9 | Team-type and use-case queries ("for agencies", "for software teams") have enough demand and a winnable results page | Unverified — `<VALIDATE: segment-query-demand>` (routine) | Low | P3 is deprioritized | | A10 | Internal links from supporting pieces pass measurable traffic and clicks to the pricing and comparison pages | Unverified — `<VALIDATE: internal-link-lift>` (routine) | Low | Supporting content grows blog traffic without reaching the target pages | | A14 | New and refreshed pieces can move pricing and comparison page traffic inside the judging window; pieces published late in the horizon have under two months to accrue | Unverified — `<VALIDATE: rank-lag-two-quarters>` (resourcing-critical) | Low | The 50% target is unreachable regardless of content quality | **Claims about competitive content coverage, baseline, and capacity** | Assumption ID | Claim | Source | Confidence | Consequence if wrong | |---|---|---|---|---| | A11 | Competitor comparison pages and third-party review or aggregator sites hold the top positions for evaluation queries, shaping which queries are winnable | Unverified — `<VALIDATE: competitor-serp>` (routine); no current source cited because the product and competitor set were not supplied | Low | Topics are chosen against SERPs that cannot be displaced | | A12 | The current organic traffic baseline for the pricing and comparison pages is unknown | Unverified — `<VALIDATE: baseline-traffic>` (routine) | Low | The +50% target cannot be measured | | A13 | Some of the 40 existing posts are refreshable or consolidatable for this audience; their performance is unknown | Unverified — `<VALIDATE: inventory-performance>` (routine) | Low | New pieces duplicate or cannibalize existing ones | | A15 | Two writers and one freelancer can sustain weekly publishing of this scope alongside existing duties | Unverified — `<VALIDATE: weekly-capacity>` (resourcing-critical) | Low | Cadence collapses or quality drops | **Assumption whose failure most invalidates the pillar structure: A7.** All four pillars are competitor-neutral by design because of A5. If most bottom-of-funnel demand sits in competitor-named queries, the pillars would be sound editorially but too small for the goal. Section 9's first test must probe A7 before any other pillar-wide claim. ## 4. Content Pillars and Editorial Guidelines ``` PILLAR P1 — Buying Criteria and Evaluation Frameworks (PROVISIONAL: A7, A6) Definition: Competitor-neutral guides that help a buyer define requirements, score options, and run a demo or RFP. Audience need: A structured way to compare tools without vendor bias (A1, A6). Business goal link: Readers in comparison mode are routed from the guide to the comparison pages and pricing page. PILLAR P2 — Pricing and Total Cost Clarity (PROVISIONAL: A8, A10) Definition: Explainers on pricing models, total cost of ownership, free versus paid tiers, and budget justification. Audience need: Understanding what a purchase will actually cost before committing (A1, A8). Business goal link: Pricing-intent queries and internal links point directly at the pricing page. PILLAR P3 — Team-Type and Use-Case Fit (PROVISIONAL: A9) Definition: Guides on what to look for in a project management tool by team type and size, without naming competitors. Audience need: Confidence that a tool suits a specific team's workflow (A1, A9). Business goal link: Segment queries route to the comparison pages and pricing. PILLAR P4 — Switching and Rollout Confidence (PROVISIONAL: A6) Definition: Migration checklists, trial plans, and onboarding guidance that lower the perceived risk of a purchase. Audience need: Reassurance that switching in a 2–4 week window is manageable (A1, A6). Business goal link: Late-stage readers are routed to pricing and trial paths. ``` **Editorial voice and style rules.** - Tone: direct, practical, buyer-side; the reader is a decision-maker under time pressure. - Reading level: plain business English, short paragraphs, no jargon without a definition. - Formatting: one clear target query per piece; a summary near the top; scannable headings; tables or checklists where the reader will compare; a stated "last reviewed" date; one contextual link to a pricing or comparison page. - Avoid: unsourced statistics; superlatives ("best", "#1", "leading") without support; naming or unmistakably identifying a competitor; disparaging comparisons; invented customer quotes or case studies; keyword stuffing. - Required disclaimers: none supplied. Any disclaimer legal later specifies becomes a hard-constraint row in Section 1. **The one topic area deliberately NOT covered:** named-competitor direct product comparisons (head-to-head pages, "X vs Y", "X alternatives"). Hard constraint R4 requires legal review, and no review process, turnaround, or reviewer was supplied. A pilot of such content can be requested only through action AP-9 in Section 12. **Evidence rule.** Pillars are a draft framework for review, not a locked editorial calendar — publication is gated by Section 12, not by finishing this section. ## 5. Channel and Format Contracts Cadence figures are template counts across the 24 publishing weeks (W3–W26). Only the pilot slots (W3–W10) are within reach of near-term approval; W11–W26 slots are NOT committed. **C1 — Long-form blog guide (new piece)** - **Primary pillar(s):** P1, P2, P3, P4 - **Cadence:** 18 of 24 publishing slots (template); pilot slots W3, W4, W6, W7, W8, W10 - **Primary metric and target:** organic clicks on the piece's target query cluster, and click-through from the piece to a pricing or comparison page. Numeric target NOT SET here; the metric owner sets it after `<VALIDATE: baseline-traffic>` resolves. - **Production effort estimate:** about 10–14 person-hours per piece (draft 6–8, edit 2–3, on-page and links 1–2, constraint check 1). Planning estimate, not measured; replaced by logged hours (`<VALIDATE: weekly-capacity>`). - **Owner:** Writer 1 or Writer 2 for P1 and P2; freelancer drafts for P3 and P4 under the editor's review; editor is accountable. **C2 — Existing-post refresh or consolidation (blog)** - **Primary pillar(s):** P1, P2, P3 (selected by the T3 audit) - **Cadence:** 4 of 24 slots (W5, W15, W25, W26) - **Primary metric and target:** change in clicks and in click-through to pricing or comparison pages versus the prior 4-week window. Numeric target NOT SET until baseline exists. - **Production effort estimate:** about 4–6 person-hours per piece. Planning estimate. - **Owner:** Writer 1 or Writer 2; editor accountable. **C3 — On-page update to a live pricing or comparison page** - **Primary pillar(s):** P1, P2 - **Cadence:** 2 of 24 slots (W9, W20) - **Primary metric and target:** organic sessions to the defined page set versus the dated baseline. The +50% target is judged at page-set level at the end of Q2, not per update. - **Production effort estimate:** about 4–8 person-hours plus page-owner and CMS time (not supplied). Planning estimate. - **Owner:** Writer 2 with the page owner (to be named); distribution owner accountable for link and tracking checks. **Planning arithmetic.** 18 × 10–14 + 4 × 4–6 + 2 × 4–8 gives roughly 204–292 person-hours, about 8.5–12 hours per week across the three writers. That is the figure `<VALIDATE: weekly-capacity>` must test against real availability. **Channels and formats NOT in scope, and why:** - Newsletter and social posting: no existing channel or capacity was supplied, and the goal is organic search traffic. - Short-form video, webinars, podcasts: no capacity supplied; not needed for search-intent content. - Link-building outreach and guest posting: no resourcing supplied. - Paid promotion: not planned; any spend requires AP-8 in Section 12. - Programmatic or bulk-generated pages: outside the editorial-review model and a duplication risk. **Internal vs. external claim separation.** Figures that may appear in published pieces: only independently sourced, cited statistics and product facts verified by the product owner on the publication date (for example, current published pricing checked against the live pricing page). Figures that stay internal: cadence, effort estimates, targets, baselines, traffic and click data, capacity, validation status, and everything in Sections 7 through 13. ## 6. Editorial Calendar Architecture **Template calendar.** These titles are representative examples, not supplied topics. Every row is unapproved until it passes Section 12, and none is a claim that content exists. Entry hypotheses (H1–H6) are defined below the table. | Period | Pillar | Working Title | Format/Channel | Owner | Status | |---|---|---|---|---|---| | W1 | n/a | Baseline snapshot and inventory audit (no publication) | Internal | Metric owner + Editor | Prep | | W2 | n/a | Query review, legal scoping request, calendar finalization (no publication) | Internal | Editor + Distribution owner | Prep | | W3 | P1 | How to Choose Project Management Software: A Buyer's Evaluation Scorecard (H1) | C1 | Writer 1 | TEMPLATE — single-piece pilot; needs AP-1 | | W4 | P2 | Project Management Software Pricing Models Explained (H2) | C1 | Writer 2 | TEMPLATE — expanded pilot; needs AP-2 | | W5 | P1 | Refresh: highest-potential existing post from the T3 audit (title set after T3) (H3) | C2 | Writer 1 | TEMPLATE — expanded pilot; needs AP-2 | | W6 | P3 | Project Management Software for Agencies: What to Look For (H4) | C1 | Freelancer | TEMPLATE — expanded pilot; needs AP-2 | | W7 | P2 | Total Cost of Ownership for Project Management Software: Seats, Add-Ons, Onboarding (H2) | C1 | Writer 2 | TEMPLATE — expanded pilot; needs AP-2 | | W8 | P4 | Moving from Spreadsheets to a Project Management Tool: A 30-Day Rollout Plan (H5) | C1 | Freelancer | TEMPLATE — expanded pilot; needs AP-2 | | W9 | P2 | Pricing page update: plan-inclusion clarity, FAQ, contextual links (H6) | C3 | Writer 2 + page owner | TEMPLATE — needs AP-3 | | W10 | P1 | Must-Have vs Nice-to-Have Project Management Features by Team Size (H1) | C1 | Writer 1 | TEMPLATE — expanded pilot; needs AP-2 | | W11 | P3 | Project Management Software for Software Teams: Evaluation Criteria (H4) | C1 | Freelancer | NOT COMMITTED — needs AP-4 to AP-7 | | W12 | P4 | A 14-Day Trial Plan for Evaluating a Project Management Tool (H5) | C1 | Writer 1 | NOT COMMITTED — needs AP-4 to AP-7 | | W13 | P1 | Project Management Software RFP Template (H1) | C1 | Writer 2 | NOT COMMITTED — needs AP-4 to AP-7 | | W14 | P2 | Free vs Paid Project Management Plans: When Free Stops Being Enough (H2) | C1 | Writer 1 | NOT COMMITTED — needs AP-4 to AP-7 | | W15 | P3 | Refresh: best-performing team-type or evaluation post, per test read (H3) | C2 | Writer 2 | NOT COMMITTED — needs AP-4 to AP-7 | | W16 | P3 | Project Management Software for Marketing Teams: What to Look For (H4) | C1 | Freelancer | NOT COMMITTED — needs AP-4 to AP-7 | | W17 | P4 | Data Migration Checklist for Switching Project Management Tools (H5) | C1 | Writer 1 | NOT COMMITTED — needs AP-4 to AP-7 | | W18 | P1 | Security and Admin Controls Checklist for Evaluating Project Management Tools (H1) | C1 | Writer 2 | NOT COMMITTED — needs AP-4 to AP-7 | | W19 | P2 | Building the Business Case for a Project Management Tool Purchase (H2) | C1 | Writer 1 | NOT COMMITTED — needs AP-4 to AP-7 | | W20 | P1 | Comparison page update: criteria table and FAQ, constraint-checked (H6) | C3 | Writer 2 + page owner | NOT COMMITTED — needs AP-3 and AP-4 | | W21 | P3 | Project Management Software for Growing Teams (10–50 People) (H4) | C1 | Freelancer | NOT COMMITTED — needs AP-4 to AP-7 | | W22 | P4 | Onboarding a Team to a New Project Management Tool: The First 30 Days (H5) | C1 | Writer 1 | NOT COMMITTED — needs AP-4 to AP-7 | | W23 | P1 | Questions to Ask in a Project Management Software Demo (H1) | C1 | Writer 2 | NOT COMMITTED — needs AP-4 to AP-7 | | W24 | P2 | Annual vs Monthly Billing for Project Management Tools: How to Decide (H2) | C1 | Writer 1 | NOT COMMITTED — needs AP-4 to AP-7 | | W25 | P2 | Refresh: pricing-cluster consolidation, per test read (H3) | C2 | Writer 2 | NOT COMMITTED — needs AP-4 to AP-7 | | W26 | P1 | Refresh: top evaluation post; measurement close-out for Section 13 (H3) | C2 | Writer 1 + Metric owner | NOT COMMITTED — needs AP-4 to AP-7 | **Entry hypotheses and checks (Principle D).** | ID | Hypothesis tied to the goal | How it is checked | |---|---|---| | H1 | Competitor-neutral evaluation guides (P1, C1) rank for comparison-stage queries and send readers to comparison or pricing pages (A6, A7) | Impressions and clicks on the target query cluster in search tooling; recorded click path from piece to target pages | | H2 | Pricing and cost guides (P2, C1) capture pricing-modifier queries and send readers to the pricing page (A8, A10) | Impressions on pricing-modifier queries; recorded click path to the pricing page | | H3 | Refreshing an already-indexed post moves faster than a new piece (A13, A14) | Time to first change in impressions, refreshed versus new, from dated logs | | H4 | Team-type guides (P3, C1) capture segment queries and route to comparison pages (A9) | Impressions on segment queries; click path to comparison pages | | H5 | Switching and rollout guides (P4, C1) capture late-stage risk queries and route to pricing or trial paths (A6) | Impressions on migration and trial queries; click path | | H6 | Direct on-page updates to the pricing and comparison pages raise their organic traffic (A10, A12) | Page-set organic sessions against the baseline snapshot, annotated with each change date | **Entry schema (calendar tool fields).** ``` entry_id | week | pillar | contract | working_title | target_query_cluster hypothesis_id | owner | constraint_check (pass/fail/legal-routed) | dedupe_check (existing URL or none) approval_action_id | status | published_url | published_date ``` **Common calendar practices deliberately NOT used:** daily posting; bulk or programmatic page generation; "X vs Y" and "X alternatives" pages; "best of" listicles ranking named competitors; gated content that hides text from search; new pieces that restate an existing post instead of refreshing it. Any topic not already scoped in Section 4 is ruled out until Section 4 is amended and reapproved. ## 7. Validation and Research Requirements **Resourcing-critical (a)** **`<VALIDATE: criteria-demand-share>`** (A7) - **What must be established:** whether competitor-neutral evaluation, pricing, segment, and switching content can attract enough comparison-stage search demand to move pricing and comparison page traffic by 50%, versus demand concentrated in competitor-named queries. - **How to establish it:** run a real content test (W3 pilot piece, then the W4–W10 expanded pilot). - **Dependent tasks/actions:** P1 through P4 as full-cadence pillars; AP-4 to AP-7; AP-9 (which activates only if this resolves adversely). - **Status until resolved:** the W3 P1 scorecard (single-piece pilot) stands in. It must not receive full-cadence commitment until this item is resolved by real test results. **`<VALIDATE: rank-lag-two-quarters>`** (A14) - **What must be established:** whether new and refreshed pieces can produce measurable movement on pricing and comparison page traffic within the judging window, and how many weeks a new piece takes to show first impressions. - **How to establish it:** run a real content test comparing a refreshed existing post (W5) against new pieces (W3, W4, W6, W7, W8, W10) using dated logs. - **Dependent tasks/actions:** the W11–W26 calendar shape (refresh versus new mix); AP-4 to AP-7; the achievability statement in Section 13. - **Status until resolved:** the W3 new piece and W5 refresh stand in. Neither may receive full-cadence commitment until resolved. **`<VALIDATE: weekly-capacity>`** (A15, R11) - **What must be established:** whether two writers and one freelancer can sustain weekly publishing of this scope, in real logged hours per piece. - **How to establish it:** run a real content test of the pilot cadence (W3–W10) with per-piece hours logged. - **Dependent tasks/actions:** C1, C2, C3 cadence commitments; AP-4 to AP-7; any extension of freelancer scope. - **Status until resolved:** the W3–W10 pilot cadence stands in. It must not be extended to a full-cadence commitment until resolved. **Routine (b)** **`<VALIDATE: baseline-traffic>`** (A12, R7) - **What must be established:** current organic sessions and clicks to the defined pricing and comparison page set. - **How to establish it:** check current search/competitive data before finalizing, using existing analytics and search tooling. - **Dependent tasks/actions:** T2, per-channel targets in Section 5, the goal check in Section 13. **`<VALIDATE: inventory-performance>`** (A13, R6) - **What must be established:** which of the 40 posts already earn impressions or clicks, which relate to evaluation, pricing, team type, or switching, and which overlap. - **How to establish it:** check current search/competitive data before finalizing. - **Dependent tasks/actions:** T3, W5 refresh title, C2 slot selection, the dedupe check. **`<VALIDATE: bofu-query-patterns>`** (A6) - **What must be established:** which evaluation-modifier query patterns the audience actually uses at this stage. - **How to establish it:** check current search/competitive data before finalizing. - **Dependent tasks/actions:** P1 and P4 target queries; final calendar titles. **`<VALIDATE: pricing-query-demand>`** (A8) - **What must be established:** demand and results-page difficulty for pricing and cost queries. - **How to establish it:** check current search/competitive data before finalizing. - **Dependent tasks/actions:** P2 titles; fallback-pillar choice in Section 9. **`<VALIDATE: segment-query-demand>`** (A9) - **What must be established:** demand and results-page difficulty for team-type and use-case queries. - **How to establish it:** check current search/competitive data before finalizing. - **Dependent tasks/actions:** P3 titles and team-type selection. **`<VALIDATE: internal-link-lift>`** (A10) - **What must be established:** whether existing internal links from blog posts already send measurable clicks to the pricing and comparison pages. - **How to establish it:** check current search/competitive data before finalizing, using existing click-path data. - **Dependent tasks/actions:** internal-link placement rules; C3 link updates. **`<VALIDATE: competitor-serp>`** (A11) - **What must be established:** who currently holds the top results for the target query clusters, and what page types they are. - **How to establish it:** check current search/competitive data before finalizing. - **Dependent tasks/actions:** topic selection per pillar; expected-result statements in Section 9. **Existing-data-first.** Existing analytics, search tooling, and the 40-post performance history are checked before any new keyword research is commissioned. Any demand figure quoted anywhere in this plan's execution is sourced from that data or a cited current source, or flagged with its `<VALIDATE: id>`; no figure is ever inserted for plausibility. ## 8. Production Sequence and Requirement Traceability **Task list (dependency-ordered)** | # | Task | IDs | Depends on | |---|---|---|---| | T1 | Name the editor, distribution owner, metric owner, legal reviewer, and page owner; define the pricing and comparison page set and edit rights | R8, R9 | None | | T2 | Capture the dated baseline snapshot for the page set from real analytics; write the measurement definition | R1, R7, A2, A12 | T1 | | T3 | Audit the 40 posts and the existing comparison pages; record a disposition for each; check existing comparison pages against R4 | R6, R10, A13 | T1 | | T4 | Review existing query, click-path, and results-page data for evaluation, pricing, segment, and switching queries | A6, A8, A9, A10, A11 | T2, T3 | | T5 | Finalize pillars and the calendar from T3 and T4; keep pillar provisional flags until validation resolves | R2, R3, R12, A1, A3, A4 | T3, T4 | | T6 | Hard-constraint check for R4: pre-publication scan of every piece and page edit for competitor names or unmistakable references; any hit is routed to the legal reviewer and recorded pass/fail on the calendar entry | R4, A5 | T1 | | T7 | Obtain written legal scoping of "direct product comparison" and the review turnaround | R4, R10 | T1 | | T8 | Produce the W3 pilot piece: draft, edit, dedupe check, T6 check, internal review | R2, A1, A7 | T5, T6, T7 | | T9 | Human review and publication of the pilot piece (AP-1); log URL and date | R3 | T8, AP-1 | | T10 | Read the early signals of the single-piece pilot per Section 9 (indexation, first impressions, click path) | A6, A7, A14 | T9 | | T11 | Produce and publish the W4–W10 expanded pilot (AP-2, AP-3), logging hours per piece | R3, R5, R11, A15 | T9, AP-2 | | T12 | Read expanded-pilot results at the end of W10; adjust pillar mix, format mix, or cadence; select the fallback pillar if needed | A6–A10, A14, H1–H6 | T10, T11 | | T13 | Commit the full W11–W26 cadence (AP-4 to AP-7), conditional on every resourcing-critical item resolved | R3, R12, A7, A14, A15 | T12, T14 clear | | T14 | Report a named blocker for every unresolved resourcing-critical item; filed at the T12 read-out whether or not blockers exist, and completed before T13 executes | A7, A14, A15 | T12 | **Traceability table** | Requirement / Assumption | Pillar / Piece | Owner | Acceptance Check | |---|---|---|---| | R1 | C3 page updates (W9, W20) and all published pieces | Metric owner | End-of-Q2 page-set organic traffic compared with the T2 baseline from real data; met or gap reported | | R2 | W3 "How to Choose Project Management Software: A Buyer's Evaluation Scorecard" | Editor | Brief records journey stage, target query, and a next-step link to a pricing or comparison page | | R3 | Calendar slots W3–W26 | Editor | Publication log versus calendar; missed slots listed | | R4 | Every piece and page edit, starting with the W3 scorecard | Editor + legal reviewer | T6 record shows zero competitor references, or a legal sign-off is logged before publication | | R5 | W6 "Project Management Software for Agencies: What to Look For" (freelancer draft) | Editor | Capacity log shows the freelancer draft; the piece passes the same T6 and dedupe checks | | R6 | W5 refresh (title set after T3) | Editor | Disposition sheet covers all 40 posts; every calendar title passes the dedupe check | | R7 | Baseline snapshot document (internal deliverable) | Metric owner | Dated snapshot and written metric definition exist and are signed | | R8 | Page-set register (internal deliverable) | Distribution owner | URL list confirmed in writing by the page owner | | R9 | Role register (internal deliverable) | Plan requester | All five roles have a named person | | R10 | Legal scoping memo and existing-comparison-page audit (internal deliverables) | Legal reviewer | Memo defines the term; each existing comparison page has a pass or flagged result | | R11 | W4–W10 expanded pilot | Editor | Capacity log with hours per piece exists for all pilot pieces | | R12 | W3 scorecard and W5 refresh | Metric owner | Dated log of time to first impressions, new versus refreshed | | A1 | W12 "A 14-Day Trial Plan for Evaluating a Project Management Tool" | Editor | Brief check: piece serves a 2–4 week decision window | | A2 | W9 pricing page update | Metric owner | Change annotated against baseline in the page-set report | | A3 | Calendar W3–W26 | Editor | Weekly slots exist and are logged | | A4 | W3–W10 pilot cadence | Editor | Capacity log names who produced each piece | | A5 | W20 comparison page update | Legal reviewer | T6 scan passes or legal sign-off is logged | | A6 | W3 scorecard | Distribution owner | T4 query-pattern review record exists before the calendar is finalized | | A7 | W3 scorecard and W10 feature checklist | Metric owner | Section 9 single-piece and expanded-pilot rows read and recorded | | A8 | W4 "Project Management Software Pricing Models Explained" | Distribution owner | T4 pricing-query data recorded; pilot impressions recorded | | A9 | W6 agencies piece | Distribution owner | T4 segment-query data recorded; pilot impressions recorded | | A10 | W9 pricing page update and links from W4 | Distribution owner | Click-path report shows clicks from supporting pieces to target pages | | A11 | W3 scorecard | Distribution owner | T4 results-page review recorded for its target cluster | | A12 | Baseline snapshot document | Metric owner | Same check as R7 | | A13 | W5 refresh | Editor | Disposition sheet shows performance data per post | | A14 | W3 new piece and W5 refresh | Metric owner | Same check as R12 | | A15 | W4–W10 pieces | Editor | Same check as R11 | ## 9. Content Testing and Readiness Checks Any pilot piece count and any traffic figure referenced below is small-scale and is not a full campaign's result. A metric is real only once the piece is actually published and the metric is actually measured; until then it is NOT YET MEASURED. Pass conditions below are thresholds of evidence, not forecasts; where a numeric threshold is needed, the metric owner sets it from the T2 baseline before publication and records it. **Testing notes for stand-ins.** - **`<VALIDATE: criteria-demand-share>`:** the W3 scorecard stands in. Passing leaves pillar-wide performance UNVERIFIED. - **`<VALIDATE: rank-lag-two-quarters>`:** the W3 new piece and W5 refresh stand in. Passing leaves pillar-wide performance UNVERIFIED. - **`<VALIDATE: weekly-capacity>`:** the W3–W10 pilot cadence stands in. Passing leaves sustained-cadence feasibility UNVERIFIED. **Readiness table** | Assumption / Req | Test level | Piece count | Expected result | Pass condition | Prerequisites | |---|---|---|---|---|---| | R1, R7, R8, A12 | internal-review | 0 | Baseline and page set documented | Dated baseline snapshot from real analytics; page set signed by the page owner; metric owner sign-off | T1, T2 | | R2, A1 | internal-review | 1 (W3 brief) | Brief matches audience and stage | Editor checklist: journey stage, target query, next-step link recorded | T5 | | R4, A5, R10 (compliance pass) | internal-review | Every piece before publication | No competitor-naming comparison | T6 scan passes, or legal sign-off logged; required disclaimers (if any) confirmed present by a second reader | T6, T7 | | R6, A13 | internal-review | 0 | Every post dispositioned | All 40 posts have a disposition; no calendar title duplicates an existing post | T3 | | A6, A8, A9, A10, A11 (routine data checks) | internal-review | 0 | Query and results-page data recorded | Data review record exists per assumption before calendar finalization | T4 | | A7 | single-piece-pilot | 1 (W3 scorecard) | Piece indexed; impressions and click path appear for a competitor-neutral evaluation query cluster | Indexed at the intended URL; non-zero impressions on at least one target-cluster query; at least one recorded click to a pricing or comparison page; thresholds beyond these set by the metric owner beforehand | AP-1, T6 | | A14, R12 | single-piece-pilot | 2 (W3 new, W5 refresh) | Time to first impressions recorded for each | Dated log exists for both pieces; difference between new and refreshed is reported, whatever its size | AP-1, AP-2 | | A7, A6, A8, A9, A10 | expanded-pilot | 7 (W4–W10) | Pillars P1–P4 and C3 each show early signals or not | Each pilot piece published in its week and T6-passed; P1 or P2 pieces meet the single-piece pass conditions; hypothesis result H1–H6 recorded per piece | AP-2, AP-3, T10 | | R3, R5, R11, A15 | expanded-pilot | 7 (W4–W10) | Pilot cadence held, hours logged | 7 pieces in 7 consecutive weeks with no missed slot; hours per piece logged; writers confirm the load is sustainable | AP-2 | | Fallback: P2 replaces P1 as the lead pillar if P1 underperforms | expanded-pilot | 2 (W4, W7 P2 pieces) | P2 shows early signals if P1 does not | P2 pieces meet the same conditions as the single-piece pass; result recorded | AP-2, T12 | | R1, A7, A14, A15 | full-cadence | 16 (W11–W26) | NOT RUN until Section 12 approvals granted | NOT RUN until Section 12 approvals granted | AP-4 to AP-7 | | R3, R5 | full-cadence | 16 (W11–W26) | NOT RUN until Section 12 approvals granted | NOT RUN until Section 12 approvals granted | AP-4 to AP-7, T14 | **What each result proves.** A single-piece-pilot PASS proves only that the pillar is not obviously wrong: the piece indexed, appeared for relevant queries, and sent at least one reader onward. It does not prove that the pillar can move page-set traffic by 50%, that demand is sufficient, or that the cadence is sustainable. Only full-cadence data, measured against the baseline over time, proves that the strategy drives the stated goal. The two are never conflated in reporting. ## 10. Legal, Compliance, and Brand Boundaries - **HIGH — OPEN: full-cadence commitment while resourcing-critical items are unresolved.** Committing W11–W26 while `<VALIDATE: criteria-demand-share>`, `<VALIDATE: rank-lag-two-quarters>`, or `<VALIDATE: weekly-capacity>` is unresolved risks wasted writer time on unproven pillars. Rule: no full-cadence commitment, no extension of freelancer scope, and no communication of W11–W26 as committed until T14 shows all three resolved and AP-4 to AP-7 are signed. - **HIGH — MITIGATED BY GATE: competitor-naming content breaching R4.** Backstop: the T6 scan by the editor before every publication, with the legal reviewer's sign-off logged on the calendar entry for any hit. A Section 12 row cannot move to approved without the T6 result recorded. Existing comparison pages are audited in T3 because their compliance status is unknown. - **MEDIUM — MITIGATED BY GATE: a required disclaimer dropped from a published piece.** None is supplied. If legal specifies any, it is added to Section 1 as a hard-constraint row. Backstop: the pre-publication checklist owned by the editor includes "required disclaimers present", confirmed by a second reader other than the drafter. - **HIGH — RULE: content that must never appear.** Unverified statistics; claims contradicting R4; uncredited sourced material; competitor pricing or feature claims; implied competitor comparisons; unsupported superlatives; fabricated customer quotes or case studies; internal metrics. - **MEDIUM — MITIGATED BY PROCESS: duplicate or conflicting pieces.** Live risk is overlap between new pieces and the 40 existing posts, and between pricing-related pieces (P2) that compete for one query. Backstop: the calendar tool maintains a one-primary-URL-per-query-cluster map; the editor runs the dedupe check at brief stage and again before publication. Only one channel (the website) is in scope, so cross-channel duplication is not a live risk. - **MEDIUM — REVIEW TRIGGER: adjacent regulated or claim-sensitive content.** No pillar is health or finance. Pricing statements about the product must match the live pricing page and are checked by the page owner; any tax, discount, refund, or contract-term claim goes to the legal reviewer. Security and admin-controls content (W18) makes claims that need verification by the product or security owner before publication. - **UNASSESSABLE until Section 7's resourcing-critical items resolve:** whether a fully constraint-compliant, competitor-neutral content set can move pricing and comparison page traffic by 50% within the judging window. No risk rating is given. ## 11. Publishing, Verification, and Correction Plan **Drafting and internal review — runnable now:** T1 through T8 (role assignment, baseline, audit, query review, legal scoping, calendar finalization, W3 draft, T6 check), plus drafting of W4–W10 pieces. **Blocked on validation:** any commitment of W11–W26, and any pillar approval for full-cadence production. **Approved pilot publication (→ Section 12):** - AP-1, the W3 single pilot piece: READY FOR HUMAN REVIEW. - AP-2, the W4–W10 expanded pilot: blocked on AP-1 (trigger is the AP-1 piece being live, indexed, and T6-clean; this is a gating check, not performance evidence). - AP-3, edits to live pricing or comparison pages: READY FOR HUMAN REVIEW once the T2 baseline snapshot exists. **Expanded-pilot checks:** at the end of W10, T12 performs a full review of Section 9 results and adjusts pillar mix, format mix, or cadence before any full-cadence commitment. **Approved full cadence requires ALL of the following (AND-conditions):** 1. Section 9's tests pass at their stated levels (single-piece-pilot and expanded-pilot). 2. All Section 12 actions AP-1 through AP-3 are complete, and AP-4 to AP-7 are signed for the pillars being committed. 3. Every resourcing-critical Section 7 item is resolved by real test results, not stubbed by the pilot stand-in. **Bounded post-publication verification (first reporting window):** - One concrete check: inspect the W3 piece's URL in search tooling to confirm it is indexed at the intended canonical URL, and click-test that its links to pricing and comparison pages resolve. - Scan all published pieces and the site for any excluded topic from Section 1, specifically any competitor-named direct comparison, and record the result. **Correction.** Before assuming an edit reaches every distribution point, confirm where the piece lives: its canonical URL, any cached or indexed snippet, and any copy circulated by others (for example in sales emails or shared documents). Updating the source file does not undo a version already shared elsewhere. Containment means republishing the corrected piece with a visible updated-on note, flagging the correction to the distribution owner and anyone who circulated the earlier version, and requesting re-indexing; a silent fix is never assumed. A piece that breaches R4 is unpublished or corrected immediately and referred to the legal reviewer. ## 12. Publishing Approval Register | Action ID | Purpose | Pillar/Channel/Scope | Expected Effect | Trigger Condition | Status | Approved by / Date | |---|---|---|---|---|---|---| | AP-1 | Publish the single pilot piece | P1 / C1 / W3 scorecard only | One live piece; first measurable signals | T8 complete, T6 passed, named editor and legal reviewer in place | READY FOR HUMAN REVIEW | ____ / ____ | | AP-2 | Publish the expanded pilot | P1–P4 / C1, C2 / W4–W10 (six pieces, excluding W9) | Six live pieces; cadence and hours data | AP-1 piece live, indexed, T6-clean | Blocked on prior action: AP-1 | ____ / ____ | | AP-3 | Publish edits to live pricing or comparison pages | C3 / W9 pricing page (W20 comparison page requires its own review) | Changes to pages that carry the target metric | T2 baseline snapshot recorded; T6 passed; page owner review | READY FOR HUMAN REVIEW | ____ / ____ | | AP-4 | Approve P1 for full-cadence production | P1 / C1, C2 / W11–W26 | Committed writer time on P1 slots | Section 9 tests pass; all resourcing-critical items resolved | BLOCKED BY VALIDATION (`<VALIDATE: criteria-demand-share>`, `<VALIDATE: rank-lag-two-quarters>`, `<VALIDATE: weekly-capacity>`) | ____ / ____ | | AP-5 | Approve P2 for full-cadence production | P2 / C1, C2 / W11–W26 | Committed writer time on P2 slots | Same as AP-4 | BLOCKED BY VALIDATION (`<VALIDATE: criteria-demand-share>`, `<VALIDATE: rank-lag-two-quarters>`, `<VALIDATE: weekly-capacity>`) | ____ / ____ | | AP-6 | Approve P3 for full-cadence production | P3 / C1, C2 / W11–W26 | Committed writer and freelancer time on P3 slots | Same as AP-4 | BLOCKED BY VALIDATION (`<VALIDATE: criteria-demand-share>`, `<VALIDATE: rank-lag-two-quarters>`, `<VALIDATE: weekly-capacity>`) | ____ / ____ | | AP-7 | Approve P4 for full-cadence production | P4 / C1 / W11–W26 | Committed writer and freelancer time on P4 slots | Same as AP-4 | BLOCKED BY VALIDATION (`<VALIDATE: criteria-demand-share>`, `<VALIDATE: rank-lag-two-quarters>`, `<VALIDATE: weekly-capacity>`) | ____ / ____ | | AP-8 | Commit distribution spend for promotion | Any paid amplification of a published piece; none planned | Spend committed against a piece | A budget is supplied and a piece has passed the expanded pilot | Blocked on prior action: AP-2 | ____ / ____ | | AP-9 | Request legal review of a named-competitor pilot piece | Outside Section 4 scope; one piece only | Legal decision on whether a named comparison is permitted | `<VALIDATE: criteria-demand-share>` resolves adversely | BLOCKED BY VALIDATION (`<VALIDATE: criteria-demand-share>`) | ____ / ____ | | AP-10 | Retire an underperforming pillar | Any of P1–P4 | Pillar's remaining slots reassigned | Expanded-pilot data show the pillar failing its pass conditions | Blocked on prior action: AP-2 | ____ / ____ | Approving one action never implies approval of another. Listing a retirement action (AP-10) does not mean it is to be executed now. ## 13. Completion Evidence and Handoff A final report must contain: - **Published pieces:** each mapped to its real URL and publication date, with any missed calendar slot listed. - **Section 9 checks:** every row itemized PASS, FAIL, NOT RUN, or BLOCKED, each with one line of evidence. - **Pilot and full-cadence results reported separately.** A pilot PASS is never presented as evidence of full-cadence performance. - **Traffic and engagement data:** actual organic traffic to the pricing and comparison page set against the T2 baseline, only if measured; otherwise "NOT YET MEASURED". - **Unresolved Section 7 items, by name:** each of `<VALIDATE: criteria-demand-share>`, `<VALIDATE: rank-lag-two-quarters>`, `<VALIDATE: weekly-capacity>`, `<VALIDATE: baseline-traffic>`, `<VALIDATE: inventory-performance>`, `<VALIDATE: bofu-query-patterns>`, `<VALIDATE: pricing-query-demand>`, `<VALIDATE: segment-query-demand>`, `<VALIDATE: internal-link-lift>`, and `<VALIDATE: competitor-serp>` with its current status. - **Residual limitations still true at handoff:** for example, the pilot's small scale, ranking lag on late-published pieces, and any pillar still marked provisional. - **Exact next steps:** for each outstanding validation or approval item, the owner, the data or test needed, and the Section 12 action it unblocks. No traffic screenshot, ranking, click figure, or approval may be fabricated or implied; an approval exists only where the Section 12 register carries a real name and date. A full calendar alone is not evidence the content strategy drives the business goal.