The most common question a business owner asks after signing up for a managed website has nothing to do with design. It is some version of this: “Is that included, or is it going to cost me?” Usually it comes right before they ask for something small, like a new phone number on the contact page, and you can hear the hesitation in how they say it. Years of being nickel-and-dimed by hourly web work teaches people to brace before asking.
That hesitation is expensive. It is the reason so many small business websites still list last year’s hours, a staff member who left in the spring, and a service the company stopped offering entirely. Nobody wanted to open a ticket and find out what it cost.
So it is worth being direct about where the line actually sits. A managed website service covers ongoing website updates, which is a broad category, but it is not a blank check for anything that touches a browser. Knowing the difference in advance means you stop guessing, stop self-censoring your requests, and start treating your website like the working asset it is supposed to be.
Routine Updates: Changing What Already Exists
The clearest way to think about a routine update is whether the request changes something the site already does, or asks the site to do something new.
Changing what exists is the everyday work of a managed website. Text edits on a live page. Swapping a photo for a better one. Updating hours, phone numbers, addresses, and the details in your footer. Adding a testimonial to the section where testimonials already live. Adding a new team member bio that follows the same pattern as the other five. Dropping a new service into your service list. Removing the holiday banner in January that somebody forgot about. Publishing a blog post you wrote, formatted the way your other posts are formatted, with a featured image attached.
Fixes belong here too. Broken links, typos, a form that suddenly stopped sending notifications, a section that looks wrong on an iPhone, spacing that went strange after a plugin update. If something on your site used to work and now does not, that is a routine request, and it should be treated with more urgency than most.
The maintenance layer is included in the same way, and it mostly happens without anyone asking. WordPress core, theme, and plugin updates run continuously in the background, backups run on a schedule, and the site gets watched for the kind of quiet breakage that nobody notices until a customer mentions it. The WordPress documentation on updates is clear that keeping a site current is the baseline for security and stability, and that is exactly why it belongs inside the subscription rather than on an invoice. Updates that only happen when somebody remembers to pay for them do not happen.
Adding a simple page counts as routine as well, as long as it uses a template the site already has and you supply the core content. A new service page built on the same layout as your other four service pages, using copy you sent over, is ordinary work. The service exists to be used this way. Unlimited update requests, handled one at a time, with most routine items turning around in a business day or two and larger ones taking closer to a week, only makes sense as a promise if the boundaries around it are honest.
The Gray Zone That Needs a Conversation First
Between “obviously included” and “obviously a separate project” sits a category that deserves its own treatment, because this is where most of the friction in managed website relationships actually happens.
Some requests are included but carry enough business consequence that they should not be executed silently. Changing your pricing page. Rewriting a guarantee. Editing policy language, warranty terms, or any claim that touches medical, financial, legal, or safety territory. Restructuring your main navigation. Rewriting the homepage hero. These are all normal update work, and a managed service should handle them, but the right first move is a short exchange confirming intent rather than a same-day publish.
The reason is simple. A typo fix has one possible outcome. A pricing change has several, and at least two of them involve a phone call you did not want to have.
Anything touching how leads reach you sits in this zone too. Form fields, notification routing, where a quote request lands, whether the confirmation email fires, how a booking link behaves. The work itself is small. The failure mode is not, because a form that silently stops delivering can cost weeks of leads before anyone notices. That deserves a deliberate test after the change, not a quick save and a thumbs up.
Search settings belong in the same bucket. Editing page titles, meta descriptions, URL slugs, redirects, and canonical tags is genuinely routine on a technical level, but the effects show up in Google rather than on your screen. Changing a URL without a proper redirect is one of the more reliable ways to lose rankings you already earned, which is why Google’s own guidance on redirects is so specific about implementation. A managed service should make these edits for you. It should also tell you what it is going to do before it does it.
What Genuinely Needs Separate Scope
Then there is work that is real, valuable, often worth doing, and simply not the same category of thing as a website update.
A full redesign is the clearest example. Rebuilding your site from the ground up is a project with its own discovery, direction, timeline, and approval cycle. It is not a change request that happens to be large. The same is true of a major migration. Moving a site to a new domain, restructuring an entire URL architecture, or consolidating two sites into one is involved enough that Google publishes a dedicated guide for site moves with URL changes, complete with staging recommendations and monitoring steps. That guide exists because migrations go wrong in ways that are expensive and slow to recover from. It deserves planning, not a queue slot.
New integrations fall outside routine scope for a similar reason. Connecting your site to a CRM, a scheduling platform, an inventory system, or a proprietary tool your industry uses is not a website edit. It is a systems project with authentication, data mapping, error handling, and a testing phase, and it usually involves a third party whose behavior nobody controls.
Ecommerce and payment work is its own world entirely. Standing up a store, changing a payment processor, or adding checkout to a site that never had it brings in compliance obligations that ordinary website content does not carry. Any business handling card data has responsibilities under the PCI Data Security Standard, and treating that as a routine ticket would be careless. Selling something online is a business decision with operational consequences, and it should be scoped like one.
Custom functionality is the last category. Calculators, quoting tools, client portals, dashboards, membership systems, anything that requires software to be written rather than configured. So is strategy work: positioning, brand direction, campaign planning, ongoing SEO programs, ads management, or large research and copywriting projects where you need someone to figure out what the page should say in the first place. Handing over a paragraph to publish is an update. Asking someone to write eight pages from scratch is a project.
None of this means NorthMac will not do the work. Most of it we will. It means the work gets defined, quoted, and scheduled properly instead of being absorbed into a queue built for a different kind of task, where it would quietly block every other client’s small requests for a month.
Why the Boundary Actually Helps You
It is tempting to read a scope list as a list of things you are not getting. In practice it works the other way around.
Vague scope does not produce generosity. It produces hesitation on both sides: the client who is not sure whether asking will trigger a bill, and the provider who is not sure whether saying yes to a two-week project means letting fifteen other requests sit. Clear boundaries remove the negotiation from ordinary work. You send the request. It gets done. Nobody discusses whether it counted.
That matters more than it sounds, because the small stuff is what decays fastest and costs the most. Wrong hours on a holiday weekend send customers to a locked door. A service you no longer offer generates calls you have to talk your way out of. A form that broke in a plugin update means leads landing in a void. These are the failures that actually lose revenue, and every one of them is a routine update that someone did not ask for because they were not sure it was free. Keeping your business details consistent everywhere, from your site to your Google Business Profile hours, is basic operational hygiene, and it only stays consistent when updating it is frictionless.
The honest summary is this. If the request changes information, fixes something broken, or adds content to a pattern your site already uses, send it and stop thinking about it. If it changes how your business runs online, introduces new systems, or asks for something the site has never done, expect a conversation and a real estimate first. That second category is not a trap, and it is not upselling. It is the difference between work that fits in a queue and work that needs a plan.
Website Updates, Handled
Most small businesses do not need a bigger website. They need the one they have to stay accurate, stay online, and stay current without it becoming another thing on their list.
That is what a NorthMac managed website is built to do. Your site is built, hosted, updated, secured, monitored, and supported for one monthly price, with unlimited update requests handled one at a time through a request process you can actually see. Routine work gets done without a conversation about whether it counts. Bigger work gets scoped honestly before anything billable happens.
If you are ready to stop maintaining your website yourself, start your managed website with NorthMac for $47 and see what is included.
