A quiet month arrives and the instinct is to do something about it. Rewrite the homepage, move the button, add a page, change the headline that has been sitting there since launch.

Sometimes that is the right call. Often the more useful thing is to leave the website alone for long enough to find out what it was already doing.

A change takes time to show

Search results do not update the moment you press save. Asked how long an improvement takes to show, Google gives a range wide enough to be worth reading in full: “some changes can take effect in a few days, but it could take several months for our systems to learn and confirm that the site as a whole is now producing helpful, reliable, people-first content in the long term.”

Google gives similar advice about reading the numbers, in a narrower case. Every so often it makes a broad change to how search works, which it calls a core update, and afterwards its guidance is “We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console.” Search Console is Google’s own free report on how a website appears in search results, and the habit being described is a general one, which is to let something finish before deciding what it did.

That is where frequent editing becomes awkward. Watching a page means watching it over a period, and each edit starts a new one. Where those periods overlap, separating the effect of one change from the next takes deliberate work. It can be done. It is simply harder than leaving the page alone and reading a single clean stretch.

Be careful with a change made on a rumor

Advice about websites travels quickly and arrives without its reasoning. Somebody hears that a particular element is bad, removes it, and never finds out whether it mattered.

Google’s own wording on this is blunt, and SEO in it means the work of making a website easier to find in search: “Avoid doing “quick fix” changes (like removing some page element because you heard it was bad for SEO).”

Before making a change of that kind, ask where the advice came from and what it was based on. If the answer is that somebody heard it somewhere, that is a reason to wait rather than a reason to act.

Take extra care with a page that is already working

There is a version of this that costs people real money, which is improving a page that was doing its job.

Google’s advice here appears in its guidance for a page that has slipped a little after a core update: “There’s no need to take drastic action (in fact, we recommend avoiding making changes to content that’s already performing well).” The situation it describes is a narrow one. The reasoning behind it is not.

A page bringing in inquiries has already shown you something real. Editing it trades a result you can see for one nobody has seen yet, and that trade deserves a reason you can say out loud rather than a feeling that the page looks dated.

Leaving the content alone is not the same as leaving the website alone

Software still needs updating. Backups still need taking, and recovery still needs testing rather than assuming. The certificate that keeps your address on https still expires, forms still break quietly, and somebody still has to notice when they do. None of that is a change to your website in the sense meant here, and none of it can safely wait for a quiet quarter. All of it has a price attached, which what it costs to keep a website running sets out.

What is being left alone is the content and the layout, while the maintenance underneath carries on exactly as before.

When leaving it alone is the wrong answer

Restraint is a default rather than a rule, and several things override it.

Anything factually wrong goes now. A price that has changed, a service you no longer offer, a member of staff who has left, an address or a phone number that no longer reaches you. Those are corrections rather than experiments, and nothing is learned by waiting.

Anything broken goes now too. A form that does not deliver, a page that does not load, a link that leads nowhere.

Anything that stops somebody using the website goes now, which includes the accessibility problems that keep a visitor from reading or navigating it at all.

A website that is failing at its job needs work rather than patience, so restraint is not the answer there either, and rebuild or optimize is where that decision starts. Waiting only helps when there is something worth the wait.

The question that separates the two

When you feel like changing something, ask what you expect to be different afterwards, and how you would know. How to tell if your website is actually working covers what would have to be in place for you to answer the second half.

If you can answer both, you have a change you will be able to judge afterwards, which is not the same as knowing it is the right one. The cost and the risk are still yours to weigh.

If the honest answer is that you are not sure, and the real reason is that the month was quiet and doing nothing feels like giving up, that is the moment to leave the page alone and let it go on doing whatever it has been doing.

If you would like a second opinion on whether a page is worth changing yet, e-mail sales@allydrez.com.