SEO support during development

When an SEO specialist joins website development, which decisions they check and which projects only need a basic setup.

A website can be beautiful and convenient, and still turn out after launch to lack the pages it needs to rank. Then the menu, mockups and code have to change. SEO support helps spot such problems while the site is still being designed and fixes are cheaper.

For this, an SEO specialist takes part in the work on structure, prototypes, design and development. How deeply to involve them depends on the role of search in the business and the complexity of the site. A simple landing page and a catalogue of thousands of products need very different amounts of work.

SEO support does not reserve a top-ten spot

Until the site is published, it has no search history and no data on how people use it. Promising a specific ranking or number of enquiries at that point would be guesswork. The specialist can prepare the foundation: define the pages needed, check their URLs and make sure search engines can find them.

That is an important but limited result. It does not promise that competitors will make room for a new site. But the team will not start promotion by redoing decisions that could have been checked before launch.

Structure comes before pretty pictures

A company may consider five services one area, while customers search for and compare each one separately. Put everything on one page, and people have to dig for their answer, while search engines struggle to understand which queries the page should rank for.

So before design, the specialist studies what future visitors search for and which questions stand behind those queries. The outcome should not be an impressive keyword file but a clear map: which pages to create, what each one covers and how they link together.

Sometimes every service needs its own page. Sometimes two services are better kept together because people see them as one task. The number of pages is not set by a formula; it follows from the content and how a visitor chooses a solution.

A mockup can get in the way of search too

Once the structure is agreed, it has to be carried down to specific pages. Using the prototype, the specialist checks whether a visitor will get an answer: a service description, terms, examples of work, answers to common doubts and a clear next step. If important information has nowhere to go, it will not find a place in the design by itself after launch.

In the mockup, the specialist looks at how this information is presented. Important text should stay text, not part of an image. On a phone, visitors need the same essential information as on a computer. An SEO specialist does not choose fonts or composition, but can show where a beautiful solution hid what people came for.

A beautiful site is not automatically searchable

The design is approved, the pages are built and the menu links work. To a visitor, everything looks finished. Now come the checks that are not visible at first glance:

• URLs. Important pages need permanent addresses. If a URL changes because of a random parameter, one page can look like several different ones to a search engine.
• Page titles. Each page needs its own title for the browser tab and search results, and the text itself needs a clear main heading.
• Crawlability. Pages meant to appear in search are open to crawlers. Service pages and useless internal search results, on the contrary, should not be offered as standalone content.
• Duplicates. If the same material opens at different URLs, search engines find it harder to choose the main page. More in the article on duplicate pages.
• Internal links. The menu, catalogue and in-text links should lead to important materials rather than leaving them buried deep in the site.

On a corporate site, service pages come first. A store adds categories, filters and product cards. When redesigning a live site, it is also important to keep the path for people following old links: previous URLs are kept or redirected to matching new pages.

In a mockup an error costs a comment; in code, a budget

Early checks save on rework. If the diagram already shows that every service needs its own page, the team plans for them in the menu and mockups straight away. The same decision after launch touches design, copy, development and testing of a live site.

With a catalogue the cost of a mistake is even more visible. Without planning filters in advance, a site can generate many nearly identical pages. Later, URLs, links and catalogue logic have to change. At the design stage it is easier to decide which filter combinations shoppers really need as separate pages.

Of course, support does not make a project invulnerable. Business requirements change, and some hypotheses can only be tested on a live site. But paying to fix an error that could have been spotted earlier would be especially frustrating.

The Publish button does not start promotion

Before publishing, the specialist checks the result against the agreed structure: do all pages open, are titles filled in, is the site not blocked from search. If a live site was migrated, they also check redirects from old URLs. On the production domain the check is repeated: settings that worked on staging sometimes get lost exactly at launch.

Then promotion of the published site begins: search engines get to know the pages, the team looks at the first data and develops the content. If demand or competition changes, the work changes too. Development support gives the site a working foundation but does not replace this next stage.

Not every website needs full SEO support

Ongoing involvement of a specialist is usually justified when a project has many pages and search should bring customers:

• a corporate site with several services or business lines;
• an online store or catalogue with categories and filters;
• a site that works across several cities or regions;
• a redesign of a live site that already gets search traffic;
• a long-term content project where the number of pages will grow.

For a temporary promotion, a closed client area or a landing page driven by ads, a basic check before launch is usually enough. A one-page site can also get search traffic, but it is hard for it to cover many different topics. More in the article on SEO and landing pages.

The price depends on how many decisions need checking

The cost of support depends on the number of page types, the size of the catalogue, the number of regions and whether a live site has to be migrated. Checking one prototype is simpler than taking part in the structure, design and development of a large store. After every revision, the specialist has to revisit part of the decisions and check them again.

A one-off consultation lets you check a finished prototype. It takes less time, but some decisions have already been made by then. Support from the first diagrams to launch costs more because it spans several stages. Its point is that feedback arrives on time, before the next stages rely on a wrong decision.

"SEO included" explains nothing

Before work starts, ask for a list of concrete deliverables: a page map, comments on prototypes and mockups, development requirements, a check of the finished site and a list of fixes before launch. Find out who makes the changes and who confirms they are done. Then "SEO included" turns from a nice line in an estimate into a clear scope of work.

If search is supposed to bring enquiries, involve an SEO specialist while the structure and mockups can still change. For a small site without that goal, start with a basic check. Either way, agree in advance which decisions the specialist checks and what you will receive by launch.