Follow the Workflow from Content Approval to Publication and Recheck

Availability and responsibility

Keep content approval, live publication and subsequent answer checks as separate workflow stages.

View full size

Approval, publication and rechecking are separate stages with separate evidence. Follow the same question and article through the sequence so a completion label does not hide missing work.

Follow the chain

1. Write the article inside Xtrusio and mark it for client approval with review comments.
2. The client reviews it in the portal and adds, edits or approves the content.
3. After approval, the client can push the article to Link Strategy as approved.
4. For a client-blog article, use the configured CMS integration or manual team upload. For third-party or guest-post placement, the journalist team contacts publishers and arranges publication.
5. Verify the actual live page and associate its URL with the correct question and plan item.
6. Record indexing evidence separately where available.
7. Run or inspect the agreed later question check.
8. Open the answer and inspect citation evidence.
9. Decide the next action from the observed result.

A pending scan should remain pending. An unsuccessful citation check should remain visible rather than being removed from the record.

Example

A hypothetical article is approved Monday, published Wednesday and checked the following week. If the later answer omits it, publication was still completed, but the hoped-for citation was not observed. The next task might be improving the answer, reviewing the selected question or collecting another comparable observation.

Review the campaign over time

A perception campaign can require continued content creation and distribution. Review the relevant question segments across comparable scans, separating broad positioning questions from questions about a specific capability.

The operating approach uses a 90-day rollout target to get a campaign live. It is not a guaranteed deadline for indexing, citations or changed perception. Use question-linked publications, observed URL matches and answer framing to report the different stages of progress.

Avoid a false before-and-after conclusion

A changed answer after publication is not automatic proof that publication caused the change. Preserve the question, engine, method and timing, and note other changes.

If work is stranded between stages

Identify the last verified event and who owns the next action. Do not create another content plan to compensate for an incomplete handoff.

Close the review with a record of delivered work, observed results and unresolved questions. Those three lists should not be collapsed into one success claim.