OnWeb · Website and cloud engineering
Web development with SEO inside the code, not after it.
Most sites get SEO as a patch after they are done: plugin after plugin trying to fix an architecture that was already wrong. OnWeb develops with the SEO team inside the project, deciding URL structure, hierarchy and schema alongside the code.
We work in English, Portuguese and Spanish. Headquarters in Belo Horizonte, Brazil.
01Overview
Web development agency
Web development decides, line of code by line of code, whether Google and AI models can read the whole site. Route structure, server response time, how a page loads an image or a script: each of these technical decisions has a direct impact on SEO, well before any content enters the picture.
OnWeb, the engineering front of the Netlinks group, develops with that order reversed: the SEO team takes part in the architecture decision, defines what needs server-side rendering, and specifies the schema alongside whoever writes the code, not after the site is already live.
That applies both to a new Next.js project and to integration with a system the client already runs: an ERP, a CRM or an e-commerce platform. The Google Cloud migration at SP Labor, for example, cut technical errors from 753 to 326 pages in a single audit.
There is no single right stack for everyone. There is the right stack for your page volume, your publishing frequency and the system your team already runs today. That is why the first stage of any project is technical, not commercial.
- 200+
- companies served since 2017
- 753 to 326
- pages with errors in the SP Labor technical audit
- 97/99
- mobile/desktop PageSpeed of the SP Labor homepage after the work
- 24h
- of project tracking in the App
02Edge
What changes when SEO enters development
A developer with no SEO guidance solves the problem in front of them: making the page work. They do not know, and do not need to know, that this URL structure will create duplicate content, or that this script load will stall Core Web Vitals.
- Rendering decided page by page, not by a single default: whatever needs fast indexing ships server-rendered, whatever is only interactive can load client-side.
- URL structure locked before coding, so a mass redirect is never needed after launch.
- A performance budget set for the project: how much JavaScript, how much image weight, what load-time target.
- A schema spec handed to the developer, not left for a generic plugin to guess at afterward.
That set of technical decisions is what separates a fast site from a site that only looks fast in the demo.
03Scope
What OnWeb develops
Next.js sites
For projects that need performance, integration and multiple languages.
Integration with existing systems
ERP, CRM and e-commerce platforms connected to the institutional site.
Cloud migration
Infrastructure on Google Cloud, fully designed in cloud management.
Performance fixes
Diagnosis and adjustment of Core Web Vitals on already published sites.
Structured data in the code
Schema applied in the template, not glued on by a plugin.
Security and monitoring
Protection against intrusion and alerts for outages or technical errors.
04Technology
How we decide the project's stack
The right question is not which technology is best in the abstract, it is which one solves your case: page volume, publishing frequency and the in-house team available.
| Next.js | Integration with an existing system | |
|---|---|---|
| Best for | A new site, institutional or catalog, with performance as the priority | A company already running an ERP or CRM that needs the site connected |
| Typical timeline | Full project in a matter of weeks | Depends on the integration's complexity |
| Technical SEO | Native, decided from the architecture up | Depends on what the source system allows you to adjust |
05Checklist
What we check before calling a site ready
Before any project goes live, it passes a fixed technical review, so no common problem slips between staging and production:
- Correct rendering on every route, with no page that depends on JavaScript for Google to read its main content.
- Server response time within target, measured under load, not on a single isolated request.
- Redirects configured for every URL that changed, with no broken link inherited from the previous site.
- Schema validated in staging, never applied directly to production without a check.
- A valid security certificate and correct HTTP headers, an item that tends to slip in rushed projects.
This checklist is what separates a calm launch from a Monday spent fixing an error that was avoidable in the first place.
06Applied
Development and migration in practice
In the SP Labor case, a WooCommerce store, the Google Cloud migration came with a full technical audit: crawl errors dropped from 753 to 326 pages, warnings from 2,803 to 1,020, the sitemap shrank from 383 to 20 files, and 6,433 images were compressed from 4.0 GB to 1.4 GB.
The technical result showed up directly in PageSpeed: 97 on mobile and 99 on desktop for the homepage. That is the kind of work that only happens when development and SEO sit at the same table, not with different vendors.
07The deliverable
What you receive
Finished work, approved by you in the App and shipped. Not a report that only describes the problem.
Technical spec
What changes, where and why, delivered before the code starts.
Published site or integration
With measured performance and schema applied.
Performance report
PageSpeed and Core Web Vitals tracked in the App.
Ongoing technical support
Maintenance and fixes available after launch.
08Who 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
Comes from Ambev and Agibank. Owns link building, digital PR and the authority that holds up both rankings and citations inside AI answers.
Ambev · Agibank
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.
09Who it is for
Where this work pays off the most
Company with a slow site
The site exists, but it takes too long to load and loses ranking because of it.
Operations that need systems integrated
An ERP or CRM that needs to talk to the institutional site or the store.
A technical team with no SEO specialist
Knows how to code but not what to prioritize to improve ranking.
A company migrating infrastructure
Needs to switch server or provider without losing ranking along the way.
10Case 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
What is a web development agency?
It is the agency responsible for building and optimizing sites and integrations for specific business goals. OnWeb ties that development to the technical SEO layer from the start of the project.
Why optimize the site during development instead of afterward?
Because architecture decisions, like URL structure and rendering, cost three times more to fix after publishing than to get right in the project.
Do you build only new sites, or integrations too?
Both. We build complete sites and also integrations with systems the client already uses, like ERP, CRM and e-commerce platforms.
Can my current site be fixed, or do I need a new project?
It depends on the existing structure. A technical audit shows whether fixing what exists is worth it or whether the cost of maintaining it outweighs starting over.
Do you handle server or cloud migration?
Yes. The full design of migration and infrastructure management is in cloud management.
How do you guarantee performance after launch?
With ongoing PageSpeed and Core Web Vitals monitoring, visible in the App, and an alert when something drifts from expected.
Does this work include security against intrusion?
Yes, the management scope includes protection and monitoring against intrusion, detailed in website management.
Do you develop for technical teams that already exist in-house?
Yes. In that format, OnWeb takes on a specific slice, like performance or migration, and works alongside the in-house team, without replacing it entirely.
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.