⌘K
DARK
MENU
DARK

Last reviewed

Learn Technical SEO: From Zero to Expert

Technical SEO is the work of making sure search engines and AI assistants can find, crawl, render and index a website's pages. This learning path takes you from zero to job-ready in four stages, with over 100 resources across videos, courses, guides, tools and communities, lessons from people who do the job, and a project at every stage.

  • 213resources
  • 4stages
  • 6 to 9 monthsto job-ready
Start the roadmapSee the tools
Time to job-ready6 to 9 months at 5 to 10 hours a week
DifficultyMedium: logic matters more than code
First job titleSEO Executive or SEO Assistant
You needA laptop and a site to practise on
Learn firstGoogle Search Console
Cost to learnFree; paid tools are optional

What is technical SEO?

Technical SEO covers everything about how a website is built and served that affects whether search engines can use it. Before a page can rank in Google or be cited by ChatGPT, a crawler has to find it, fetch it, read it and decide to store it. Technical SEO makes each of those steps work.

It sits alongside two other parts of SEO. On-page SEO makes the content match what people search for. Off-page SEO earns links and mentions from other sites. Technical SEO is the foundation under both: if it is broken, good content and strong links can’t help.

  1. 1DiscoverCrawlers find URLs through links, sitemaps and direct submissions.
  2. 2CrawlA bot requests the page, follows robots.txt rules and reads the response.
  3. 3RenderGoogle runs the JavaScript so it can see the full page. Many AI crawlers don't.
  4. 4IndexThe page is stored, and one URL is chosen as the canonical version.
  5. 5Rank and citeStored pages appear in results and AI answers when they answer a query best.

What does a technical SEO specialist do?

What a technical seo specialist doesYour website goes in. Crawl and audit sites, Monitor Search Console, Write developer tickets, Check releases before they ship, Plan site migrations, Keep sites readable for AI. Found, read and cited comes out, and results feed back into the next round.DATA AND RESULTS FEED THE NEXT ROUNDYOUR WEBSITEFOUND, READ ANDCITEDTECHNICALSEO1Crawl and auditsites2Monitor SearchConsole3Write developertickets4Check releasesbefore theyship5Plan sitemigrations6Keep sitesreadable for AI
The work flows clockwise from 1 to 6. Each step is explained below.
  1. 1Crawl and audit sitesRun crawls with Screaming Frog or Sitebulb and turn hundreds of warnings into a short, prioritised fix list.
  2. 2Monitor Search ConsoleWatch indexing, crawl stats and Core Web Vitals, and investigate drops the day they happen.
  3. 3Write developer ticketsDescribe the problem, show example URLs, say what correct looks like and how to test it.
  4. 4Check releases before they shipTest status codes, canonicals, robots rules and rendering on staging before every launch.
  5. 5Plan site migrationsMap old URLs to new ones, set up redirects and track recovery after domain, CMS or URL changes.
  6. 6Keep sites readable for AIMake sure AI crawlers can reach key pages and that structured data describes the business correctly.

How to learn technical SEO: a step-by-step roadmap

Work through the stages in order. Each stage mixes formats so you can learn the way that suits you, then proves the skill with a checklist and a project. The hours are a rough guide for someone starting from zero. Use the filter to show only videos, only courses or only free resources.

Learning roadmap for Technical SEO4 stages and 213 resources from beginner to job-ready.YOUR ROADMAPTechnical SEO4 stages, 213 resources, one project per stageBEGINNER10 TO 20Basics20 to 30 hours220 TO 50Core skills40 to 60 hours350 TO 80Practice80 to 120 hours480 TO 100MasteryOngoingJob-ready: SEOExecutive or SEOAssistant
Your route through this learning path. Select a stage to jump to it.
Show
1

0 to 20About 20 to 30 hours

Stage 1: Technical SEO basics

Understand how search engines find, read and store pages, and read the HTML and HTTP signals they rely on.

How search engines and AI assistants work

Start with the whole journey from a link to a ranking, so every later topic has a place to fit.

Key concepts
  • Crawling
  • Indexing
  • Ranking
  • Rendering
  • Search index
  • AI Overviews
  • Retrieval for AI answers

HTML, HTTP and DNS for SEO

You do not need to code, but you must read a page source, know what a status code means and understand how a domain name finds a server.

Key concepts
  • The head section
  • Title tag
  • Meta description
  • Headings
  • Anchor links
  • View source vs inspect
  • Status codes
  • Response headers
  • DNS

Google Search Console and Bing Webmaster Tools

The free tools every technical SEO uses daily. Learn the Page indexing report and URL Inspection first, then connect Bing as well.

Key concepts
  • Page indexing report
  • URL Inspection
  • Performance report
  • Sitemaps report
  • Property types
  • Bing Webmaster Tools

Free extensions, crawlers and checkers

You do not need a paid tool to start auditing. Install two or three extensions and use the free crawlers for status codes, headers and duplicate content.

Key concepts
  • Browser extensions
  • Free crawlers
  • Header checks
  • Status code checks
  • Duplicate content

Read one complete guide end to end

Different writers explain the same ideas differently. Pick one or two of these and read them in full before stage 2.

Key concepts
  • Pick one guide
  • Finish it
  • Note what you do not understand
  • Compare two writers

Check yourself: you are ready for the next stage when you can

Project

Set up and read your own site

Create a free WordPress or Blogger site with ten pages, or use a site you already control. Add it to Search Console and Bing Webmaster Tools and submit a sitemap.

Deliver
A one-page note explaining what the Page indexing report shows after two weeks, with screenshots.
Done when
You can explain every status in the report and why each page is or isn't indexed.
2

20 to 50About 40 to 60 hours

Stage 2: Crawling, indexing and site structure

Control what gets crawled and indexed, and explain why any page is or isn't in search.

Crawl and index control

robots.txt decides what can be crawled; meta robots and noindex decide what can be indexed. Add crawlable links, clean URLs and mobile-first indexing to complete the picture.

Key concepts
  • robots.txt
  • User agents
  • Disallow vs noindex
  • Meta robots
  • X-Robots-Tag
  • nosnippet
  • Crawlable links
  • Mobile-first indexing

Sitemaps, canonicals, duplicates and pagination

Sitemaps tell search engines what you want indexed; canonical tags tell them which version of similar pages to keep.

Key concepts
  • Sitemap index files
  • lastmod
  • Only indexable URLs
  • rel=canonical
  • Duplicate URLs
  • Parameters
  • Canonical signals
  • Pagination

Status codes, redirects and site architecture

Redirect chains, soft 404s and server errors waste crawling and lose link value. How pages link together decides what gets crawled most and what looks important.

Key concepts
  • 301 vs 302
  • Redirect chains
  • Soft 404
  • 410 Gone
  • 5xx errors
  • URL structure
  • Click depth
  • Orphan pages
  • Hub and spoke

Structured data, images and video

Structured data tells search engines and AI systems what a page is about: a product, an article, an organisation. Learn the vocabulary and test everything.

Key concepts
  • JSON-LD
  • schema.org types
  • Rich results
  • Organization and Person
  • sameAs
  • Structured data policies
  • Image alt text
  • Image and video sitemaps

Courses and crawling in practice

If you prefer one guided course over separate topics, pick one of these and do it end to end.

Key concepts
  • Pick one course
  • Finish it
  • Run a crawl
  • Segment a crawl
  • Apply each module to a real site

Check yourself: you are ready for the next stage when you can

Project

Your first crawl report

Crawl a real 100 to 500 page site with Screaming Frog's free version (a local business, a charity or your own site), and practise first on crawler-test.com.

Deliver
A report of the ten biggest issues, why each matters, and the fix, ranked by impact.
Done when
Someone without SEO knowledge can read your report and know what to fix first.
3

50 to 80About 80 to 120 hours, mostly hands-on

Stage 3: Technical SEO audits in practice

Run a full audit on a real site, prioritise the fixes, get them built and measure the result.

Running a full audit and reading Search Console data

An audit is only as good as its prioritisation. Learn a repeatable process, then adapt it. Read Search Console like a doctor reads test results: every status has a cause.

Key concepts
  • Crawl configuration
  • Issue prioritisation
  • Templates vs pages
  • Crawl comparison
  • Audit deliverables
  • Developer tickets
  • Page indexing report
  • Crawl Stats

JavaScript SEO and rendering

More sites are built on React, Vue and Next.js. You need to know when content depends on JavaScript and what that costs.

Key concepts
  • Client-side rendering
  • Server-side rendering
  • Static generation
  • Hydration
  • Rendered HTML
  • Lazy loading

Page speed and Core Web Vitals

Learn what the three metrics measure and which fixes developers can actually make.

Key concepts
  • LCP
  • INP
  • CLS
  • Field vs lab data
  • CrUX
  • Lighthouse

Site migrations

Domain changes, redesigns and CMS moves are where most traffic is lost, and where technical SEOs earn their reputation.

Key concepts
  • URL mapping
  • Redirect maps
  • Benchmarks
  • Staging checks
  • Post-launch monitoring

AI crawlers, agent readiness and CMS platforms

AI assistants use their own bots with their own rules, and most sites you audit run on a CMS. Check access for each bot and learn where the CMS keeps its SEO settings.

Key concepts
  • Search vs training crawlers
  • User-fetch bots
  • AI Overviews eligibility
  • Agent-friendly pages
  • CMS defaults
  • SEO plugins
  • Theme templates

Check yourself: you are ready for the next stage when you can

Project

A real audit that gets fixes shipped

Audit a real business site with permission: a friend's business, a charity or your employer. Agree which fixes they'll build.

Deliver
An audit deck, the tickets you wrote, and a before-and-after Search Console comparison four to eight weeks after the fixes.
Done when
At least three fixes are live and you can show what changed in the data.
4

80 to 100Ongoing, 6 months or more

Stage 4: Advanced technical SEO

Handle large sites, unusual setups and constant change, and lead technical work with engineering teams.

Large sites, crawl budget and log files

On sites with hundreds of thousands of URLs, what Google chooses to crawl becomes a real constraint. Server logs are the ground truth behind Search Console summaries.

Key concepts
  • Crawl capacity
  • Crawl demand
  • Faceted navigation
  • Parameter handling
  • Access logs
  • Bot verification
  • Wasted crawl

International SEO and hreflang

Multi-country and multi-language sites need hreflang, which is easy to get wrong at scale.

Key concepts
  • hreflang
  • x-default
  • ccTLDs vs subfolders
  • Return tags
  • Language vs region

AI crawlers, bot control and edge SEO

Each AI company documents its own bots, and the CDN is where you enforce the rules. Know the names, what blocking each one does and how to act at the edge.

Key concepts
  • Training vs search crawlers
  • User agents
  • robots.txt rules for AI bots
  • CDN bot rules
  • Edge workers
  • IndexNow
  • llms.txt

Automation, SEO testing and diagnosing traffic drops

Senior roles expect you to pull data at scale, test changes properly and stay calm when traffic falls. Start with regex and the Search Console API, then add Python.

Key concepts
  • Python
  • Regex
  • Custom extraction
  • Search Console API
  • BigQuery
  • SEO testing
  • Algorithm updates
  • Annotations
  • Segmenting traffic
  • Technical vs content causes

Advanced training, newsletters, podcasts and communities

At this level you learn most from other practitioners. Pick one course, one podcast and one community.

Key concepts
  • Specialist courses
  • Podcasts
  • Communities
  • Conferences
  • Newsletters

Check yourself: you are ready for the next stage when you can

Project

A public case study

Lead or support a migration, a large-site crawl project or a traffic-drop investigation.

Deliver
A public case study with before-and-after data, including what went wrong and what you would do differently.
Done when
A hiring manager could read it and understand exactly what you did and what changed.

Technical SEO tools to learn

Learn firstGoogle Search ConsoleWhat Google itself sees: indexing, crawl stats, Core Web Vitals and search performance.FreeLearn firstScreaming Frog SEO SpiderCrawls a site the way a search engine does. The standard audit tool in most job adverts.Free planChrome DevToolsInspect HTML, network requests, headers and rendering in your browser.FreeBing Webmaster ToolsBing indexing data, which also feeds Copilot, plus IndexNow submissions.FreePageSpeed InsightsCore Web Vitals from real users and lab tests for any URL.FreeRich Results TestChecks the structured data Google can read on a page.FreeTechnicalSEO.com toolsFree testers for robots.txt, rendering, hreflang and more.FreeSitebulbCrawler with prioritised, explained audit hints. Good for learning why issues matter.PaidScreaming Frog Log File AnalyserShows which pages bots really request, from your server logs.Free planLooker StudioDashboards that report Search Console data to managers and clients.FreeSchema Markup ValidatorChecks any schema.org markup, including types Google shows no rich result for.Free

Is technical SEO a good career?

Yes, for people who like solving puzzles and working with developers. Technical SEO is one of the most specialised parts of marketing, and the specialism tends to hold its value as search changes.

Every SEO channel depends on it

Content, links and AI search only work if pages can be crawled and indexed, so technical checks come first in almost every SEO audit.

AI search raises the stakes

AI assistants send their own crawlers, and many don't run JavaScript. Sites now have to be readable by more bots with different rules.

It bridges marketing and engineering

People who can turn a ranking problem into a clear engineering ticket are scarce in most teams, which makes the skill valuable.

It opens several career doors

Technical SEOs move into SEO leadership, growth product management, analytics and engineering roles, or go independent as consultants.

Technical SEO career path and jobs

  1. Entry

    SEO Executive or SEO Assistant

    Runs crawls, monitors Search Console and logs issues for developers to fix.

  2. Mid

    Technical SEO Specialist

    Owns audits, writes tickets, checks fixes and tests every release.

  3. Senior

    Technical SEO Manager or Lead

    Sets priorities with engineering, leads migrations and sets standards for templates.

  4. Leadership

    Head of SEO or SEO Director

    Owns organic growth across technical, content and AI search, with a budget and a team.

  5. Specialist

    SEO Engineer

    Builds SEO into code, templates and rendering, usually on large sites and marketplaces.

  6. Independent

    Technical SEO Consultant

    Runs audits and migrations for several clients at once.

Common technical SEO mistakes beginners make

MistakeTreating every crawler warning as urgent.

Do thisRank issues by pages affected and their value. Most audit warnings can wait; a few can't.

MistakeBlocking pages in robots.txt to remove them from Google.

Do thisLet them be crawled and add noindex, or return 404 or 410 if they're gone.

MistakeLaunching without checking staging leftovers.

Do thisCheck robots.txt, noindex tags and canonicals within minutes of every launch.

MistakeWriting audits that read like essays.

Do thisWrite tickets: example URLs, the problem, what correct looks like and how to test it.

MistakeOnly checking Googlebot.

Do thisTest access and readability for Bing and the AI crawlers too, especially on JavaScript sites.

MistakeFixing things without measuring.

Do thisRecord the release date and compare data before and after. Results are what get you hired and promoted.

How to get a technical SEO job

Employers hiring a first technical SEO look for evidence that you can find problems, explain them and get them fixed. Your portfolio matters more than certificates.

Job-ready checklist

  • You can run a crawl and explain every major issue it finds
  • You can read Search Console's indexing and performance reports fluently
  • You can explain JavaScript rendering and when it causes problems
  • You have written developer tickets that were built
  • You can plan a basic site migration with a redirect map
  • You can talk about one project where your fixes changed the numbers

Portfolio pieces that get interviews

  1. A technical audit of a real site, with your prioritised fix list
  2. A crawl comparison: JavaScript rendering off versus on, with what changed
  3. A redirect map and launch checklist for a migration, real or practice
  4. A before-and-after case study with Search Console data and dates

Technical SEO interview questions

A page isn't showing in Google. How would you find out why?

A strong answer covers: URL Inspection first: is it indexed, crawled, blocked or canonicalised elsewhere? Then robots.txt, noindex, status code, canonical, internal links and whether the content needs JavaScript. A good answer follows a clear order, not a random list.

What's the difference between robots.txt and noindex?

A strong answer covers: robots.txt controls crawling, noindex controls indexing. A blocked page can still be indexed from links, and noindex only works if the page can be crawled. Mention when you'd use each.

How would you prioritise 200 issues from an audit?

A strong answer covers: Impact on important pages, number of pages affected, effort and risk. Group issues by template, fix the ones that affect revenue pages first, and explain the trade-offs to stakeholders.

Walk me through a site migration.

A strong answer covers: Benchmark first, crawl and inventory every URL, map old to new, set 301 redirects, test on staging, launch with monitoring, then check logs, Search Console and rankings for weeks after. Mention what usually goes wrong.

How do AI crawlers change technical SEO?

A strong answer covers: More bots with different rules: training versus search crawlers, many not running JavaScript, and robots.txt or firewall settings that block them by accident. Show you'd test access for each one.

Technical SEO glossary

Crawling
A bot requesting pages and following links to discover more of a site.
Indexing
Storing a crawled page so it can appear in search results and AI answers.
Rendering
Running a page's JavaScript to build the final content a user sees.
Crawl budget
How many URLs a search engine is willing and able to crawl on a site in a given time.
robots.txt
A file at the root of a site that tells crawlers which paths they may request.
noindex
A meta tag or header that tells search engines not to keep a page in their index.
Canonical URL
The version of a page a search engine chooses to index when several URLs show the same content.
301 redirect
A permanent redirect that passes users and most signals from an old URL to a new one.
Soft 404
A page that says 'not found' to users but returns a 200 status code to bots.
XML sitemap
A file listing the URLs a site wants search engines to crawl and index.
hreflang
An attribute that tells search engines which language or country version of a page to show.
Structured data
Code, usually JSON-LD, that describes a page's content using schema.org types.
Core Web Vitals
Google's three user-experience metrics: LCP for loading, INP for responsiveness and CLS for visual stability.
Mobile-first indexing
Google using the mobile version of a page for indexing and ranking.
Server-side rendering
Building the full HTML on the server so crawlers get the content without running JavaScript.
Faceted navigation
Filters on listing pages, such as size or colour, that can create millions of URL combinations.
Log file
A server record of every request, including which bots asked for which URLs and when.
Orphan page
A page with no internal links pointing to it, so crawlers struggle to find it.
Redirect chain
Several redirects in a row before reaching the final URL, which slows crawling and loses signals.
Edge SEO
Changing pages or headers at the CDN level, for example with Cloudflare Workers, without touching the CMS.
User agent
The name a bot or browser sends with each request, such as Googlebot or OAI-SearchBot.
IndexNow
A protocol that lets sites notify Bing and other engines instantly when URLs change.

Technical SEO FAQs

Do I need to know how to code for technical SEO?

You need to read code, not write it. Learn enough HTML to inspect a page, enough HTTP to read status codes and headers, and enough JavaScript to know when content depends on it. Most technical SEOs never ship code; they write clear tickets and check the result.

How long does it take to learn technical SEO?

As a rough guide, with five to ten hours a week you can finish the basics in about a month and be ready for a first role in six to nine months, if you do the projects. Real expertise comes from working on many different sites, which takes years.

What's the difference between technical SEO and on-page SEO?

Technical SEO makes sure pages can be crawled, rendered and indexed. On-page SEO makes the content on those pages match what people search for. They overlap on titles, headings and internal links, and most SEO jobs need both, with one as your main strength.

Is technical SEO still relevant with AI search?

More than before. AI assistants rely on crawlers too, and several don't run JavaScript, so a page that hides its content behind scripts or blocks those bots can't be cited. Checking access for every crawler is now part of the job.

Which technical SEO certification is worth getting?

Certificates help less than a portfolio, but a structured course keeps you on track. Free options include the Ahrefs and Semrush technical SEO courses; Tech SEO Pro is a respected paid option. Pair any course with a real audit you can show.

Can I learn technical SEO for free?

Yes. Every core topic on this page has free resources, and the main tools have free versions: Search Console, Bing Webmaster Tools, Screaming Frog up to 500 URLs and PageSpeed Insights. Paid tools and courses speed things up but aren't required.

More learning paths in the seo and ai search map

  • Content and on-page SEOKeyword research, search intent, briefs and on-page optimisation.
  • AI search optimisation (AEO and GEO)Getting cited and recommended in ChatGPT, Perplexity, Gemini and AI Overviews.
  • International SEOHreflang, market selection and localisation for search.
  • Local SEOGoogle Business Profiles, citations and reviews.
  • E-commerce SEOProduct and category pages, faceted navigation.
  • Programmatic SEOComing soonData-driven page templates at scale.
  • Enterprise SEOComing soonSEO across large sites, teams and governance.
  • Link building and digital PREarning links and mentions through stories and data.
  • Marketplace SEOComing soonRanking inside Amazon, Jumia and Etsy search.
  • App Store OptimisationApp store rankings and conversion.
  • Video SEOComing soonYouTube and video search.