AutoSEO: on-page optimisation that also works at night

Execution is the real bottleneck

Ask any SEO team in Munich why their last content refresh took eight weeks. The answer is always the same: not research, not writing, but execution. An SEO manager spots in an analysis that 300 product pages need new title tags. They send an Excel list to the dev team. The ticket backlog accepts it in four weeks. A junior developer copies the values manually into the CMS, mistypes 12 lines, and the QA cycle drags on for another two weeks.

In that time the SERP has changed twice, a competitor has updated their content, and the original recommendation is partially outdated. This pattern repeats in at least 8 out of 10 DACH SMEs we work with. It costs the client more than any other SEO inefficiency: our internal analysis at Munich SEO shows a median of 41 days between „recommendation identified“ and „change live“.

AutoSEO reduces that median to 3 minutes after approval. That's the essential reason clients see more ranking movement after 90 days than in the 24 months before.

What AutoSEO actually changes

AutoSEO only touches on-page signals — things that live in the HTML of a page. It doesn't change editorial content (article text or product descriptions). What it does:

Approval workflow: no wild automation chaos

The most important difference from cheap „SEO automation plugins“: AutoSEO changes nothing without approval. Every planned change runs through a four-stage process:

How it binds to your CMS

Semalt AutoSEO integrates natively with the systems most used in DACH:

• WordPress: official plugin that complements Yoast/RankMath/AIOSEO (doesn't replace them). Changes are written to the WP database via WP-CLI or REST API, with full nonce-based auth handshake.
• TYPO3: extension (compatible with v11/v12/v13) targeting tt_content entries and meta records.
• Shopware 6: app in the Shopware Store that modifies Product and Category entities via Admin API.
• Contao: bundle for Contao 5 with roles-and-rights integration.
• Shopify, Magento 2, WooCommerce, Prestashop: native connectors with app-store presence.
• Custom / headless: REST and GraphQL APIs, plus a Git-based workflow (changes as pull requests in your repo, deployed by your existing CI/CD).

The Git-based workflow is especially interesting for teams managing content in Markdown or MDX (Next.js, Astro, Hugo, Jekyll, Docusaurus). Instead of writing directly to the database, Semalt opens a PR with the recommended changes — the SEO team reviews on GitHub/GitLab, the merge triggers your existing deployment. No new deployment path, no new compliance questions.

Audit trail and rollback

Every change AutoSEO makes is stored with a full audit trail: who approved, when, previous version, next version. For enterprise clients the log is written to a separate S3-compatible bucket in EU data centres (Frankfurt) so that internal audit and compliance requirements are met.

Rollback works per change (revert a single meta description) or per batch (revert every change from the last 24 hours, e.g. if a Google core update had negative effects). Rollback for up to 10,000 URLs takes less than 60 seconds.

DACH specifics: TYPO3, Shopware, Contao

Three CMSs are disproportionately represented in Munich and the German-speaking SME market, and Semalt's competitors barely serve them:

1. TYPO3 — the extension supports multi-site setups, PageTree nested content and the typical tt_content elements. AutoSEO respects TYPO3 backend rights and never makes a change the logged-in editor wouldn't be allowed to make themselves.
2. Shopware 6 — Product, Category and CMS-Page changes go through the official Admin API. Multi-channel setups (different sales channels for DE/AT/CH) are fully supported, with correct hreflang between sales channels.
3. Contao — bundle for Contao 5 with role-based permissions and translation workflow. AutoSEO produces change proposals in the primary language, which then flow into other languages via the Contao translation workflow.

Case study: e-commerce from Sendling, 4,200 products

A B2B shop for lab supplies in Sendling, running on Shopware 6, had typical issues in 2026:

• Meta descriptions were auto-generated from the first 160 characters of the product description — mostly generic, without search intent.
• Product schema was missing the new Merchant Listing required fields Google introduced in 2026.
• hreflang between DE-DE, DE-AT and DE-CH was asymmetric on ~600 URLs.
• Over 800 product images had no alt text.

AutoSEO was activated on 12 April 2026. In the first 14 days:

2,340 changes proposed. 2,087 approved (89 %). 253 rejected or manually revised. All 4,200 products had, by 26 April: unique SERP-optimised meta descriptions; complete Merchant Listing schema; symmetric hreflang clusters; alt texts on every image.

SEO impact after 90 days: organic clicks +47 %, Merchant Listing impressions (newly unlocked) +180 %, organic pipeline +34 %. Before AutoSEO the internal team had estimated roughly 8 person-months for the same execution — realistically 14 months given other priorities. AutoSEO delivered it in two weeks.

FAQ

Does it change my editorial content?

No. AutoSEO only touches structural on-page signals (meta, schema, hreflang, alt, internal links, redirects, sitemap, robots.txt). Blog article text or product descriptions remain unchanged — that's the content team's responsibility.

What happens during a CMS upgrade?

The plugins/extensions follow the CMS's official update cycles and are tested before every major release. On breaking changes the deployment mode pauses (changes still collected, not executed) until compatibility is restored.

Can I review everything myself?

Yes — manual approval mode is on by default. For teams that want to work faster, auto-approve can be enabled per change type or per URL pattern. Example: alt-text changes automatic, everything else manual.

How do you make sure no harmful change goes live?

Three safety layers: (1) every proposal is checked against 40+ rulesets (e.g. „no title tag longer than 60 characters“, „no canonical to a 404 URL“), (2) manual approval, (3) atomic deployment with instant rollback on error. Additionally a staging mode can be enabled that tests changes in a staging environment first.

What does it cost?

AutoSEO is included in the professional Semalt tier (no separate upsell). Enterprise tiers add multi-site management and dedicated support.

Can I cancel and keep the changes?

Yes — every change is „permanent“ in the sense that it's written into your CMS, not into a separate Semalt database. On cancellation only the inflow of new proposals stops; existing meta tags, schema blocks etc. remain in your CMS.