What we build

Websites

Company websites and B2B platforms on WordPress or custom builds, with design, audits and speed optimisation.

Website development →

What we run

SEO

Visibility in Google and in language models. One team looks after search, your business profile and what ChatGPT and Gemini say about your brand.

Search engine optimisation →

What we run

Advertising and campaigns

Campaigns judged on net profit after returns and cost of goods, not on the ROAS in the ad platform. Creative is made in-house, so it never waits for a third supplier.

Digital marketing agency →

What we run

Analytics and data

Measurement first, decisions second. Ad, store and warehouse data in one place, so a budget conversation takes fifteen minutes, not three meetings.

Web analytics for e-commerce →
Home/Services/Websites//Astro websites

Astro websites built for Google and AI answers

A modern website delivers all of its content in the first response from the server. It is read by more than people: before anyone clicks a result, a search engine's bot and a language model's bot fetch the page. Most of the second kind never run scripts and never wait for a slow server. We build the site so both get the full page instead of a skeleton, while a person still sees it quickly on a phone.

What a bot fetches before anyone clicks: full content in HTML, a Markdown twin, an llms.txt index and bot policy controlled by the site owner Astro 6-12 weeks a typical company website project
Trusted by
Technology partners
Where we start

Three places where a website loses before anyone sees it

None of them show up in a campaign report or an analytics panel: there is no visit, so there is nothing to count.

The model answers, and does not mention you

A client asks an assistant for a supplier and gets three names. If your site cannot be read by a machine, you are not one of the three, even if you rank high in a search engine.

The bot fetches an empty page

Content drawn in by a script does not exist for most model bots. The server hands over a skeleton, the bot saves a skeleton, and that is all that is left of your offer in its memory.

A slow site loses the enquiry before the offer

On a phone with a weak signal, the first second counts. Google's threshold for a good page is 2.5 seconds to show the main content, and every visit that does not last that long is lost, along with its cost in the campaign.

Definition

What Astro is, and how it differs from sites built with JavaScript frameworks

Astro is an open-source framework for building websites, where the finished HTML is generated once, at publish time, rather than on every visit. A site built this way delivers full content in the first server response, with no requirement that a visitor run scripts, and also exposes that content in a machine-readable form. A model does not look at a page, it fetches text. It gets either the full thing or a skeleton, and that is decided by how the site is built, not by how much editorial work went into it.

Sources: the llms.txt specification · Core Web Vitals in Google's documentation · Astro's documentation

Content in the first response

The HTML is ready before anyone asks for it. There is no database that might respond slowly, and no requirement for a bot to execute code.

A machine-readable version

Every page has a Markdown twin, and an llms.txt index guides a model through the site. The JustIdea site exposes this for over 400 pages: every address with a .md ending returns the page's plain text.

You decide who gets access

Letting a specific bot in or blocking it is a rule enforced at the network edge, not a request in a text file that can just be ignored.

Scope

What exactly we do when building a modern website in Astro

  • ✓ Workshop and content map: which questions the site needs to answer, and for whom
  • ✓ Design of the views, signed off one by one before coding starts
  • ✓ Build in Astro: full content in the first server response, with nothing waiting on scripts
  • ✓ A machine-readable layer: a Markdown twin and an llms.txt index, structured data, headings set up to be quoted in fragments
  • ✓ Bot policy at the network edge, and speed thresholds written into the handover protocol, not checked after the first campaign
  • ✓ A content-editing layer for your team: a browser panel and MCP tools for an assistant
  • ✓ Publishing on Cloudflare's edge network, forms wired into a CRM together with tracking and consents, and a repository under your own account

What we build it on

Astro in static mode Cloudflare Workers and edge network Markdown twins and llms.txt compiled at publish time schema.org structured data GA4 and Google Tag Manager Forms wired into HubSpot or your own CRM
Step by step

Architecture, design, build and performance: four stages, each ending with a hand-off

We do not disappear for two months. After every stage you get something concrete to sign off, and you know what happens next.

  1. 1

    Workshop and content map

    1-2 weeks

    We work out who should land on the site, what questions it needs to answer, and which views that requires. We come out with a sitemap and copy for the key sections.

  2. 2

    Design

    2-4 weeks

    The home page comes first, since it sets the standard for the rest. The other views go for sign-off in batches, with feedback kept in one place.

  3. 3

    Build and the machine layer

    3-5 weeks

    Coding the views, structured data, Markdown twins, llms.txt and bot policy. Alongside it we build the layer your team uses to change content without touching code.

  4. 4

    Sign-off against thresholds, and handover

    ongoing work

    We check speed at hand-off, not after the first campaign. Alongside that, training your team and handing over the repository, then ongoing development if you want to leave that with us.

Boundaries of this service

When an Astro website makes sense, and when WordPress is the better choice

Short answer

Astro makes sense when speed, security and how crawlers and language models read the site all matter, and content changes on a scale of days, not seconds. We advise against WordPress for a simple business card: keeping up with plugins and updates costs more than it gives back. It wins where a team publishes daily.

The site you are reading runs on Astro: over 400 pages compiled into static files at publish time, each with a Markdown twin for models. Content here is changed by the JustIdea team itself, through the editorial panel and through an assistant, so we are talking about something we work with every day ourselves.

A site compiled into static files at publish time, against a site with a panel and a database that the team changes every day

This is the right service

  • The site needs to be quoted by AI models and fast on a phone.
  • Content changes on a scale of days and weeks, not a dozen times a day.
  • You do not want to keep up with plugins, a database and updates.

Start with something else

  • Your team publishes daily and needs a panel: that is WordPress websites.
  • The site needs to run a process, a login and integrations: that is a custom web solution.
  • You have a site and just want it faster: that is speed optimisation.
Other services

What else we can do for you

A website rarely ends at launch: alongside it usually sits visibility, tracking or upkeep. Below are three related services, each with its own scope and its own quote.

WordPress websites

We build company sites on WordPress: a self-service panel, language versions, forms and tracking.

View ›

Custom web solutions

A dedicated website with features no plugin can build: calculators, client portals, document workflows, integrations.

View ›

GEO

Generative Engine Optimization: we implement GEO so your brand gets cited in AI answers (Google AI Overviews, ChatGPT, Perplexity).

View ›
Bots and models

Who fetches your site's HTML before a person does

Traffic you never see in a campaign report. Four things that, on a site compiled to static files, are your decision, not a side effect.

Search engine bots

They get the full content straight away, with nothing to wait for. A fast server response translates directly into how many pages they manage to fetch in a single visit.

Language model bots

GPTBot, PerplexityBot and ClaudeBot mostly do not run JavaScript. For a model to quote your page, it has to fetch it in full first, and a site compiled to static files looks the same to them as it does to a person.

A version built for machines

Alongside the HTML, every page has a Markdown twin, and an llms.txt index guides a model through the site. It is the same content, just without the page layout and navigation.

Control stays with you

Which bot gets in, how often and to what, is set at the network edge. That is an enforced rule, not a request in a text file that can just be ignored.

Content management

How content changes when there is no panel wired into a database

A site like this can be edited without a developer, just with a different tool than a panel wired into a database. Below are four routes a change can take to reach the site; you pick the one that fits your team, and you can use all of them at once.

A sentence to an assistant

You write what needs to change, and an assistant calls a tool that swaps the field in the content. No logging into a panel, and no ticket to the agency.

A browser panel

The same set of changes, available through a form with a preview. For people who would rather see the field and click save.

A check before publishing

A price outside the agreed list, a figure with no source, or a photo with no description does not go through. The change gets rejected with a reason, instead of landing on the site as an error.

A trail for every change

Every edit is signed by a person and recorded in the repository's history. You can see who changed a sentence, when, and exactly what it said before.

Reviews

Websites: what clients say

„
Responsiveness, an understanding of our needs and taking the initiative are what let us call our joint project a success.
Magda SkórskaDigital Marketing, LPP / House
„
They were always one step ahead of the competition, optimizing campaigns in real time.
Katarzyna LenartowiczE-Commerce Manager, VANDA NOVAK • Clutch 5.0★
„
Their responsiveness and strategic approach made them a reliable and results-driven partner.
Andrzej SteckiCEO, BookingHost • Clutch 5.0★
Client reviews

You are choosing a framework you don't know, so check the people instead

We build modern websites on Astro, a name most clients have never heard of and have no way to check before the project starts. What you can check is deadlines, communication, and whether the site still works a year later. That is what the reviews clients left after working with us are about.

4.96 / 5

weighted average of 224 reviews across three platforms. Clients gave them, and each site below links to the profile with the full text of every review.

Read the reviews
Certifications and partnerships

Astro does not hand out badges, so we show what can actually be checked

Behind the framework stands an open-source project, not a vendor handing out partner statuses. What is left is a ranking based on verified reviews, and the status of the tools a site like this runs on after launch.

Top Web Developers, Legal, Poland

Clutch, ranking of website developers for the legal industry

A ranking of website developers, not of WordPress alone. Clutch verifies every review with a call to its author, so a placement rests on delivered projects, not on a submission to a directory.

Google Premier Partner

Google, top tier of the Google Partners programme

A site with no server-side back end gets all its knowledge of visitor behaviour from tracking in the browser. The status gives us support on Google's side when setting up events and consent mode, so a report does not fall apart after the first content edit.

HubSpot Certified Partner

HubSpot, certified team partnership

Since the site does not store enquiries itself, a form has to land straight in the system the sales rep works in. The team's certification covers wiring that up, together with what happens to the enquiry once it is sent.

Doubts before working together

Four things we hear about sites with no classic CMS

Each one has a grain of truth. Below is what is left of them once you check.

„Without WordPress we can't change anything ourselves”

You can, just with a different tool. Text, photos and pages stay on your side, through a panel or an assistant. The difference is that you cannot accidentally break the site's layout, because the template is not editable from the panel.

„We'll deal with AI optimisation later”

Later means at the next rebuild: you lose all the time until then, plus another 6 to 12 weeks for the build itself. Whether a machine gets full content is decided by how the site is built, and that decision is made in the first week of work. Bolting it onto a finished site with plugins costs more than doing it right the first time.

„This sounds like a solution for developers”

The code stays on our side, just as with WordPress. On your side is the content, and that looks like a form with fields, or a plain sentence written to an assistant. The site you are reading right now is run exactly this way.

„We have a WordPress site, it just runs slowly”

Then we start with measurement, not a rebuild. Speed optimisation is a separate service and is often enough. We only suggest rebuilding the site once the problem sits in the construction, not the configuration.

FAQ

Astro websites: questions before you decide

How is an Astro website different from a WordPress website?

In the moment the HTML is created. WordPress assembles a page on every visit, querying a database and running plugins. Astro assembles it once, at publish time, and the server just sends the finished file. That is where both the speed and the fact that a bot gets full content, even without running scripts, come from.

What does it mean for a site to be built for language models?

That the model gets the full content, not a skeleton. Three things decide it: all the content sits in the first server response, every page also has a machine-readable version, and an llms.txt index tells the model what exists on the site at all. The JustIdea site you are reading right now has had this set up from day one, across more than 400 pages.

How is this different from a GEO service?

In scope and horizon. Here we build a site a machine can read in full, and that is where this service ends. GEO is ongoing work to get models to mention your brand in their answers, together with measuring citations and working on content. Either one on its own works less well, but the foundation has to come first.

We already have a website, wouldn't speed optimisation be enough?

Often it is, and we say so plainly, because optimisation is cheaper and faster. We start with measurement, not a rebuild. We only build a site from scratch when the problem sits in the construction itself, for example when the content only appears after scripts run, so a model's bot never sees it at all.

Does website speed affect Google rankings?

It does, but indirectly and more weakly than the industry likes to claim. Google measures speed with Core Web Vitals thresholds and treats them as one signal, not as a ranking lever. The stronger effect shows up elsewhere: a faster-responding server lets a crawler fetch more pages in one visit, and a visitor does not leave before the content appears.

Can this kind of site be edited without a developer?

It depends on the version, and we say so plainly. A simple site has no panel, because the content changes only a few times a year and it is cheaper to send us a request than to maintain a system nobody uses. On a larger site we add two ways in: a browser panel to click through, and a set of tools an assistant can use to change content from a plain-language instruction, even from a company chat window. That is exactly how the JustIdea team runs this very site.

How much does a modern website cost?

From €1,960 net for a simple site with no admin panel, and a larger company site is quoted individually. That quote depends on the number of designed views, language versions and integrations. Work after launch is billed at €80 net per hour of a specialist's time. The biggest part of the cost is not the engine, but the design and the work on content.

When is Astro not a good choice?

When the site needs to show data changing minute by minute, run user accounts, or handle a basket linked to a warehouse. We also advise against it when a team wants to rearrange page layouts and add sections itself without a developer: the template is not editable from a panel here, and that is a deliberate trade-off. In both cases we say so at the first meeting and suggest a database-backed application or WordPress instead.

Modern websites: what is worth knowing before a quote

Why a website has to be readable by machines

More and more buying questions no longer end in a list of links, but in an answer generated by a model. The model does not invent that answer, it assembles it from text it fetched earlier. If your site hands a bot a skeleton instead of content, you have nothing to get into that answer with, no matter how good your offer is. A modern website therefore has to be readable twice: for a person, and for the machine acting on their behalf.

Where website speed actually comes from

Website speed does not come from a caching plugin, it comes from there being nothing to calculate at the moment someone visits. The document sits ready on an edge server close to the visitor and gets sent straight away. The gain shows most on a phone with a weak signal. We write speed thresholds into the handover protocol, so we check them before launch, not after the first campaign. The same property works on bots: the faster the server responds, the more pages it manages to fetch in one visit.

What disappears along with the database and the plugins

This is the mechanism that makes the two things above possible at all, and it also brings a real saving on upkeep. The most common cause of site failures disappears, the entry point for automated break-ins disappears, and so does the monthly bill for a server that has to carry that database. The weekly gamble of updating plugins from a dozen different authors disappears too.

Astro next to React, Vue and Next.js

Astro does not rule out the libraries your team already knows. A component written in React, Vue or Svelte can be embedded on the page, and the framework renders it to HTML at publish time, loading JavaScript only where an element genuinely needs to be dynamic, for example in a calculator or a filter. This architecture is called islands. We write configuration and content schemas in TypeScript, and longer text, like posts or documentation, in Markdown or MDX. When a site is really an application with logins and data changing by the second, an application framework such as Next.js is sometimes the better fit, and we say so before quoting.

Performance, rendering and SEO

Rendering HTML at publish time instead of on every visit is the main source of the performance: page load time does not depend on a database or on the number of plugins. For SEO that means a search engine's bot gets the full content in the first response. We check performance against Core Web Vitals thresholds at hand-off, where a page counts as good if it shows its main content within 2.5 seconds. By default Astro sends no JavaScript to the browser if the page does not need it, so load speed does not drop as the site grows with more pages.

What kind of sites Astro suits

Content-driven sites: a company website, a campaign landing page, a portfolio, an expert blog, product documentation and marketing pages. Where content changes on a scale of days rather than seconds, the framework generates static pages with ready-made HTML, so at the moment of a visit there is nothing left to calculate. A static website will not, however, replace a store with a basket and a warehouse: that is a separate service with its own quote.

Start with a conversation, not a ten-page brief

We go through your sales process and tell you what scope makes sense for your budget. If fixing your current site is enough, you will hear that straight away.

Instead of a ten-page brief, an hour-long call ends with an agreed website scope
Book a workshop and website quote The call is free, we prepare the quote after the workshop
Contact

A conversation about your numbers: 30 minutes

The call is led by a new business specialist. When we get into the details of an account, the specialist for that channel joins in. We reply within one business day.

A quick review of your tracking and campaignsThree priorities for the next quarterA written summary that stays with you

Before the meeting we review your website, your visibility and what your campaigns show from the outside. We will not open with “so, what does your company do?”.

4.96 224 reviews
By sending the form you agree to the processing of your data in line with our Privacy Policy.

What happens after you send it
01
within 1 business day

We reply to your email

The reply comes from the same new business specialist who will run the call. No qualification form and no call from an unknown number.

02
this week

A 30-minute conversation

We go through your numbers and your questions. If it turns out we are not the right fit, we will tell you straight away.