What is actually available today
This workflow is not runnable. Metadata Pack Generator is registered as planned rather than live, so the page shows a placeholder instead of a working form. There is nothing to submit and nothing to receive, and saying so plainly is more useful than a page that looks like a tool and then does nothing when you press the button.
The parts of this job that do work today are separate pages. The meta title and description length checker measures what you have written against the thresholds where Google starts truncating, and the Open Graph preview shows how a link will render when someone shares it. Between them they cover the checking half of the job, which is the half where mistakes are expensive.
- The workflow itself is planned, not enabled
- Meta length checking works today on its own page
- Open Graph preview works today on its own page
- No account or credits are involved while it is unavailable
What the workflow is designed to produce
The design is a packaging pass rather than a writing pass. It takes a source that already exists, a published page, a draft, or product copy, and returns the metadata layer around it: several title options rather than one, meta descriptions written to sit inside the visible length, and Open Graph copy that reads well as a social card rather than as a search result.
Several options per field is deliberate. Metadata is the one place where a small wording change moves click-through noticeably, and a single suggestion gives an editor nothing to compare against. The intended output is a short menu you choose from, not a decision made for you.
- Title options, not one title
- Meta descriptions sized for the visible length
- Open Graph copy written for a social card
- Output meant to be edited, not pasted blindly
How it will work when it ships
When this workflow is enabled it will follow the same path as the live AI workflows on this site, which means it will not run in your browser. The text you submit is sent to a server endpoint, forwarded to a model provider, and the run is recorded against your account. Signing in and having AI credits will be required, and rate limits apply.
That is a real difference from most tools here, where files and text never leave the device. It is worth knowing in advance: unpublished copy submitted to an AI workflow is copy you have shared with a third-party provider, so treat embargoed or confidential drafts accordingly.
- Server-side, not local, once it ships
- Sign-in and AI credits will be required
- Submitted text reaches a model provider
- Runs are recorded against the account that made them