WordPress vs Webflow vs Shopify: what SEO automation can edit

SEO automation is only as useful as the fields it can reach. A recommendation to rewrite a heading is no help if no outside tool can edit that heading.

The three big platforms store the same things in different places. On one, a page's main heading is a field you can change from outside; on another, it is part of a layout that only a person can edit. On one, an edit goes live the moment it is saved; on another, it waits for a publish that also releases everything else on the site.

This guide sets out, field by field, what automation can edit on WordPress, Webflow and Shopify, the access it needs, when edits go live, how to check and undo them, and the limits. A worked example runs a queue of twelve changes through it.

The four fields

• SEO title: the page's title tag. Google usually shows it as the clickable headline in results.
• Meta description: a short summary of the page. Google sometimes shows it under the headline.
• H1: the main heading on the page itself.
• Body: the page content, where new sections, FAQs and internal links go.

The matrix

Ship/Scale writes to all five rows as described here: WordPress posts and pages (SEO fields through Yoast or Rank Math), Webflow CMS items in full and static pages' SEO title and meta description only, and Shopify products, collections, pages and articles.

WordPress

SEO title and meta description. WordPress itself has no meta description field and builds the title tag from the post title and site name. Both fields come from an SEO plugin such as Yoast or Rank Math, which stores them alongside each post. Automation writes to those plugin fields, so without a plugin there is nowhere to write them. Some setups need an extra step before outside tools can reach the plugin's fields; a good tool will tell you when it can't.

H1. Most themes display the post or page title as the H1, so changing the H1 means changing the title. Editing the title of a published post doesn't change its URL. Some themes and page builders add their own heading inside the content instead; check the live page before assuming which element is the H1.

Body. The post or page content. Pages built with a visual page builder may store much of their layout outside the main content, so check one such page before trusting automation across all of them.

Access needed. A WordPress user who can edit and publish both posts and pages. The Editor role can; an administrator account isn't needed. The tool connects with an application password: a separate password for that user, created in their profile, which you can revoke on its own without changing their normal login.

Going live. An edit to a published post or page is live as soon as it is saved. WordPress keeps revisions of the title and content; SEO plugin fields may not appear in them.

Webflow

Webflow has two kinds of page, and they behave very differently.

CMS items are entries in a collection, such as blog posts or location pages, displayed through a template page. Automation edits the item's fields, which only changes the page if the template uses them. If the template's SEO title is bound to an "SEO title" field, editing that field changes the title tag; if it is typed into the template's settings, it won't. The H1 is usually bound to the item's name, and the body to a rich text field. A CMS item can be published on its own, so an edit can go live without publishing the whole site.

Static pages are designed one by one in the Designer. Outside tools can change their SEO title and meta description; the H1 and body copy are edited in the Designer, by a person. And static-page SEO changes only go live when the whole site is published. A site publish releases everything unpublished on the site, including someone's half-finished Designer work. That is the main risk with Webflow, and why a site publish triggered by automation should be something you opt into, not a default.

Access needed. A site API token with read and write access to the CMS and to pages, plus permission to publish.

Shopify

SEO title and meta description. Every product, collection, page and blog article has its own search engine listing fields, separate from its title. Changing them doesn't change the product name or anything in the page content.

H1. Most themes display the product, collection, page or article title as the H1. For products this matters: the product title is the product's name everywhere in the store (collection grids, search, the cart) and in any sales channel that uses it. Usually the SEO title is the field to change.

Body. The product or collection description, or the page or article content. On many themes the description is only part of a product page, with other sections coming from the theme. New content appears wherever the theme shows the description.

Access needed. A custom app in the store with read and write access to products (which include collections) and to online store content (pages and blog posts).

Going live. Edits to an active product or a visible page go live as soon as they are saved.

When edits go live

Checking and undoing

Check the live page, not the admin. After each change, view the live page's source and find the title tag, meta description, H1 and new section. A caching plugin or content delivery network can serve the old version for a while, so a missing change may simply be cached.

Check what Google sees. Search Console's URL Inspection tool can fetch the live page as Google does. Google's Rich Results Test checks structured data such as FAQ schema. Two cautions: Google shows a new title only after it recrawls the page, and it sometimes shows different text from your title or description. Google also shows FAQ rich results for very few sites now, so the value of an FAQ is the answers on the page, not a larger search result.

Undo from a record, not from memory. Don't rely on platform history: it varies by platform and by field (WordPress revisions, for example, may not include SEO plugin fields). The dependable undo is a record of each field's exact value just before the change. A safe undo should also refuse if someone has edited the page since, or it will overwrite their work.

Ship/Scale runs in approve mode by default, so nothing is written until you approve it, unless you switch on autopilot for a site and type of change. It logs every change with the value it replaced, re-reads the live page to verify each one, and its rollback restores the old value exactly and refuses if the page has changed since. The guide to approving and undoing automated SEO covers the approval side.

A worked example: a queue of twelve changes

Take an agency with three clients: a WordPress blog, a Webflow marketing site and a Shopify store. This month's recommended changes are below. The queue is illustrative.

Counting them:

• Written by automation and live without a site publish: changes 1 to 6 and 10 to 12, which is 6 + 3 = 9.
• Written by automation but waiting for a site publish: change 7, which is 1.
• Needing a person in the Designer: changes 8 and 9, which is 2.
• Total: 9 + 1 + 2 = 12. So 9 of 12 changes (75%) can run from approval to live page with nobody opening an editor.

The three Webflow static-page changes (7, 8 and 9) share one step: a site publish. The sensible order is for a designer to make changes 8 and 9, check nothing else is waiting to be published, then publish the site once, which takes change 7 live at the same time. If each Designer edit takes about 15 minutes, that is 2 × 15 = 30 minutes plus the check, and one site publish instead of three.

Two rows need a second look. Change 3 assumes the theme shows the page title as the H1, so check the live page. Change 10 edits the product's SEO title, not its title, so its name in the store stays the same.

Where the limits are

• Webflow static pages. The H1 and body live in the Designer, and SEO changes need a site publish that releases all other pending work. Treat these as shared jobs between automation and a person. On CMS items, a template that doesn't use a field ignores edits to it.
• WordPress page builders and unusual themes. The H1 may not be the page title, and the visible content may not be the main content field.
• Shopify product titles. The H1 is the product name everywhere it appears. Change the SEO title instead unless renaming is the point.
• Google decides what to show. It may rewrite your title, ignore your meta description, or take a while to recrawl the page. A correct edit on the page is not the same as a changed search result.
• Access that outlives the work. Use a dedicated account, token or app for automation, give it only the access in the lists above, and revoke it when you stop.

The short version

Most SEO fields are writable from outside on all three platforms: WordPress posts and pages (SEO fields through an SEO plugin), Webflow CMS items and Shopify products, collections, pages and articles. The exception is Webflow static pages, where only the SEO title and meta description can be changed and they go live with a site publish that releases everything else too. Edits on WordPress and Shopify are live on save, so check the live page after every change and keep a record of each field's previous value for undo.