📘 What makes technical SEO actually work?
Technical SEO is the work of making a site easy for search engines to crawl, render, index, and serve. Google's pipeline runs
What you’ll learn
- Crawling & Indexing FoundationsExplain how Google crawls, renders, and indexes pages, and correctly choose robots.txt, noindex, and XML sitemaps to control each stage.Search works as a pipeline: crawl, render, index, rank, and a page can drop out at any stage. robots.txt controls crawling but is not a reliable way to keep a page out of the index, while a noindex meta tag or X-Robots-Tag header controls indexing — and requires the page to be crawlable to be obeyed. XML sitemaps are discovery hints that should list only canonical, indexable URLs. Crawl budget matters mainly for very large or fast-changing sites and is wasted on duplicates, faceted URLs, and soft 404s. Google renders JavaScript but can defer it, so critical content and links should be available without relying solely on client-side JS.
- Site Architecture & CanonicalizationDesign a shallow, well-linked site architecture and apply rel=canonical correctly to consolidate duplicate content onto a preferred URL.A flat, logical site structure with descriptive internal linking helps crawlers discover pages and distributes link equity to priority content, while orphan pages are starved of both. Duplicate content (http/https, www variants, parameters, trailing slashes) splits signals and wastes crawl budget rather than incurring a penalty. The rel=canonical link element is a strong hint, not a directive, telling Google which URL to treat as authoritative; Google can override it when signals conflict, so canonical, sitemap, and internal-link signals should agree. Canonical, 301 redirect, and noindex are distinct tools — consolidate, move, or exclude respectively.
- Status Codes, Redirects & HTTPSInterpret HTTP status codes and apply the correct redirect type, distinguishing 301 vs 302 and 404 vs 410, while implementing HTTPS correctly.HTTP status codes tell crawlers how to treat a URL: 2xx success, 3xx redirection, 4xx client error, 5xx server error. A 301/308 is a permanent redirect that Google uses as a canonicalization signal toward the target, while a 302/307 is temporary and keeps the original canonical. A 404 means not found (may return) and a 410 means gone (deindexed slightly faster), with little practical SEO difference. Redirect chains and loops waste crawl budget and should be collapsed to a single hop. HTTPS, a lightweight ranking signal since 2014, requires a valid certificate, http→https 301s, https canonicals, and no mixed content.
- Structured Data & Rich ResultsImplement schema.org structured data using JSON-LD that accurately reflects page content to qualify for rich results without violating guidelines.Structured data uses the shared schema.org vocabulary to describe page content to machines, making pages eligible for enhanced rich results in Search. Google recommends JSON-LD, a separate script block that is easiest to maintain at scale, over Microdata and RDFa. Eligibility is not a guarantee — Google decides whether to show rich results, and pages must follow both general and type-specific guidelines. Markup must reflect content visible to users; fabricated or hidden markup violates guidelines and can trigger a manual action that removes rich results. Validate with the Rich Results Test and monitor Search Console enhancement reports.
- Core Web Vitals, Mobile & InternationalEvaluate pages against the Core Web Vitals thresholds and address mobile-first indexing and hreflang for international targeting.Core Web Vitals are three field metrics assessed at the 75th percentile: LCP (loading, good ≤2.5s), INP (responsiveness, good ≤200ms), and CLS (visual stability, good ≤0.1). INP replaced FID on March 12, 2024 because FID measured only the first interaction's input delay, whereas INP captures latency across all interactions. Field data (CrUX) drives the assessment, while lab tools like Lighthouse aid debugging. Google completed mobile-first indexing in late 2023, so mobile pages must have content and markup parity with desktop. hreflang annotations, using ISO language/region codes, must be reciprocal with a self-reference and an x-default for international targeting.
- Guided Project: Technical SEO Audit (Case Memo)Produce a prioritized technical SEO audit case memo that diagnoses crawling, indexing, architecture, redirects, structured data, Core Web Vitals, and international issues with evidence and recommended actions.The project walks through scoping an audit (site, business goal, in-scope areas, tools like Search Console, a crawler, URL Inspection, Rich Results Test, and PageSpeed Insights) and working layer by layer. Start with crawling/indexing using robots.txt, the sitemap, and the Index Coverage report; then audit internal linking, canonicalization, status codes, redirects, and HTTPS via a crawl; then validate structured data and measure Core Web Vitals plus mobile and hreflang readiness. Findings are prioritized on an impact-versus-effort basis into quick wins and larger projects. The memo opens with an executive summary, presents themed findings with evidence and actions, and closes with a prioritized roadmap and success metrics.
Questions this course answers
A product page has both a Disallow rule in robots.txt and a noindex meta tag, yet the URL keeps appearing in Google's index. What is the most likely cause?
noindex must be crawled to be obeyed; a Disallow rule prevents Google from fetching the page, so the directive is never seen and the URL can still be indexed. noindex works as both a meta tag and an HTTP header, robots.txt doesn't 'force' indexing, and a canonical isn't required for noindex to function.
Which scenario best describes a situation where crawl budget is a genuine concern?
Crawl budget primarily matters for very large and/or rapidly changing sites, where faceted navigation can generate enormous numbers of low-value URLs. Small, static, or rarely updated sites are crawled comfortably within budget, so it isn't a practical concern for them.
What is the correct way to describe an XML sitemap's role?
A sitemap helps search engines discover URLs but does not guarantee indexing, and it should contain only canonical, indexable, live URLs. It is not a tool for excluding pages (that's noindex), and it complements rather than replaces internal linking.
A product is legitimately reachable at two URLs that users need (e.g., via two category paths), and you want signals consolidated on one. Which tool fits best?
rel=canonical keeps both URLs accessible to users while telling Google which to index and consolidate signals onto — ideal when both versions must remain live. A 301 would remove access to one URL, noindex would drop it from search entirely, and Disallow would just block crawling without consolidating signals.
Why is rel=canonical described as a 'hint' rather than a 'directive'?
Google treats rel=canonical as a strong signal but can override it when conflicting signals point elsewhere, which is why consistency across canonical, internal links, sitemap, and redirects matters. It works across domains (cross-domain canonicals), doesn't expire, and doesn't require a 301 to function.
What is an 'orphan page' and why does it matter for technical SEO?
An orphan page has no internal links pointing to it, so crawlers struggle to discover it and it receives little to no internal link equity. It's defined by missing inbound internal links — not by outbound links, a 404 status, or a robots.txt block.
Grounded in trusted sources
- Google Search Central, SEO Starter Guide and crawling/indexing docs, https://developers.google.com/search/docs
- Google Search Central, Core Web Vitals / page experience guidance
- Schema.org / Google rich-results documentation
- web.dev performance and CWV primers
- Moz / Ahrefs technical SEO audit checklists (practice patterns)
Every Wunder lesson is built from real, reputable sources — never invented.
Related courses
Wunder is a personalized learn-anything platform — tell it any topic and it builds a beautiful, fact-checked course in minutes, with narration, a knowledge check, and a college-style University track.
© 2026 Wunder Learning LLC · Terms & Privacy