PlaysbyMoat8
Back to the library
The workflow guideMarketing

Prepare a researched search-content draft

Move from a seed keyword to a researched article draft that an editor can improve and approve.

6 implementation stepsIntermediate

How this works

Move from a seed keyword to a researched article draft that an editor can improve and approve. A search-content draft should answer a useful reader question with evidence, not merely expand a keyword into a long page. Search demand, factual accuracy, and business relevance are separate decisions that need explicit review.

Move from query intent to an approved topic, then research and outline before drafting. Keep a claim ledger and distinguish measured search data from estimates or unavailable metrics. Deliver an editable draft or CMS draft with unresolved checks visible.

Before you start

Editorial remit

Define audience, product relevance, and excluded topics.

Search evidence

Use available keyword data and current result observations.

Source standards

Agree acceptable primary sources and treatment of uncertain claims.

Prepare the inputs

seed_query
Required

Search phrase

Record locale and intended audience.

keyword_data
Required

Queries and metrics

Include source date and metric definitions.

product_facts
Required

Approved references

Avoid inserting nonexistent capabilities.

editorial_brief
Required

Format and purpose

State what the reader should understand or do.

research_sources
Required

Documents with locators

Preserve access and publication dates.

Implementation, step by step

  1. Expand intent options

    • Group related queries by the problem they express.
    • Separate informational, comparison, and transactional intent rather than mixing them into one article.

    Checkpoint: A topic-intent map.

  2. Select a defensible topic

    • Compare relevance, evidence availability, and available search signals.
    • Keep volume and difficulty unknown when no verified data exists.

    Checkpoint: An approved topic brief.

  3. Research the reader's questions

    • Collect primary evidence and concrete examples for the important sections.
    • Record disagreement and avoid treating repeated secondary summaries as independent support.

    Checkpoint: A research and claim ledger.

  4. Build the outline

    • Order sections around the reader's decisions and likely knowledge gaps.
    • Include useful examples and limitations rather than copying the result-page structure.

    Checkpoint: An original evidence-backed outline.

  5. Draft and format

    • Write clear prose that follows the outline and preserves factual qualifications.
    • Use the requested format or an available CMS draft interface; label placeholders.

    Checkpoint: An editable article draft.

  6. Review before release

    • Verify claims, calculations, quotations, and any image permissions.
    • Record open checks and a later measurement plan that separates traffic from qualified business outcomes.

    Checkpoint: A reviewed publication candidate.

Decisions along the way

Query intent is too broad

Choose a narrower question or a series with explicit boundaries.

A key claim has no primary support

Qualify it, omit it, or leave an editorial question.

Search metrics are stale

Use them as historical context and avoid precise current-demand claims.

What you will produce

researched-article.md

Markdown

An original draft for editorial review.

Include: title · introduction · sections · examples · limitations · open_checks

article-evidence.csv

CSV

Supports factual review and updates.

Include: claim_id · section · source_ref · date · status

Check the result

  • Confirm the article answers the chosen intent.
  • Trace important claims to accessible sources.
  • Check product mentions are relevant and accurate.
  • Review originality, useful examples, and unsupported certainty.

When something goes wrong

The draft becomes generic filler

Return to the reader questions and remove sections without a useful answer.

A source cannot be verified

Mark the claim unresolved rather than invent a citation.

CMS formatting alters the content

Compare the rendered draft with the approved source text.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Draft an article on handling invoice exceptions.

Inputs

Synthetic example. Synthetic research supplies a manual approval process and an OCR extraction guide, but no evidence for fully automatic payment decisions.

Expected result

Synthetic expected result. The outline separates extraction, validation, and human exception review. It does not promise autonomous payments or guaranteed cost savings.

Run a small pilot

Start small

One topic with a manageable source set.

Record the baseline

Record research and editorial correction time.

Agree success criteria

Agree factual support and reader usefulness before measuring later search results.

Stop or revise

Stop publication if the central recommendation lacks evidence or required expertise.

Keep the scope clear

  • A draft is not permission to publish or distribute source material.
  • Search popularity does not prove conversion potential or business impact.

Check before using

Verify factual claims, image rights, and originality before publication. Search traffic does not establish conversions or business impact.

Business activities

  • Create and publish content

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Seed keyword · Search-volume and difficulty data · Editorial structure and product facts

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗