SEO already at the website design stage – what do companies forget about?

Many companies think about SEO too late. First, a project is created, then implementation, and only at the end someone asks if it is possible to "add positioning". The problem is that some errors are very expensive to undo. If the service structure is bad, the links are not crawlable, the mobile version has less content, and the titles and meta descriptions are random, you won't fix it with one plugin or one on-page audit. Therefore, SEO is most profitable when it is part of the project from the beginning.

Companies think about appearance first and structure later

Google reminds us that creating useful and well-organized content influences search results more than many other individual actions. In practice, this means that the website design should start with questions about the offer, user intention, subpage logic and contact path - and not with the hero section layout itself. Highly visible Polish materials on SEO website design also lead in this direction, emphasizing information architecture and content planning even before the development stage.

Linking and navigation must be understandable by Google

This is one of the most often overlooked foundations. Google can index a link if it is a real HTML element <a> with the href attribute. At the same level, anchor text is important - the documentation explicitly advises against general phrases such as "click here" or "more", because they do not provide good context to both the user and the search engine.

If the designer and developer do not plan this at the component level, it is very easy to build a website that looks modern but has poor discoverability and poor internal linking.

Titles and meta descriptions are not cosmetic, but a layer of communication with the SERP

Google automatically determines the title link based on multiple sources, but explicitly recommends that each page have its own descriptive <title>. The meta description, on the other hand, does not guarantee a one-to-one display - Google most often generates a snippet from the page content, but may use a meta description if it better describes a given page.

For the project, this means a simple conclusion: you need to plan not only a mock-up, but also a pattern of titles, descriptions and edit fields in the CMS - for service pages, articles, case studies and categories.

Mobile-first is not about responsiveness at the end, but a design decision at the beginning

Google uses the mobile version of your website content for indexing and rankings. Importantly, the documentation points out that if the mobile version has less content than the desktop version, you can expect a drop in traffic - because Google receives less information about the website.

Content can be collapsed into accordions or tabs, but it should not be simply deleted in the mobile version. The domination of the smartphone in the purchasing process of Poles (82% of online buyers according to the Gemius report) makes mobile-first an SEO requirement and a business requirement at the same time.

JavaScript and modern animations must support visibility, not block it

Google supports JavaScript, but the documentation leaves no doubt that several elements need to be optimized. Navigation is particularly important - Google's examples show that routing based on # fragments and loading content via hashchange are inferior to the approach with the History API and real URLs.

In other words, if you're building a modern website with animations, transitions, and dynamic components, the technical design must include rendering, indexing, and meaningful URLs from the start.

Performance is not a post-deploy add-on

Google indicates that Core Web Vitals are used by ranking systems, and good thresholds include LCP up to 2.5s, INP up to 200ms, and CLS up to 0.1 at the 75th percentile of views. The site may be beautiful, but if the hero image chokes the load, the interface is slow to respond, and elements jump around as you scroll, you're missing out on both the user experience and the opportunity for better visibility.

Structured data and content types need to be planned in advance

Google explains that structured data helps recognize the content of pages. For articles, the Article, NewsArticle and BlogPosting tags can help Google better understand the title, image and publication date. If you want to run a company blog for SEO, it is worth providing author fields, publication dates, updates, lead image and category taxonomies in the CMS project.

It's much cheaper than adding exceptions later after dozens of published entries.

Check out how we combine SEO with WCAG accessibility

What companies forget most often

The most frequently overlooked things include no service content map, too general a menu, a design with no room for blog growth, incorrect internal links, separate mobile mockups with cut off content, heavy components without a performance budget, and no post-implementation measurement plan. Only at the end does someone ask about Search Console.

Meanwhile, Google recommends using Search Console and analytical data to monitor performance, and many risks can be detected or reduced already in the mock-up and prototype phase.

Ask for a quote for a website with SEO from scratch

Find out how we take care of maintenance and monitoring after implementation

Request a free quote →

Checklist - SEO from the design stage

Example with tagged assumption

Assumptive example - B2B company with six services

If each service is to receive a separate subpage, CTA, FAQ section, case studies and space for blog development, SEO should enter the project already at the stage of information architecture, mockups and the CMS model. Otherwise, you later have to rebuild the menu, content, metadata and often the publication model itself.

This is a conclusion resulting directly from Google documentation on titles, meta descriptions, mobile-first and links, as well as from current Polish publications on website design for SEO.

Frequently asked questions