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.
| Setting | What it changes | Default |
|---|---|---|
| Pause everything | Pauses autoblog, fixes, evidence refresh and reports together. Resuming restores whatever was on before. | — |
| Autoblog | Scheduled blog pipelines. Resuming re-enables only the pipelines that were on. | — |
| Fixes | Pauses auto-apply, auto-send, the page loop and deploy repair. Per-fix buttons still work. | — |
| Evidence refresh | Pauses 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. | — |
| Reports | Pauses monthly report generation. The reporting mode is remembered and restored on resume. | — |
| Monthly SEO budget | The 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 agent | Sends 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 pages | What 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 commits | FTP-deploys fix commits on Bluehost-hosted sites. Owner or admin only, and dormant until the terminal service and tenant credentials are in place. | Off |
Paid research cadence (Advanced)
How often Zyan refreshes paid search evidence by itself. The panel shows a live monthly estimate as you choose.
| Setting | What it changes | Default |
|---|---|---|
| Off | No automatic paid research. The preview reads Off, $0 a month. | Default for every mode except Full Autopilot |
| Weekly | Every 7 days, roughly $8.70 a month at the $2 per-run estimate. | — |
| Every 2 weeks | Every 14 days, roughly $4.35 a month. | Inherited default under Full Autopilot (monthly until 2026-09-22) |
| Monthly | Every 30 days, roughly $2.03 a month. | — |
| Quarterly | Every 90 days, roughly $0.68 a month. | — |
Optional content lanes (Advanced)
Both are off by default.
| Setting | What it changes | Default |
|---|---|---|
| Internal-linking sweep | Adds up to three links to each new post from older posts on its keyword, through the live-fix lane. | Off |
| Promote audit errors automatically | Adds 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.
| Setting | What it changes | Default |
|---|---|---|
| Pages the AI must never edit | Protected paths, one per line, that the writer and fix agents must leave alone. | — |
| Country | The country preset research runs against. A non-country code here breaks research-target creation. | — |
| Local market locations | The towns and areas local research and Map Pack tracking measure. This picker saves separately from the section. | — |
| Writer model | The model the blog writer uses. Left empty on the desktop lane, the signed-in subscription's default model runs. | — |
| Content guidelines | Extra writing direction handed to the writer on every run. | — |
| Effort | Reasoning effort for the writer. | — |
| Max turns | Maximum agent turns per writing run. | — |
| Timeout minutes | The run time limit. Local runs can be saved up to 240 minutes. | — |
| Prefer desktop runner for blog drafts | Drafts run on an open, bound desktop's Claude subscription with no API spend. | On |
| Cloud fallback for waiting drafts | After a few minutes with no desktop, sends the draft to the cloud writer using your API credits. | Off |
| Additional content paths | Extra directories the blog writer may edit, one path per line. Advanced. | — |
| Language code | The research result language. Advanced. | en |
| Who this website is for | Shows the stored target audience. Read-only here — it is edited on the Research brief. | — |
| Image style notes | A 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.
| Setting | What it changes | Default |
|---|---|---|
| Connection readiness | A 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 date | The month reporting comparisons start from. It cannot be in the future, and it cannot be re-locked from here afterwards. | — |
| Capture baseline | Locks the reporting baseline snapshot. | — |
| Map Pack tracking | The local rank grid — listing, grid size, keywords, cadence and monthly budget. | — |
| AI provider keys | Reports whether the writer and review providers are configured. Platform-level. Advanced. | — |
| Index coverage | Indexing state for the website's pages. Advanced. | — |
| Run health | Named problems such as a research provider fault, a stale autoblog run, not-generated reports, a scheduler problem, or no tracked keywords. Advanced. | — |
| Scheduler job history | Recent 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
| Setting | What it changes | Default |
|---|---|---|
| Monthly report autopilot | Off, Draft for review, or Auto-attach after QA. Auto-attach is owner or admin only to arm. | Off |
| Generate on day of month | The day, 1 to 28, the monthly report is generated. Saves when you leave the field. | Off until set |
| SEO reporting | Includes 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 posts | Shows 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 results | Shows 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 term | Allows 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
| Control | Saves |
|---|---|
| The four automation lanes | On click |
| Client visibility switches | On click, after a confirm when the client is notified or a service leaves their plan |
| Paid research cadence and budget fields | With Save automation settings |
| Auto-send fixes, Recently changed pages and Bluehost deploy | With Save fix automation, which appears once you change one |
| Content & page rules | With Save all |
| Local market locations | Separately, from its own picker |
| Generate on day of month | When you leave the field, or on Enter |
| Map Pack tracking panel | With its own Save, except client visibility |
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| A cadence change did not stick | Cadence fields need the section's save button | Click Save automation settings |
| A content rule did not stick | The section commits together | Click Save all |
| Paid research stopped for the month on a website with no budget typed | On a metered workspace a blank budget runs against $15 a month, and this month's $15 is used | Type 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 typed | On 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 there | Wait 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 paused | The monthly budget is reached | Wait 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 on | Its page was changed recently and Recently changed pages is set to Wait | Send it by hand, choose Go last, or let the page finish its wait |
| A member cannot arm auto-attach | Arming it needs owner or admin rights | Ask an owner or admin |
| A member cannot change the generic-domain rule | It needs an owner or admin | Ask an owner or admin |
| The client says SEO is missing from their portal | SEO reporting is off and nothing else has opened their SEO tab | Turn on SEO reporting, or attach a report |
| SEO reporting will not switch off | A service billed through Stripe keeps the client seeing it | Cancel the charge in the client's billing first — the switch never stops a charge |
| Map Pack results reads Not shown | Map Pack shows inside SEO reporting, and SEO reporting is off | Turn on SEO reporting |
| Cron-step history says it is not available | It is not exposed to workspace logins | Use Run health and Scheduler job history instead |
| Bluehost deploy after fix commits does nothing | It needs owner or admin rights, terminal wiring and FTP credentials | Confirm both with your platform operator before relying on it |