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, auto-send, the page loop and deploy repair. Per-fix buttons still work.—
Evidence refreshPauses the recurring research and evidence pulls (setup, Google evidence, paid research), auto-sent fixes, the page loop and the strategy review. Rank panels and deploy repairs keep running.—
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 = $15 a month: paid research runs against $15 and the group's header pill reads $15 (default). Type a number to set your own cap. On a workspace exempt from credit metering, a blank budget has no monthly cap — only Command Center keyword data stops at $15 — and the field and pill say so (No cap · keyword data $15).Blank ($15 a month)
Auto-send fixes to the desktop agentSends fixes with no instant patcher to your open desktop app, by priority — Off, P0, P0–P1, P0–P2 or All, two open fix orders per website at a time.Off
Recently changed pagesWhat auto-send does with a fix for a page Claude changed recently. A page whose content or keywords a run changed waits up to 38 days while Search Console measures the change, and new search demand brings it back early. With SEO learning on (the default), a measured drop from about day 17 is recorded as context and the page keeps waiting; with SEO learning off, that drop also brings it back early. A page a run only touched (a link, a small correction) waits 14 days. Wait holds the fix; Go last sends it after every other fix. Speed, schema and link fixes never wait, and sending by hand always works.Wait
Bluehost deploy after fix commitsFTP-deploys fix commits on Bluehost-hosted sites. Owner or admin 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.Inherited default under Full Autopilot (monthly until 2026-09-22)
MonthlyEvery 30 days, roughly $2.03 a month.—
QuarterlyEvery 90 days, roughly $0.68 a month.—

Optional content lanes (Advanced)

Both are off by default.

SettingWhat it changesDefault
Internal-linking sweepAdds up to three links to each new post from older posts on its keyword, through the live-fix lane.Off
Promote audit errors automaticallyAdds error-tier checks from a completed site audit to the Technical queue. Free, errors only.Off

Bluehost deploy has its own requirements

Bluehost deploy after fix commits is owner or admin 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 owner or admin 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
SEO reportingIncludes SEO reporting in the client's plan: their SEO tab shows your attached reports and Map Pack results with no offer wall, and their Services page lists it as included in their plan. Off takes it out of their plan.Off
Blog postsShows autoblog posts on the client's calendar and, when your catalog sells it, includes Blog content in their plan. Turning it on notifies the client when new posts get scheduled this month; posts already published stay when it is turned off.Off
Map Pack resultsShows Map Pack results in the client portal and in SEO reports opened online. It shows inside SEO reporting: switched on while SEO reporting is off, it reads Not shown.Off
Domain is a generic service termAllows generic service words from the domain in reports and rank checks. Business-name keywords stay excluded. Owner or admin.—

The three client-visibility switches save immediately; a flip that notifies the client or takes a service out of their plan asks you to confirm first. The report day saves when you leave the field, and an invalid day is never written — the field snaps back and explains why.

These are the same three switches as the SEO, per project block on the client's Client visibility page. SEO reporting is the included SEO Reporting & Technical SEO service: on when the service is included in the client's plan, off cancels it. Blog posts covers Show scheduled blog posts in client Content Center on the website's autoblog schedules and the included Blog content service; it is on while anything behind it is on, and its hover says when posts are not reaching the calendar yet. A greyed switch says why on its hover. While a switch is off, the eye-slash button beside it hides the offer from the client, and a paused service shows Resume. A service billed through Stripe never switches off here: the switch stays on and says why, so cancel the charge in the client's billing first. A website without a client portal of its own is switched here too — its services are included for it alone, on the portal it signs in through, and a line under the switches names that portal. If the client's services cannot be read, the section says so and the switches cover the SEO Command Center parts only.

On the Portfolio, Manage websites shows one SEO reporting dot per website — on whenever the client sees SEO reporting (the included service, or an older reporting setting still on; a hidden offer keeps it off unless another of their portals has reporting), off otherwise; its label reads on, off or hidden. The dot changes nothing; click it to open that website's SettingsReporting & clientClient visibility. It is greyed out on a website that is not enrolled.

What saves how

ControlSaves
The four automation lanesOn click
Client visibility switchesOn click, after a confirm when the client is notified or a service leaves their plan
Paid research cadence and budget fieldsWith Save automation settings
Auto-send fixes, Recently changed pages and Bluehost deployWith Save fix automation, which appears once you change one
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 stopped for the month on a website with no budget typedOn a metered workspace a blank budget runs against $15 a month, and this month's $15 is usedType a monthly SEO budget to set your own cap, or wait for next month
Readiness says Command Center keyword data reached its $15 default on a website with no budget typedOn a workspace exempt from credit metering a blank budget caps only Command Center keyword data, and this month's $15 is used. Strategy runs and drafting have no monthly SEO budget thereWait for next month — each keyword-data pull you start asks you to confirm meanwhile — or type a monthly SEO budget, which then caps every lane, strategy runs included
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 fix was not auto-sent although auto-send is onIts page was changed recently and Recently changed pages is set to WaitSend it by hand, choose Go last, or let the page finish its wait
A member cannot arm auto-attachArming it needs owner or admin rightsAsk an owner or admin
A member cannot change the generic-domain ruleIt needs an owner or adminAsk an owner or admin
The client says SEO is missing from their portalSEO reporting is off and nothing else has opened their SEO tabTurn on SEO reporting, or attach a report
SEO reporting will not switch offA service billed through Stripe keeps the client seeing itCancel the charge in the client's billing first — the switch never stops a charge
Map Pack results reads Not shownMap Pack shows inside SEO reporting, and SEO reporting is offTurn on SEO reporting
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 needs owner or admin rights, terminal wiring and FTP credentialsConfirm both with your platform operator before relying on it