Netlinks

OnWeb · Web engineering and cloud

Web engineering and cloud that holds up your SEO.

A fast, secure, machine-readable site is not a finishing touch on an SEO program: it is the floor it stands on. OnWeb is the Netlinks engineering practice, covering builds, management, hosting and Google Cloud with the same team that answers for your rankings.

We work in English, Portuguese and Spanish. Headquarters in Belo Horizonte, Brazil.

Data center corridor lined with server racks and thin lime and teal light, an engineer walking away

01Overview

Web engineering

Web engineering is the practice that builds and maintains the machine your content lives in: the code of the site, load speed, protection against intrusion, the structured data AI models read, and the infrastructure that survives a traffic spike. At Netlinks this practice has its own name: OnWeb.

OnWeb does four things: it builds websites in Next.js and WordPress, it manages sites that already exist, it hosts on managed infrastructure, and it runs Google Cloud for companies already there. Same delivery standard, same tracking inside the Netlinks App.

The value of having engineering inside an SEO agency shows up in week three, when the consultant needs to change URL architecture, ship structured data in the product template and cut 1.2 seconds off load time. Instead of filing a ticket with a vendor who has never seen the plan, the work goes straight to the team that wrote the code.

200+
companies served since 2017
97 and 99
PageSpeed mobile and desktop on the SP Labor homepage
4
practices: builds, management, hosting and cloud
24h
of monitoring in the App, with alerts on WhatsApp

02The brand

OnWeb, the engineering arm of the group

OnWeb is the Netlinks group brand for web engineering and cloud. It grew out of the technical team that already carried our SEO projects and became a practice of its own, because sites and infrastructure stopped being a detail. They are where positions are won and lost.

Hiring OnWeb means hiring the team that also answers for the search side of your account. The developer shipping the template knows why that H1 exists, why the URL sits at that depth, and why the product schema needs the availability field filled in.

The brand has its own site at onweb.com.br and operates inside Netlinks, under the same governance, the same contract and the same reporting. You are not managing two vendors.

  • Sites in Next.js and WordPress on a custom theme, with no heavy visual page builder
  • Managed infrastructure on Google Cloud with Cloud Run, Cloud SQL and a CDN
  • Uptime, PageSpeed and Core Web Vitals monitoring inside the Netlinks App
  • Security remediation and malware cleanup, with hardening after the incident
Layered translucent panels floating over a dark surface with teal light, representing cloud infrastructure

03Scope

The four engineering practices

The practices can be bought together or on their own. Most clients start with one and add the others once the bottleneck moves.

Web development

A new site in Next.js or WordPress, with the architecture drawn by the SEO team before the first line of code. Details in web development.

Website management

Monthly maintenance of the site you already run: speed, updates, backups, security, uptime and on-page fixes. Details in website management.

Web hosting

Managed hosting on Google Cloud with a CDN, SSL, automatic scaling and nobody else sharing your server. Details in web hosting.

Google Cloud management

Migration, cost, security and observability for companies already running in the cloud. Details in cloud management.

Migration without losing rankings

Platform, domain or URL structure changes with a full redirect map and daily monitoring afterward. Run alongside website migration.

Performance and Core Web Vitals

Diagnosis and repair of LCP, INP and CLS on a live site, without rebuilding it. Run alongside website optimization.

04Cadence

How web engineering runs through the month

Engineering without a calendar turns into a ticket queue. Every OnWeb contract runs a fixed cycle, with an agreed maintenance window and a report you can read without a translator.

  1. Week 1

    Technical check

    Uptime for the month, PageSpeed on your highest-traffic pages, crawl errors in Search Console, plugin and theme versions, certificate validity and a restorable backup.

  2. Week 2

    Fixes and improvements

    Tasks prioritized with the SEO consultant go into production: template, schema, images, caching, redirects, accessibility.

  3. Week 3

    Update window

    Core, plugins and dependencies updated in staging first, validated, and only then pushed to production.

  4. Week 4

    Report and plan

    What changed, how much faster the site got, what was blocked and what comes next month. All visible in the App.

  5. Always

    Monitoring

    Uptime checked every 5 minutes, with an alert the moment the site stays down for more than 5 minutes, straight into the shared WhatsApp group.

  6. Incident

    On call

    Downtime, intrusion or a traffic spike each have a defined path: restore, clean up, harden, and a written account of what happened.

05Performance

Speed is ranking, and it is revenue

A slow site loses twice. It loses in Google, because Core Web Vitals feed the page experience signals. And it loses at the till, because every extra second of load time drags down conversion on any store or form.

Speed work starts with honest measurement: field data from Search Console, taken from real users, not only the lab score in PageSpeed Insights. Then comes the right order: images, fonts, third-party JavaScript, caching, server, and only at the end, template refactoring.

At SP Labor, an e-commerce operation selling laboratory equipment, the engineering package compressed 6,433 images, from 4.0 GB down to 1.4 GB, and left the homepage at 97 on mobile and 99 on desktop in PageSpeed. The full story is in the SP Labor case study.

Macro shot of a laptop screen edge with a page loading extremely fast, light streaks

06Comparison

Engineering inside the agency, a web shop, or a freelance vendor

All three setups exist and all three work in some context. What changes is who answers when the site goes down, and who makes sure a technical decision helps rankings instead of hurting them.

OnWeb inside NetlinksWeb design shopFreelance vendor
Who sets the architectureSEO consultant and engineers together, before any codeDesign team, with SEO reviewing afterwardWhoever is available
Structured dataIn the template, validated and monitoredA generic plugin, when it appears at allOut of scope
After launchMonthly management, uptime, updates and securityEngagement ends at deliveryBilled by the hour
InfrastructureManaged Google Cloud, with cost reviewed monthlyResold shared hostingClient account, no clear owner
When the site goes downAlert within 5 minutes and an on-call teamA ticket during business hoursDepends on their calendar
ReportingNetlinks App, 24 hours a dayMonthly PDFA loose email

07Security

What a compromised site actually costs

An intrusion on a corporate site rarely takes the page down. It does something worse: it injects third-party pages, redirects mobile visitors into scams, and spends the authority you spent years building. By the time Google notices, the traffic loss has already happened.

Engineering handles this in three phases:

  • Before. Updates in an agreed window, credentials kept out of the codebase, least-privilege access, a backup someone has actually restored, and a filtering layer in front of the site.
  • During. Identify the entry point, clean the infected files, remove the injected pages and request reprocessing from Google.
  • After. Hardening, credential rotation, file-change monitoring and a written incident report a board can read.

That is the exact sequence we ran for Nobre, a Brazilian gift and hamper holding company, on a ClickFix-style intrusion cleanup followed by a store audit in 2026. The case study is Nobre.

08Integration

Engineering and SEO on the same plan

Most SEO recommendations die in a development backlog. When both sides sit in the same company, the request ships as a task with a written spec rather than a suggestion in a spreadsheet.

In practice, that is what integration unlocks: structured data applied in the template instead of page by page, redirects mapped before a migration, images in the right format from upload onward, correct hreflang across languages, and a sitemap that reflects what actually exists.

The search-side technical practices live in technical SEO and structured data. Engineering is what puts both of them live.

A developer's dual monitors showing blurred code and a page speed gauge, mechanical keyboard on the desk

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 in Next.js or WordPress

Custom theme, clean code, architecture agreed with the SEO team, and an admin your marketing team can actually operate.

Managed infrastructure

Google Cloud with Cloud Run, Cloud SQL, CDN and managed certificates. Automatic scaling at peak, cost reviewed every month.

Uptime monitoring

Checks every 5 minutes, with an alert in the shared WhatsApp group when the site stays down past 5 minutes.

A security routine

Updates in an agreed window, restorable backups, hardening, and incident response with a written report.

Measured performance

PageSpeed and Core Web Vitals for your highest-traffic pages, with history inside the App.

Structured data in the template

Organization, Product, Service, Article, FAQ and Breadcrumb marked up in code and validated before release.

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.

  1. 01

    Technical diagnosis

    A read of the current site, the hosting, the infrastructure bill and what is blocking SEO today. No commitment.

  2. 02

    Scope and priority

    It becomes clear what is a repair on the current site and what is a new build, with effort and expected gain attached.

  3. 03

    Staging

    Everything is built and validated off the live site, behind a password-protected address, never straight into production.

  4. 04

    Controlled release

    Redirect map, indexing checks, and daily monitoring through the first two weeks.

  5. 05

    Monthly management

    Speed, security, updates, backups and on-page fixes enter the monthly cycle.

  6. 06

    Quarterly review

    Cloud spend, capacity, technical debt and what belongs on the roadmap for the next 90 days.

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 at Netlinks

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 at Netlinks

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 at Netlinks

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.

12Who it is for

Where this work pays off the most

A company with a stuck site

The site exists, but every change depends on a vendor, takes weeks and breaks something else. Engineering takes over the code and the routine.

Large stores and catalogs

E-commerce and B2B catalogs with hundreds or thousands of items, where speed, internal search and product schema turn into revenue.

Teams already in the cloud

Companies on Google Cloud that want spend under control, security reviewed, and someone on call when the alert fires.

FAQ

Frequently asked questions

What does web engineering cover in practice?

It is the practice that builds and maintains the technical layer: site code, speed, security, structured data and infrastructure. At Netlinks that practice is OnWeb, and it works next to the SEO team, because architecture decisions move rankings.

Do I have to buy all four practices together?

No. You can take only the build, only monthly management, only hosting, or only Google Cloud administration. Most clients start with one and add the others once the bottleneck moves.

Will you work on the site I already have?

Yes. WordPress, Next.js, Shopify, VTEX, WooCommerce or a custom system. The diagnosis says whether the right move is repairing what exists or rebuilding, with the number that justifies the call.

Do you serve clients who are not on an SEO retainer?

We do. Plenty of companies come in through a build or through monthly management and only later add the search practices. It happens the other way around too.

What happens when the site goes down?

Monitoring checks the site every 5 minutes. Once it stays down past 5 minutes, the alert lands in the shared WhatsApp group. From there it is restore or repair, followed by a written account of what happened.

Can you migrate platforms without losing rankings?

Yes, and it is one of the most requested projects. The work starts with a URL inventory and a redirect map, runs in staging, and is monitored daily after the switch. See website migration.

Who watches the cloud bill?

The engineering practice itself. Rightsizing oversized machines, billing anomaly alerts and a monthly cost report by service are part of cloud management.

How much does a web engineering project cost?

It depends on the size of the site, the number of pages or SKUs, the platform, and how much of the operation stays with Netlinks. The diagnosis carries no commitment and pricing comes with the scope.

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.