Netlinks

OnWeb · Web engineering and cloud

Website management with someone on call.

Monthly maintenance for the site you already run: speed, updates in an agreed window, tested backups, protection against intrusion, uptime checks every 5 minutes and on-page fixes. You see all of it in the App and hear about problems before your customers do.

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

A monitoring wall with several uptime and performance graphs in green, dark room

01Overview

Website management

Website management is the retainer that keeps a live site fast, secure, current and online. It is website maintenance run on a routine rather than by ticket: an agreed update window, a backup someone has already restored once, and monitoring that speaks up before a customer calls to complain.

Most companies discover they need this the expensive way. The site sits down for two days over a holiday, or an odd redirect starts hitting mobile visitors, or the contact form silently stops sending and nobody notices for three weeks. None of that shows up in a traffic report in time.

Netlinks runs management through OnWeb, the group engineering practice, with the same team that answers for search on your account. That is why the package does not stop at the technical layer: it also carries the on-page work search demands, from the page title to the structured data that broke in the last update.

5 min
between uptime checks
97 and 99
PageSpeed mobile and desktop on the SP Labor homepage
200+
companies served since 2017
24h
of WhatsApp support with Alfred and the team

02Scope

What website management covers

The base package is the same for everyone and grows with the platform and the size of the site. Nothing inside the agreed scope is billed as a separate ticket.

Speed and Core Web Vitals

Monthly measurement of your highest-traffic pages in PageSpeed Insights and in Search Console field data, with fixes prioritized by impact.

Security and hardening

Permissions reviewed, credentials kept out of the codebase, a filtering layer in front of the site and file-change scanning.

Restorable backups

Daily copies of the database and files, with periodic restore tests. A backup nobody has restored is not a backup.

Updates in a window

Core, theme, plugins and dependencies updated in staging, validated, and only then published, at an agreed time.

Uptime monitoring

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

On-page fixes

Titles, meta descriptions, headings, missing image alt text, broken internal links and broken schema enter the monthly queue.

03Performance

Speed: what we measure and the order we fix it in

A PageSpeed score is a symptom, not a diagnosis. What matters is field data: how long your real visitor, on their phone, on their network, waited for the page to become usable. That number lives in Search Console and it is the one Google uses.

Fixes follow an order, because changing everything at once burns hours and breaks layouts. Images first, usually half the weight of the page. Then fonts and third-party JavaScript, the trackers and widgets someone installed and nobody removed. Then caching and the server. Template refactoring comes last.

At SP Labor, that sequence compressed 6,433 images from 4.0 GB to 1.4 GB, and the homepage closed at 97 on mobile and 99 on desktop in PageSpeed. The full story is in the SP Labor case study, and the dedicated practice is website optimization.

  • LCP, INP and CLS measured in the field and in the lab, month over month
  • Images converted to modern formats and served at the size actually needed
  • Third-party scripts inventoried: who installed them, why, and what they cost in milliseconds
  • Caching and CDN configured to match the platform
Macro shot of a laptop screen edge with a page loading extremely fast, light streaks

04Security

Protection against intrusion, before and after the incident

A compromised corporate site rarely goes offline. The attacker does something worse: injects third-party pages on your domain, sends mobile visitors into a scam, and burns authority you spent years building. By the time anyone notices, traffic has already dropped.

The prevention routine is dull and it works: plugins and core kept current, passwords out of versioned config files, least privilege per user, two-factor on the admin, tested backups, and a filtering layer deciding what reaches the server.

Once an incident has happened, the playbook changes: identify the entry point, clean the infected files, remove the injected pages, rotate every credential, request reprocessing from Google, and harden so it does not repeat. That is what ran for Nobre, a gift and hamper holding company, on a ClickFix-style intrusion cleanup followed by a store audit. The case study is Nobre.

Data center corridor lined with server racks and thin lime and teal light

05Cadence

How website maintenance runs through the month

The cycle never changes, only the improvement queue does. You know which week each thing happens in, and you are never surprised by an update during peak hours.

  1. Week 1

    Check

    Last month's uptime, PageSpeed on key pages, Search Console errors, outdated versions, certificate validity and a backup restore test.

  2. Week 2

    Improvement queue

    Technical fixes and on-page work prioritized with the SEO consultant go into production with deadlines.

  3. Week 3

    Update window

    Core, theme, plugins and dependencies updated in staging first, with layout and form checks before anything ships.

  4. Week 4

    Report

    Availability for the month, speed trend, what was fixed, what was blocked and next month's plan, all in the App.

  5. Always

    Monitoring and support

    Uptime every 5 minutes, alerts on WhatsApp, and an open channel with Alfred, the AI that runs our queue, 24 hours a day, with the human team in the same group.

  6. Incident

    On call

    Downtime, intrusion or a traffic spike each have a defined path: restore, clean up, harden, and a report written in language a board can use.

06Comparison

With management, without it, or with a vendor on tickets

The cost of having no management never lands in the vendor spreadsheet. It lands in lost traffic, a form that stopped sending, and the week burned when somebody has to understand the site from scratch.

Netlinks managementNo managementVendor on tickets
UpdatesIn an agreed window, tested firstWhen someone remembers, straight to productionOnly once something breaks
BackupsDaily, with restore testedWhatever the host keeps, unvalidatedDepends on the plan
Site downAlert in 5 minutes, team on callYou hear it from a customerOpen a ticket and wait
SpeedMeasured and improved every monthDegrades on its own with every new pluginOut of scope
On-page and schemaReviewed in the cycle, alongside SEOBreak with nobody watchingNot part of the job
CostMonthly and predictableZero until the incidentHourly, always under pressure

07Visibility

What you see in the App, without asking for a report

Website management is usually sold as a black box: you pay the retainer and get a generic PDF at month end. At Netlinks, what the team does appears in the Netlinks App in real time, 24 hours a day:

  • Availability, with the history of every check and every outage logged, duration included.
  • PageSpeed and Core Web Vitals for your highest-traffic pages, month over month, so you can see the line move.
  • Delivery queue: what is in production, what is waiting for your approval and what already shipped.
  • Alerts: certificate about to expire, a new crawl error, a meaningful ranking drop, broken schema.
  • History: everything changed on the site, when and by whom, so the origin of a change is never in doubt.

Support lives on WhatsApp, in a group with your team and ours, with Alfred answering 24 hours a day and escalating to a human when the case calls for it. The full picture is in technology.

08Platforms

Which platforms we work on

Management covers the site you already have, without demanding a platform change as a condition to start:

  • WordPress and WooCommerce, custom theme or not, including sites inherited from other vendors.
  • Next.js and other code projects, with versioned deploys and a staging environment.
  • Closed platforms such as Shopify, VTEX and Tray, within what the platform allows: on-page, schema, theme speed, images and integrations.
  • Sites on dedicated servers or in the cloud, including Google Cloud managed by Netlinks itself, detailed in cloud management.

When the diagnosis shows the current site costs more to keep than to replace, we say so with the number attached, and the conversation moves to web development. Until that day comes, the job is keeping what exists fast, secure and online.

09The deliverable

What you receive

Finished work, approved by you in the App and shipped. Not a report that only describes the problem.

Monthly health report

Availability, speed, updates applied, incidents and next month's plan, in language a board understands.

Uptime monitoring

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

Tested backups

Daily copies of database and files, with restores validated periodically in a separate environment.

Update window

Core, theme, plugins and dependencies updated outside peak hours, always after testing.

On-page corrections

Titles, meta descriptions, headings, image alt text, broken internal links and schema fixed within the cycle.

Incident response

Downtime, intrusion or traffic spikes with a defined response path and a written report afterward.

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

    Diagnosis of the current site

    A read of the platform, plugins, hosting, speed, security and Search Console errors. No commitment.

  2. 02

    Stabilization plan

    Month one is usually cleanup: backups, the backlog of updates, critical error fixes and server tuning.

  3. 03

    Into the routine

    The maintenance window, the owners and the alert channels are agreed, and the shared WhatsApp group is created.

  4. 04

    Monthly cycle

    Check, improvement queue, update window and report, always in the same weeks.

  5. 05

    Continuous improvement

    Speed, accessibility, structured data and on-page work advance month over month, prioritized with the SEO team.

  6. 06

    Quarterly review

    Capacity, infrastructure cost, technical debt and what needs to become a project in 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

Companies with no technical team

The site was built by a vendor who disappeared, nobody knows where the hosting lives, and every change turns into a saga. Management takes all of it over.

Stores that cannot go down

E-commerce where an hour offline is lost revenue and an intrusion is brand damage. Monitoring and on-call become a requirement.

Marketing teams that want autonomy

Teams that need to publish campaigns and new pages without waiting on a developer's calendar, with someone guaranteeing the technical base.

FAQ

Frequently asked questions

What does website management cover?

It is the monthly retainer that keeps a site fast, secure, current and online. It covers speed, updates in an agreed window, restorable backups, security and incident response, uptime monitoring and the on-page fixes search demands.

What is the difference between website management and hosting?

Hosting is where the site runs: server, CDN, certificates and scaling. Management is what happens to the site running there: updating, measuring, fixing, protecting and improving. You can buy both or just one. See web hosting.

Will you take over a site built by another agency?

Yes, and it is the most common case. Month one is usually cleanup: access organized, backups created, the backlog of updates applied with testing, and whatever is broken repaired. After that the routine settles.

How often do you update plugins and core?

Monthly, in a window agreed with your team, always after validation in staging. A critical security patch is the exception and ships outside the cycle, with notice.

What if my site gets hacked?

There is a defined path: identify the entry point, clean the files, remove injected pages, rotate credentials, request reprocessing from Google and harden the site. An incident report follows. That is how the ClickFix-style intrusion cleanup ran at Nobre.

Will monitoring warn me before a customer does?

Yes. The site is checked every 5 minutes and the alert reaches the shared WhatsApp group once it stays down past 5 minutes. Expiring certificates and new crawl errors trigger warnings too.

Does management include building pages and publishing content?

It includes publishing and edits inside the agreed scope. Content production at scale is a separate practice, handled by the content team within SEO consulting.

How much does website management cost?

It depends on the platform, the size of the site, page volume and the level of on-call the operation requires. The diagnosis of your current site carries no commitment, and the proposal comes with a detailed 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.