Asking for the homepage without an address
A request that names a section by its heading is ambiguous when you have several language versions and campaign pages. Require the full address every time.
Website update request form: the page, the exact wording and the approver
A website update request is the intake for changes to pages that already exist, such as new copy, a replaced image, a price or a removed page. It should identify the page by its full address, quote the current text, and supply the exact replacement along with the person who approved it. Changes to prices, legal wording or policy need their own approver before a web editor touches the page.
What people search
Website update request form: 10 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Field blueprint
The page, the change and the sign-off
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Requester name | Short text | Required | Names the person who asked for the change, so the editor knows who to ask about it. |
Work email | Required | Lets the web editor reply about wording or timing. | |
Page addressThe full web address, starting with https | Short text | Required | Identifies the exact page. Several pages can share a heading, so the address is the only reliable reference. |
Type of changeWording or copyImage or videoPrice or offerRemove contentBroken link or errorOther | Dropdown | Required | Tells the web editor what kind of change this is and which approver to check. |
Current text | Long text | Optional | Quotes what the page says now, so the editor can find the right sentence quickly. |
Replacement textPaste the final wording. Do not describe the change in general terms. | Long text | Required | Gives the exact words to publish. The form cannot accept attachments, so the final copy has to be pasted here. |
Image or document locationA link to the approved file | Short text | Optional | Links to the approved image or document, stored where the editor can open it. |
Approver name | Short text | Required | Names the person who approves the wording or the price. For legal text, that is counsel. |
Approval confirmedYes, approved in writingNot yet | Single choice | Required | Records whether the approver has agreed before the change is made. The form does not confirm approval itself. |
Go-live target date | Date | Optional | Sets a target for the change. Leave blank if it can go live when it is ready. |
Time-sensitive?Yes, it must be live by the target dateNo, any time is fine | Single choice | Required | Tells the editor whether to prioritize the change or make it on the next pass. |
Sensitive content checkIf the change touches pricing, legal terms or staff details, route it to that owner first. | Section header | Separates routine copy edits from changes that need counsel, finance or HR review. | |
Notes for the editorDo not include unpublished financial, legal or personnel details. | Long text | Optional | Captures context such as the campaign the page supports. |
Try it
Check that the request reads well from the editor's side
After a response arrives
From submission to a live change
Watch the grid, since the notice comes late
Each request reaches the form's creator only after the hourly processing job has run in production. The web editor should watch the grid rather than wait for that notice.
Check the approval before editing
Compare the approver's written yes with the copy you are about to publish. If the pasted text differs from the approved draft, send it back to the requester instead of correcting it yourself.
Export the grid for a monthly content review
Export CSV from the submissions grid to see which pages change most often and which requests are still open.
Assign each change to a named owner
When Customer Care cases are on in the form settings, each request becomes a case with the priority, tags and assignees you set. Assign copy changes to the web editor, and price or legal changes to the owner of that decision.
Mistakes to avoid
Website requests that cause rework
Publishing wording that was approved only in chat
A yes given in a chat message is hard to show later. Keep the written approval with the request, in the same place the editor records the change.
Pasting a whole page to change one word
Ask for the exact sentence that changes. A full-page paste makes it hard to see what was edited, and it invites unrelated edits.
Sending price or legal text through a copy request
Prices, legal terms and policy text need their own approver. Route them to the finance or counsel owner rather than to general web edits.
Frequently asked questions
What is a website update request form?
It is the intake for changes to existing pages, such as copy edits, a replaced image, a removed page or a broken link. It records the page, the exact change and the approver before a web editor makes the edit.
Is there a template for a website update request?
You can copy this field list. The parts that do the most work are the page address, the current text, the replacement text and the approver. The same fields work for a website change request form template, so one list can serve both names.
Should a new page use this form?
No. A new page needs decisions about navigation, its title and who maintains it after launch. Use a separate request for that, and keep this form for changes to what already exists.
Does the form publish the change?
No. The form collects the request and notifies the creator after a scheduled job processes it. A web editor still makes the change on the site.
Browse by category
More requests in IT & Technical Support
Requests
Hardware Request
Requests
Software Access Request
Requests
VPN/Remote Access Request
Checklists
Asset Checkout/Return
Reports
Internal Bug Report
Surveys
IT Service Desk Feedback
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
