Websites and webshops
Website and webshop development for the page on your phone
The buyer is on a phone, and the page is still loading. The search does not show your site. We build the website or the webshop around that, from Ho Chi Minh City, for a company anywhere. A first working site is ready in 2 weeks.
One webshop we built moved from position 98 to the top 3 on Google, in 2 weeks.
Example screens from websites we built, with names and logos removed.
Where the site fails today
01
The phone is still loading
Your buyer is on a phone. They tap the link, and the page has not finished loading. They wait, then they open the next result. You see a visit that never became a request or an order.
02
The search does not show you
Someone types what you sell into Google. Your page is not in the list. The position is a question mark, or it sits too far down to reach. The title Google would show is missing, or it is the same line on every page.
03
A headline waits on a ticket
A line on the page is wrong, and your team cannot change it. They file a ticket and wait. The site runs on a template many other companies share, so the page never really looked like yours.
The same pages, two ways
On the left, position, load time and title are missing or weak. On the right, the new site, with a page that has loaded.
| Page | Google position | Load time | Title for Google |
| Home | ? | slow on a phone | ? |
| Category | ? | ? | ? |
| Product | ? | ? | missing |
| Contact | ? | ? | ? |
I searched what we sell. We are not on Google.
The home page is still loading on my phone. What do I tell them?
We need a title Google can show. I do not have one.
Example screens from websites we built, with names and logos removed.
What you lose if nothing changes
A buyer searches on a phone and stays with the first page that has finished loading. Yours is still waiting, so they read someone else and order there. The load time decided it before anyone on your team saw the visit.
You replace the site, and the old address and the new one do not match. The position you had can slip on launch day, while the headline is still wrong and the ticket is still open.
What we build in the first release
The first release loads on a phone, with a path, a title and a description Google can read. A working version is ready in 2 weeks. More languages, connections and old addresses wait until we name them with you.
Example screens from websites we built, with names and logos removed.
What we have built
Screens from sites we built, with names and logos removed: a tableware and glass webshop in Belgium, in four languages; a webshop in Asia; a restaurant; and two sites for one group, care and hospitality. Click through, or let it run.
A navy tableware shop home with a hero about the table and two paths, for home buyers and for the trade.
Example screens from websites we built, with names and logos removed.
One build
From position 98 to the top 3
A webshop we built sat at position 98 on Google. Two weeks later it was in the top 3. We do not name the shop or the search. We bring you there, and we keep you there.
Top 3
from position 98 on Google, in 2 weeks
How the 2 weeks go
A first working site takes 2 weeks. More languages, more connections, or old addresses that must keep their place, can take longer. We say so on the call, before we start.
Days 1 to 2
We open the phone and the search
We open the page on a phone and the search that should show you. We note the load, the position if you have it, and the title. Then we name the first pages, and what waits: extra languages, connections, and old addresses.
Days 3 to 10
We build the first pages
We build the pages we named so they load on a phone. Each one has a path, a title and a description. You see them during these days. A shop includes the product page. What we agreed to leave out stays out.
Days 11 to 12
We connect what this release needs
A shop sends its product feed to Google Merchant Center. Agreed languages get their own path, title and description. If an agent may search and fill a cart, we connect WebMCP, and the customer keeps the last click.
Days 13 to 14
Your team uses the site
Your team opens the site on a phone and walks one task: a page, a title for Google, and a product in the cart if it is a shop. We stay with what blocks these two days. Day 14 ends with a working site.
What sets the price and the build time
Six things decide the price and the build time. On a 30-minute call we go through them against your pages and your search.
- Languages: how many the site needs, each with its own path, title and description for Google.
- Pages: how many unique pages the first release holds, and which of them a buyer opens on a phone.
- Site or shop: a set of pages, or a shop with a product feed for Google Merchant Center and a cart.
- Connections: what the site has to talk to besides the feed. Each connection we add changes the work.
- Copy and old positions: who writes the text, and whether addresses you already have on Google have to move with the new site.
- Hosting and care after the first site: where it runs, and what you want from us once your team is using it.
Questions before the call
A first working site is ready in 2 weeks. More languages, connections or old addresses can take longer, and we say so first. We do not promise your positions will hold on launch day. One webshop moved from position 98 to the top 3 in 2 weeks. That case is not the offer, and not position 1.
We do not name a system on this page. On the call we look at the headline and who on your team should change it. If that edit is in the first release, it is inside the 2 weeks. A separate login changes the build time and the price.
Code, the domain and the hosting account are named on the call, against your agreement. This page does not replace that list. We will not describe a rented shop and a site you hold as if you receive both.
Six things make the quote: languages, pages, site or shop, connections, copy and old positions, and hosting plus care after the first site. There is no amount on this page. On the call we say which of the six apply, and what that does to the price and the 2 weeks.
If the paths, the titles and the load on a phone are already right, a new skin can be enough. If the page does not finish loading, or Google has no title, the first release is a new site. We say which one the 2 weeks cover before we start.
We do not publish a score here. A number without the page, the tool and the date would be a picture. Open the site on a phone and see if the page has finished loading. A measured load time is named on the call, or it is not claimed.
Day 14 ends with a working site: pages on a phone, a path, a title and a description, and the product feed if it is a shop. Code, the domain, hosting and who may edit a page are confirmed on the call, not added on this page.
Each language has its own path, title and description, and a shop sends a product feed to Google Merchant Center. That is not a place on Google. We do not offer position 1, or the top 3 as a package. The move from 98 to the top 3 is one case.
Bring the phone and the search
Bring the page that is slow on a phone, and a search that does not show you. On the call we name the first release, and which factors change the price and the 2 weeks.