OnWeb · Web engineering and cloud
Web development built to rank.
A new site in Next.js or WordPress, with the architecture drawn by the SEO team before the first line of code, structured data written into the template and speed measured in PageSpeed. You follow every stage in the App, from wireframe to launch.
We work in English, Portuguese and Spanish. Headquarters in Belo Horizonte, Brazil.
01Overview
Web development
Web development is where most organic traffic is won or lost before it exists. URL structure, heading hierarchy, image weight, the product template and semantic markup are decisions that stay in the site for years. Fixing them later costs three times what it costs to get them right during the build.
Netlinks builds through OnWeb, the group engineering practice, under one fixed rule: the SEO team goes in before design. The keyword map becomes the site map, every page is born pointing at a clear search intent, and the developer receives the schema spec alongside the layout.
We build in Next.js when a project needs performance and integrations, and in WordPress on a custom theme when the client team has to publish daily on its own. Either way, no heavy page builder, no plugin doing what code should do, and website management available from the day it goes live.
- 200+
- companies served since 2017
- 298
- SKUs in the Safetline B2B catalog, rebuilt in Next.js
- 14
- ranking landing pages on the Master Milhas site
- 24h
- of project tracking inside the App
02Definition
What changes in web development built for search
Every agency delivers a good-looking layout. What separates a site that brings in customers from a site that merely exists is a set of invisible decisions made before the first pixel:
- Architecture drawn from the keyword map. Every service, product or category page is born pointing at real search intent with known volume. A page with no demand behind it does not go in the menu.
- Stable, shallow URLs. Short, readable addresses with no needless parameters, designed to last. Changing them later costs redirects, a temporary ranking dip and an audit nobody planned for.
- Structured data in the template. Organization, Product, Service, Article, FAQ and Breadcrumb written into the template code, not pasted page by page by a plugin.
- Performance as a design decision. Modern image formats, self-hosted fonts, JavaScript trimmed to what is needed, and caching configured from the first deploy.
- Room for content to grow. FAQ blocks, comparison blocks and question sections planned into the template, because that is the material AI models quote.
None of these cost extra at the start. Retrofitted later, they cost your development team's calendar, a month of lost traffic and an uncomfortable conversation with the board.
03Technology
Next.js or WordPress: how we choose
There is no correct platform in the abstract. There is the one that fits your case, based on who publishes content, how often, and with which integrations. The table below is the same one we use in the scoping meeting.
| Next.js | WordPress on a custom theme | |
|---|---|---|
| Best for | Premium corporate sites, B2B catalogs, digital products, multilingual sites | Content-heavy blogs, daily publishing by the client team, WooCommerce stores |
| Who publishes | The team uses a custom panel or an integrated headless CMS | The team publishes directly in the admin, with no developer involved |
| Performance | Server rendering and image optimization by default | Depends on caching, a lean theme and plugin discipline |
| Structured data | Generated in code, per page type | Generated in the theme, without relying on a generic plugin |
| Multilingual | One URL per language and hreflang written in code, done properly | Requires a well-defined domain or directory structure |
| Maintenance | Dependencies updated on a cycle, versioned deploys | Core, theme and plugins updated in an agreed window |
04Project
What happens in month 1, month 2 and month 3
A mid-size corporate site takes 8 to 12 weeks. Large catalogs and stores take longer, and the schedule is set per stage in the scope. The order never changes.
- Month 1
Map and architecture
Keyword mapping by intent, a read of the competitors ranking today, an inventory of the current site, a URL map and wireframes for the key templates. This document drives everything else.
- Month 1
Screen design
Homepage, service or product page, listings, blog and forms. Responsive design drawn mobile first, with contrast and visible focus reviewed.
- Month 2
Development
The template in Next.js or WordPress, reusable components, form and CRM integrations, the content panel, and schema by page type.
- Month 2
Content in place
Copy, titles, meta descriptions and images go into the pages with the SEO consultant reviewing. Nothing ships with placeholder text.
- Month 3
Testing and cutover
Password-protected staging, PageSpeed and accessibility checks, form testing, a redirect map from the old site, and release in an agreed window.
- Month 3
Post-launch
Two weeks of daily indexing and error monitoring, sitemap submission, a traffic comparison before and after, and entry into the monthly management routine.
05Technical edge
Structured data written into the template
Structured data is how a site explains to a machine what is on the page: that this is a product with a price and availability, a service with a service area, a company with an address, a question with an answer.
It is the layer Google uses to build rich results and the layer language models lean on to be sure of what they are asserting when they cite a source. A new build is the one moment this comes cheap, because the markup is born in the template and covers the next thousand pages.
Each page type gets the schema it deserves, validated in staging before release. After launch, monitoring flags it when an update breaks the markup. The full practice sits in structured data.
- Organization and LocalBusiness with address, phone and opening hours
- Product with price, availability and ratings, where the store allows it
- Service with service area, for service and city pages
- Article, FAQPage and BreadcrumbList across the blog and inner pages
06Track record
Sites Netlinks has put live
Each project below started from a different problem, and all of them went through the same process: map before design, schema in the template, testing before cutover.
Master Milhas
A new 2026 site with a self-service sales flow and a client area. It now has 14 ranking landing pages, one of them on the first page of Google. See the Master Milhas case study.
Safetline
An industrial B2B catalog rebuilt in Next.js, with 298 SKUs organized by product family and internal search that returns the right item.
Planning
Two Next.js sites hosted on Google Cloud, sharing a component base while publishing independently for each brand.
CLM Controller
An international structure live: the .com in English, Spanish and Chinese, the .com.br for Brazil only, 2,013 redirects mapped and complete hreflang. See the CLM Controller case study.
SP Labor
A laboratory equipment store rebuilt and migrated to Google Cloud, with the homepage at 97 on mobile and 99 on desktop in PageSpeed.
Leo's Marble & Granite
A countertop business in Massachusetts, with product guides and inner pages built as a silo, in English. See the Leo's Granite case study.
07Risk
Replacing a site without losing what already ranks
If you already have traffic, the fear is legitimate: a badly handled cutover costs months of rankings. The drop almost always comes from the same handful of causes, and every one of them is avoidable.
What we do before any cutover: a full URL inventory of the current site, a 301 redirect map from every old address to its new one, a page-by-page content comparison so nothing that ranks gets dropped, canonical and hreflang checks, and a sitemap refreshed on release day.
After the switch, monitoring runs daily for two weeks: coverage in Search Console, crawl errors, positions on the highest-traffic pages, and speed. The full method sits in website migration. For CLM Controller, 2,013 redirects were mapped before the new build went live.
08Continuity
Launch day is the start, not the finish line
A website is software: it ages, collects plugins, receives content from different hands and breaks when browsers change. A project that ends on release day becomes, within twelve months, exactly the old site you just retired.
So every Netlinks build ships with an agreed continuity path:
- Monthly management, covering speed, updates, backups, security and on-page fixes. Detailed in website management.
- Managed hosting on Google Cloud, with automatic scaling and certificates that renew themselves. Detailed in web hosting.
- Content and search, so pages keep gaining ground in Google and in AI answers, with the SEO consulting team.
- Tracking in the Netlinks App, with rankings, traffic, PageSpeed, uptime and the delivery queue, 24 hours a day. Detailed in technology.
You decide how much of that stays with Netlinks. What we do not recommend is shipping a fast, secure site and leaving it without an owner the following month.
09The deliverable
What you receive
Finished work, approved by you in the App and shipped. Not a report that only describes the problem.
A site map by search intent
A document listing every planned page, the keyword it targets, estimated volume and the competitor ranking for it today.
Approved responsive design
Key screens drawn mobile first, with contrast, visible focus and navigation tested before development starts.
A site in Next.js or WordPress
Custom theme, clean code, no heavy page builder, and an admin your team can operate on its own.
Schema per page type
Semantic markup written into the template and validated in staging before release.
Redirect map
Every URL on the old site pointed at its new address, with verification after the cutover.
Performance report
PageSpeed and Core Web Vitals on key pages before and after, with history kept in the App.
10How it works
From the audit to the page going live
The same path on every project, with an owner and a date on each step.
- 01
Scoping call
Goals, audience, sales cycle, required integrations and who will publish content afterward. No commitment.
- 02
Map and wireframes
Keyword mapping, URL architecture and page skeletons, approved before design begins.
- 03
Design
Key screens in your brand system, reviewed on desktop and on a 360-pixel-wide phone.
- 04
Development
Template, components, integrations, schema and content, with partial releases visible in staging.
- 05
Cutover
Redirects, sitemap, final checks and release in an agreed window, with daily monitoring for two weeks.
- 06
Management
Entry into the monthly routine of speed, security, updates and continuous on-page improvement.
11Who leads
Who leads your project
The three of them own the process and manage the team on every account. No senior who shows up at kickoff and disappears: they sign off on the plan, review the work and talk to your team.
Digo Garcia
Founder and CAIO
Over 20 years in digital. Built and scaled Letras.mus.br, then worked at Méliuz and in the joint venture with Globo.com. Owns AI, technical SEO and engineering inside every project.
Letras.mus.br · Méliuz · Globo.com
André Mousinho
Chief SEO Officer
Comes from Rock Content, Tray/Locaweb and LWSA. Designs the keyword mapping, the content architecture and the GEO strategy that turns a brand into the answer.
Rock Content · Tray/Locaweb · LWSA
Gabriel Raposo
Chief Authority Officer
Leads link building and digital PR at Netlinks and ran, for Netlinks, the authority programs for BTG Pactual and Agibank. Before that, a career at Ambev. Owns the authority that holds up both rankings and citations inside AI answers.
Link building and PR · BTG Pactual and Agibank for Netlinks
And the team behind them: Nathália Barcala (cofounder and COO, governance), Roberto Murta (CTO), Marcelo Ligere (senior advisor, 30+ years, formerly Grupo Globo) and Alfred, the artificial intelligence that runs the day to day: delivery queue, reporting and 24/7 support on WhatsApp.
12Who it is for
Where this work pays off the most
Companies replacing a site
You have the brand and the traffic, and you know the current site works against you. The job starts by protecting what ranks and fixing what blocks.
B2B catalogs and stores
Hundreds or thousands of items, internal search that has to work, and product schema that turns into rich results.
Multilingual operations
Companies selling in more than one country, needing one URL per language, correct hreflang and copy written for each market.
13Case studies
Results with a name, a number and a date
Real projects, with what was done and what changed. No generic charts and no promises of a position.
FAQ
Frequently asked questions
How long does web development take at Netlinks?
A mid-size corporate site runs 8 to 12 weeks, from keyword map to cutover. Large catalogs and stores take longer, and the schedule is set per stage in the scope, because the bottleneck is usually content approval rather than code.
Do you build in WordPress or in Next.js?
Both. WordPress on a custom theme when your team publishes daily and needs full autonomy in the admin. Next.js when the project calls for performance, integrations or a multilingual structure. The call is made in the scoping meeting, with the comparison table on the table.
Do you use Elementor, Divi or another page builder?
We do not use heavy page builders. They make the first week easier and charge it back in load time, duplicated markup and plugin lock-in. We deliver a custom theme with editable blocks your team can use without breaking the layout.
Does the new site come optimized for SEO?
Yes, which is why the keyword map opens the project. URL architecture, titles, meta descriptions, images, speed, structured data and the sitemap are all in scope. Ongoing content and authority work is the next step, in SEO consulting.
Will I lose Google rankings when I switch sites?
Not when the cutover is run with a URL inventory, a 301 redirect map, a content comparison and daily monitoring afterward. For CLM Controller, 2,013 redirects were mapped before the switch.
Who writes the copy?
Netlinks writes it, reviewed by the SEO consultant, or we work with material your team already has. Either way, every page gets a title, meta description and heading structure aligned to the keyword it targets.
Is hosting included?
It can be. We offer managed web hosting on Google Cloud, and we also hand the site over to run on infrastructure your company already uses. What we will not do is deliver without naming who owns the server.
How much does a website cost?
It depends on page or SKU count, integrations, how much new content is needed and the platform. The diagnosis carries no commitment, and the proposal comes with scope and a stage-by-stage schedule so you can weigh investment against opportunity.
Keep reading
Related services
Next step
Get a diagnosis of your case
Tell us what your company sells and to whom. One of the three looks at your scenario, points out what is holding organic back today and shows where we would start.
- A review of your site and your market, with no commitment
- An answer from a senior specialist within 24 business hours
- A direct conversation: what can be done, in what order and how deep
Prefer WhatsApp?
Chat directly with a Netlinks Expert on WhatsApp.
Rather talk now? WhatsApp is answered by the team, with Alfred covering the rest of the day.
Talk to an Expert
Fill out the form and we will get back to you within 24 business hours.