ZyanDocs

Settings reference

Every SEO Command Center setting for a website, in the four groups they appear in, with what each one changes and which ones save on click.

Pick a website in the Command Center, then open Settings. It has four groups — Automation & budget, Content & page rules, Data & tracking and Reporting & client — and this page lists what is in each of them.

Saving is not uniform, and it catches people out. Lane switches and client visibility save the moment you flip them. Cadence fields need Save automation settings. Content and page rules commit with one Save all. The market locations picker saves on its own, and the report day saves when you leave the field.

Before you start

Budget, cadence and the owner-only rows need owner or admin rights. A website excluded from the Command Center keeps its Builder SEO surfaces but does not run automation, and the Settings tab says so.

Automation & budget

The four lanes at the top decide what runs without you. The header pill shows how many are running, for example 3/4 running.

SettingWhat it changesDefault
Pause everythingPauses autoblog, fixes, evidence refresh and reports together. Resuming restores whatever was on before.
AutoblogScheduled blog pipelines. Resuming re-enables only the pipelines that were on.
FixesPauses auto-apply and desktop auto-dispatch. Per-fix buttons keep working.
Evidence refreshThe recurring research and evidence pulls — setup, Google evidence, paid research and the visibility panels.
ReportsPauses monthly report generation. The reporting mode is remembered and restored on resume.
Monthly SEO budgetThe monthly cap that automated paid research and autopilot drafting run against. Blank means paid research is paused entirely.Blank
Auto-send fixes to the desktop agentSends fixes with no instant patcher to your open desktop app, by priority — Off, P0 only, or P0 and P1.Off
Bluehost deploy after fix commitsFTP-deploys fix commits on Bluehost-hosted sites. Account owner only, and dormant until the terminal service and tenant credentials are in place.Off

How often Zyan refreshes paid search evidence by itself. The panel shows a live monthly estimate as you choose.

SettingWhat it changesDefault
OffNo automatic paid research. The preview reads Off, $0 a month.Default for every mode except Full Autopilot
WeeklyEvery 7 days, roughly $8.70 a month at the $2 per-run estimate.
Every 2 weeksEvery 14 days, roughly $4.35 a month.
MonthlyEvery 30 days, roughly $2.03 a month.Inherited default under Full Autopilot
QuarterlyEvery 90 days, roughly $0.68 a month.

Optional content lanes (Advanced)

All five are off by default.

SettingWhat it changesDefault
Refresh stale postsA daily refresh brief for posts whose Search Console clicks fell more than 40% against their 90-day pace. Free, maximum two a day.Off
Internal-linking sweepAdds up to three links to each new post from older posts on its keyword, through the live-fix lane.Off
Service-area page proposalsBriefs a service-area page when a grid keyword underperforms on two scans. Maximum two a day, and it never drafts or publishes.Off
Promote audit errors automaticallyAdds error-tier checks from a completed site audit to the Technical queue. Free, errors only.Off

Two lanes have their own requirements

Arming FAQ / PAA expansion requires a fresh desktop runner advertising that capability. Bluehost deploy after fix commits is account-owner only and stays inert without the terminal service and tenant FTP credentials.

Content & page rules

What the AI may write, where it may write it, and what it must not touch.

SettingWhat it changesDefault
Pages the AI must never editProtected paths, one per line, that the writer and fix agents must leave alone.
CountryThe country preset research runs against. A non-country code here breaks research-target creation.
Local market locationsThe towns and areas local research and Map Pack tracking measure. This picker saves separately from the section.
Writer modelThe model the blog writer uses. Left empty on the desktop lane, the signed-in subscription's default model runs.
Content guidelinesExtra writing direction handed to the writer on every run.
EffortReasoning effort for the writer.
Max turnsMaximum agent turns per writing run.
Timeout minutesThe run time limit. Local runs can be saved up to 240 minutes.
Prefer desktop runner for blog draftsDrafts run on an open, bound desktop's Claude subscription with no API spend.On
Cloud fallback for waiting draftsAfter a few minutes with no desktop, sends the draft to the cloud writer using your API credits.Off
Additional content pathsExtra directories the blog writer may edit, one path per line. Advanced.
Language codeThe research result language. Advanced.en
Who this website is forShows the stored target audience. Read-only here — it is edited on the Research brief.
Image style notesA style hint for manual image generation and edits only. Autoblog sources its own images and ignores this.

One Save all commits this section. The market locations picker is the exception and saves on its own.

The target audience has exactly one editor

It is the Research brief, under StrategyResearchBrief. This panel shows it read-only with a link across, so two copies can never disagree.

Data & tracking

Connections, freshness and run health.

SettingWhat it changesDefault
Connection readinessA traffic-light list of Search Console, Analytics, research evidence, the Google connection, the research brief, site knowledge and the reporting baseline, each with its own fix button.
Baseline start dateThe month reporting comparisons start from. It cannot be in the future, and it cannot be re-locked from here afterwards.
Capture baselineLocks the reporting baseline snapshot.
Map Pack trackingThe local rank grid — listing, grid size, keywords, cadence and monthly budget.
AI provider keysReports whether the writer and review providers are configured. Platform-level. Advanced.
Index coverageIndexing state for the website's pages. Advanced.
Run healthNamed problems such as a research provider fault, a stale autoblog run, not-generated reports, a scheduler problem, or no tracked keywords. Advanced.
Scheduler job historyRecent scheduled runs. It loads on demand — use Refresh inside the panel. Advanced.

SEO cron-step history reads Not available for workspace logins. That is expected; it is platform-operator diagnostic data, not something missing from your workspace.

Reporting & client

SettingWhat it changesDefault
Monthly report autopilotOff, Draft for review, or Auto-attach after QA. Auto-attach is account-owner only to arm.Off
Generate on day of monthThe day, 1 to 28, the monthly report is generated. Saves when you leave the field.Off until set
Active SEOShows SEO as an active service in the client's portal. Nothing SEO-related reaches the client until this is on.
Live SEO dashboardLets the client open the live daily dashboard, independently of report delivery.
Map Pack resultsShows Map Pack scan results in the client's portal.
Domain is a generic service termAllows generic service words from the domain in reports and rank checks. Business-name keywords stay excluded. Owner only.

The three client-visibility switches save immediately. The report day saves when you leave the field, and an invalid day is never written — the field snaps back and explains why.

What saves how

ControlSaves
The four automation lanesOn click
Client visibility switchesOn click
Paid research cadence and budget fieldsWith Save automation settings
Content & page rulesWith Save all
Local market locationsSeparately, from its own picker
Generate on day of monthWhen you leave the field, or on Enter
Map Pack tracking panelWith its own Save, except client visibility

Troubleshooting

SymptomCauseFix
A cadence change did not stickCadence fields need the section's save buttonClick Save automation settings
A content rule did not stickThe section commits togetherClick Save all
Paid research is blocked everywhereThe monthly SEO budget is blankEnter a positive number
Scheduled research and drafting have pausedThe monthly budget is reachedWait for next month, raise it, or run it yourself as an owner and accept the overrun
A member cannot arm auto-attach or the generic-domain ruleBoth are owner-onlyAsk the account owner
Cron-step history says it is not availableIt is not exposed to workspace loginsUse Run health and Scheduler job history instead
Bluehost deploy after fix commits does nothingIt is owner-only and needs terminal wiring plus FTP credentialsConfirm both with your platform operator before relying on it