Automations

Automations is a store of optimizations. Each one is a rule that watches a specific field on your site and fixes it when a condition is met — continuously, without manual work.

Categories

• SEO — titles, meta descriptions, headings, anchor titles.
• GEO — structured data and answer-engine oriented markup.
• Media — image alt text and media metadata.
• Speed — performance-oriented markup optimizations.
• Accessibility — alt text, heading structure, descriptive links.
• Social — Open Graph and Twitter/X cards.

Activating your first automation, step by step

1. Open Automations and filter by category.
2. Click an automation to open its configuration panel.
3. Set the trigger condition: if missing, if empty, if not empty, if shorter than N characters, if longer than N characters.
4. Add an optional prefix / suffix for fixed text, e.g. | Brand.
5. Define the scope — all pages, specific templates, product types or URL patterns.
6. Save, then switch the toggle on.
7. Wait for the next crawl, then check the changes history to confirm the values Tuurbo wrote.

Choosing trigger conditions well

• Use if missing for a safe first pass: nothing you wrote by hand is touched.
• Use if shorter than N to upgrade weak values without rewriting good ones.
• Use if not empty only when you deliberately want AI to override existing content.

Recommended rollout

1. Week 1: missing meta descriptions and missing titles.
2. Week 2: image alt text and social cards.
3. Week 3: structured data for GEO/AEO.
4. Week 4: heading structure and internal anchor titles.

Running them in waves keeps the changes history readable, so you can tie a ranking movement to a specific batch.

Monitoring

Applied changes appear in the changes history with before/after values, and generated content is listed in the Generations tab of the SEO page. From there you can:

• review a generated value and edit it manually;
• exclude a URL from a rule;
• pause the automation without losing its configuration.

Locked automations

An automation can be locked because it belongs to a higher plan or because it requires a connector (for example writing back to a product catalogue). The panel tells you which of the two applies.