Content pages
Set up one brand for one market at a time. We save your choices as a draft, then check them before any scheduled work starts. Publishing a page requires your review and a safe test of its publishing connections.
Start hereHow to set up a page
What is a “page” here?
It is a saved setup for one brand in one market. It tells us who the content is for, where to find relevant stories and where approved drafts should go.
Follow these seven steps
- Identity and audience: choose the brand, market, language and readers. We then look for local news publishers.
- News publishers: review the local sources we found. Add another only if you need it.
- Knowledge: prepare and approve the brand’s own facts and assets. Add local facts where needed.
- Publishing destinations: choose whether this page uses WordPress and select the social accounts it may use.
- Writing and safety rules: review the shared model choices and add any page-specific restrictions.
- Schedules: choose when this page checks news, prepares campaigns and handles approved posts.
- Final review: check what is ready, agree to the setup test and publish only when every requirement is met.
Why save one section at a time?
Later choices often depend on earlier ones. A green check means that section is saved and ready for its next step. If a check fails, your draft remains. Read the note beside the button, make the change and try again.
Where do articles and social posts go?
A brand may have one connected WordPress site and one default page for articles, images and previews. Other market pages can stay social-only. You can also skip WordPress for a new brand while preparing its draft. If you connect a site, use a WordPress application password; we verify and encrypt it, then remove it from this form. For social media, connect the account in Buffer, return here and scan. Buffer credentials do not appear on this page.
What happens after you click Publish page?
We first check the page’s sources and build one test campaign for your review. Zoala keeps its existing campaign rules. Every other brand uses only the knowledge package, links and assets you approved for that brand. After you approve the test, we schedule a temporary Buffer post for a safe future time, check its channel, text, image and time, then delete it and confirm removal. The page goes live only when every check passes. You can close the progress window while it continues.
Things people usually ask
It says “Needs attention”. Did I break it?
Probably not. It just means one check still needs an answer. Open that section and read the short note beside its button. Your saved draft is safe.
Can I add a completely new market?
Yes. Its own market supplies the main stories. Opened stories from the brand’s other markets may help as supporting evidence, but the new page’s own country is kept out of that supporting pool.
I added a Buffer channel. Why can’t I select it?
Press scan and give Buffer a moment to finish connecting it. When it appears below, press Use for this page. If Buffer says the channel is locked or disconnected, fix that in Buffer first.
Do I need LinkedIn, Facebook and Instagram?
No. One working social channel is enough. Artwork follows the channels you actually select, so the page does not make unused formats.
Why did the scheduler refuse my time?
Another page is too close to it. Keep each recurring run at least one hour away from the schedules on other pages so they do not fight for the same AI capacity.
How do I pause it without losing anything?
Open Schedulers and press Pause this page’s work. This pauses only the page’s campaign-building and publishing clocks; the shared news sweep keeps serving the other pages. This page, its campaigns and its history stay put. Archive page also stops its work and hides it from everyday dashboard views, so use that only when retiring the whole page.
Can I change the page later?
Yes. Come back here, edit the section and save it again. The system checks the new setup before using it.
For developersHow page settings reach the workflow
The short version
The page selects the shared content-automation-baseline@1 workflow. Each campaign receives a frozen copy of its page settings, so later edits do not rewrite a running campaign. Zoala continues through its existing adapter. A different brand receives the document-driven adapter only after its own reviewed knowledge package is approved.
What lives where
A region holds countries and a timezone. A brand holds shared knowledge and, when connected, one WordPress site. That site may serve several markets. Each page chooses its own Buffer channels. The browser receives public links and IDs, never provider secrets.
How the automatic bits work
Saving Identity and audience asks the server to search Google News for that market and turn the publishers it finds into fixed, domain-scoped feeds. Buffer scan first asks the API key which workspaces it can see, then reads the channels from all of them. No separate workspace ID should be needed.
Saved does not mean running
A draft can hold its schedules without starting ordinary work. A setup test is allowed only when this page has an approved brand package and every other check passes. Activation also needs consent and a 31-day conflict check that keeps page runs at least an hour apart.
Provider safety
WORDPRESS_DEFAULT and BUFFER_DEFAULT are routing labels, not credentials. A WordPress application password may be submitted once through the protected configuration route; the API verifies the user and category, stores only an AES-256-GCM envelope and never returns the secret. Buffer credentials remain server-only and never enter a redirect URL. A later delegated provider flow should use OAuth Authorization Code with PKCE.
The setup test
content_page_setup_runs remembers the exact checkpoint. Workflow 25 advances source sweep, editorial, human review and a reversible Buffer preflight on one-minute heartbeats, one saved stage at a time. Approval remains a human decision. The preflight custom-schedules the approved social payload, reads it back, deletes it before its due time and verifies deletion. It must never call WordPress publication or Buffer “share now”.
Before you ship a change
- Run typecheck, the Agent API tests and the dashboard DOM/proxy tests.
- Prove a new market gets its own publishers, not another market’s fallback.
- Prove Buffer scan works with only the server API key; do not depend on a hand-entered workspace ID.
- Run the whole draft → schedules → consent → setup-test path in memory.
- Check generated workflows even if you did not edit a workflow file.
- After merge, verify Cloudflare, the exact container SHA, migrations, Workflow 25 and the read-only preflight.
Useful “why?” answers
When does a new brand need code?
Normally, it does not. Prepare and approve that brand’s own knowledge package here and the document-driven adapter will use it. We keep the page as a draft only when required evidence, CTA routes, safety rules or logo approval is missing. A genuinely new publishing integration or output type may still need development work.
Why keep an incomplete draft?
So your work is not lost. Saved does not yet mean safe to run; we check the complete setup before starting campaigns.
Why share WordPress but not Buffer channels?
A brand’s website can serve several markets. Social accounts may be market-specific, so each page chooses its own connected channels.
Why are schedules separate?
A visible page is not permission to start paid work or publish. Every schedule has its own switch, next run time and safety checks.
Developer fallbackInstall brands and regions
Most admins should not need this section. Use it to install reusable identity primitives; provider credentials are never entered here.