Update the Pay and Open Roles on a Live Hiring Page with MCP
Published
On this page
A hiring page rarely stays the same for long. You raise the rate to compete with the coffee shop down the street, or the counter is covered and now you need help in the back. You do not have to rebuild the page. Ask the same assistant that built it.
This guide follows on from Build a Hiring Page and Job Application Form with MCP. Using the bakery page from that guide, it walks through two common updates: raising the pay from $17 to $18 an hour and adding a second role, baker's assistant, by asking ChatGPT or Claude in chat.
Two things to know before you edit
The pay shows up in more than one place. A typical hiring page mentions the rate in the line above the headline, in the intro, in the job details, and again next to the application form. Fix only the job details and the page now says $17 at the top and $18 further down. Applicants notice, and the one who quotes the lower number in the interview is not wrong. So ask for every mention of the pay to change, and check the preview yourself.
The page and the form go live at different times.
- Page edits go into a draft. The live page does not change until you ask to publish
- Changes to the application form — new questions, new choices — show up on the live page right away
So the order matters: update the page draft, check it, publish the page, and then change the form. Do it the other way around and, for a while, the live page advertises counter staff only while the form already offers a baker's assistant job nobody has described.
Before you start
- ChatGPT or Claude, still connected to FormEdge from when you built the page
- A note of what is changing — the new rate, the role you are adding or dropping and what it involves, and when the new rate starts
Editing needs the create and edit permission; publishing needs the publish permission. If you left publishing out when you connected, publish from the dashboard at the end or add the permission.
Walkthrough
Ask for all the changes at once — and hold off on publishing
Put both changes in one request. Replace the parts in parentheses with your own page and details.
Prompt to paste
Update my FormEdge hiring page "(e.g. Hearth & Grain Bakery — now hiring)". - The pay goes from $17 to $18 an hour. Change every mention of the pay on the page, including the line above the headline, the intro, the job details and the text next to the application form. Keep "plus tips" wherever it appears. - We are also hiring a baker's assistant (early-morning prep, shaping dough, cleanup). Update the headline, the intro, the position and duties in the job details, and the text next to the form so they cover both roles. - Update the page title and the page description (the text shown in search results and link previews) to match. - Do not change any other numbers, such as the shift times or the weekly hours. - Do not change the application form yet. Do not publish. Tell me every place you changed and give me a preview link.
The AI updates the page draft, lists what it changed, and sends a preview link. Before editing it may save the current page as a version, so there is something to go back to (it asks first only if the version history is already full).
Check the preview for anything left behind
Open the preview on a phone as well as a desktop and look for:
- The old rate anywhere on the page. Use your browser's find-in-page and search for "17" — it catches "$17", "$17.00" and "17/hr"
- "plus tips" still attached to the pay everywhere it was before
- Other numbers that should not have moved — the shift times and the weekly hours
- Both roles named the same way in the headline, the job details and the text next to the form
- The page title in the browser tab, which also shows in search results and link previews
- The page description in the AI's list of changes. It shows in search results and link previews but not on the page itself, so the preview cannot show it
Point the AI at anything that is off.
Prompt to paste
The text above the application form still says "Apply for counter staff". Change it to "Apply for counter staff or baker's assistant".
None of this is live yet, so take as many rounds as you need.
Publish the page, then update the form
When the preview is right, publish and then change the form in the same request. If the new rate does not start until later, stop here and send this on the day it starts. The draft stays out of sight, and the live page keeps the current rate until then.
Prompt to paste
Looks right. Publish the page. Once it is published, add a required question to the application form, "Which position are you applying for?", with the choices "Counter staff", "Baker's assistant" and "Either". Put it right after the email field.
If the form already asks which position, ask for the choices to be changed instead.
Prompt to paste
Change the choices for "Which position are you applying for?" to "Counter staff", "Baker's assistant" and "Either".
When you stop hiring for a role, remember to take it out of the form as well. A choice left on the form after the role is gone keeps bringing in applications for a job that no longer exists.
Check the live page
Open the live page and confirm:
- The pay and the roles match what you approved in the preview
- The form asks which position, and the choices match the roles on the page
Then apply once yourself and check that the position you picked shows on the application in the dashboard (and in the notification email, if you set it to include the application).
Common snags
| Snag | What to do |
|---|---|
| The old rate is still somewhere on the page | Tell the AI where. Searching the preview for the old number first lets you list every spot in one go |
| Other numbers changed too | Name the numbers to put back. Adding "do not change any other numbers" to the first request prevents it |
| "plus tips" disappeared from one mention of the pay | Ask for it to be added back there. Naming what to keep in the first request prevents it |
| The live page has not changed | Page edits stay in the draft until you ask to publish. Check the preview, then ask to publish |
| The form changed before the page did | Form changes go live right away. Publish the page now, or ask for the new question to be removed until you do (if you changed the choices on a question that was already there, ask for the old choices back) |
| The AI says it cannot publish | The connection does not have the publish permission. Publish from the dashboard, or add the permission to the connection |
After the update
Applications you already have are not affected. If someone applied at the old rate, mention the new one when you call them back.
Every publish keeps a version of the page, so you can ask the AI to "restore the version that was published before and publish it again". Only a limited number of versions are kept; the oldest ones drop off first.
To close the posting when the job is filled, see When the position is filled in the first guide.
FAQ
- Can I make these changes in the dashboard instead?
- Yes. Edit the page text in the page editor and the role choices in the form editor. Page edits made in the dashboard also stay out of the live page until you publish again.
- What happens to applications I already received?
- Nothing. Changing the form's choices does not rewrite answers that were already submitted.
- Can I undo the update?
- Yes. Each time you publish, that version of the page is kept. Ask the AI to “restore the version that was published before and publish it again”. The form has no version history, so ask for its choices to be changed back.
- Do I have to use the same AI I built the page with?
- No. ChatGPT and Claude can both update the page, as long as they are connected to the same FormEdge workspace.
Related reading
Put up a hiring page today
Start on the free plan — build it, publish it, and keep it current from chat.
Get started freeNo credit card required · Free plan available