Content (Beta)

Content workflow (Beta)

The Content module turns eligible owned actions into a content inventory and optimization workflow. Ideas remain connected to the evidence that suggested a title, format, or page opportunity.

Content Ideas counts active project content ideas after the module synchronizes eligible open owned actions. Generated Drafts counts those active ideas whose generation status is generated. Writer Prompt shows Configured when the project's brand-specific writer prompt is present and Default when it is blank. These are workflow counts and configuration state; none is a visibility, publication, indexing, citation, or traffic metric.

1. Configure content settings Review the project's content preferences before generating or accepting work.
2. Review the source action Confirm the prompt, competitor, source, and intent behind the idea.
3. Decide create versus improve Avoid publishing a duplicate page when an existing URL can satisfy the same intent.
4. Brief and produce Add brand expertise, original proof, editorial review, and the correct market language.
5. Measure later Keep the relevant prompts stable and watch future answer and source evidence after publication.

Reports and exports

Reports stores generated reporting packages. Overview and supported detail screens can also export CSV or PDF. An export represents the project and filter scope at generation time, so name and share it with that context.

• PDF is suited to a readable stakeholder summary with selected charts and evidence.
• CSV is suited to governed analysis, reconciliation, and joining with internal data.
• Run and answer exports help audit completeness when a headline metric looks surprising.

Share results responsibly

• Include the date range, providers, markets, prompt count, and completion status.
• Separate observed evidence from interpretation and planned action.
• Do not compare reports with materially different prompt or competitor sets without noting the change.
• Keep sensitive account exports within the intended customer team.

Build a content measurement loop

Content work should begin and end with a clearly defined customer question. Before production, record the prompts, current answers, source pattern, competitors, and baseline metrics connected to the opportunity. This prevents a later improvement from being judged against an unrelated dashboard average.

1. Define the hypothesis State which audience question the content should answer and which evidence suggests the current experience is incomplete.
2. Choose the best existing destination Decide whether to improve a relevant page or create a new one based on intent, overlap, authority, and maintainability.
3. Add original value Include expert knowledge, first-party data, clear claims, supporting proof, and useful structure that competitors or generic summaries do not provide.
4. Publish and record the date Note the final URL, release date, distribution, and any external activity that could affect interpretation.
5. Reassess repeated evidence Watch the same prompts, sources, and providers over several comparable runs before judging impact.