Earn the Sophyx Certified Technical GEO Specialist – Professional credential.
Technical GEO Specialist is a free 12-lesson video course by Sophyx for developers and technical SEOs. You learn to build a site that AI systems can fetch, read, trust and act on, and to keep it that way: verified bot access, facts in the first HTML response, structured data, pages and APIs that AI agents can use, and checks on every deploy. It builds on Answer Engine Specialist, and every lesson works through one fictional company: Gearwick Bikes, an online bike shop.
Regular price USD 129.Your first certification is free.
Free with any paid Sophyx plan. Certificates take up to 30% off your plan. See plans
Level
Professional · GEO-300
Lessons
12 lessons
Video
36 min in total
Price
USD 129
Lesson 1 of 12 · Technical GEO Specialist
AI crawlers and fetchers
Captions, 3:04
Sophyx Certified Technical GEO Specialist – Professional
Verifiable · valid 12 months
Who it's for
Developers
You own the code and the deploys. You want AI fetchers to get the facts in the first response, and checks that stop a release from breaking it.
Technical SEOs
You know crawling and indexing. You want to know which AI bots visit, how to check they are real, and how to set a bot policy for each job.
Platform teams
You run the servers and the CDN. You want verified bot logs, alerts when AI bots get errors, and responses that stay fast.
Before you start
Answer Engine Specialist (AE-200) first is recommended, plus comfort with HTTP, HTML and a terminal. If you already know how AI search works, you can start here.
Worked examples
The lessons follow Gearwick Bikes, a fictional online bike shop whose storefront is a JavaScript app, and its fictional rival Tarnway Cycles. Every brand in the course is fictional and every number is illustrative.
What you'll be able to do
A sample of the 36 objectives across the 4 modules.
Verify who a bot really is
Write a bot decision table by job
Serve key facts in the first HTML response
Model your brand as entities with stable @ids
Run an agent walkthrough of a key task
Build an MCP server with tools and resources
Alert on errors sent to verified bots and on new tokens
Add GEO checks to the deploy pipeline
Look inside
Twelve lessons in four modules: let AI in, make the site machine-readable, get it ready for agents, then observe and operate.
Lesson 1AI crawlers and fetchers3:04
Lesson 2Bot policy as code3:03
Lesson 3What fetchers see3:03
Lesson 4Structured data as a graph3:07
Lesson 5Semantic HTML for passages3:03
Lesson 6Discovery files and feeds3:06
Lesson 7Pages agents can use3:00
Lesson 8APIs and MCP for brands2:59
Lesson 9Fast, reliable responses2:58
Lesson 10AI bot logs, verified2:49
Lesson 11AI referral plumbing2:58
Lesson 12GEO CI and governance2:59
Syllabus
4 modules, 12 lessons, about 36 minutes of video. Each lesson has captions, chapters, a transcript and a practice quiz.
1
Module 1 · 3 lessons ·
Let AI In
The three jobs AI bots do and how to verify a bot before you trust it; bot policy as code (robots.txt by job, control tokens, CDN rules, proposals labelled); what a fetcher without JavaScript actually receives.
AI companies run bots for three jobs: training crawlers, search indexers, and user-triggered fetchers that fetch a page the moment a person asks an assistant something. Each bot names itself with a product token inside its user agent string; Google-Extended and Applebot-Extended are control tokens, not crawlers. A token is only text, so verify a bot before you trust it: the vendor's published IP list, reverse then forward DNS, or a signed request (Web Bot Auth, an IETF draft). Bot names and behaviours are as of October 2026.
Bot policy is one decision per job, written as code and tested. robots.txt (RFC 9309) groups rules by product token, applies the longest matching path, and can announce your sitemap; most vendors cache it for about a day. Decide per job: search indexers and user-triggered fetchers bring answers and visits; training is a business choice; control tokens such as Google-Extended set AI use without touching the crawl. Your CDN or WAF adds a second layer: allow verified bots by category, block the unverified. Newer signals (Content Signals, the IETF AIPREF drafts) are proposals, and some user fetchers say robots.txt may not apply to them. Keep the policy in version control with a test for every allowed token.
A fetcher receives one HTTP response. Googlebot and Applebot render JavaScript; the crawlers and user fetchers from OpenAI, Anthropic and Perplexity did not in the largest published study (Vercel and MERJ, 2024), and none of them documents rendering as of October 2026, so a page whose facts arrive only through scripts is empty to them. (Browser agents are a different case: Lesson 07.) Test it: fetch the page as the bot with JavaScript off and read the HTML. Serve the facts in that first response with server-side rendering, static generation or pre-rendering, and keep the status honest: a 200 for real pages, a real 404 for missing ones, no consent walls, interstitials or geo-blocks in front of bots, and no "soft 404" shells.
2
Module 2 · 3 lessons ·
Machine-Readable by Design
Structured data as an entity graph with stable @ids; HTML written as quotable passages; discovery files and feeds judged by what they earn.
Structured data is a graph, not a sprinkle of snippets. In JSON-LD, give every real-world thing one node with a stable @id, reuse that @id on every page that mentions it, and connect the nodes: the organisation, its website, its locations, its products and offers, its people. Link each entity to its official profiles with sameAs. Keep the markup true to the visible page, because Google ignores or penalises markup for things users cannot see, and validate it on every deploy. Google says no new markup is required for its AI features (as of 2026); the graph still removes ambiguity about who you are.
AI systems quote passages, so write the page as passages. One question per section, answered in the first sentence under a heading that says the question; article and section elements with a clean h1–h6 order; tables for specifications and comparisons; ordered lists for steps; time elements for dates; a lang attribute; link text that names its target. Text inside tabs and accordions counts when it is in the HTML, not when it is loaded on click. Specs in images, PDFs and carousels are invisible: put them in text.
Discovery files tell bots what you have and what changed. A sitemap lists canonical URLs with an honest lastmod (50,000 URLs and 50 MB per file; index files above that), announced with a Sitemap line in robots.txt. IndexNow pushes changed URLs to Bing, Yandex, Naver, Seznam, Yep and Amazon, but not to Google. Feeds (RSS, Atom) and HTTP validators (ETag, Last-Modified) tell fetchers what is fresh. llms.txt is a proposal: a markdown map of your key pages; as of 2026 no major assistant documents reading it when it answers, and Google says its AI features need no AI text files, so publish it cheaply and judge it by the fetches in your own logs.
3
Module 3 · 3 lessons ·
Ready for Agents
Pages agents can operate; one source of truth exposed as an API and an MCP server; fast, cacheable responses that never shrink the crawl.
AI agents (as of October 2026: ChatGPT's cloud browser, Claude's computer use, Google-Agent) act through the page the way assistive technology does: they read the accessibility tree and operate real controls. Give them real forms with labels, buttons that are buttons, links with names, visible state and error messages, keyboard paths with no hover-only menus, and a checkout that does not hide steps behind scripts or unlabelled icons. Let verified agents through your bot defences, and keep consent walls off the task path. The test is the walkthrough: find, compare, act.
Assistants and agents can call you directly. Expose one source of truth as an API: an OpenAPI description, read-only endpoints for facts such as price, stock, hours and specs, and the same data your pages show. The Model Context Protocol (MCP) standardises how an assistant connects: a server offers tools and resources over Streamable HTTP, with OAuth 2.1 for anything personal, and consent before any action. Rate-limit, log and version it, and keep it in sync with the site, because two sources of truth make two different answers. App directories are built on MCP servers (as of October 2026, ChatGPT's plugin directory, which replaced its app directory in July 2026); treat their rules as dated.
Fetchers give up fast. Keep time to first byte low, serve bots from the edge cache, and use Cache-Control, ETag and 304 so unchanged pages cost nothing. Google shrinks its crawl when responses slow down or return 5xx and 429, and a robots.txt that errors can hold crawling back altogether. Rate limits should spare verified bots; redirects should land in one hop; Core Web Vitals (LCP 2.5 s, INP 200 ms, CLS 0.1 at the 75th percentile) keep the human side fast. Monitor with synthetic fetches as the bots.
4
Module 4 · 3 lessons ·
Observe and Operate
A verified bot log pipeline with alerts; referral plumbing that keeps the AI source attached; GEO checks in CI with owners and a change log.
Turn raw logs into a verified bot feed. Parse CDN or server logs, classify each request by product token and job, then verify: match the IP against the vendor lists you refresh daily, do reverse and forward DNS with a cache, and check signatures where bots sign. Store the result with the status code and the path. Then alert on what matters: 403, 429 or 5xx sent to a verified bot, a new token appearing, a key page no longer fetched, robots.txt fetches failing. Keep IP retention short. (GEO-310 reads the same feed for metrics; this lesson builds it.)
A click from an AI answer only shows as an AI visit if the plumbing keeps the source attached. Browsers default to strict-origin-when-cross-origin, sending only the origin across sites and nothing on an HTTPS-to-HTTP step, so serve HTTPS everywhere. ChatGPT appends utm_source=chatgpt.com; a redirect that drops the query string, a canonicalisation step, a consent wall or a geo-redirect to the home page loses it. Make sure landing pages exist, log the referrer and the UTM on the server, and test the path from an answer link to the final page. GA4's AI Assistant channel (as of 2026) can only see what survives.
Everything in this course can be undone by one deploy. Put the checks in CI: robots.txt allow tests per token, a fetch of each key page as a bot with JavaScript off that fails on an empty shell, structured-data validation against the entity graph, sitemap validity and lastmod sanity, a TTFB budget, a referral test, and a check that staging rules never ship. Give each policy an owner, keep a change log, and review the vendor documentation quarterly, because tokens and rules change. GEO is operated, not launched.
Watch, practice, prove, then get certified: the same four steps in every Xlearn by Sophyx course.
1
Watch
Watch all 12 lessons. Each one is about 2 to 3 minutes, with captions, chapters and a transcript.
2
Practice
Take the practice quiz after each lesson. Try as often as you like, and every wrong answer tells you why.
3
Prove
Pass the final exam: 40 questions, 60 minutes, 75% to pass, and 24 hours between attempts. Pass it and the certificate is yours.
4
Get certified
Your certificate gets its own credential ID and a public page anyone can check. Add it to LinkedIn in one click or download the PDF. It is valid for 12 months.
Final exam
You can retake it after 24 hours.
questions
40
minutes
60
to pass
75%
Your certificate
One page that proves what you learned, with a link anyone can open to check it.
Xlearn by Sophyx
Certificate of completion
Sample
This certifies that
Your name
has earned the credential
Sophyx Certified Technical GEO Specialist – Professional
for completing the 12 lessons of Technical GEO Specialist and passing the final exam.
Code
GEO-300 · Professional
Valid
12 months
Credential ID
GEO-300-26-7K2M9QXD
Verify at
sophyx.io/verify/GEO-300-26-7K2M9QXD
Verified
Sample certificate. Yours carries your name and its own credential ID.
A unique, random credential ID
A public verification page anyone can open
One-click Add to LinkedIn
A PDF you can download and share
Valid for 12 months
It is a Sophyx credential, not an accredited qualification.
The discount lasts while your certificates are valid. A new certificate never lowers the discount you have. It applies to Pro, Agency Lite and Agency Pro.
Technical GEO Specialist (GEO-300) is a free 12-lesson video course by Sophyx for developers and technical SEOs. It teaches you to build a site that AI systems can fetch, read, trust and act on, and to keep it that way. It ends with the Sophyx Certified Technical GEO Specialist – Professional certificate.
Who is it for?
Developers, technical SEOs and platform teams: the people who own the server, the CDN, the templates, the structured data and the deploys, and who get asked whether AI can actually read the site.
Do I need Answer Engine Specialist first?
It is recommended, not required. You should know how AI search works, which Answer Engine Specialist (AE-200) covers, and be comfortable with HTTP, HTML and a terminal.
What does it cover?
Four modules. Let AI in: which AI bots visit, how to check they are real, a bot policy kept as code, and what a bot that does not run JavaScript receives. Machine-readable by design: structured data as one connected graph, HTML written as quotable passages, and sitemaps, feeds and llms.txt. Ready for agents: pages AI agents can use, an API or MCP server for your facts (MCP is a standard way for an assistant to connect to a service), and fast responses. Observe and operate: verified bot logs, AI referral tracking that survives redirects, and checks on every deploy.
What is the worked example?
Gearwick Bikes, a fictional online bike shop whose storefront is a JavaScript app, and its fictional rival Tarnway Cycles, a plain server-rendered shop. All brands in the course are fictional and all numbers are illustrative. Platform details such as bot names are stated as of October 2026.
How long does it take?
There are 12 lessons and about 36 minutes of video, each lesson with a practice quiz. Then comes the final exam.
What is the final exam like?
The final exam has 40 questions, a 60-minute limit and a 75% pass mark, with 24 hours between attempts.
Is the certificate an accredited qualification?
No. It is a Sophyx credential, not an accredited qualification, and it does not come from a university or a government body. It shows that you watched the course, took the practice quizzes and passed the final exam. Anyone can check it on its public verification page, and it is valid for 12 months.
Is it free?
Your first certification is free. Free with any paid Sophyx plan. The regular price of Technical GEO Specialist is USD 129.