How Seofyme works

The editor panel scores your content locally; Seofyme Cloud is only called when you explicitly ask it to draft copy or run a hosted audit.

5 min read

Seofyme is deliberately split into a local layer that runs entirely inside WordPress (or the Shopify app) and an optional Cloud layer that only gets called when you ask for hosted AI drafting or a hosted audit. Understanding that split explains why most of the plugin works with zero network calls and zero account.

The local layer

When you open a post in the block editor, the Seofyme panel reads the draft, your focus keyphrase, and your site's settings, then runs checks entirely in the browser or in PHP on your own server: keyphrase placement, meta length, heading structure, internal link count, image alt coverage, and readability. Sitemap generation, schema output, redirect matching, and the 404 monitor also run locally on every request — nothing leaves your server for these.

The Cloud layer

Two features specifically call out to Seofyme Cloud: hosted title & meta generation (a faster alternative to bringing your own OpenAI/Anthropic key) and hosted site audits (a full crawl run on Seofyme's infrastructure instead of your own server's CPU). Both are metered against your plan's monthly quota and authenticated with the API keys you generate in your account.

LayerRuns whereNeeds an account?Examples
LocalYour WordPress server / the Shopify appNoOn-page scores, sitemaps, schema, redirects, 404 monitor, internal linking
CloudSeofyme's serversYes (API keys + a Cloud plan)Hosted AI drafting, hosted site audits

Billing follows the product you're on

WordPress users are billed for Seofyme Cloud through CacheRocket — the same billing account used by CacheRocket's own caching and CDN products, if you have one. Shopify merchants are billed through Shopify Admin in USD instead, since Shopify requires billing to run through its own APIs for listed apps.

Note

If you never touch AI drafting or hosted audits, Seofyme never talks to the network beyond the checks WordPress itself already makes (e.g. checking for plugin updates). The free toolkit really is fully local.