04 Build
Websites & technical SEO
Company and product websites in Next.js or prerendered React, with the technical SEO built into the code, so search engines and AI assistants can read them correctly.
Outcome: One consistent story for people, search engines and AI tools.
The public website is often where buyers, and the AI assistants they ask, form a first picture of your company. This service builds it to be read as clearly by machines as by people: a version for every language you sell in, accurate metadata and structured data that describe the company.
It fits a new company or product site, a relaunch, or an existing site that search engines index poorly, that describes the business in contradictory ways or that exists in only one language. Screens behind a sign-in belong to front-end development; this service covers the public site around them.
Typical needs
- Search results show old titles, the wrong pages or a previous domain
- A new site or a relaunch that has to work in every language you sell in
- AI assistants that describe your company vaguely or confuse it with another
What you receive
- Multilingual routing with hreflang, canonical URLs and sitemap entries for every language
- Metadata, a JSON-LD entity graph and llms.txt, all built from the same facts
- Permanent redirects from old addresses and domains, so existing links keep working
Approach
How the work runs.
- 01
One page per search intent
Pages are planned around what buyers search for in each language, so every page has one clear job and no two pages target the same query. Titles, headings and URLs follow from that plan.
- 02
Company facts, written once
Name, legal details, services and products are defined in one place and reused in the page copy, llms.txt and the JSON-LD graph, whose nodes are linked by stable identifiers — so every format says the same thing.
- 03
Language versions and URLs
Each language gets its own URLs, a canonical tag, reciprocal hreflang links and sitemap entries. Old addresses redirect permanently to the new ones, so bookmarks and links from other sites land on the right page.
- 04
Checks that keep it correct
Automated tests check title and description lengths, language links and structured data, so a later edit that breaks them fails a test instead of going unnoticed. Speed and accessibility are measured on the built pages.
Technologies
- Next.js
- TypeScript
- schema.org JSON-LD
- Vercel
Live example
deusengineering.com: English and Serbian pages with hreflang, a JSON-LD entity graph and llms.txt. pametniadvokat.rs (opens in a new tab) (Pametni Advokat): llms.txt and prerendered Serbian pages, each with its own title, description and JSON-LD.
The engineer who does this work is the founder, Filip Volf — you work with him directly.
Questions
About this service.
How is this different from React, Next.js & TypeScript front ends?
React, Next.js & TypeScript front ends cover application interfaces — the screens people work in, often behind a sign-in. This service covers the public website: the pages search engines and AI tools read, their language versions, metadata and structured data. Many projects need both, built in the same stack.
How do you make a website readable for AI assistants?
Mostly as for search engines. Pages are served as complete HTML that crawlers read without running scripts, and the company’s name, legal entity, services and products are stated the same way in the copy, the JSON-LD and llms.txt, a plain-text summary for the AI tools that read it. No one controls what an AI tool cites; contradictions and gaps leave it to guess.
What can we expect in search results?
Technical SEO groundwork rather than positions: pages that can be crawled and indexed, one canonical URL each, correct language links, accurate titles, descriptions and structured data, and a sitemap submitted to the search engines. Where a page then appears also depends on the competition, the search engines and time, so no position is promised.
Related services
- 02
Product & UX/UI design
Outcome: A product shaped around the real work — agreed before the build begins.
- 03
React, Next.js & TypeScript front ends
Outcome: Interfaces people use quickly — and developers change safely.
- 08
Cloud infrastructure & integrations
Outcome: Routine releases and observable integrations.
Next step
Let’s talk about what you’re building.
Describe what you need built or fixed, how the work runs today and the constraints. You get clarifying questions or a first outline of the approach — by email, in English or Serbian.