Skip to content

Settings

Where your publishing destinations, data connections, Telegram and notification preferences live, and what each one affects elsewhere.

AccountUpdated 26th August 20263 min read

It sits at the bottom of the sidebar, alongside Get Help.

Overview#

Settings holds everything that configures the project rather than measuring it: the sites and accounts you connect, how alerts reach you, and what you get told about.

Most of it gets set once and then forgotten, which is fine. The part genuinely worth coming back to is the connections, because they fail quietly rather than loudly.

Connections#

WordPress and Webflow are publishing destinations. Connect whichever one runs your site and drafts will publish straight to it. Webflow takes a little more setting up, because collections carry custom fields that differ from site to site, so you map those once here and every later publish reuses the mapping. See Publishing.

Google Analytics, Google Search Console, Google Ads and Bing Webmaster Tools all bring outside data in, and Integrations covers what each of them adds.

Check your connections after any credential change, because an expired token does not announce itself. What happens instead is that the screen quietly stops showing new data, which looks identical to a quiet week and gets noticed considerably later than it should.

Telegram#

Telegram Notifications sends agent output and alerts to Telegram, so approvals can reach you without opening the dashboard at all.

Connect Telegram starts the process and shows a link, with Generating link... while it prepares one. Scan or click the link completes the pairing, after which Connected and Linked as confirm which account has been attached. Disconnect Telegram unlinks it again.

Telegram Notifications

Connect Telegram
starts the pairing and shows a link
Scan or click the link
completes it from your phone
Linked as
confirms which account is attached
All team members
everyone receives agent output
Only the person who triggered it
no five-people-notified problem
The last two are the decision that keeps the channel from being muted.

There is a delivery choice here worth a moment's thought: All team members or Only the person who triggered it. The first is right where a team genuinely shares responsibility for approvals. The second avoids notifying five people about something one person started, which is otherwise the fastest route to everybody muting the channel and nobody seeing anything.

Notification preferences#

Notification preferences controls what Seerly emails you about. These are set per person rather than per project, so everyone on the team chooses their own. See Notifications.

Connections are independent, so the order is preference rather than requirement, but one order pays better than the rest. Google Analytics first, because baselines only accumulate from the day you connect. Search Console second if organic search matters to you. The publishing destination when you actually start publishing rather than in advance, since an unused connection is one more credential to rotate. And Telegram last, once agent output exists to deliver, at which point the delivery scope decision is real rather than hypothetical.

Best practices#

  • The publishing destination connected if you publish to your own site, since it takes the copy-and-paste step out of the channel you will use most.
  • Google Analytics connected early, so a baseline exists before you start changing things.
  • Telegram delivery scoped sensibly rather than notifying everybody by default.
  • Connections verified after any credential change.

Next steps#

  1. Connect Google Analytics first. It has the widest value and is available on every plan.
  2. Connect WordPress or Webflow when you actually start publishing rather than before.
  3. Add Search Console if organic search matters to you, since the cross-surface comparison it enables is where a number of useful findings come from.
  4. Set Telegram delivery to match how your team actually works, not how it is organised on paper.
  5. Re-check connections periodically, particularly after anybody rotates credentials.

Limitations#

Settings configures the project. It does not change what Seerly measures, which comes entirely from your topics and prompts. See Prompts.

Notification preferences are personal, so changing yours does not change anybody else's.

Related