📘 This use case demonstrates rendering a proposed metadata template against the live pages, then staging it as a draft PageWorkers optimization to preview in place.
Best for: SEO and content teams using PageWorkers · Uses: crawl metadata and PageWorkers, via your AI assistant
Overview
Rewriting titles, meta descriptions, or H1s across a template usually means approving a spreadsheet of proposed values and finding out how they render once they are live. Botify MCP can render the proposed template against the live pages first, then create the change as a draft PageWorkers optimization, so it can be previewed in place before anyone publishes it.
Prerequisites
Botify MCP connected to your AI assistant, such as Claude or ChatGPT. See Connecting to the Botify MCP for setup steps.
PageWorkers enabled on the project, and the access needed to create and publish optimizations.
A completed crawl covering the pages you want to change.
Description of the problem
A metadata template that reads well in a spreadsheet can behave differently on the page. It runs long on the categories with the longest names, or it drops a qualifier the current title carries and the page ranks for. Neither is visible until the values are rendered against the real pages.
Application
Ask for the current metadata alongside a preview of the proposed template:
Pull the current title, description, and H1 for the top 5 category pages on acme-outdoors.com, then preview what the title would be with the template {{category}} — {{count}} Styles | Acme Outdoors. Show me the titles side by side first.
Why this prompt works:Asking for the current and previewed values together is what makes the comparison reviewable. A preview on its own does not show what the change replaces.
Naming the fields, rather than asking for "metadata", returns each one separately, so a template that only changes the title does not obscure the description and H1 that stay as they are.
The preview renders the template against each page, so the values reflect what the variables resolve to on that page rather than in the example.
Compare current against previewed. Check the length of the longest result, and check whether the template drops any wording the current value carries.
Ask for the pages you want to keep to be created as a draft optimization:
Leave the sleeping-bags page out and create a draft optimization with the other four.
Why this prompt works:Excluding pages at this point keeps the dataset and the review in one place, rather than creating the optimization and then editing its dataset.
The optimization is created in Botify as a draft. It is not applied to the live site until someone publishes it.
Open the optimization in PageWorkers. The preview there shows each page rendered with the change in place, which is the check to make before publishing. Publish from PageWorkers.
Follow-up prompts
"Add the remaining category pages to the same optimization." — extends the dataset once the pattern is agreed.
"Show me the previewed description and H1 for the same pages." — covers the fields the first pass left out.
"Do any of these pages rank for a term the new title drops?" — catches wording worth keeping before publishing.
Make it repeatable
Keep the preview step even for a template you have used before. The variables resolve per page, so a template that is safe on one set of categories can still run long on another.
Name optimizations so the dataset and the date are identifiable later. A draft nobody can place is a draft nobody publishes.
After the change goes live, use Checking Whether a Ranking or Traffic Shift Lines Up With a Change to read performance either side of the publish date.
Result
The proposed change reviewed against the live pages, then staged in PageWorkers as a draft, where it can be previewed in full and published by someone with the access to do it.
Read next
Related topics