Jake Labate

Deploy Layer

Most SEO recommendations wait weeks for a developer, and the ones that ship leave no record of what was there before. Deploy Layer publishes SEO settings straight to live WordPress and Webflow pages, keeps the value each change replaced, and takes any of it back in one click. It holds no opinion about what should change.

Open Deploy Layer See how it works

What It Is

Deploy Layer is the last step between an SEO decision and the live page. You connect a site, pick a page from its own list, and set the title, meta description, robots, canonical, Open Graph and X tags, and structured data. The change goes out to the site in the background, and the value it replaced is kept beside it.

It deploys, tracks and reverts. It never decides. What should change is the job of an audit, a person, a spreadsheet or an AI. Deploy Layer is deliberately the part underneath all of them, so any of them can ship a change the same way and every change can be taken back the same way.

What Deploy Layer keeps

Every change with its before value

What was set, on which page, through which route, and what it overwrote.

What a dev ticket keeps

A request with no history

Shipped weeks later if at all, with nothing to roll back to.

There are four ways in: a dashboard, a CSV upload, a REST API, and an MCP server for Claude. All four end in the same queue, the same history and the same undo.

The Problem It Solves

Three things go wrong between an SEO recommendation and the live page:

  • The fix waits on a release. A rewritten title sits in a sprint backlog behind work that ships revenue, so the recommendation goes stale before it goes live.
  • The change leaves no record. Once a value is overwritten in a CMS field, nobody can say what it was, who changed it, or put it back.
  • Two things print the same tag. An SEO plugin, the theme and WordPress itself can each write a canonical or a title, and a search engine picks one of them.

Giving the SEO admin access to the CMS fixes the first problem and makes the other two worse. Changes get faster and the history gets thinner, and nobody checks what the page actually prints afterwards.

Deploy Layer takes SEO settings out of the release cycle and puts them in a layer that records and reverses every change. It then reads the live page back to confirm there is one of each tag, so a fast change is also a checked one.

Where It Gets Used

Four moments where shipping the change is the hard part.

  • After an audit. The findings become a CSV of URL, field and value. The whole file is previewed against the live pages, published as one batch, and can be undone as one batch.
  • From Claude. In claude.ai or Claude Code, ask in plain words to set the title of a page, and it goes out through the MCP server. A dry run first shows what would change without changing it.
  • From your own code. A script, Zapier or Make calls the REST API with a key you made in the dashboard, and the change lands in the same history as one made by hand.
  • On a site that already has an SEO plugin. On a client's WordPress with Yoast or Rank Math installed, changes are written into that plugin's own fields rather than printed as a second tag, and its value goes back on undo.

How It Works

You do two things: connect a site, and say what each page should be. The diagram follows one batch for a fictional shop, from the routes a change can come in by, through the preview and the queue, to the two kinds of site it lands on.

Nothing in the loop is generated. Every value on the page is one somebody set, and the one before it is kept.

  1. Connect

    A WordPress site gets a small plugin, paired with a one-time code from the dashboard that works once, for one hour. A Webflow site connects with a site API token that can read and write Sites and Pages and nothing else. Both connections are stored encrypted.

  2. Set

    Pick a page from the site's own list and edit its settings in tables grouped by topic, with a character guide on the title and description. Or upload a CSV of URL, field and value, call the REST API, or ask Claude. Every route turns into a batch.

  3. Preview

    A dry run checks each change against the live page before anything is written. A value that is already live is skipped as a duplicate, a page that was edited since is skipped as stale, and a field the platform cannot take is refused with the reason.

  4. Publish

    The batch runs on a queue in the background and retries a change that fails. On WordPress, a field an SEO plugin owns is written into that plugin's own settings, and any other field has whatever printed it before taken out of the head and replaced. On Webflow, the site is published once per batch, about a minute later, or left for you to publish yourself.

  5. Check

    After each change the live page is read back and every tag is counted. A second canonical or title, from the theme or another plugin, is flagged on the change itself, because a search engine picks one of two at random.

  6. When a change was wrong

    Undo

    Undo the last change to one field on one page, or a whole batch. The value it replaced goes back, including the SEO plugin's own value when the change was written into it. Both the change and the undo stay in the history.

Three decisions worth naming. The WordPress plugin exposes primitives rather than tactics, so new behaviour ships on the server and the plugin on a client's site rarely needs updating. An installed SEO plugin is written through rather than fought, so its admin screen and the live page agree. And structured data is only ever added: Deploy Layer never removes another plugin's JSON-LD graph.

Who Owns Each Step

  • Code should be responsible for the defined.
  • AI should be responsible for the undefined.
  • Humans should be responsible for the outcome.

In this product, code runs 3 of 6 steps. No step needs AI, because nothing in it is left undefined. You connect the site, decide what each page should say, and decide whether a change stays.

Swipe sideways to follow the steps in order.

  1. 01

    Connect The Site

    Install the WordPress plugin and pair it with a one-time code, or paste a Webflow site API token.

  2. 02

    Say What Changes

    In the dashboard, a CSV, your own code, or by asking Claude. Deploy Layer has no opinion about the value.

  3. 03

    Preview

    Checks every change against the live page. Values already live and pages edited since are skipped.

  4. 04

    Publish

    Runs the batch on a queue, writes through an installed SEO plugin, and keeps the value each change replaced.

  5. 05

    Check The Live Page

    Reads the head back and counts every tag. A setting printed twice is flagged on the change.

  6. 06

    Keep Or Undo

    Undo one field or the whole batch, and the value it replaced goes back. Both stay in the history.

Who It Is For

Anyone who owns SEO recommendations but not the release that ships them. Consultants and agencies working on client WordPress and Webflow sites, in-house SEO leads queued behind a product roadmap, and anyone building an SEO agent that needs a safe place to write, with an undo.

It is deliberately narrow. It changes what a page tells search engines and social sites, keeps a record, and checks the result, and it stops there.

  • Not an SEO plugin. It suggests nothing and scores nothing. On a site that already has one, it works through it.
  • Not a CMS. Pages, content and templates stay where they are. It writes head settings, and from a CSV, headings and link anchors.
  • Not an audit tool. What to change comes from somewhere else. Deploy Layer is where that decision gets shipped and, if needed, taken back.

Status And Access

Yes. Sign up, connect a WordPress or Webflow site, and pick a page.

Status
Since Nov 2026Live
Who can use it
Anyone who signs up
Sign-in
Email
Cost
Free
Your data
In your account
Source code
Private
Install
A small WordPress plugin, paired once with a code from the dashboard. Webflow sites connect with a site API token instead, and nothing is installed.
Works today
Title, meta description, robots, canonical, Open Graph and X tags and JSON-LD on WordPress, with headings and link anchors by CSV. On Webflow, the title, meta description and social title and description.
Not yet
Webflow CMS item pages, and platforms other than WordPress and Webflow.
API
A REST API with keys you create and revoke yourself. Add deploy.jakelabate.com/mcp to claude.ai as a custom connector, or to Claude Code.
Data handling
Your sites, their page settings and the history of every change with the value it replaced. Each site's connection token is stored encrypted.

A Recommendation Only Counts Once It Ships

Getting a title or a canonical onto the live page, with a way back, is the part this handles. Deciding which pages to change, what to change them to, and in what order is the work. That is what an engagement is for.

Get In Touch