Corporate Website Design and Build
A corporate site that loads fast, behaves properly on mobile, and lets both search engines and AI crawlers read every word of its content.
In most businesses a corporate site does two jobs at once: it is the brand’s shop window and a source of information a search engine can read. The second job is usually skipped. That is how sites appear that look fine but have a broken heading structure, text stuck behind scripts and seconds of blank screen on mobile.
We build the site starting from content: which pages exist, what question each one answers, and what the visitor should do at each step. Moving to design before the information architecture is settled makes adding pages later — and fixing the search side — expensive.
On the technical side the criteria are fixed: the page should arrive from the server as complete HTML, open quickly on mobile, keep its addresses permanent, and carry structured data that says the same thing as the visible page. These criteria are not only for Google; they matter just as much to AI crawlers that read a page without running JavaScript.
What this service covers
The scope differs between a new build and a rebuild. On a new site the work starts with information architecture; on a rebuild the first job is protecting the addresses and visibility you already have.
Information architecture and page plan
We write down which pages will exist, how the menu is built and what question each page answers before anything is designed. Whether services get one page each or share a single page is decided here; splitting them later means changing addresses.
Design and mobile behaviour
We design on mobile rather than desktop, because that is where most visits come from. Touch targets, form fields, menu behaviour and readability are checked at real screen widths, and no block is allowed to scroll the page sideways.
Speed and technical foundations
Image formats, font loading, script weight and cache headers are planned from the start. Page content reaches the browser as complete HTML; where content only appears after JavaScript runs, both search engines and AI crawlers see partial text.
Content management and multilingual structure
We set up an editing arrangement your team can add pages and posts through. If a second language is needed, each language gets its own address and the two declare each other reciprocally; setups where language only switches in the browser stay invisible to search engines.
Structured data and handover
Company details, contact information, service and FAQ schemas are added so they match the visible page exactly. At handover the domain, DNS, certificate, sitemap, robots and analytics setup are complete, and admin access stays in the business’s name.
How we work through it
Timing depends on the number of pages, whether content is ready and how fast the approval loop runs. The schedule below describes a typical build; it is not a commitment.
- Stage 1 — first week
Scope and page plan
We review the current site, the page structures competitors use and your own sales flow. The output is a page list with the purpose of each page written next to it. On a rebuild, an inventory of existing addresses is produced here too.
- Stage 2 — weeks 2-4
Design and content placement
Main templates are designed, copy is placed and mobile behaviour is checked. If content comes from your side, copy is the only thing this stage waits on; the approval loop is the single biggest influence on the timeline.
- Stage 3 — development
Development and technical checks
Pages are built, speed is measured, structured data is added and forms are tested with real submissions. On a rebuild, the redirect map from old addresses to new ones is prepared at this point.
- Stage 4 — launch and after
Launch and first-month watch
After launch we watch indexing, error pages and form submissions. On a rebuild we check for address-level drops in the first weeks; if a page has gone missing, its redirect is completed.
What we do not promise
The most expensive misunderstanding in website work is expecting the site itself to bring customers. We write the limits down at the start:
- A new site alone does not bring rankings or a rise in demand; the site is the foundation, visibility is separate work.
- We do not commit to a fixed delivery date. Content and the approval loop set the timeline more than anything else; a project waiting on copy runs long regardless of design.
- We do not offer unlimited revisions. Revision rounds are agreed up front; unlimited rounds blur the scope and end badly for both sides.
- We do not treat stock photography as brand photography. If there are no real photos of the premises, team or work, we will not present the page as though there were.
- Domain, hosting and admin panels are opened in your name. If we part ways, the site, its content and the access stay with you; we do not hold anyone through technical dependency.
What we measure
A site succeeds through measurable behaviour, not approval. The list is deliberately short:
- Load time on mobile and desktop, plus Core Web Vitals field data.
- How many pages are indexed in Search Console and what share of addresses report errors.
- The number of form submissions, phone calls and WhatsApp starts.
- How far visitors read on each page and where they leave.
- On a rebuild, whether old addresses keep their traffic after the redirects.
Frequently Asked Questions
Let us map out your site together
We look at your current site or your need for a new one and write up the page plan, the technical requirements and the addresses a rebuild has to protect.
Get in touch