One of the original React frameworks for SSG. Still used on many sites — especially blogs and docs. Gatsby SEO is good but requires maintenance and migration to current versions. Gatsby is mature with rich plugin ecosystem. If your site is already on Gatsby — we optimize it and prepare migration to Gatsby 5+ or Astro/Next.js when needed.
Gatsby 2/3/4 are deprecated — we recommend migration to 5+ or an alternative. Cost and risk assessment.
Unified meta-tag system via gatsby-plugin-react-helmet with automatic canonical and og.
Auto-generated markup from MDX/Markdown frontmatter via templates.
gatsby-plugin-sitemap and gatsby-plugin-robots-txt setup with proper exclude rules.
gatsby-plugin-image (or migration to gatsby-plugin-sharp). Critical for LCP.
If Gatsby 2/3 — migration plan to 5+ or switch to Astro/Next.js without SEO loss.
Gatsby 2 unsupported since 2022 — vulnerabilities, slow builds, risks.
Using legacy component — slow LCP, no AVIF/WebP support.
Large sites take 30-60 minutes — can't publish fresh content quickly.
Complex GraphQL query architecture often leads to incomplete meta tags on pages.
Old SEO plugins conflict with newer versions.
Dev mode becomes unusable — slows development, SEO fixes painful.
Which Gatsby version, which plugins, what's deprecated. Decision: update or migrate.
Speed measurements, bottleneck identification, improvement plan.
react-helmet setup, meta-data unification, JSON-LD markup.
Plugin setup with proper config. Hooks on content updates.
Migration to gatsby-plugin-image, AVIF/WebP, font optimization.
If stack is too outdated — plan to switch to Astro or Next.js without ranking loss.
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.