How do I request one Webflow change on many pages?
Name every Webflow page in one written request, say if they share a component, and rank the work against the 10 hours.
Send one written request that lists every page, the change, and what must stay the same. Say if those pages share one component or each has its own copy. The plan is $999 per month with 10 hours, and an hour is time spent, not one hour per page. Extra time is $75 per hour and starts only after you approve a written estimate.
List every page in one written request
A change that should happen in more than one place is still one request. Send a single note that names every page, the exact change, and what must stay the same. Five separate threads for the same sentence can be read as five different jobs, and the hours can be spent twice.
Example: the phone number in the footer is wrong. The pages are the homepage, /services, /pricing, /contact, and the blog template. One note lists those five, pastes the new number once, and says the rest of the footer stays. Do not write 'update the footer everywhere' with no list. A page you forgot to name is a page that stays wrong.
Communication is asynchronous and written only. There are no calls or meetings where you can point at a sitemap. The list in the thread is the list that gets done.
Say if the pages share one component
Some repeated blocks are one component used on many pages. Some are separate copies that only look alike. The request should say which one you have, because the work is not the same.
If the footer is a component, name it. The component guide explains that an edit to the main component can update every instance, and that an unlinked instance is its own copy. If you already unlinked the footer on /contact, say so. That page will not follow a main component edit.
If each page was built on its own, list the URLs and say they are separate copies. Ask for the same change on each named page. Do not assume a matching heading means the pages share a class or a component.
Example of a component note: 'Change the footer phone on the main Footer component. Also check /contact, where the footer was unlinked. Do not restyle the links.'
Example of copies: 'These are separate sections, not one component: the hero on the homepage, /services, and /pricing. Replace the label Book a call with Email us. Leave the button colors as they are.'
Hours follow the time, not the page count
The plan is one price for every existing Webflow site: $999 per month, including 10 hours. An hour is time spent on the written request. It is not one hour per page, and it is not free because the sentence is the same.
A shared component can be a short edit. Ten separate copies, with a check on a phone for each, can take longer. If the list would pass the hours that are left, additional work is $75 per hour. Before work exceeds the included hours, I share a written estimate and ask for your written approval. Additional work starts only after you approve it.
You can also narrow the list so it fits. Name the pages that must change in this period, and name the pages that can wait. A shorter list is a written change to the request. It does not pull unused hours into the next period. Unused hours expire at the end of the billing period and do not carry over.
Urgent requests are reviewed and picked up within 24 hours. Other requests are reviewed and picked up within 48 hours. Those windows are pickup times. They are not a promise that every page in a long list will be live when the window ends.
Rank the batch against the rest of the month
A many-page change still sits in one queue. Put it in the order you want relative to the other requests. The priority guide is how to rank a period against the 10 hours. This page is only the case where one change has many URLs.
If the footer phone is wrong on the live site, put that list first and let a new testimonial wait. If the change is a wording preference and a form is broken, say the form comes first. Two notes that both say 'do this first' do not create a second set of hours.
A new website or a full redesign is a separate project. A request to rebuild every page in a new layout is that project, not a many-page sentence change. The brief guide is the fuller note for one update. Use it when you are describing the outcome, and use this page when the outcome repeats.
Keep one list in the thread
Send the pages, the final text or file, and what done looks like, including a phone if the repeated block wraps or stacks. If you later need to drop a URL, say so in the same thread and name the line to ignore. A second thread that lists three of the five pages can leave the old five-page line active.
Your Webflow subscription and hosting stay in your own account. The many-page note does not move the site.
The Webflow retainer is the monthly plan these requests use. The retainer guide explains the ongoing work the included hours cover. Use this page when one change belongs on more than one page.
Questions & answers
Does each page in the list cost one hour?
No. An hour is time spent on the request. A shared component and ten separate copies do not take the same time, so the page count is not a price list.
Should I open one thread per page so each change is easy to find?
No. Keep one thread for the shared change. A second thread that repeats three of the URLs can leave the old list active beside it.
What if only the blog template should change?
Name the template and say that existing posts should follow it. If one post was unlinked or built on its own, name that item too, or it will not follow the template edit.
Does saying publish also approve extra hours for the long list?
No. Additional work is $75 per hour and starts only after you approve a written estimate. A publish reply is about the result you reviewed, not a yes for time past the 10 hours.
Need a hand with your Webflow site?
View membership