$100 Website Offer

Get your personal website + domain for just $100.

Limited Time Offer!

Claim Your Website Now

Eight Website Goals Worth Rereading Every Single Month

Every website begins with a plan, and most plans are written in a hopeful mood. A few months later the site has a new menu, a redesigned header and three pages nobody remembers asking for. The plan, meanwhile, sits in a folder, still insisting on its original priorities. That mismatch is the quiet reason many web projects feel scattered.

The cure is gentle: once a month, reread your website goals and ask of each one whether it still fits. Keep it, adjust it, or drop it. Below are eight goals that tend to appear on almost every website to-do list, each paired with a small story and the single question worth asking at the monthly reread.

Why a list of eight

Eight is not a magic number; it is simply how many recurring goals show up when you listen to people talk about their sites. Few teams hold all eight at once, and that is fine. Think of the list as a menu. At your next reread, pick the ones that apply, ignore the rest, and add any goal of your own that the menu missed. The structure below is the same for each item: a short story, then the question to ask.

1. “Get the homepage right”

A freelance designer once told a story about a homepage rewrite that took an entire spring. By the time it launched, the shop had pivoted to a different product line, and the careful new headline described a business that no longer existed. The goal had been sensible in March and obsolete by June.

Monthly question: does the homepage goal still describe what visitors come here to do today? If the business has moved, rewrite the goal before touching a pixel.

2. “Make sure every essential page exists”

Many owners keep a mental checklist of the pages a site needs: services, about, contact, pricing, and a few more. This goal quietly ages as the business grows. A structural walkthrough of which pages a company site cannot do without makes a handy companion for the reread, because it gives you a neutral checklist to hold your own list against.

Monthly question: which page is missing now that was not needed before, and which page has become dead weight?

3. “Plan before we build”

Planning goals are the ones people feel proudest of and revisit least. A team might have promised itself to draft requirements before development, then drifted into building on instinct once deadlines pressed. One step-by-step article about sketching a company website ahead of the build can remind you what that promise looked like when it was fresh.

Monthly question: are we still planning first, or has the habit slipped? If it slipped, was that a mistake or a sensible change?

4. “Publish something every week”

Content calendars are the classic casualty. A small publisher wrote a weekly goal in January, kept it through spring, and by autumn was posting in irregular bursts while feeling guilty about it. The goal was never reread, so it was never renegotiated.

A related point: a goal that keeps failing is usually telling you something. Either the target is too large for the time available, or the work is not as important as it seemed. Both are valuable discoveries, and the monthly reread is where they come to light.

Monthly question: is this rhythm still realistic for the people doing the work? An honest “every other week” beats a failing weekly promise.

5. “Improve search visibility”

This goal is vague enough to survive for years without meaning anything. Reread it each month and press it for detail: which pages, for which audience, in what way? A goal about search is only useful if it can be turned into a specific thing to do before the next reread.

One useful trick is to write the goal as a sentence beginning with a verb and ending with a place on the site. “Rewrite the service descriptions on the main services page” can be started tomorrow. “Improve search visibility” cannot, and the difference is felt at the reread, when you try to decide whether the goal is progressing.

Monthly question: can I name one concrete step toward this goal that I can finish in the next few weeks? If not, adjust the wording until I can.

6. “Speed up the site”

Speed goals tend to arrive after a frustrating afternoon and fade once the frustration does. Then a new plugin, a heavier image library or a tracking script arrives and the site slows again without anyone deciding it should.

Monthly question: is page speed still a priority, or has something more urgent replaced it? Either answer is fine, so long as it is chosen.

7. “Keep the platform up to date”

Maintenance goals are the least glamorous and the most easily forgotten. A site owner may write “keep everything updated” in the first month, then discover half a year later that a theme and several extensions have been waiting patiently. The monthly reread is a gentle nudge toward the routine upkeep that no one wants to do.

It also helps to attach a date to the upkeep goal. Even a rough note such as “last checked early in the month” turns a vague intention into a fact that can be reread. If the date is far in the past, the goal has already told you what it needs.

Monthly question: who is actually responsible for updates, and when did they last happen?

8. “Learn the skills to run this ourselves”

The final goal on many lists is about people rather than pages: learning enough to manage the site without constant outside help. Skills goals drift particularly easily because they have no deadline. Reread yours monthly and decide whether the skill you wrote down is still the one you need. Learners in other industries face the same choice; the site for the aviation-focused online learning service AirCrewU, for instance, lays out its offering by subject area and describes itself as independent. It is a reminder that good learning menus help you choose, and a monthly reread helps you choose again.

Monthly question: is the skill still relevant to where the site is heading, and have I actually practised it lately?

How to run the reread without it becoming a chore

Keep it short. Set a timer for thirty minutes, put the goals on one page, and read them in order. For each, ask its monthly question, then mark it keep, adjust or drop. Write one line at the bottom about what changed on the site since last time: a redesign, a new service, a departing colleague. Those lines accumulate into a surprisingly useful history of why decisions were made.

If eight goals feels like too many, trim the list. Most small sites do well with four or five live goals, and the rest can sit out until they earn a place.

A story to end on

A small agency kept a goals page for one client site and reread it every month for a year. Midway through, the client’s priorities moved from attracting visitors to converting a smaller group of regulars. Because the goals were reread monthly, the shift appeared in the notes early, and the redesign that followed was smaller and cheaper than the one the agency had originally planned. Nothing dramatic happened; the plan simply stayed truthful.

That is what a monthly reread buys a website: not perfection, but a plan that keeps its word with reality. Pick a date, open the list, and read it as though a stranger wrote it. Whatever no longer fits has had a good run and can go.

Related Posts

Near Misses as a Career Skill for Web Developers

Why handling a caught mistake well is a learnable skill for CMS and web developers, and how to show it in a portfolio or interview.

Read More

Five Website Clean-Up Myths That Keep Your CMS Cluttered

Five comfortable beliefs about website housekeeping, and the simpler habit that replaces them: trim drafts, plugins and media files as you work.

Read More

Website Teardown Checklist: Audit a Finished Business Site First

A practical five-part checklist for taking apart a finished business website, structure, content, navigation and technical clues, before you plan your own CMS build.

Read More

Eight Plain-Word Fixes for Clearer Website Copy and CMS Labels

Menus, buttons, error messages and admin fields often use insider words. Eight practical fixes, each with a before and after, to make your site easier to read.

Read More

Page Cap, Plugin Cap or Palette Cap: Which Site Limit Fits?

A friendly comparison of three self-imposed limits for CMS builds, covering pages, plugins and palettes, with when each one helps and where it hurts.

Read More

Why Web Projects Slip: Diagnosing the Unchosen Trade-Off

Late, over budget and still rough? A diagnosis-first look at web projects that never decided whether speed, cost or quality would give, plus the written fix.

Read More
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x