The perfect foundation for content sites: static generation, zero JS by default, perfect Core Web Vitals. SEO on Astro works out of the box — the optimizer's job is to not break it and scale it. Astro is our top choice for blogs, corporate sites, and media projects. Of all modern frameworks, Astro delivers the best Core Web Vitals and indexation from day one.
astro.config configuration — separate static/SSR strategies for different site sections.
client:visible / client:idle for heavy components so first paint isn't blocked.
Each page gets unique title/description/og — no duplicates.
Auto-generated Article, BreadcrumbList, FAQPage markup from content frontmatter.
@astrojs/sitemap with proper priorities and changefreq. Separate maps for large projects.
Correct markup via @astrojs/i18n, x-default, canonical for each language version.
When client:load used instead of client:visible — Google sees a 'jumping' DOM and penalizes the page for CLS.
Astro 4+ introduced View Transitions — without proper client-router config, analytics breaks.
Markdown without schema validation: some pages ship without a title or description, and nobody notices for weeks.
A plain image tag instead of the built-in component: images ship at original size and format, and the first screen takes noticeably longer.
Accidental dev-build deploys = massive JS bundle and speed loss.
Static sites without CI/CD auto-deploy on content changes — Google doesn't see freshness.
Review astro.config, integrations, server-output. SSG vs SSR vs hybrid.
PageSpeed Insights + Chrome DevTools for all page types.
Unified system via Layout component and Content Collections with zod validation.
@astrojs/sitemap setup, robots exclusions, multilingual markup.
Internal link structure, breadcrumbs, related blocks on every page.
GSC, regular speed and indexation reports every 2 weeks.
This is the central question on any modern framework. Everything else — meta tags, markup, speed — is decided after it.
| Mode | What a crawler sees | When it fits |
|---|---|---|
| Static generation | Ready HTML with all content — the best case for indexing | Content changes rarely: services, articles, catalogues without frequent price updates |
| Server rendering | Ready HTML assembled per request | Data changes often: stock, prices, personalisation |
| Client rendering | An empty page; content appears after scripts run | Account areas and internal interfaces — things that should not be indexed anyway |
| Mixed mode | Depends on which part of the page ships immediately | Catalogues with static cards and dynamic blocks |
A common mistake is client rendering on pages meant to bring people from search. Easy check: open the page source and search for your own text. If it is not there, a crawler may not see it either.
On modern stacks, every SEO strategy starts with correct rendering and indexation. Nothing else works without it.
LCP, INP, CLS — the three metrics Google uses to grade real UX. SSG/SSR stacks make them easy to push into the green.
We work directly with your developers — fixing what SEO tools alone can't reach.
Not 'set it and forget it' — we watch indexation, speed and rankings continuously and send a report once a month.
30-minute call with a senior strategist. We'll review the codebase, indexation and Core Web Vitals — and propose a realistic plan.