Blog Studio

Screen before generating

Blog Studio checks the available demand evidence before generation. A refused run carries a reason and supporting figures. Unverified demand means the screen could not establish the case; it is not equivalent to confirmed absence.

If you know something the evidence cannot capture, such as a newly launched service, you can choose “Draft anyway.” The run records the override.

New content or a refresh

A new draft starts with a target query. A refresh also uses the existing page URL. Supported actions from the recommendation queue can seed this context in Blog Studio.

Business & voice settings and your input guide the writing. Review the draft, confirm facts and business claims, and refine it before publishing. The draft is a starting point for editorial work.

Publishing and the live URL

Use a supported publishing connection or your own publishing workflow. Record the actual live URL when Onça does not already have it. A prepared draft and a published page are different states.

Publishing manually? Follow Publish an article without a connector for the download, website, and live-address steps.

Publishing setup is separate from reading a public site. Connection requirements depend on your publishing platform.

Read the outcome

With the published URL and available Search Console data, refresh reporting compares the page before and after the change. New-post reporting distinguishes a page that is seen from one that earns clicks. A lack of data is shown separately.

These are observations about the published page, not proof that the edit caused a change. Read them alongside the original decision and demand evidence.

See the opportunity queue for supported actions and Getting started for connections.