Websites

For larger tasks I draw up a SOW — Statement of Work — that describes the deliverable, the responsibility, the timeline, the price, and the most important limitations. It is a practical way to avoid different expectations before the work begins.

What characterises a good business website?

A good business website makes it easy for the visitor to understand the business. It clearly explains what you offer, who it is relevant for, and how to proceed. That sounds simple, but many websites fail exactly here. They may contain nice images and general phrases, but leave the visitor with more questions than answers.

A website should therefore be assessed on more than its visual expression. Design matters, because it affects credibility, readability, and user experience. But the design must support the message. If the most important information is hidden behind animations, unclear menu items, or long blocks of text, a nice look does not help much.

The good website typically has a clear front page, clear service pages, an understandable navigation, and relevant ways to get in touch. It explains not only what the business does, but also how the collaboration works, what the customer can expect, and what sets the business apart from the alternatives.

That does not mean every website has to be large. A smaller business can often manage with a compact solution if the few pages are well developed. A larger organisation may need several entry points, audiences, and features. The scope should match the business and the tasks the website is to solve.

You have direct contact with the person who both advises on the task and is close to the technical execution. That reduces the risk of important details being lost between sales, project management, design, and development.

Who writes the text for the website?

The text is often the part of a website project that is underestimated. Many businesses assume the texts can be written quickly once the design is ready. In practice, the content is decisive for structure, SEO, and conversion. There are several ways to work:

1. The customer provides finished texts.
2. The customer provides raw material, which I structure and edit.
3. The texts are produced as a separate deliverable through interviews and research.
4. We combine existing material with new content.

The important thing is that responsibility is agreed. If a website is missing texts, images, or product information, the project cannot be finished, no matter how much technical work has been done. I can help with structure, headings, messages, calls to action, and SEO direction. For larger text production it may be relevant to agree a separate content deliverable or involve a specialised copywriter.

Generative AI can be used as help for drafts and structure, but content should not be published uncritically. A business's most important service pages should not sound like generic text that could appear on any competitor's website.

Ownership and binding

Ownership is an important point, because the market contains very different agreement models. Some solutions are bought as a project, while others are delivered as a subscription with binding, where the customer cannot necessarily take the website with them.

My basic model is that the customer owns the delivered solution, the agreed design, the content, and the business's data once the project is paid for. Third-party software, fonts, images, plugins, and services can be subject to their own licence terms, and it must be stated if they are used.

You are not forced to host with me. Managed hosting and service agreements are an option, not a condition for keeping the website.

No supplier can transfer ownership of software or material that the customer has not bought the rights to. So licences, stock photos, premium plugins, and external subscriptions should be documented.

What should you prepare?

You do not need to draw up a complete specification. The following information does, however, make it easier to get off to a good start:

• A short description of the business
• The most important services or products
• Primary audiences
• A link to the current website
• Examples of pages you like — and why
• Known features and integrations
• Who provides texts and images
• Desired time for launch
• Any budget or expected level

The budget is not only relevant for the supplier. It helps choose a realistic solution. If the wishes are larger than the budget, the task can be split into phases or narrowed down to the most important part.

After launch, the ongoing work begins

A website does not automatically stay relevant. Services change, employees move on, prices are updated, and the technology evolves. After launch the business should have a plan for:

• Updating content
• Software updates
• Backup
• Security
• Measuring traffic and enquiries
• Improving pages that do not perform
• New cases and articles
• Checking forms and integrations

That does not mean the website has to be changed every week. But the responsibility should be clear. A forgotten website gradually loses value. If you do not want to handle the operations yourself, it can be managed through hosting and service agreements.

Why work directly with a freelance digital consultant?

With me, you have direct contact with the person who both advises on the task and is close to the technical execution. That reduces the risk of important details being lost between sales, project management, design, and development.

I work across WordPress, WooCommerce, Laravel, integrations, SEO/GEO, and automation. That means the website can be assessed in the context of the business's other systems and workflows.

That does not mean I do all specialities alone. For projects that need extensive branding, advanced photo/video, legal advice, or other special areas, the relevant professionals can be involved.

The way of working best suits businesses that want direct dialogue, clear scoping, and a solution that is not tied to a closed platform or a long contract. You can read more about me and see selected cases.

A website's structure matters more than many think

The structure determines how the content is organised, and how easy it is for visitors and search engines to understand the site. If all services are gathered on one long page, it can be hard to create a clear message around each service. If, conversely, many almost identical pages are created, the site can become unmanageable and create overlap. A typical business website can, among other things, consist of:

• Front page
• About the business
• A separate page for each important service
• Cases or references
• Knowledge, news, or articles
• Contact
• Privacy policy and other necessary legal pages

It is not a fixed template. The structure should also support internal links: an article can link to the relevant service, a service page can link to a case, and a case can link to contact. That way the connection between the business's expertise and offerings becomes clearer.

The front page must explain the business quickly

The front page is not necessarily the first page all visitors see. Many arrive directly on a service page from Google or via a link. But the front page is still central, because it gathers the business's most important message. A good front page should normally:

• Explain the business's core service
• Say who the service is for
• Make it clear what the next step is
• Give access to the most important service pages
• Create credibility through experience, cases, or concrete information
• Answer the most common objections

A common problem is that the front page becomes a collection of a little about everything without clear prioritisation. Another mistake is that it is primarily about the business itself and only late explains what the customer gets out of the collaboration.

You should be able to edit ordinary content yourself

A business should normally be able to change text, images, employees, contact details, and ordinary pages without contacting a developer every time. That does not mean all parts of a website should be freely editable. Too many options can make it easy to break the design or create inconsistency. A good solution gives freedom in the right places and protects the overall structure. At handover we can go through:

• Editing pages
• Replacing images
• Creating news or articles
• Form messages
• Users and access
• Updates and maintenance
• Backup and security

What is included in a website?

The concrete content depends on the quote. The table can be used as a general explanation, but it is not a fixed package — the individual points are agreed for the specific project.

Website or webshop?

A website typically presents the business, services, and information and leads the visitor towards contact, booking, or an enquiry. A webshop makes it possible to choose products, pay, and complete a purchase online. The technical and administrative complexity is often greater with webshops, because payment, shipping, stock, products, VAT, order handling, and customer emails all have to work together.

Design should support content and credibility

A professional design does not have to be spectacular. It should first and foremost be consistent, readable, and appropriate to the business. Colours, typography, images, spacing, and components must fit together, so the site feels well made. The design should also take practical matters into account:

• The text must be easy to read on mobile and computer
• Buttons and forms must be easy to use
• Contrasts must be clear
• The navigation must be understandable
• The site must not depend on unnecessary animations
• Visual elements must have a purpose

There is a difference between a lawyer, a local tradesperson, an association, and a creative business. The visual expression should therefore be chosen based on the business's identity and audience — not on what is popular on design blogs.

Websites and SEO are connected from the start

SEO should not first be considered after launch. The website's structure, URLs, headings, internal links, content, and technical quality affect the ability to be found. A good SEO foundation includes, among other things:

• Logical and readable URLs
• One clear main heading per page
• Descriptive page titles and meta descriptions
• Content that matches the user's search intent
• Fast and mobile-friendly rendering
• Correct indexing
• Sitemap and necessary technical settings
• Internal links between relevant pages
• Images in appropriate sizes with meaningful descriptions
• The option to expand the site with new content

It is important to be realistic. A technically correct website does not guarantee top rankings. Competition, the domain's history, the business's reputation, backlinks, and the quality of the content also play a role. The website should therefore make it possible to continue working with SEO — it should not be built so that each new sub-page requires a developer.

GEO and visibility in AI services

More people search for information through AI services and AI-based search results. That does not change the need for a good website. On the contrary, AI systems also require clear and trustworthy sources if they are to understand the business correctly. A website that should be easy to understand for both search engines and AI systems should, among other things:

• Describe services concretely
• State the business, person, and geographical area clearly
• Have a logical structure and clear headings
• Contain original information, experiences, and cases
• Answer relevant questions directly
• Avoid contradictory or outdated information
• Connect knowledge, cases, and services with internal links

GEO is not a guarantee that the business will be mentioned in an AI answer. But clear, well-documented, and original content increases the likelihood that the business can be understood and used as a source. I have written more about the difference between GEO and SEO if you want to dig deeper.

Mobile friendliness is not an extra feature

Many visitors come from a phone. So the website should not only be able to be shown on mobile; it should be pleasant to use on mobile. That means, among other things, that:

• The text is not too small
• Buttons can be tapped without problems
• The menu is simple
• Forms are not unnecessarily long
• Images and components adapt to the screen
• Important ways to get in touch are easy to find
• The site does not become heavy and slow on mobile networks

The mobile version should not be treated as a scaled-down desktop page. Some elements should be placed differently, and the content often has to be prioritised more sharply.

Speed and technology

A slow website can frustrate visitors and make it harder to achieve good results. Speed is affected by hosting, images, code, plugins, third-party scripts, fonts, and many other factors. I build with a focus on avoiding unnecessary complexity — every significant element should have a function.

A plugin can be a good solution if it is well documented, maintained, and fits the need. Custom code can be the right solution if the standard tools create unnecessary complexity. The choice should not be based on an ideological rule that everything must be custom-built or everything must be standard.

A website must be built for a specific audience

A common mistake is trying to write to everyone. The result is often a general message that no one feels directly addressed by. Before we build the site, we should therefore agree on who is most important. It can be local private customers, businesses within a particular industry, associations, partners, or candidates for open positions. When the audience is clear, it becomes easier to decide:

• Which questions the site should answer
• Which language should be used
• Which cases and examples are relevant
• Which objections the site should handle
• Which action is most important
• How much professional or technical explanation is needed

A craft business's customers, for example, often need to see areas of work, geographical area, images of previous jobs, and a simple way to get a quote. A consultancy may have a greater need to explain method, experience, specialities, and way of working. An association may first and foremost need to make information, membership, and events easy to find. So the site should not be built from a standard package alone.

New website or redesign?

A redesign is not always necessary. If the problem is only individual texts, images, or technical errors, a smaller task can be more sensible. A redesign typically makes sense when:

• The structure no longer fits the business
• Important services are hard to find
• The site does not work properly on mobile
• The design affects credibility negatively
• The system is hard to maintain
• The content has been built on top of itself without direction
• The technology limits new features
• There is a need for a new SEO structure

Before a redesign, existing data should be examined if it is available. Which pages get traffic? Which pages have backlinks? A new site should not uncritically remove valuable content or change all URLs. When URLs change, redirects must be planned, so visitors and search engines are sent to the relevant new page.

What does a professional website cost?

The price depends on scope, design, number of pages, content, features, integrations, and how much material the customer already has. A simple website with a few well-developed pages is a different task from a multilingual solution with a membership system, integrations, many content types, and extensive migration. The price is affected, among other things, by:

• The number of unique page types
• The need for custom design
• The number of pages to be set up
• Text production and research
• Images, video, and graphics
• Forms and features
• Multilingual content
• Integrations with external systems
• Migration from an existing website
• SEO analysis and redirects
• Teaching and documentation

I do not give a fixed price without knowing the task. In return, scope and price are described clearly before the project begins. If the project contains uncertain or exploratory parts, it must be stated how they are handled.

Two different ways to buy a website

It is more useful to compare ways of working together than to claim that all agencies work the same way. The table compares a project-based solution with a standardised subscription solution.

No model is automatically right or wrong. A subscription solution can suit businesses that want a standardised deliverable and bundled operations. A project-based solution often fits better when the business wants to own the solution, have greater flexibility, or has particular needs. The agreement should always be read carefully.