Solutions · Construction & fit-out
In construction, the decision is made months before the request and starts with a technical question asked in search. We build the structure that has one page for each such question, in Romanian and Russian, and we say from the start how many pages can be made honestly — that is, for how many questions we have a real answer.
Already builtO implementare proprie, verificabilă din exterior: site-ul de conținut al unui producător de material de construcții are 89 de rute-șablon în cod, aproape toate pagini de întrebare concretă — cum se termoizolează mansarda, pereții, podul, podelele; densitatea; clasa de foc; compoziția; durata de viață; comparația cu alți izolanți; calculul cantității și al costului; costurile de încălzire; certificatul energetic — iar harta de site de pe producție listează 202 adrese, numărate de mine pe 06.09.2026. Site-ul e bilingv, cu fișiere de traducere separate, câte 14 blocuri fiecare, și e exportat static, deci se servește de pe o găzduire obișnuită, fără proces în spate. A doua implementare, pe același tipar, e un site de transport de materiale de construcții: 266 de pagini generate dintr-un generator de 2.892 de linii, cu câte o pagină pe tip de marfă. Două rezerve, spuse amândouă: (1) ambele lucrări sunt marcate nepublicabile în inventarul nostru de portofoliu — clienții nu au confirmat, iar site-urile nu poartă atribuirea noastră — deci le descriem fără nume și fără adresă, iar citările rămân interne până la acordul lor scris; (2) nu putem susține și nu vom scrie poziții, trafic sau număr de pagini indexate, pentru că nu avem acces la consola de căutare a clienților.
A building material people do not know does not sell from a product page. And in construction, almost nobody looks for the brand: they look for the job. “How do I insulate the attic”, “what density is needed”, “what fire class does it have”, “how much does it cost to heat a house”, “how long does it last”, “is it better than mineral wool”. These are questions asked months before a quote is requested, by people who at that moment have no reason to know your name.
The structure that answers that is not a blog. It is a set of pages, each dedicated to a single question, linked to one another and linked to the material. In the work we cite: 89 template routes, almost all pages for concrete questions — how to insulate the attic, the walls, the loft, the floors, density, fire class, composition, service life, comparison with other insulators, calculating quantity and cost, heating costs, the house energy certificate. The production sitemap has 202 addresses, because each page exists in Romanian and in Russian.
In construction, bilingualism is not a matter of image. The worker who searches “чем утеплить мансарду” and the owner who searches in Romanian are two different people in the same house, and often the first one makes the decision. Translation is done in separate files, with the same content blocks, not by automatic browser page translation.
And now the limit you must hear before signing: the number of pages is not a figure we choose to impress. A page can be made for every question for which there is a real answer — with data from the manufacturer, with a calculation, with a comparison. One hundred pages that repeat the same paragraph are worse than thirty good pages: they bring nothing and make the site hard to maintain. That is why the first deliverable is the inventory of questions, not a contract for a number of articles.
What it covers
The inventory is made on operations and real decisions: what is insulated, with what, in what order, what is calculated, what is it compared with. Each question gets a page only if it has its own answer — from a technical sheet, from a calculation, from a comparison. We deliver the list before writing a page, with the questions we reject and the reason.
“How do I insulate an attic” and “how do I insulate a floor” are different jobs, with different materials and a different audience. On a single long article, both are lost. In the work cited, the structure has separate pages for the attic, walls, loft and floors, plus the property pages — density, fire class, composition, service life.
The quantity calculation, the thermal insulation cost calculation, heating costs, savings after thermal insulation, the energy certificate. In construction, the person searching already has a surface in mind and wants a number. A page that gives them the calculation is read to the end; one that talks about quality is not.
The comparison page is the most searched for and the easiest to spoil. Our rule: the technical data of the material are the producer’s claims and are attributed as such, and the comparison is made on named criteria, not on adjectives. No “best”, no “only” — not out of caution, but because a comparison without a criterion convinces no one who is actually buying.
Bilingual by language segment in the address, with separate translation files — 14 content blocks each. Each page has its pair, which is why the number of addresses in the site map is approximately double the number of pages. We do not use browser machine translation: what is not translated in the file is not translated at all, and it shows.
The site is built as static files, without a back-end process — it can be served from a standard cPanel hosting. For a local manufacturer or distributor, that means a low operating cost and something more important: the site does not go down because a service has failed.
On the same pattern, we built a construction materials transport site with one page per type of goods — concrete slabs, blocks, reinforcement, posts, concrete rings, paving stones and kerbs, containers — plus pages for the city sectors: 266 pages generated from a 2,892-line generator. The structure by area is used only where there is a real difference in content, not as a mechanical multiplication.
We go through each address with direct requests, without following redirects, with at most six simultaneous requests, and we put 23 columns per address: response code, canonical address, title, description, language variants, visible text volume. We deliver the table. The old addresses each get a verdict: stays, redirects permanently or disappears.
We do not promise positions, growth percentages or a number of visits. “202 addresses in the site map” does not mean 202 indexed pages — these are two different things and we do not have access to the client’s search console to speak about the second. And we do not promise citations in responses generated by assistants: there is no position to buy there.
Traseul
The first delivery is two tables: the list of project questions that deserve their own page, with the source of the answer for each, and the status of each address published today, with 23 columns. This is where it is decided, with figures, how many pages can be done honestly.
A new structure, with the Russian pair for each page, the canonical address resolved in one place, and the sitemap generated from data. Each old address receives a written verdict. We deliver the permanent redirects list.
The text of a page about how to insulate an attic is written with someone who has insulated attics, not with an editor who has read other websites. We deliver the structure of each page and the questions it must answer; the technical data comes from the manufacturer and is attributed.
The site is built as static files and published on the existing hosting. After publication, a check runs that opens each page and fails if the expected response code, canonical address or language pair is missing. We deliver the script so the check can be repeated without us.
The data
The rules differ from one industry to another. These are the ones that apply in construction & fitting out.
A case
The situation
A thermal insulation material manufacturer had a visibility problem, not a price problem: someone searching “how do I insulate the attic” has no reason to know what the material is called, so they do not search for it. A product page cannot appear in a search where the product is not mentioned.
What we built
We built the site as a set of question pages: how to insulate the attic, walls, loft, floors; density, fire rating, composition, service life; comparison with other insulations; calculating the quantity and cost; heating costs; the home energy certificate. 89 template routes in code, each with its pair in Russian, from separate translation files. The site is exported statically, so it is served from the client’s usual hosting, without a backend process.
What came out
The live sitemap lists 202 addresses, and both language versions respond. The structure covers the questions people ask before they know which brand they want — which, in construction, are the only questions that appear in search months before demand.
What the case does not say
“202 addresses in the sitemap” does not mean 202 indexed pages, and we do not have access to the client’s search console: no claims about positions or traffic. The technical data about the material — density, fire rating, service life — belong to the manufacturer and are their claims, not our measurements.
Questions
As many as there are work questions with a real answer from you. In the project we cite, there came out 89 template routes and 202 addresses in the sitemap, in two languages. But the figure for you comes from inventory, not from an offer. Ten pages that really answer something beat thirty that repeat the same paragraph.
Because a blog is arranged chronologically, and work questions do not age: “how do I insulate the attic” is searched just as much every autumn. A stable page, linked in the site structure, which is updated when the information changes, is something different from a 2024 article pushed further and further down the archive.
Yes, with attribution: they are the manufacturer’s claims, backed by its sheets and certificates. What we do not do is repeat them as facts verified by us and add superlatives over them. And a certificates page is published only if the document can be shown.
In construction, in the Republic of Moldova, almost always yes — the tradesperson and the owner often search in different languages, and the technical decision is often made by the former. The translation is done in separate files, with the same content blocks; each page has its pair, which is why the number of addresses is roughly doubled.
No. We do not have publishable measurements about positions and we do not sell what does not depend on us. What we deliver is verifiable in other ways: the inventory of questions, the address structure, the table with the status of each address, redirects for the old ones, and post-publication verification.
No. We build the site as a static export, so it is served from ordinary cPanel hosting, without a backend process. It is a choice that keeps operating cost low and removes an entire category of failures from the equation.
We do them only where there is a real difference in content — an area with a different type of construction, a different access regime, a different transport cost. Mechanical multiplication of the same page across twenty neighbourhoods is visible and does not help. On a materials transport site, we built such pages because the goods and the area really changed the answer.
Where we establish together — usually in a team messaging channel, so it arrives in minutes, not in an inbox opened in the evening. What should be known: the request contains a property address and contact details, so from the start it is written who sees it and how long it is kept.
We do not give a timeframe, because that would be an invented figure: we do not control the engine, the competition, or the season. What we can say is what we deliver and when — the inventory, the structure, the pages, the checks — and what can be verified at any time in the address table.
Tell us about your process. Together we decide what is worth building, what we can connect, and how we check the result.