Back to Services

ANNÁVE TECH · Services

Your React site is invisible where buyers search. I fix the code that causes it.

Scan → codebase → fix. Fixed fee. No agency overhead.

50% of B2B buyers start in ChatGPT or Perplexity now, not Google. Most React and Next.js sites are not readable there. Not because of content. Because of render failures, missing schema, and broken markup that AI systems silently skip. I scan your site, trace the exact failures, and fix them.

AI Search Readiness

Structured data · rendering · schema

Your pages may rank on Google. That does not mean ChatGPT, Perplexity, or Google AI Overviews can parse them. The gap is structural: SPA shells with no machine-readable content, missing JSON-LD, incomplete Organization schema. These are render and markup problems — not content problems.

  • json_ld_missing — no structured data on any page
  • json_ld_org_incomplete — Organization schema present but missing name, logo, or sameAs fields AI systems use to identify your brand
  • rendering_ssr_missing — raw HTML served to crawlers contains almost no visible text; your content may not exist to Google or AI systems at all

Fix included. One engagement, not a report you hand to an engineer.

Core Web Vitals

LCP · CLS · INP · ranking signals

Google's mobile performance thresholds are direct ranking signals. 53% of sites fail them.

  • lcp_poor — Largest Contentful Paint above 2.5s. Confirmed from live PageSpeed data. Traced to root cause in your codebase.
  • cls_poor — Cumulative Layout Shift above 0.1. Content jumping during load. Ranking signal since 2021.

Not a PDF of scores you already have in your dashboard. Root cause in code, then the fix.

Rendering and Indexability

SSR · robots · staging exposure

Your React app may not be indexed where your buyers search. Googlebot receives an empty shell. AI systems see no structured data. Neither of these show up in your dashboard until traffic is already gone.

  • rendering_ssr_missing — empty SPA shell detected from the outside; SSR is missing or misconfigured
  • robots_blocking_assets — robots.txt blocks the CSS and JS files that render your pages; Google scores a broken version of your site
  • staging_exposed — staging environment responding publicly with no auth

All confirmed from live server responses before anyone is contacted.

International Expansion

hreflang · localization readiness

Next.js has a known bug: alternates.languages can render hreflang in the body instead of the head. Google ignores it. Your localized pages compete against your English pages instead of alternating with them. Worth checking before spending months on content localization.

  • hreflang in wrong document position
  • missing x-default tags
  • incomplete return-links between language alternates
  • canonical conflicts with hreflang

All confirmed from live HTTP responses.

How an engagement works

Technical Audit — €200 fixed fee

Funded SaaS. React, Next.js, or Angular.

Teams where the CTO does not want to allocate engineering sprints to decode an audit report. Live scan. Written report. Delivered async — no discovery call required.

Request an Audit
What is included in the €200 audit?

Written scan report with every confirmed finding, severity, and business impact. Codebase analysis tracing root cause to file and line where repo access is granted. Fix implementation or implementation-ready guidance. No retainer by default. No monthly call.

Is this the same as the cold outreach scan?

No. The paid Technical Audit is a client engagement: full written report, codebase analysis, and fix implementation. The entry point is €200 fixed fee.

What if there is nothing to fix?

If the scan finds no fixable issues, the report still documents what was checked and confirmed clean. If issues are found and you want them fixed: separate engagement, separate quote, same direct work.