Automation and schedules

LogNorm does two kinds of work without anyone clicking. Some research runs on a schedule you choose, per website: a fresh site audit, a re-analysis of your competitors, an AI visibility check and a weekly growth review. The rest of the growth loop runs on its own: new findings become moves, moves get scored and ranked, shipped work gets measured and your team gets a Monday digest. This page covers both, what each run costs and how to tell when something didn't start.

Scheduled research#

Each website has four schedules, set separately:

The site audit, competitor analysis and growth review are Off by default; the AI visibility check is Weekly. The schedule belongs to the website, not the workspace: if you grow several sites, set each one on its own.

Choose a cadence

1. Open the page for the research you want to schedule

   Go to Site for the site audit, Competitors for competitor analysis, or AI Visibility for AI visibility checks. Make sure the right website is selected in the website switcher.

2. Click the schedule button in the header

   It reads Schedule when nothing is scheduled. Once a cadence is set it shows the cadence and the next run, for example Weekly · next tomorrow at 09:40.

3. Pick Off, Daily, Weekly or Monthly (AI visibility also offers Twice a week)

   The change saves straight away and takes effect immediately; there is no separate save button. The panel then shows the Next run and the Last run.

How the next run is worked out

LogNorm doesn't keep a fixed timetable. The next run is always the last run plus the interval, and the last run counts whether it was scheduled or started by hand. That has a few practical consequences:

• Running it yourself resets the clock. If you click Re-analyse site on a Tuesday with a weekly schedule, the next scheduled audit moves to the following Tuesday.
• Changing the cadence applies at once. Switch from monthly to weekly and, if the last run was more than a week ago, the next run is due right away.
• Runs start within about 15 minutes of coming due. LogNorm checks for due runs every 15 minutes. When the next run is already due, the panel says starting shortly.
• Competitors are timed one by one. Each active competitor has its own last run, so the header shows the soonest competitor to come due. Paused or removed competitors aren't analysed.

Times in the panel are shown in your browser's time zone. While a run is in progress the button shows running and the panel says Running now.

Who gets scheduled runs#

Scheduled runs are for active accounts: a paid plan or a trial that hasn't ended. A few conditions apply on top of that:

When an account lapses, LogNorm keeps the cadence you chose and simply pauses it. Reactivate the plan and the schedule picks up again without you touching it. Which plans include competitor tracking is set per plan; see pricing.

What scheduled runs cost#

A scheduled run costs the same credits as the same run started by hand: a site analysis plus an SEO audit for the site schedule, and one competitor analysis per active competitor. Credits are held when the run is queued and settled at what the job actually used. A daily schedule on several competitors adds up quickly, so pick the slowest cadence that keeps your data fresh enough. See Credits and billing for how holds work and what each job costs.

When a scheduled run doesn't start

If a run comes due but can't start (not enough credits, your monthly spend cap is reached, or the workspace is suspended), LogNorm doesn't keep retrying every 15 minutes. It records the attempt, shows it in red in the schedule panel (The scheduled run 2 hours ago didn't start: …, with the reason) and tries again after one full interval, just as if it had run.

With competitor analysis, if one competitor can't start for a workspace-wide reason like credits, LogNorm stops trying the rest in that check rather than failing each one.

What LogNorm runs on its own#

Beyond these schedules, the growth loop keeps itself moving. None of this needs a setting; it follows from what you've already set up.

After a site analysis

Every site analysis (the first one when you add a website, a scheduled one, or one you start) is followed automatically by an SEO audit. If your plan includes them, it also looks for competitors and researches keywords seeded from your site. Keyword research runs at most once a week this way. New keyword research in turn refreshes the search landscape on the Competitors page.

Synthesis: turning findings into moves

Whenever a producer finishes (keyword research, a competitor analysis, a site audit, a Search Console sync or an AI visibility run), LogNorm schedules opportunity synthesis about a minute later. Bursts of findings collapse into one synthesis per website. Synthesis reads everything new and creates or updates moves.

Move scorecards and ranking

New moves arrive in bursts, so LogNorm waits about 90 seconds after the last one, then scores them together: each gets a scorecard, likely duplicates are merged or flagged, and open moves are ranked against each other head to head. Synthesis triggers the same pass as soon as it finishes. New moves are slotted in against the existing order without reshuffling everything, and your own “rank higher / lower” choices and plan drag-and-drop are respected on every pass.

Weekly re-rank. So Monday starts from a fresh order, every website with open moves gets a full re-rank at least once a week. It won't run if the moves were already scored in the last 24 hours. To force one now, use Re-score and re-rank on the Moves page. Scoring is billed by what the decision calls actually use, fractionally, with no upfront hold.

Outcome measurement

When content tied to a move is published, LogNorm records a 28-day baseline and marks the move as measuring. Every six hours it checks each website that has something to measure or a Search Console connection. It measures moves at 28 and 90 days, waiting a few extra days for Search Console data to settle. The same check watches for decay: pages whose clicks fell by 30% or more over the last 28 days compared with the 28 before, which become moves of their own. See Results and measurement.

Other recurring checks

Rank checks, AI visibility runs and GEO audits use credits the same way as when you start them yourself. Search Console syncs are free. Like scheduled research, a recurring run that can't get its credits doesn't start.

The weekly digest#

Every Monday, from 07:00 UTC, LogNorm emails each member of the workspace a digest, with a matching in-app notification. For each website it covers:

• this week's plan, against your weekly target;
• unfinished moves carried over from earlier weeks;
• moves LogNorm recommends;
• last week's outcomes: wins and measured moves;
• pages that decayed.

It goes out once per week, and only to workspaces that have moves and whose plan includes the digest. To turn it off or on, go to SettingsGeneral and use Monday digest email (owners and admins). To see what it looks like, click Send me a preview on the Growth Dashboard; the preview goes only to you. More in Growth Plan.

Troubleshooting#

Related#