Essentials
8 guided hoursModules 1-2. An introduction with practical exercises and a small reviewed artifact.
MARKETING · SOME SEO FAMILIARITY
Turn search data into a useful work queue.
Automate repeatable SEO research, technical checks and reporting while keeping content decisions under human review. Work with sample Search Console and crawl exports to build a prioritised SEO workflow.
COURSE OVERVIEW
Build repeatable SEO audit, content planning and reporting workflows with data validation and human review. Create an SEO operations toolkit; automation does not guarantee search rankings.
OPTIONAL AI PRACTICE
Selected modules include an optional prompt-and-review exercise. Verify the result using the underlying skills taught in this course.
Explore the Prompting FoundationA STARTING POINT THAT FITS
Modules 1-2. An introduction with practical exercises and a small reviewed artifact.
Modules 1-6, including Essentials. Complete the core labs and an assessed practical project.
Two extension modules and a four-hour project clinic after practitioner readiness.
These are curriculum planning options. We confirm the timetable, delivery format, fees and required accounts before enrolment. Practitioner includes Essentials; the two durations are not added together.
Download the Curriculum PDFWHAT YOU’LL LEARN
Marketers, website owners and SEO practitioners who want a repeatable way to audit, organise and report on search performance.
Basic familiarity with SEO and spreadsheets. Python knowledge is useful for code-based exercises; a spreadsheet-based workflow can be used.
THE COURSE OUTLINE
Each module connects a concept to a practical task. Open a module to see its topics and exercise.
Crawling is fetching a page; indexing is processing it for possible retrieval; ranking selects and orders results for a particular search. These stages depend on different evidence. A successful HTTP response proves availability at the observation time, but it does not prove indexing or a future position. Riverstone Learning needs a monthly review, not an automatic publishing machine. Describe the decision, required inputs, owner, frequency and acceptance criteria before selecting a tool. A useful outcome is a reviewed queue with traceable evidence. Traffic growth is a downstream hypothesis, not a guaranteed automation result. Automation can organize exports and expose missing information; it cannot replace expertise about learners. Prioritize accessible, accurate course descriptions and helpful examples. Do not manufacture search volumes, credentials or learner testimonials. Content generation should support an editor who checks facts and relevance before any proposed publication.
Write an automation brief for a monthly SEO review.
One row represents a specific date, page and query combination in the training fixture. Real exports can have different dimensions and filtering. Write the grain beside the table before summing anything. The same URL appearing for different queries is expected; an identical full key requires a duplicate investigation. Click-through rate is clicks divided by impressions, expressed as a percentage. Aggregate it by adding clicks and impressions first. Averaging row percentages gives small rows too much influence. When impressions are zero, display not applicable rather than zero or an error, and inspect whether clicks contradict the denominator. Blank values mean unknown unless the source defines otherwise. Keep original exports, record the date range and filters, and write cleaned outputs separately. Normalize whitespace consistently without removing meaningful URL paths or query terms. Flag invalid numeric values and suspicious duplicates rather than silently inventing replacements or deleting evidence.
Create a validated dataset from sample search exports.
A crawl observes HTTP responses and link destinations at one time. A 404 indicates a missing requested resource; a redirect needs a destination check; a 200 can still contain a soft error or blocked content. Keep observed facts separate from diagnosis and avoid assuming every response identifies a Google indexing decision. Missing titles, duplicate titles and conflicting canonicals can be flagged with deterministic rules. Titles should describe the page; descriptions may help users understand results but are not guaranteed snippets. A canonical is a signal about preferred URLs. Review page purpose and rendered content before recommending a corrective change. An issue queue needs a stable identifier, affected page, rule, observed value, likely impact and next verification step. Broken enrolment links may deserve attention before a description gap. Label confidence and responsibility explicitly. An automatic flag should request investigation, not assert that an unverified fix will improve rankings.
Build a technical issue list from a sample crawl export.
Queries express different needs: learning a skill, comparing courses or enrolling. Start with the actual words in the fixture and the documented page purpose. Group similar intents while retaining the original queries and uncertainty. AI can suggest labels, but an analyst should review ambiguous terms and avoid inventing demand estimates. A page with impressions and few clicks may have an unclear title, weak relevance, competition or another explanation. The dataset alone does not establish cause. Pair metrics with a content inspection and propose a small improvement hypothesis. Record what would support or challenge it instead of asserting a guaranteed traffic gain. A content brief identifies the audience question, existing coverage, factual sources, useful example and reviewer. For an academy, accurate prerequisites, sample projects and learning outcomes may help prospective students. Do not claim accreditation or jobs without evidence. Keep an editor responsible for checking claims before any draft reaches the website.
Create a content improvement queue with evidence and proposed actions.
Group these sample search and content issues into an improvement queue. Use the evidence provided and identify missing data. Do not invent search volume or publish content.
Validate the proposed issues against the exports and review every recommendation before a website change.
Period comparison requires equal duration, consistent filters and a comparable data cut. Holidays, course launches and incomplete recent data can change interpretation. Label baseline and current ranges, units and extraction times. Report what changed without assigning cause unless a documented event or further evidence supports that explanation. An alert is a request for review, not a diagnosis. Specify the metric, absolute and relative thresholds, minimum baseline and data-completeness condition. A tiny page can show a large percentage swing from one click. Pair percentages with counts and explain which comparisons are suppressed when inputs are missing or insufficient. A useful report connects findings to rows, page URLs and methodology. State missing periods, excluded duplicates and uncertainty. Separate observations, possible explanations and proposed checks. Give the reader a clear next step and responsible owner; a polished chart cannot compensate for silently comparing different scopes or incomplete inputs.
Generate a monthly SEO report and a sample exception alert.
A dependable workflow validates required fields before calculation. Missing exports, renamed columns and invalid dates should produce clear errors rather than plausible-looking reports. Write tests for normal, empty and malformed inputs. Distinguish a valid zero-result report from a failed run that never received the expected data. Use a fixed input snapshot, stable issue identifiers and an output folder per run. Record schema, thresholds and source dates so reviewers can reproduce findings. Reprocessing the same inputs should not multiply issues. Keep original exports unchanged and document deliberate rule changes that alter output between workflow versions. The operating guide names who supplies exports, who runs the checks and who reviews findings. Include a checklist for stopping on validation failure, rebuilding from a known input and performing the review manually. No website edits occur in the learning workflow. Any later publishing process requires a separately controlled approval stage.
Demonstrate the workflow with a repeat-run checklist and manual fallback.
AFTER THE CORE COURSE
Build a verified learner FAQ
Design an extraction contract
Complete both four-hour extension modules and a four-hour project clinic. Entry uses the core project and readiness evidence.
BRING THE SKILLS TOGETHER
Combine sample search and crawl exports into a technical issue list, a content improvement queue and a monthly report. Include a human review checkpoint before any website change.
A learning project using sample or permitted material. The final scope is agreed for your learning plan.
KEEP EXPLORING
Reference material to complement the Hawa Enterprises curriculum. Account features may vary; basic-feature or manual alternatives support the core exercises.
Course outline published by Hawa Enterprises. Updated . Ask about the learning plan.
GOOD TO KNOW
No. The course focuses on useful operations, data checks and content improvement. Search rankings, indexing and traffic outcomes are not guaranteed.
No automatic publishing is part of this outline. Content drafts and proposed changes require factual checks and a person’s review before use.
These details are confirmed by email before you commit. The curriculum gives guided-hour options for Essentials, Practitioner and Advanced. Actual schedules, fees and delivery arrangements are confirmed before enrolment. Ask about the course you want and your preferred timeline.
Choose a course and complete the enrollment wizard with your name, email and WhatsApp number. Review your details before sending the enquiry. Hawa Enterprises will discuss your starting level, goals and course arrangements before enrolment is confirmed.
YOUR NEXT SKILL STARTS HERE
Tell us your goal, starting level and preferred timeline.