SEO changes in Glasgow: 3 minutes, not 6 weeks in a Trello column

What AutoSEO actually changes on your site

AutoSEO isn’t a chatbot spitting generic tips into a WordPress dashboard. It’s an execution layer. Findings come out of the Semalt technical audit, priorities come out of the AI keyword engine, and the changes land on the pages that need them. The scope is deliberately narrow: on-page only. Nothing touches product prices, legal copy, or checkout flows — the stuff a Sub Club night manager and a Glasgow Green events team both need left alone. Everything it does write is reversible with one click. Ship it, watch it, roll it back if you don’t like it. The graft’s the thing; the fear of breaking something is the thing that stops most sites ever getting fixed.

Platforms supported: WordPress, Shopify, WooCommerce, Umbraco

WordPress dominates the Glasgow SME market, so it gets the deepest integration: a native plugin distributed through the WordPress.org repository, supporting classic, block editor and any Gutenberg-based theme (Astra, Kadence, Blocksy, GeneratePress). WooCommerce is treated as a first-class subset with Product schema support and stock-status awareness.

Shopify comes second in our Glasgow customer base, particularly for D2C brands (fashion, food, whisky). The Shopify app installs from the App Store, respects theme sections, and never touches liquid files it did not create. Umbraco — still popular for Scottish public-sector work and a few larger financial-services clients — is supported via an official package that speaks the Content Delivery API. For everything else (Craft, Statamic, custom Laravel, Sitecore) the REST API handles it, and we ship an SDK that most Glasgow agencies wire up in an afternoon.

Hosting: Fasthosts, Krystal, Kualo and the deploy window

UK small businesses run on UK hosts. The big three we see in Glasgow — Fasthosts (Gloucester), Krystal (London / Manchester) and Kualo (London) — each have their own maintenance-window quirks. Krystal, for example, runs LiteSpeed with LSCache; a title change on WordPress will not surface until the cache purges. Kualo runs a strict daily backup cycle where deploys after 02:00 Europe/London get folded into the next day’s snapshot. Fasthosts throttles WP-Cron on shared plans.

AutoSEO detects the hosting environment automatically from HTTP headers on install and schedules deploys accordingly: it runs cache-purge hooks after every write on Krystal, avoids the Kualo backup window, and switches to server-side cron rather than WP-Cron on Fasthosts. All of it is Europe/London-aware, including the twice-yearly BST transitions where every naive scheduler in existence gets an hour wrong.

GDPR-aligned change audit trail

Every AutoSEO change writes an immutable record: what changed, who authorised the change (agent identity or human operator), when it deployed, and the exact before/after content. The audit trail is exportable as JSON, CSV or a signed PDF suitable for evidence in an ICO investigation. For Scottish public-sector customers subject to FOI and PSBAR 2018 requirements, the trail is essential.

Case study: Partick physiotherapy chain, three clinics

A physiotherapy chain with clinics in Partick, Byres Road and Merchant City engaged AutoSEO in January 2026. They had a WordPress site on Krystal, run by a solo marketing manager, no in-house developer, and a queue of 74 SEO recommendations from a previous audit that had been sitting in a Trello board for eight months.

Semalt’s technical audit re-ran, produced 91 findings (some of the old ones no longer applied), and AutoSEO started shipping fixes on a nightly cadence:

Total developer hours used: zero. The marketing manager reviewed and approved bundled changes weekly via the AutoSEO dashboard, and rolled back one internal-link addition that had triggered a false-positive link-density alert on a treatment page.

Safety rails: what AutoSEO will not touch

Automation without safety rails is a liability. AutoSEO is scoped hard. It will never modify: product prices, checkout flows, legal pages (privacy, terms, cookie policy), pages tagged with a “do not edit” class, any page marked as under a live A/B test, or any content in a language pack Semalt has not been explicitly authorised for. It will also not deploy any change flagged by the pre-flight linter (contains a broken link, invalid schema, invalid HTML).

Every deploy also runs a post-flight verification: AutoSEO waits ninety seconds after a write, re-fetches the URL through your CDN, and confirms the intended change actually surfaced. On LiteSpeed, Cloudflare and Fastly setups this is the difference between a change that lives on origin and a change your visitors actually see. If verification fails, the change is automatically rolled back and the marketing manager gets a notification — not a 24-hour silence followed by an angry client email on Monday morning.

On the WordPress side, the plugin coexists cleanly with Yoast SEO, RankMath, All in One SEO, and WP Rocket. AutoSEO writes to its own meta fields and only mirrors into the SEO-plugin fields with your explicit permission. That means Glasgow agencies migrating retainers can adopt AutoSEO incrementally without ripping out an existing setup that clients have paid for.

AutoSEO vs. Yoast vs. RankMath vs. manual agencies

FAQ

Does it install on WordPress multi-site?

Yes. Network-wide activation supported, with per-site permission scoping. Common on Scottish agency setups managing 15-40 client sites. Log in and install the plugin.

What happens if my developer edits the same field manually?

AutoSEO detects the manual edit on the next crawl and defers to the human. The finding is re-queued with a “human override detected” note; nothing overwritten silently.

Does it respect my brand voice?

Yes. During setup you either upload a brand voice document or point AutoSEO at 20-30 URLs it can learn tone from. Rewrites match that tone within a measured Levenshtein tolerance.

Is there a review step before changes go live?

Optional. Free tier defaults to auto-deploy with rollback. Paid tiers allow batched weekly review. Public-sector customers on our Umbraco integration use a mandatory approval workflow with two signatories.

How does it handle a WooCommerce site with 8,000 SKUs?

AutoSEO batches product-level changes to respect your host’s write throughput. On Krystal LiteSpeed, we typically write 500 products per hour. Stock-status changes never trigger schema regeneration — only content changes do.

How does it connect to the rest of the platform?

Findings from the technical audit, priorities from the keyword AI, and competitor moves from competitor analysis all feed the AutoSEO queue. Results feed back into Analytics. One loop.