The right website feature is not the fanciest thing on the proposal. It is the part that makes the next useful action easier, whether that action is booking, donating, enquiring, buying, or simply trusting you enough to get in touch.
If you are comparing design options, the practical questions are usually the same. Which pages do I actually need? Do I need ecommerce or just better enquiry flow? What should be included for mobile, accessibility, and SEO? How do I tell the difference between real functionality and decorative fluff? That is the point of a feature-first checklist: fewer adjectives, better decisions.
Good website planning is less about trends and more about usable structure. Guidance from the Google SEO Starter Guide, the W3C introduction to accessibility, and web.dev’s Core Web Vitals overview all point in the same direction: clear pages, predictable navigation, readable content, and fast, mobile-friendly delivery do more for real visitors than vague promises about a site looking “modern.”
This guide maps common website goals to the features that support them. You will see which core pages matter, what to ask for in forms, galleries, SEO, support, and ecommerce, and how to use that checklist in a call with a designer. If you want the local context around this site’s service approach, the home page, Features of Taeko Website Design page, Support page, and Blog index are useful companion reads.
Why features beat vague promises
Most design proposals sound good in the abstract. They mention custom design, clean layout, strong branding, user experience, maybe a sprinkle of SEO, and by the end everyone has nodded politely while learning almost nothing. The structure is wrong. A website is not a mood board with hosting. It is a working system for helping the right visitor do the right next thing.
A useful checklist starts with outcomes:
- Artists usually need portfolio credibility, event visibility, and an easy path to contact, bookings, or commissions.
- Charities usually need trust, clear impact messaging, donation or volunteer pathways, and simple updates for campaigns and news.
- Small businesses usually need service clarity, enquiry flow, local visibility, and sometimes a straightforward route to products or payments.
Once the goal is visible, the feature list becomes easier to judge. You stop asking, “Does this site feel impressive?” and start asking, “Does it support the workflow we actually need?” That question is less glamorous, but it has the decency to be useful.
| If your goal is… | The feature that matters most | What to ask your designer |
|---|---|---|
| Show your work and build confidence | Portfolio or gallery structure with clear project pages | How will visitors browse work by category, medium, or project type? |
| Get enquiries | Strong calls-to-action plus a reliable contact form | Where will the main enquiry action appear on mobile and desktop? |
| Run campaigns or collect donations | Clear landing pages, trust signals, and friction-light forms | What does the donation or support path look like from first click to confirmation? |
| Sell online | Product layout, checkout clarity, and payment setup | Do we need full ecommerce now, or will enquiry-led selling do the job first? |
| Publish updates without calling a developer every time | Simple editing workflow inside WordPress | Which sections can our team edit safely without changing the layout? |
Feature checklist: core pages and structure
Start with the bones of the site. Not every organisation needs dozens of pages, but almost every serious website needs a small set of pages that answer the visitor’s first questions quickly.
- Homepage: this should explain who you are, who you help, and what action matters next. If the homepage tries to say everything at once, it usually says very little.
- Services or what you do: small businesses need a plain-language explanation of services, deliverables, and who the offer is for. If you do not have a separate services page yet, that content still needs a visible home.
- Portfolio or work: artists and studios need a place to show finished work in context, not just a folder of detached images.
- About page: visitors use this to decide whether you are credible, active, and real. It should answer “why you” without turning into autobiography under duress.
- Contact page: this should offer one clear route to enquiry, with useful prompts and no scavenger hunt for the form.
- Latest news or blog: this helps keep the site current and gives you a clean place for updates, events, announcements, or case stories.
When reviewing a proposal, ask to see the page hierarchy. Not just the visual mock-up, but the actual content structure. Which pages sit in the main navigation? Which sections repeat across the site? Where will new posts, projects, events, or campaign updates live six months from now? A pretty first draft can hide a messy long-term structure.
For artists, a common mistake is putting all effort into the gallery while leaving the biography, contact path, and availability details underfed. For charities, the common mistake is the opposite: strong mission copy, weak action pages. For small businesses, it is often a homepage that gestures vaguely at expertise while the real service explanation is missing or buried. Different sectors, same structural issue.
Feature checklist: conversion and trust
Once the page structure exists, the next question is whether the site helps visitors act. Good design is not only visual. It reduces hesitation.
- Clear calls-to-action: every key page should make the next step obvious. Enquire, donate, book, view work, request a quote, join the mailing list: choose the primary action and support it consistently.
- Reliable forms: if your form is confusing, overlong, or broken on mobile, the design is failing where it matters most. The W3C forms guidance is a useful outside benchmark for labels, instructions, and error handling.
- Fast load times: a giant image carousel is not a personality trait. On slower connections it is often just delay with confidence.
- Mobile-first layout: the proposal should show how key content stacks on a phone, not only on a wide desktop screen.
- Accessibility basics: readable contrast, clear headings, obvious focus states, and descriptive links help everyone, not just compliance checklists.
Trust features are usually modest. Contact details that are easy to find. Testimonials or examples that feel specific rather than staged. Helpful headings. A form that confirms submission clearly. For a charity, it may also include trustees, impact reports, or campaign context. For a business, it may be pricing guidance, service areas, or lead times. For an artist, it may be exhibition history, media coverage, or commission information.
If a proposal spends ten minutes discussing animation and thirty seconds discussing what happens after someone taps “submit,” the priorities may need renovation.
Feature checklist: content, updates, and portfolio management
This is the section many buyers skip, then regret later. You are not only buying a launch. You are buying the day after launch, and the forty ordinary Tuesdays after that.
- Blog or news setup: can your team add updates without breaking layout or needing custom formatting every time?
- Gallery or portfolio filtering: if you have more than a handful of projects, visitors may need categories by medium, service type, project scale, or campaign.
- Reusable content sections: ask whether testimonials, calls-to-action, FAQs, and image-text blocks can be reused without rebuilding them from scratch.
- Editorial workflow: who can draft, review, and publish updates? Is there a simple process, or does every small change become a technical errand?
This is also the moment to separate website features from internal-tool needs. If your organisation eventually needs a client portal, stock system, volunteer dashboard, or booking back office, that is adjacent work, not the same scope as a marketing site. In some cases a separate AI web app generator or custom internal tool project may be the right companion piece, but it should be scoped separately from the public website so neither job gets blurred.
Ask to see the editing view, not just the public page view. A site can look clean on the front end and still be a backstage maze held together by guesswork and one brave person who remembers which block not to touch.
Feature checklist: SEO that supports real people
SEO is most useful when it behaves like good information architecture instead of a ritual. You do not need a performance of expertise. You need pages that make sense to both visitors and search engines.
- Local SEO basics: if place matters, your pages should mention the locations you serve naturally and consistently.
- Page titles and meta descriptions: ask who writes them, whether they can be edited, and how duplicates will be avoided.
- Internal linking: related pages should connect naturally so visitors are not dropped into dead ends.
- Image alt text: ask whether the content workflow includes descriptive alt text for meaningful images. The W3C alt text decision tree is a practical reference if you want the simplest version of the rule.
- Schema basics: you do not need buzzwords here. You need to know whether the site can support relevant structured data and who decides what is worth adding. Ask for examples that fit your site instead of generic markup theatre.
A good SEO question is: what part of this setup helps a human visitor understand us faster? If nobody can answer that, the tactic may be decorative rather than useful.
Feature checklist: ecommerce and enquiries
Not every site needs full ecommerce on day one. Some businesses are better served by a clean enquiry process, especially when pricing is variable, projects are custom, or stock is limited. The important thing is to choose based on workflow, not on the assumption that a checkout always makes a site feel more serious.
| If you sell… | Usually the better first move | Why |
|---|---|---|
| Standard products with clear prices and repeatable fulfilment | Full ecommerce | Visitors can buy without manual follow-up |
| Custom services, commissions, or bespoke projects | Enquiry-led flow | You need context before pricing or confirming scope |
| Small ranges, seasonal drops, or made-to-order pieces | Either can work | Choose based on how much stock, shipping, and admin you can manage |
| Donations, tickets, or campaign support | Purpose-built action pages | The path should feel trustworthy and very easy to complete |
If ecommerce is included, ask about product layout, image handling, shipping notes, payment options, cart behaviour on mobile, and checkout friction. If you are not ready for that complexity, there is nothing unserious about starting with a well-built enquiry route. The wrong feature set is more expensive than the smaller one.
Feature checklist: support and maintenance
A website is not finished because it launched. It has entered operations. That is a less romantic sentence than some agencies prefer, but it is closer to the truth.
- Backups: ask how often they happen and who is responsible for restores if something goes wrong.
- Security updates: ask whether WordPress, theme, and plugin updates are included and how post-update checks are handled.
- Content support: ask whether your team can request page edits, post uploads, or image swaps as part of ongoing support.
- Ownership and access: ask who owns logins, hosting, domains, and connected services.
- Escalation path: ask what counts as routine support and what becomes a separate project.
If you want a wider practical view of ongoing care, the site’s Support page is the obvious next stop. The important part for a proposal is that maintenance is described in tasks, not mist.
How to use this checklist in a call: 10 questions to ask your designer
1. Which pages are essential for our first launch, and which can wait? 2. Where does the main call-to-action appear on mobile and desktop? 3. What does the contact, booking, donation, or checkout journey look like from first click to completion? 4. Can we see how blog posts, news items, or portfolio entries will be added in WordPress? 5. Which parts of the site can our team edit safely without changing the layout? 6. How are accessibility basics handled in the design and build? 7. What is included for page titles, meta descriptions, image alt text, and internal links? 8. Do we need full ecommerce now, or would an enquiry-led setup serve us better first? 9. What support is included after launch for updates, backups, and content changes? 10. If we later need a portal, dashboard, booking system, or other custom tool, how would that be scoped separately?
You do not need perfect technical language to ask good questions. You only need enough clarity to keep the conversation tied to function. That alone filters out a surprising amount of hand-waving.
Common nice-to-have traps to avoid
- Over-designed homepages with weak structure: if visitors cannot work out what you do in a few seconds, the elegance is not helping.
- Animations before fundamentals: motion is optional; readable content and working forms are not.
- Full ecommerce before the business workflow is ready: checkout is only one piece. Products, stock, shipping, refunds, and admin also exist, however inconvenient that may be for the fantasy version of launch day.
- Large galleries without filtering or context: more images do not automatically create more confidence.
- SEO sold as mystery: if the explanation cannot survive plain English, keep your wallet in a defensive position.
The better priority order is usually simple: clear structure, clear action, clear editing workflow, clear support. After that, you can add refinement without building on fog.
A practical way to prioritise your build
If you are trying to make a decision this week, reduce the proposal to three columns: must-have now, useful next phase, and nice if budget allows. Put every feature into one of those columns. Portfolio structure, contact flow, mobile readability, accessible forms, and easy updates usually land in the first group. Fancy motion, extra integrations, and speculative features often belong lower down.
The best website feature set is not the biggest one. It is the one that fits your real operating system: how you publish, how visitors decide, how enquiries arrive, how campaigns run, and how your team keeps the whole thing current without dread. Start there, and the proposal becomes much easier to judge. If you want to turn that shortlist into a real brief, the Contact page is the right place to continue the conversation.