Use logs, international targeting, migration controls, and disciplined roadmapping to manage complex SEO work. Work through the four lessons, apply each exercise to a real, approved, personal, or sandbox site, and retain the result in your continuing portfolio.
Recommended prerequisite: access to a real, client-approved, personal, or sandbox website. Units 1–3 require no prior SEO experience.
Progress is self-reported. Mark a lesson complete only when you are satisfied with the applied work—not because you reached the bottom of the page.
Want completion marks to survive navigation? Save progress in this browser. Without opt-in, progress lasts only on the current page.
Lesson 12.1Not started
Server Log Analysis
Actual requests, bot verification, response patterns, crawl frequency, parameter traps, and retention limitations.
Open on YouTube. Interfaces, platform policies, and product details may have changed; learn the durable principle rather than memorizing buttons.
Learn
The working idea
Actual requests, bot verification, response patterns, crawl frequency, parameter traps, and retention limitations.
Translate this principle into an observable decision: identify the audience task, the evidence available, the business consequence, and the verification method. Keep facts, assumptions, and recommendations separate.
Do the work
Exercise
Analyze sanitized logs and identify three hypotheses, supporting evidence, limitations, and next tests.
Acceptance check: your output should name its source evidence, assumptions, intended user or business outcome, and how the conclusion could be verified.
Quick check
Compare your reasoning
1. What can logs show that a simulated crawl cannot?
Compare with guidance
What the server actually received over time.
2. Why verify claimed bot identities where possible?
Compare with guidance
User-agent strings can be spoofed.
Portfolio handoff
File the evidence
Save the exercise output in your own course workbook or project folder. This site does not upload or retain your work.
Lesson 12.2Not started
International SEO and Hreflang
Language/region codes, reciprocal clusters, self-canonicals, localization, and validation.
Open on YouTube. Interfaces, platform policies, and product details may have changed; learn the durable principle rather than memorizing buttons.
Learn
The working idea
Language/region codes, reciprocal clusters, self-canonicals, localization, and validation.
Translate this principle into an observable decision: identify the audience task, the evidence available, the business consequence, and the verification method. Keep facts, assumptions, and recommendations separate.
Do the work
Exercise
Design a four-URL alternate cluster with canonicals, return links, `x-default` decision, and localization plan.
Acceptance check: your output should name its source evidence, assumptions, intended user or business outcome, and how the conclusion could be verified.
Quick check
Compare your reasoning
1. What is a return-link error?
Compare with guidance
One alternate references another that does not reciprocate.
2. Why should valid alternates usually self-canonicalize?
Compare with guidance
Each is intended as an indexable version for its audience, not a duplicate to consolidate away.
Portfolio handoff
File the evidence
Save the exercise output in your own course workbook or project folder. This site does not upload or retain your work.
Translate this principle into an observable decision: identify the audience task, the evidence available, the business consequence, and the verification method. Keep facts, assumptions, and recommendations separate.
Do the work
Exercise
Build a runbook with ten mappings, benchmarks, owners, launch sequence, seven-day monitoring, and emergency thresholds.
Acceptance check: your output should name its source evidence, assumptions, intended user or business outcome, and how the conclusion could be verified.
Quick check
Compare your reasoning
1. Why are homepage redirects poor substitutes for equivalent destinations?
Compare with guidance
They break intent and may be treated as soft errors.
2. Name one rollback trigger.
Compare with guidance
Widespread 5xx, accidental blocking, broken revenue paths, mapping failure, or severe uncontrolled deindexing.
Portfolio handoff
File the evidence
Save the exercise output in your own course workbook or project folder. This site does not upload or retain your work.
Lesson 12.4Not started
Prioritization, Experiments, and the 90-Day Roadmap
Translate this principle into an observable decision: identify the audience task, the evidence available, the business consequence, and the verification method. Keep facts, assumptions, and recommendations separate.
Do the work
Exercise
Build a 90-day roadmap containing no more than ten initiatives. Each needs owner, evidence, impact, confidence, effort, dependency, risk, metric, test, and stop condition.
Acceptance check: your output should name its source evidence, assumptions, intended user or business outcome, and how the conclusion could be verified.
Quick check
Compare your reasoning
1. Why should low-confidence, high-cost work start with a smaller test?
Compare with guidance
It limits risk and gathers evidence before broad commitment.
2. What makes a roadmap different from a backlog?
Compare with guidance
A roadmap expresses prioritized outcomes, sequence, dependencies, ownership, and measurement—not every possible task.
Portfolio handoff
File the evidence
Save the exercise output in your own course workbook or project folder. This site does not upload or retain your work.
Unit 12 exam
Apply it without pretending the browser is your professor.
Status: Not attempted
Knowledge prompts
Explain one log limitation; define reciprocal hreflang; identify three migration controls; distinguish roadmap from backlog.
Practical assignment
Respond to a scenario involving a CMS migration and two new markets. Submit logs baseline, hreflang architecture, redirect plan, launch controls, rollback thresholds, and 90-day roadmap.