Technical SEO is precondition, not substitute
Without a solid technical foundation, neither the best content nor the best link building moves the needle. Technical SEO makes sure the machine can read what you already have.
SEO + GEO · Technical SEO
Technical SEO · Core Web Vitals
Technical SEO for B2B companies: Core Web Vitals, SSR rendering, crawl budget, indexation and URL architecture. The foundation that makes content rank.
- Core Web Vitals in the green (LCP < 2.5s, INP < 200ms, CLS < 0.1) at the real 75th percentile of Google
- Optimized crawl budget crawlable URLs prioritized, parameters and facets under control
- Time to indexation reduced to days, not weeks, on newly published pages
- 0 critical errors in Search Console: coverage, mobile usability and schema in the green
Technical SEO is the discipline that optimizes web infrastructure —performance (Core Web Vitals), crawlability, indexability, rendering, URL architecture, hreflang, canonicals, robots, sitemap and structured data— so search engines can discover, render, understand and index every page correctly.
Unlike content SEO or link building, technical SEO doesn't aim to write better or earn links: it aims to make sure the machine can read what you already have. It's a precondition, not a substitute. A technically sound site is the one that ranks on Google and gets cited by ChatGPT, Perplexity, Gemini and AI Overviews.
What technical SEO covers
10 audit areas we work on every project
Full technical SEO stack applied to B2B environments: WordPress, Next.js, Shopify, headless and complex ecommerce. Execution order: top first.
Core Web Vitals at the 75th percentile
Google measures CWV in the field (CrUX), not in Lighthouse. Target: LCP < 2.5s, INP < 200ms, CLS < 0.1 at the real p75 of mobile and desktop users.
INP replaced FID in March 2024
Interaction to Next Paint measures the latency of the worst user interaction. Third-party scripts (analytics, chat, ads) are the main cause of bad INP.
Crawl budget is finite on large sites
On sites >10k URLs, log analysis is essential to see what Googlebot crawls and to block traps (facets, parameters, sessions).
SSR or SSG, not pure CSR on indexable content
Googlebot processes JS with delay (two-wave indexing). SSR/SSG resolves indexation on the first pass. CSR only for private areas.
Coherent URL + canonical + hreflang triangle
An error in one of the three vertices breaks the other two. Bidirectional hreflang with x-default, absolute canonical without loops, aligned sitemap.
robots.txt with explicit access for AI bots
Allow GPTBot, PerplexityBot, Google-Extended, ClaudeBot and OAI-SearchBot. Blocking by omission means disappearing from generative engines.
Schema @graph as ground truth
JSON-LD enriched with Organization, WebPage, Article, Service, FAQPage, BreadcrumbList and speakable. Schema disambiguates when the text isn't clear.
Governed 3-tier redirects
Cronuts policy: .htaccess for infra only, redirects plugin for content migrations, functions.php only for documented programmatic rules.
Continuous monitoring, not a one-off audit
Weekly CWV, weekly Search Console coverage, monthly crawl diff, alerts on schema regressions. Technical debt is paid in daily interest.
Core Web Vitals
The 3 experience KPIs Google measures in the field
CrUX data (real 75th percentile of users) on mobile and desktop. Not lab Lighthouse.
LCP
Largest Contentful Paint
good < 2.5spoor > 4.0s
Time until the largest visible element renders. Hero, hero image, h1.
INP
Interaction to Next Paint
good < 200mspoor > 500ms
Latency of the worst user interaction. Replaced FID in March 2024.
CLS
Cumulative Layout Shift
good < 0.1poor > 0.25
Visual stability during load. Layout shifts hurt ranking.
Technical stack
6 pillars worked in parallel
Each lever has its own KPI, tool and owner. No overlaps, no gaps.
Performance
Lighthouse 95+ mobile, CrUX p75 green, critical CSS, AVIF/WebP, code-splitting, HTTP/2.
Crawl & logs
Log analysis, facet and parameter crawling, clean robots.txt with AI bots allowed.
Rendering
SSR/SSG on indexable content. CSR only for private areas. Selective prerender.
Schema @graph
Organization + WebPage + Service + Article + FAQPage + Breadcrumb + speakable, validated.
hreflang
Bidirectional with x-default, segmented sitemap, absolute canonical with no loops.
Redirects 3-tier
.htaccess infra · plugin for content · functions.php only for programmatic rules. Zero chains.
Frequently asked questions
What B2B CMOs and CTOs ask before signing
What is technical SEO and why does it matter?
Technical SEO is the discipline that optimizes web infrastructure —performance, crawlability, indexability, rendering, architecture, schema— so search engines can discover, render and index every page correctly. Without that foundation, neither content nor links work: Google cannot rank what it doesn't understand.
What are Core Web Vitals and what thresholds should I meet?
Core Web Vitals are three user experience metrics Google uses as a ranking signal: LCP (Largest Contentful Paint) below 2.5 seconds, INP (Interaction to Next Paint) below 200 milliseconds and CLS (Cumulative Layout Shift) below 0.1. They are measured at the 75th percentile of real users, not in Lighthouse.
What is the difference between INP and FID?
INP (Interaction to Next Paint) replaced FID (First Input Delay) in March 2024. FID only measured the first interaction; INP measures the worst interaction latency throughout the user's whole visit. It's a more demanding metric and reflects real interactivity better.
Does Googlebot execute JavaScript?
Yes, Googlebot renders JavaScript using a recent version of Chromium, but it does so on a second pass (two-wave indexing) with a delay of days or weeks. That's why we recommend SSR or SSG on content that needs to index fast. Pure CSR is only acceptable for private or non-indexable areas.
What is crawl budget and when does it matter?
Crawl budget is the number of URLs Googlebot crawls on your site in a given period. It matters on large sites (>10,000 URLs, ecommerce, media) where the bot must prioritize. On smaller sites the relevant thing isn't the budget but that rendering, canonicals and sitemap are coherent.
How do you set up hreflang correctly?
Hreflang must be bidirectional: each language version declares all the others and itself. An x-default is added for the fallback. It must be coherent with each URL's canonical and with the XML sitemap. Validate with specific tools like Merkle or Sistrix Hreflang Checker.
What JSON-LD schema should I deploy on a B2B site?
At minimum: Organization (with sameAs to LinkedIn, Crunchbase, GMB), WebPage with speakable, BreadcrumbList, Service or Product depending on page type, FAQPage where applicable and Article on the blog. Deploy it as a @graph with entities linked by @id, validated with Rich Results Test.
How long does a technical SEO project take to show results?
The full audit takes 2-3 weeks. Core Web Vitals improvements show up in CrUX within 28 days (Google measurement window). Indexation and schema changes can reflect in Search Console within days. Impact on rankings and organic traffic typically shows between days 60 and 90, depending on site volume.
Do I need technical SEO if I already have WordPress and Yoast?
WordPress and Yoast cover the basic layer but don't solve rendering, field Core Web Vitals, crawl budget, URL architecture or enriched @graph schema. A technical audit usually finds problems with canonicals, hreflang, redirect chains and red CWV even when Yoast marks everything green.
Does technical SEO affect visibility on ChatGPT and Perplexity?
Yes. Generative engines use their own crawlers (GPTBot, PerplexityBot, Google-Extended, ClaudeBot) and read JSON-LD schema to understand entities. A site with misconfigured robots.txt, pure CSR rendering or no schema is practically invisible to ChatGPT, Perplexity, Gemini and AI Overviews.
Closing
Technical SEO is invisible, but you feel it
Technical SEO is invisible, but you feel it: it's the difference between a site that ranks with the content it already has and one that publishes a lot and never moves positions. Core Web Vitals at the 75th percentile, optimized crawl budget, SSR/SSG rendering, coherent canonicals, bidirectional hreflang and validated @graph schema are the six pillars that separate a serious SEO project from a well-intentioned blog.
At cronuts we treat technical SEO as a mandatory foundation before any content or link building initiative. Because without that foundation, neither the best article nor the best backlink converts into organic traffic. And because generative engines —ChatGPT, Perplexity, Gemini, AI Overviews— amplify the advantage of a technically impeccable site: if Google does not understand you, the LLM will not cite you either.
If you want to know the state of your technical SEO debt and which 90-day plan resolves it, write to info@cronuts.digital and we'll deliver an initial audit with diagnosis and priorities.