Skip to content
Menu
Talk on WhatsAppPortuguês

Websites and landing pages

Websites and landing pages built to convert

Fluxo builds two kinds of page with different jobs: the institutional website, which exists to be found in search and carry brand credibility, and the landing page, which exists to convert traffic from a specific campaign. Both are built in Next.js with static pages, delivering fast loads, JavaScript-free readable content and full SEO control. You own the code, with no platform subscription.

Talk on WhatsApp
  • Next.js
  • Static pages
  • Core Web Vitals
  • Landing page
  • Institutional site
  • Accessibility
  • Structured data
  • Responsive

What is included

What you receive

  1. 01

    Custom design, not a template

    A layout drawn from your visual identity. A recoloured template reads as a template, and visitors notice before reading the first line.

  2. 02

    Genuinely static pages

    HTML ready at the server, no waiting for JavaScript to assemble the screen. That is what earns high Core Web Vitals and what makes pages readable by AI crawlers.

  3. 03

    SEO from the factory

    Titles, descriptions, canonicals, sitemap, robots and structured data from the first page. Not a later phase, part of the build.

  4. 04

    Accessibility

    Verified contrast, keyboard navigation, visible focus and content that works without JavaScript. Beyond being correct, it is the same work that helps indexing.

  5. 05

    Measurement configured

    Analytics, conversion events and CRM integration wired up on delivery, so campaigns never launch on top of missing tracking.

  6. 06

    No platform rent

    The code is yours, hosted on your account. You are not locked into a subscription just to keep your own site online.

Process

How we run it

Talk on WhatsApp
  1. 1

    Architecture

    We define which pages exist and what each answers, before any design. A beautiful site with wrong architecture does not rank.

  2. 2

    Content

    We write the copy for every page. Layouts filled with placeholder text always break when real content arrives.

  3. 3

    Design and build

    Interface designed and implemented in waves, highest commercial value page first.

  4. 4

    Audit and handover

    Performance, accessibility, technical SEO and JavaScript-off reading verified before launch. Then a walkthrough for your team.

Institutional site or landing page?

They are different products, and confusing them is expensive. An institutional site has many pages and lives on organic search. A landing page has one page, no menu, and lives on paid traffic. Neither replaces the other.

Institutional siteLanding page
GoalBe found and build credibilityConvert campaign traffic
Number of pages10 to 501
Navigation menuYesNo, deliberately
Traffic sourceOrganic search and AIGoogle Ads and ChatGPT Ads
Typical timeline4 to 8 weeks1 to 2 weeks
How it is measuredOrganic traffic and positionConversion rate and cost per lead

A landing page drops the menu on purpose: every link that does not lead to conversion is an exit. On an institutional site the menu is essential, because the visitor came to research, not to decide right now.

Why Next.js instead of WordPress or a visual builder

The choice is not ideological, it is consequential. Visual builders generate heavy pages that depend on JavaScript to display text. That hurts Core Web Vitals and, more seriously, leaves the page nearly empty for language model crawlers, which do not execute JavaScript.

WordPress remains a reasonable choice when the client team publishes heavily and already knows the tool. In those cases we say so instead of pushing what we prefer.

What makes a page convert

  • A clear promise above the fold: the visitor must know in five seconds what you do and for whom.
  • One primary action, repeated. Three competing buttons split the decision and drop conversion.
  • Proof before the ask: a number, a testimonial or a concrete case before the form, never after.
  • Speed: every extra second of load time measurably reduces conversion, and the effect is larger on mobile.
  • Short forms: every extra field costs completions. Ask only for what you will actually use in the first conversation.

Who maintains the site afterwards

Delivery includes training and project documentation. From there you can maintain it in house, hire anyone you like, or continue with Fluxo on monthly maintenance. Because the code is yours and hosting sits in your account, leaving does not mean losing the site.

Frequently asked questions

How long does it take to build a site?
A landing page is ready in 1 to 2 weeks. An institutional site takes 4 to 8 weeks, depending on page count and how fast content gets approved. What delays website projects is rarely development, it is client material and feedback.
Can I edit the site afterwards?
Copy and images live in content files separated from the code, and you get training to edit them. If your operation publishes heavily, we assess together whether an editing panel is worth its added cost and complexity.
Does the site come optimized for Google?
Yes. URL structure, titles, descriptions, structured data, sitemap, robots and speed are part of the build. That is different from ongoing SEO consulting, which is the work of earning positions over months.
Do you build online stores?
We build product showcases with WhatsApp ordering, which covers most local business cases. Full checkout with payments and inventory we assess case by case, because an existing platform often serves better than custom development.
What does hosting cost?
Static sites like ours typically run inside Vercel free tier for normal local or B2B volume. If traffic grows enough to require a paid plan, the cost is in the tens of dollars per month, paid by you directly to the provider.

Services that usually pair with this