WP Geeks Content Update Policy

Effective date: 31 January 2026
Applies to: The unlimited content updates included in WP Geeks maintenance and management packages.
Works alongside: This policy sits alongside our Development Rates And Terms of Service. That document covers rates and billing. This one covers how content updates work. If you’ve signed a development agreement with us for a particular project, that agreement is separate from both and covers that project on its own.

1. What “Unlimited” Means

Your maintenance and management package includes unlimited content updates. Here’s exactly what that means, so there are no surprises on either side.

Unlimited means unlimited requests. There’s no cap on how many you send us — not per month, not per year. Send as many as you like.

It doesn’t mean these three things:

It doesn’t mean any one request can be any size. Each request still needs to be a content update. Section 3 explains what that is.
It doesn’t mean we work on several of your requests at once. You have one request with us at a time. Section 2 explains how that works.
It doesn’t mean development or design work is free. Building new features, designing new looks, or writing code is separate work that we quote for you.

One thing worth knowing: our Client Terms document lists services we bill by the hour, and some of those overlap with content updates. That’s on purpose. For example, “WooCommerce work” is billable development when it means building a new checkout. But changing the price on a product you already sell is a content update. What matters isn’t which document mentions something — it’s whether your request meets the four requirements in Section 3.

Think of content updates as ongoing upkeep for your website’s words and pictures. Not a replacement for hiring us to build something new.

2. How the Queue Works

Priority requests jump the queue. We add all requests to the queue in the order they’re received. If you have the Ultimate plan with priority service, your request moves to the next available priority spot in the queue so it gets started sooner. The first priority spot is #1. The next is #3, then #5, then #7, and so on. We alternate priority requests and standard ones so nobody is neglected and every job keeps moving forward.
You have one request with us at a time. This is what makes unlimited possible. Because nobody can flood the queue with fifty requests at once, everyone’s work gets done quickly — including yours.
Send your next request once the current one is finished. There’s no waiting period. As soon as we deliver, you can send another.
“Finished” means we’ve delivered it to you. Not while it’s still being checked on our end. You’ll get a clear message when your request is done.
Sent a second request while one’s still open? No problem — we’ll hold it and start it as soon as your current one is delivered. You don’t need to send it again.
We aim to finish each request within 4 to 24 working hours. How long it takes depends on how many other requests are waiting and how much work is involved. We usually work Monday to Friday, except for public holidays, and that’s how we officially count request completion hours. But don’t be surprised if you catch us working extra hours in the evenings or on weekends, because we’re always prepared to do so if it’s necessary to make sure your task is finished within three business days.

That range is a target, not a promise. A few things can stretch it:

The queues being unusually busy — both the standard queue and the priority queue for urgent requests.
Public holidays or office closures.
Waiting on you for something. If we need to ask you a question or you haven’t sent the pictures yet, the clock pauses until we hear back.
Us checking whether a request is a content update or a bigger job (see Section 5). The clock pauses during that too.

Need something faster? Just ask. We can sometimes move a request into the priority queue for an extra fee — that’s the urgent rate in our Client Terms (1.5 times the normal hourly rate). We’ll always agree it with you first.

If something’s going to take longer than expected, we’ll tell you rather than leave you guessing.

3. What Counts as a Content Update

Here’s the simple test we use: if we can make the change from the WordPress dashboard without writing code or going into your website’s files, we’ll do it. The dashboard is the screen you see when you log in to your website.

If a change needs someone to write code, or get into your website through cPanel or FTP (technical back-door tools for reaching the files your website is built from), it’s development work instead. We still do that work — it’s just quoted separately.

The four requirements below spell that rule out. You can check your own request against them before you send it.

3.1 The Four Requirements

Your request needs to tick all four boxes. If it misses one, we’ll quote it as separate work instead. We’ll always tell you first, so you can decide what you’d like to do.

Requirement 1 — You send us the words and pictures.

We put your content on your website. We don’t come up with it. If you send the final wording, the final pictures, and tell us where they go, that’s a content update. If we’d have to write the wording for you, design a graphic, choose the photos, or decide how the page should look, that’s different work.

Ask yourself: Have I given them everything to put on the page — or am I asking them to come up with it?

Requirement 2 — We can do it from the WordPress dashboard.

This is the main one. If the change can be made using the buttons and settings already on those screens, it’s a content update. If it needs code written, files edited, or a login through cPanel or FTP, it needs a quote.

Ask yourself: Could someone make this change by clicking around after logging in — or does it need a developer writing code?

Requirement 3 — It uses a page design you already have.

New pages and new blog posts are absolutely included. You just need them to use a design already used somewhere on your website.

So “add a new service page that looks like our other service pages” is a content update. “Design a brand new look for our services page” isn’t — that’s design work.

Ask yourself: Am I asking for a new page that looks like pages I already have — or for a new look to be designed?

Requirement 4 — It’s one thing at a time.

One request covers one page, one blog post, one product, one form, or one menu.

If you have five changes to that same page, put them all in the one request — that’s fine and it’s the sensible way to do it. But if you need changes across lots of different pages at once, that’s a bigger job and we’ll quote it. Splitting a big job into lots of separate requests doesn’t get around this (see Section 5).

Ask yourself: Is this one page — or is it lots of them?

3.2 Yes / No Examples

The quickest way to check is to find your situation below.

What you want	Yes — that’s a content update	No — that needs a quote
Words on a page	You send us new or changed words and tell us where they go.	You ask us to write the words for you.
Pictures	You send us the pictures and tell us where to put them.	You ask us to find, choose, or design pictures for you.
A brand new page or blog post	You send us the words and pictures, and it uses a design your website already has.	You ask us to design a new look for that page.
Products in your shop	You send us the details or pictures for a product, and it works like your other products.	You ask us to build a new kind of product page or a new checkout process.
Plugin settings	You ask us to change a setting in a plugin you already have, using the dashboard.	You ask us to write code so a plugin does something it can’t already do.
Moving things around a page	You ask us to move words, pictures, or sections around, using the tools already on that page.	You ask us to rebuild how the whole page is put together.
Colours and text size	You ask us to change a colour or text size using a setting already there.	You ask us to write code to get a look those settings don’t offer.
Menus (the links across the top of your website)	You ask us to add, remove, rename, or reorder a link.	You ask us to redesign how your whole website’s navigation works.
Contact forms	You ask us to add, rename, or remove a field on a form you already have.	You ask us to connect that form to a new email, payment, or customer system.
Google search text	You send us the wording you want showing when your page appears in Google.	You ask us to research keywords or review how your website ranks.

3.3 Examples of Things We’ll Do

Words

Add new words to a page or blog post, once you send them.
Fix a typo, or update a phone number, address, or price.
Replace old wording with new wording you give us.
Remove words or a section you no longer want.

Pictures

Add new pictures you send us.
Swap an old picture for a new one you send us.
Crop or resize a picture using WordPress’s own picture tools.

New pages and blog posts

Build a new page using a design your website already uses, once you send the words and pictures.
Publish a new blog post you’ve written.

Moving things around a page

Move a section of a page up, down, or across.
Copy a section that’s already on the page and fill it with new wording you send us.
Reorder items in a list.

Menus

Add, remove, rename, or reorder a link in your menu.

Shop products

Add a new product, once you send the details and pictures.
Update the price, stock number, or description on a product you already sell.
Put an existing product into an existing category.

Forms and plugin settings

Add, rename, or remove a field on a form you already have.
Turn a plugin setting on or off, or change a setting like the email address a form sends to.

Colours and sizes

Change a colour, text size, spacing, or button style using a setting already built in.

Links

Fix or update a link that’s broken or out of date.
Point an old web address to a new one, using the tool already set up on your website.

Testimonials, team members, and FAQs

Add a new testimonial, team member, or FAQ, using the same design as the existing ones.
Update or remove one that’s already there.

Google search text

Update the title and description that show when a page appears in Google, once you send us the wording.

Alt text

Add or fix alt text — the written description of a picture. It’s read aloud to people using screen readers, and Google uses it too.

3.4 The Short Version

A content update is words and pictures you send us, added or changed from the WordPress dashboard, using a design your website already has, one page at a time.

Not sure? Just send it. We’ll look at it and tell you which it is before we start. It costs nothing to ask.

4. What Needs a Quote Instead

Everything below misses at least one of the four requirements. We’re not refusing this work — we do it all the time. It just gets quoted and billed by the hour under our Client Terms (with the usual one-hour minimum), rather than going through the content update queue.

Some of these overlap with services listed in our Client Terms document. That’s expected, and it doesn’t change anything — what matters is whether your request meets the four requirements.

Designing a new look for a page, or a new page design — misses Requirement 3. Building a page with a design you already have is included; creating a new design isn’t.
Writing your words, designing graphics, or choosing your photos — misses Requirement 1.
Custom development — writing or editing code, custom themes, custom plugins, or connecting your website to another system through code. Misses Requirement 2.
Custom CSS — code written to get a look your settings don’t already offer. Misses Requirement 2.
Installing a new plugin or theme to add something your website can’t currently do. Misses Requirement 2.
Connecting your website to a new service — a customer database, payment provider, email marketing tool, or booking system. Misses Requirement 2.
Building a new shop from scratch, or reorganising a whole product catalogue. Misses Requirements 3 and 4.
Moving your website to new hosting, rebuilding it, or redesigning it. Misses Requirements 3 and 4.
Keyword research, SEO reviews, or strategy work — misses Requirement 1.
Building a marketing campaign across several new pages. Misses Requirements 3 and 4.
Anything needing a new plugin or theme purchase, a new licence, or us dealing with an outside company on your behalf.
Fixing a broken website — if something’s gone wrong and needs diagnosing, that usually means getting into the files or code. Misses Requirement 2. This is covered by technical support or development hours. (If you think your website’s been hacked — strange content appearing, files changed — tell us straight away. That’s handled under your security cover, not billed as troubleshooting.)
Changes across lots of pages at once — for example, “update this same detail on 200 pages.” Misses Requirement 4. Breaking it into lots of separate requests doesn’t change that (see Section 5).

Not sure which side something falls on? Send it anyway — we’ll tell you.

5. What We Need From You

To keep things moving:

Send everything with the request. Final wording, final pictures, and where it goes.
Make sure you’re allowed to use it. You’ll need the rights to any words, pictures, or logos you send us.
Be clear about what you want. If we’re unsure what you mean, we’ll ask — but the clock pauses while we wait for your answer.
One item per request (Requirement 4). Several changes to the same page? Put them all in the one request. Changes to different pages? Those are separate requests, sent one after the other.

6. When Part of a Request Needs a Quote

Sometimes a request is partly a content update and partly something bigger. When that happens:

We’ll do the content update part as normal.
We’ll quote the rest separately, under our Client Terms hourly rates. Note that the one-hour minimum applies to that part, even if it’s a short piece of work.
We’ll tell you which is which before we start, or as soon as we spot it. No surprises.

7. Fair Use

Content updates aren’t capped by a stopwatch, so we ask for fair use instead. This is what lets us offer genuinely unlimited requests rather than a limited allowance.

We don’t have a secret quota. We’re not going to penalize you for having a busy week — or month — or quarter. We look for usage patterns across weeks and months that consistently monopolize an unfairly disproportionate amount of developer time compared to others and conflict with our policy guidelines. Here are a few specific examples:

Constantly making ambiguous or incomplete requests: Submitting requests without the necessary assets (final wording, images, or placement instructions) creates significant back-and-forth communication, which pulls our focus from active development and delays completion.
Regularly requesting out-of-scope development: Repeatedly submitting requests that require custom coding or design work—rather than simple content updates via the dashboard—creates an unnecessary administrative burden, as it forces us to regularly decline the work and prepare quotes that ultimately remain uncommissioned.
Disproportionate monopolization of pooled resources: Our developers’ time is pooled and distributed among our clients on request. Even within our guidelines, a client that consistently maintains maximum request frequency with exceedingly time-consuming requests will monopolize an unfair proportion of our developers’ time, which is meant to be distributed somewhat equitably among clients.

The common thread among these behaviors is that they either waste, or monopolize an unfair amount of, our developers’ time, which should be spent serving other clients. We apply this reasonably and in good faith. If we perceive a problem, we will speak to you about it before taking any action. We certainly won’t use it as an excuse to turn down good-faith requests. If we think there’s an issue, here’s what happens:

We ask. We might ask you a question, or suggest splitting a request, before we start.
We quote. We might quote part or all of the request as separate work.
We write to you. If a long-term pattern continues after we’ve talked to you about it multiple times, we’ll issue a formal citation with a defined time period in which to adjust.
We pause the queue. If the issue remains unresolved, we may pause your content update requests until we’ve sorted out the issue. This wouldn’t affect anything else in your package — hosting, security, and backups carry on as normal.

We’d much rather have a conversation than restrict anything. Steps 3 and 4 are an absolute last resort.

8. Reasonable Requests

In contrast to the Fair Use policy, we also have a Reasonable Request policy. We’re reasonable people, and no set of rules covers every situation. We do make some allowances for requests that may technically conflict with a policy, but that we feel are reasonable and would not disrupt the normal flow of work.

Sometimes a request will technically miss one of the four requirements, but it’s clearly a fair thing to ask, it’s no real trouble for us to do, and the queue is small. When that happens, the developer reviewing your request has the authority to approve it for completion. They will notify you that the task would normally be rejected (and why), but it’s your lucky day and your task met our Reasonable Request conditions. Then they will get to work. They don’t need to send it back to you for a quote, and they don’t need to check with anyone first.

Reasonable Requests are always and can only be the voluntary decision of the task developer. You can not ask for them. Any client request for a task to be considered a Reasonable Request will be automatically rejected.

Please note: this is a judgement that is made case-by-case and depends on how busy we are. It’s us being flexible to accommodate good-faith requests when we can, but it’s not always possible. So, if we say yes to something once as a Reasonable Request, don’t expect it to happen again just because you make a similar request. There are many factors at play. This is a bonus we like to offer when we can.

10. Changes to This Policy

We may update this policy from time to time. It applies to requests sent after any update.

This policy sits alongside our Client Terms, Rates & Service Conditions rather than replacing it.

If you’ve signed a development agreement with us for a particular project, that’s a separate thing entirely. It stands on its own and covers everything to do with that project. This policy doesn’t apply to it, and doesn’t change it.

By sending us a content update request, or by carrying on with your maintenance and management package, you’re accepting this policy as it stands at the time.