Technical SEO is the process of making your website easy to crawl, index, and load quickly so that Google and AI answer engines can actually find and display your content. Without this foundation, your content doesn't matter—it simply never gets seen.
This guide is for you if you run an e-commerce store, a SaaS company, or a multilingual brand and need to know exactly what needs fixing behind the scenes before you scale content to new markets. We cover crawling, performance, structured data, and a concrete checklist you can use today.
You don't need to be a developer to understand this. You just need to know which errors are actually costing you traffic and in what order you should fix them.
Key takeaways
- Google has over a 95% market share in Norway, so technical optimization must in practice follow Googlebot's rules for crawling and rendering, according to Optimal Digital.
- Over 60% of all searches in Norway are done on mobile, which is why mobile-first indexing is no longer optional; it's the standard Google measures you against.
- Core Web Vitals thresholds for 2026 are clear: Largest Contentful Paint under 2.5 seconds, Cumulative Layout Shift under 0.1, and Interaction to Next Paint under 200 milliseconds, according to Mementor.
- Structured data via JSON-LD for Organization, Article, Product, FAQPage, and BreadcrumbList delivers rich search results and makes it easier for AI answer engines to understand your content, according to Nettrafikk.
- Subfolders like example.com/en/ are recommended over subdomains for multilingual websites because they consolidate domain authority instead of spreading it thin.
What is technical SEO?
Technical SEO is the optimization of a website's source code, architecture, and server settings—everything happening behind the scenes, unlike content optimization which deals with text and keywords, according to Nettrafikk. It is the bridge between what you publish and what the search engine is actually able to read, understand, and display.
You can write the best article in the world. If Googlebot can't crawl it, the page takes 8 seconds to load, or the URL points to a misconfigured canonical tag, the content doesn't count. Technical SEO removes these barriers first.
Its four pillars are crawling (does the bot find the page?), rendering (can it interpret the code?), indexing (does the page end up in Google's index?), and performance (does the page load fast enough for the user?). Everything else—link building, keyword optimization, content calendars—builds on top of this foundation.
Crawling and indexing: does Google actually find your pages?
Crawling and indexing determine whether Google even knows your page exists. Errors here—such as broken links, redirect loops, or missing canonical tags—prevent pages from ever entering the index, no matter how good the content is.
The most common mistakes we see on Norwegian websites:
- 404 errors that pile up after product cleanups or site redesigns, wasting crawl budget without returning any value.
- Redirect loops where URL A points to B which points back to A, halting the bot entirely.
- Missing or incorrect canonical tags, leading to duplicate content and diluted ranking power, according to Anadigme.
- Blocked resources in robots.txt, often by accident, preventing Google from rendering the page correctly.
- Outdated or incorrect XML sitemaps pointing to pages that no longer exist.
The solution is tedious but effective: self-referencing canonical tags on every page, permanent 301 redirects upon URL changes, and a sitemap that actually matches what is live. Google Search Console shows you precisely which pages are excluded and why—that's your first stop, not a last resort.
Website performance and Core Web Vitals: how fast does the page need to be?
Website performance is measured today through Core Web Vitals, three concrete metrics Google uses to evaluate your user experience directly in rankings. If you exceed these thresholds, you lose visibility—regardless of how great your content is.
| Metric | Threshold for 2026 | What it measures |
|---|---|---|
| Largest Contentful Paint (LCP) | Under 2.5 seconds | How fast the largest visible element loads |
| Cumulative Layout Shift (CLS) | Under 0.1 | How much the page \"jumps\" while loading |
| Interaction to Next Paint (INP) | Under 200 ms | How quickly the page responds to clicks and taps |
The concrete actions that actually move these numbers: switch image formats to WebP or AVIF, set up browser and server caching, roll out a CDN, and eliminate render-blocking scripts that delay Time to First Byte (TTFB), according to Medium. A single heavy third-party widget—a chatbot, a lead form, a tracking script—is often the entire difference between a green and a red Core Web Vitals report.
Tools like Google PageSpeed Insights and GTmetrix give you concrete numbers here and now, while Sitebulb and Screaming Frog SEO Spider uncover performance issues across your entire website rather than just one page at a time, according to Mementor.
Structured data: making content machine-readable
Structured data is code—typically JSON-LD—that tells search engines and AI answer engines precisely what kind of content a page contains without requiring them to guess. Implemented correctly, it yields rich search results and a better foundation for AI answer engines to cite you accurately.
The most valuable schema types to start with:
- Organization – confirms who the brand is, complete with name, logo, and social profiles.
- Article – marks up blog posts and news with an author and publication date.
- Product – displays price, availability, and reviews directly in search results.
- FAQPage – structures questions and answers so they can appear as expanded results.
- BreadcrumbList – shows the website hierarchy in search results, according to Nettrafikk.
This is also where technical SEO meets GEO directly. An AI answer engine like ChatGPT or Perplexity reads structured data much the same way Google does—it looks for clear, machine-readable facts it can safely cite. Unclear or missing schema makes it harder for both types of engines to trust your content.
Mobile and multilingual websites: the technical foundation for international growth
Mobile and multilingual architecture are where technical SEO becomes strategic, not just defensive. Over 60% of searches in Norway happen on mobile, and Google indexes the mobile version of your site by default—not the desktop version, according to Optimal Digital.
This means a responsive design that works fine on desktop but creates horizontal scrolling or hidden menus on mobile penalizes you directly in rankings.
When expanding to new markets, URL structure becomes crucial. Subfolders like example.com/en/ or example.com/de/ consolidate domain authority in one place, whereas separate subdomains or entirely new domains spread it thin across multiple \"new\" websites in Google's eyes. Add correct hreflang tags so Google displays the right language version to the right user.
The technical foundation is one thing. The content placed on top of it is another—and here we often see companies cutting corners with machine translation instead of real local content, which hurts both the reading experience and credibility in new markets. If you want the full process from technical foundation to publishing, you can see how an SEO audit is built step by step.
How to perform a technical SEO audit: 7 steps
A technical SEO audit follows a fixed sequence because errors early in the chain—crawling and indexing—make everything afterwards irrelevant. Always audit in this order:
- Run Google Search Console and check for coverage errors, excluded pages, and manual actions.
- Crawl the entire website with Screaming Frog or Sitebulb to find broken links, duplicate content, and missing canonical tags.
- Test speed with PageSpeed Insights and GTmetrix and note LCP, CLS, and INP for your most important pages.
- Check robots.txt and XML sitemap manually to confirm that nothing important is blocked or missing.
- Validate structured data with the Google Rich Results Test for every schema type you use.
- Test the mobile view on an actual mobile device, not just in browser developer tools.
- Prioritize errors by impact: fix what blocks indexing first, then performance, and finally polish structured data.
You will find this exact sequence in professional audits from Norwegian agencies like Search Planet, Horn Media, and Transact, according to Nettrafikk. Doing this every 3–6 months catches problems before they cost you months of lost traffic.
Technical SEO vs. GEO: same foundation, new goal
Technical SEO and Generative Engine Optimization (GEO) build on the same foundation—crawlable, fast, and structured content—but they optimize for different recipients. SEO targets Google's ranking algorithm, whereas GEO targets AI answer engines like ChatGPT, Gemini, and Perplexity that cite you directly within an answer.
A page that is slow, poorly structured, or full of duplicate content struggles in both worlds simultaneously. But GEO poses an extra requirement: the content must be clear enough, factual enough, and locally relevant enough for an AI model to dare cite you as a source over a competitor.
This differs from standard vanity metrics. It is not enough to count the number of words published or pages indexed. What matters is whether your brand is actually mentioned when someone asks an AI answer engine about your product or industry—which requires verifiable citation tracking, not guesswork or inflated reports.
Frequently asked questions
What is the difference between technical SEO and content SEO?
Technical SEO is about website source code, speed, and structure—everything that determines whether a search engine can find and read the page. Content SEO is about the text itself: keywords, relevance, and how well the content answers the user's query. You need both; a technical foundation without good content won't rank, and good content without a technical foundation will never be seen.
How often should you perform a technical SEO audit?
A full technical audit should be carried out every 3–6 months, or immediately after a site redesign, a major design update, or migration to a new CMS. Smaller checks of Core Web Vitals and Search Console should happen monthly, as performance issues often creep in gradually via new third-party scripts.
Does technical SEO affect visibility in ChatGPT and other AI tools?
Yes. AI answer engines still need to be able to crawl and understand your website to fetch facts they can cite, and structured data makes it easier for them to interpret content correctly. A slow, poorly structured website is just as invisible to an AI answer engine as it is to Google.
Do I need a developer to fix technical SEO errors?
It depends on the error. Issues like canonical tags, robots.txt adjustments, and sitemap updates can often be handled in the CMS by a marketer with some training. More extensive problems—such as rendering errors, server configuration, or code-level Core Web Vitals optimization—typically require a developer or a dedicated technical SEO specialist.
How much does a technical SEO audit cost?
Pricing varies based on website size and complexity, ranging from a simple one-off check of a small site to a comprehensive audit of a multilingual e-commerce store with thousands of pages. The most important thing is not the price alone, but that the audit provides a concrete, prioritized list of what needs fixing first—not just a generic report.
Next steps: let UPGeoSEO test your website
You now have the framework: crawling and indexing first, then speed, then structured data, and finally the multilingual layer on top of it all. The next step is to actually run the check on your own website, not just read about it.
UPGeoSEO analyzes your website for both classic Google rankings and visibility in AI answer engines like ChatGPT, Gemini, and Perplexity, tracking whether your brand is actually being cited—no guesswork involved. You get a one-off audit without a subscription if you just want answers now, or ongoing tracking if you are scaling to new markets.
You approve the content—we publish it, technical foundation and locally adapted copy included. No clumsy translations, no inflated numbers to hide behind.
