Corporate website design and development: fast-loading, managed from the panel, and yours to keep.

We wrote this guide for business owners and marketing leads who want to build a new corporate website or rebuild their current one. The principles we describe are based on documentation from Google Search Central, Google Tag Platform, WordPress.org, W3C, web.dev and OWASP; the sources are in the numbered list below the FAQ. We verified version names and criteria against the source as of September 2026. Our field observations are marked separately under the heading “Expert note”.

Our work on a corporate site runs in three layers: strategy and information architecture; design and development; launch and operation. markention.com is run with the same method and tools: our own WordPress theme, Google Analytics 4, Google Tag Manager, Microsoft Clarity, Search Console, Bing Webmaster Tools, Yandex Webmaster and Data Studio dashboards.

What is a corporate website, and what should it carry?

A corporate website is the official address, with a domain and content owned by the company, that explains who the company is, what it offers and how to reach it; it should answer the three questions a visitor asks before deciding: what does this company do, is it right for me, and who do I contact? A visitor coming from an ad, a search or a recommendation often meets the company here for the first time. That’s why corporate web design is a content and structure job before it’s a visual one.

Google writes that its automated ranking systems are designed to surface reliable information created primarily to benefit people.² Of the qualities Google calls experience, expertise, authoritativeness and trustworthiness (E-E-A-T), the most important is trust.² The same document suggests asking whether it’s self-evident to visitors who created the content.² On a corporate site, the answer is the about, team, address, contact and legal information pages; we keep these pages, the site’s trust layer, visible in the menu and the footer.

What should be decided before having a corporate website built?

The first decision for a company that wants a website built is which job the site should get each visitor to do, and how that will be measured; colors and templates come after this decision. If these decisions change later, the sitemap, design and measurement change too; that’s why we put the five decisions below in writing in the first meetings.

1. Goal: the site’s business goal; quote requests, phone calls, dealer applications, hiring or investor relations.
2. Key actions: the actions that will show this goal and be measured in GA4; form submissions, phone clicks, catalog downloads.
3. Visitor groups: customers, dealers, job candidates, press; which question each group brings to the site.
4. Content sources: where each page’s information will come from; product documents, certificates, team details, references with publication permission.
5. Ownership and access: whose name the domain, hosting and measurement accounts will be opened in, and who will work in the admin panel with which permissions.

How do you build the sitemap and information architecture?

The sitemap is the plan that starts from the questions of visitor groups, groups pages by topic, and sets where each page will sit in the menu, in the URL and in internal links. Google writes that organizing a site logically can help search engines and users understand how pages relate to the rest of the site.¹ Because parts of the URL can appear as breadcrumbs in search results, it also recommends using words in URLs that mean something to users.¹ On sites with more than a few thousand URLs, grouping similar topics in directories can help Google learn how often the URLs in each directory change.¹

After drawing the tree, we write down which page each page will get a link from; a page that gets no links from anywhere is hard to find for visitors and search engines alike. Google, too, mostly finds pages through links on pages it has already crawled.¹

How is a content plan written around search intent?

The content plan sets, before design, which question each page will answer and which words visitors use to ask it. Google says users who know a topic well may search with different words from beginners, and that writing with these differences in mind can have a positive effect on search performance.¹ So we pull the queries from Semrush and Search Console data, and place the answer to each on the page where it fits most naturally.

Among the shared qualities of helpful content, Google lists being easy to read and well organized, unique and up to date; it recommends breaking long text into paragraphs and sections and making it navigable with headings.¹ According to the same document, Google Search doesn’t use the keywords meta tag, and excessively repeating the same words, known as keyword stuffing, is against its spam policies.¹ We don’t stuff keywords into pages; we give each page one main question and the sub-questions that support it. The search side is covered in detail on our SEO consulting page.

Why do we build corporate sites on WordPress with panel-managed components?

We use WordPress and panel-managed components so that content on a corporate site can be updated without a developer and without breaking the layout; WordPress provides the role, block and pattern infrastructure this needs out of the box. The table below shows the permissions of the four of the six default roles we use on corporate sites; on a single-site install, only the Administrator can install plugins and update the core, themes and plugins.⁴

Alongside roles, two block editor features protect the layout. A synced pattern is a component that, once edited, updates everywhere it’s used; WordPress 6.3 renamed reusable blocks to patterns.⁵ We build sections repeated on every page, such as a contact band, this way. Content-only editing (contentOnly), introduced in WordPress 6.1, hides design tools at the pattern or template level while allowing the content of blocks to be edited, and protects the layout by preventing extra inner blocks from being added; design tools can be reopened when needed through the “Modify” link in the toolbar.⁶

What does WCAG 2.2 accessibility change on a corporate site?

WCAG 2.2 sets testable success criteria so a site can be used with a keyboard, a screen reader and a touchscreen; on a corporate site, it affects menus, forms and buttons most. W3C published WCAG 2.2 as a W3C Recommendation on 5 October 2023; the version added nine new success criteria and removed criterion 4.1.1 Parsing.⁷ The new criteria that create direct work on a corporate site are:⁷

• Focus Not Obscured (2.4.11, AA): an element that receives keyboard focus shouldn’t be entirely hidden by author-created content, such as a band fixed to the bottom of the page.
• Target Size (2.5.8, AA): targets used with a mouse or touch (a pointer) should be at least 24×24 CSS pixels, except for defined exceptions.
• Dragging Movements (2.5.7, AA): every action done by dragging should also be possible with a single pointer, without dragging.
• Consistent Help (3.2.6, A): if help mechanisms such as contact details appear on several pages, they should be in the same relative order.
• Redundant Entry (3.3.7, A): if information entered earlier in the same process is needed again, it should be auto-populated or available to select, except for defined exceptions.

We apply these criteria component by component at the design stage, and test with a keyboard and a screen reader before launch. Interface design is covered in detail on our UX/UI design page.

How are Core Web Vitals protected at the design stage?

Core Web Vitals are protected when image, font and script decisions are made at the design stage with the thresholds in mind. According to web.dev, for a good experience LCP (Largest Contentful Paint) should happen within 2.5 seconds, INP (Interaction to Next Paint) should be 200 milliseconds or less, and CLS (Cumulative Layout Shift) should be 0.1 or less.⁸ As a measure, it recommends looking at the 75th percentile of page loads, separately for mobile and desktop.⁸ These are primarily field metrics measured on real visitors; lab measurement is for testing before launch and catching regressions before they reach users.⁸ In the lab, Chrome DevTools measures all three; Lighthouse, which runs without user interaction, can’t measure INP, so Total Blocking Time (TBT) is used instead.⁸

In design, this translates into these decisions: a single main image of known size in the first screen, a fixed message instead of large auto-rotating sliders, a limited number of font files, and space reserved in advance for every image and embedded element. Measuring speed and fixing it on existing sites is covered on our website speed optimization page.

How is a site prepared for search engines and measurement?

Preparing for search engines and measurement covers writing a unique title and description for every page, marking up company information with structured data, and setting up measurement tags so they depend on the visitor’s consent choice. According to Google, a good title is unique to the page, clear and concise, and accurately describes the content; a good description is also short and unique to the page, and includes the most important points.¹ An image’s alt text should describe the relationship between the image and the content briefly and descriptively.¹

We mark up company information with Organization structured data. According to Google, this markup on the home page can help the search engine understand the organization’s administrative details and disambiguate it from others in search results; some properties can also influence visual elements shown in search results and the knowledge panel, such as the logo.³ There are no required properties; properties that apply to the organization, such as name, address, phone and logo, are added. It’s recommended to place the markup on the home page or a single page such as about, not on every page.³

We set up measurement through Google Tag Manager, with Consent Mode. Consent Mode adjusts how Google tags behave based on the visitor’s consent choice; in the basic setup, tags don’t load until the visitor interacts with the cookie banner, and in the advanced setup, cookieless pings are sent when consent is denied.⁹ Google states that obtaining consent is the site owner’s responsibility, and that it can be done with a cookie banner or a consent management platform (CMP).⁹

How are updates, backups and security handled after launch?

After launch, the site is run with core, theme and plugin updates, regular and tested backups, and configuration audits. WordPress automatic background updates arrived with version 3.7; on new sites installed with 5.6 and later, minor and major core releases update automatically by default, while previously installed sites only get minor releases unless an administrator separately turns on major updates.¹⁰ By default, plugins and themes update automatically only in special cases set by the WordPress security team to close critical vulnerabilities; the documentation also recommends taking a backup before updating.¹⁰ We handle the remaining updates as part of maintenance.

A WordPress backup has two parts: the database that holds the site’s content, and the core, theme, plugin and uploaded files.¹¹ The WordPress documentation recommends keeping at least 3–5 recent backups in different locations, such as the hosting server, cloud storage and a local computer, and taking backups weekly on small sites that publish few posts and daily on busy ones.¹¹

For security we work from the OWASP Top 10; in the 2025 edition of this list, a standard awareness document for developers and web application security, the top three are broken access control, security misconfiguration and software supply chain failures.¹² The examples given in the category descriptions, violating the principle of least privilege, leaving unnecessary features enabled, and components that are outdated or from untrusted sources,¹² show up on a WordPress site as, respectively, administrator permissions broader than needed, debugging and file editing settings left on, and plugins that aren’t updated or whose source is unclear.

How do our corporate website services run through launch and the first 30 days?

Before launch, speed, accessibility, search, measurement and operations checks are completed; the first 30 days are spent measuring. We apply the list below on every site.

The steps of the first 30 days:

1. Week 1 · Indexing and measurement: the sitemap is submitted to Search Console, redirects and error pages are monitored, and key events are confirmed to land correctly in GA4.
2. Week 2 · Panel and roles: the first updates are made together with the content owner, and roles and permissions take their final form.
3. Week 3 · Behavior: forms, menu use and the pages where visitors leave are read through Microsoft Clarity recordings.
4. Week 4 · First report: search visibility, key events and the field speed data that’s starting to build up are reported, and the task list for the second month is drawn up.

Google writes that changes can take anywhere from a few hours to a few months to be reflected, and that you generally need to wait a few weeks to assess the effect;¹ for rebuilds where URLs change, it also expects temporary ranking fluctuations and, for medium-sized sites, a transition of a few weeks or longer.¹³ That’s why we do the first search reading in the fourth week and track monthly after that.

Web design agency, freelancer or website package: what’s the difference?

A company searching for a “web design agency”, a “web design company” or simply someone to build its website usually ends up choosing between three models. What separates them is who builds the site, with what responsibility, and who runs it after launch.

We combine agency delivery with consulting: one team handles the sitemap, content, design and development, and keeps running the site after launch with updates, backups and measurement.

How should you choose a web design agency?

When comparing proposals, look at ownership, scope and what happens after launch before you look at portfolio samples. Ask for written answers on these points:

1. Domain and accounts: will the domain, hosting, Analytics, Tag Manager and Search Console be opened in your company’s name? A domain registered to the agency leaves your site’s address with them if you part ways.
2. Panel and layout: who will change text and images in the panel, and how, and what keeps alignment, spacing and colors intact when they do?
3. Old URLs: in a rebuild, will every old URL be listed and connected to its new counterpart with a permanent redirect?
4. Maintenance and backups: who handles updates and backups, how often, and will restoring from a backup actually be tested?
5. Theme code: will the code be handed over to you, or can the site only run on the agency’s own platform?
6. Promises: a proposal that promises the top spot on Google or a set number of visitors is skipping the fact that rankings are Google’s decision.

What determines corporate website pricing?

The cost of a corporate website depends more on the work the site has to do than on its page count. These are the factors you should see as separate lines in a proposal:

We work out the scope together in the first meeting, then send a proposal with each item written out. Provider fees such as the domain and hosting are paid directly to the provider from accounts opened in your company’s name.

Corporate website pricing: starting prices and ranges

The lower end of each range is the starting price; excluding VAT. Scope is confirmed in a written proposal after the first meeting. As of October 2026.

If you’d like to look at your current site and goals together, pick a meeting day below.