New to SEO
Start with SEO tutorials for beginners: discovery, indexing, Search Console metrics and links.
Start with fundamentalsLEARN SEOKIT
Follow SEO tutorials from beginner concepts to repeatable workflows with Search Console and GA4. Read the method, open the matching report and finish with a concrete action.
SEO LEARNING PATH
Learning SEO works best when each concept leads to a task. Pick the point that matches what you need today; you do not have to complete every card in order.
Start with SEO tutorials for beginners: discovery, indexing, Search Console metrics and links.
Start with fundamentalsUse a bounded playbook for CTR, decay, indexing, cannibalization or reporting.
Browse practical workflowsMove from one-off checks to monitoring, shared reports and source-aware automation.
Build an SEO routineStart here if Google Search Console and its core SEO metrics are new to you.
How Google finds, stores and shows pages, what affects rankings, where to start and how to check the result in Search Console.
The free Google service explained: its main reports, how to add your site, what it does not show and why its numbers differ from Analytics.
How Google counts impressions and clicks, why more impressions is not the goal and how to read the four ways the two numbers move.
The CTR formula, what average position means in Search Console, why one average can mislead and how to judge CTR against your own site.
How to check whether a page is indexed, what Crawled, Discovered and other Search Console statuses mean and when not being indexed is fine.
What the documentation says about links and brand, what counts as link spam, how to mark paid links and how to measure the effect.
Each workflow maps to reports that already exist in SEOKit.
A bounded seven-day plan: baseline, candidates, intent, one change and a queue of at most three tasks, with Google-sourced limits.
Four gates, a same-query click gap and the limits of the report: find queries near page one worth a test, without invented uplift.
Split an observed click loss into demand and performance, run four gates and choose refresh, consolidate, fix or leave.
What a title tag is, Google’s own rules for it and how to test one honest rewrite: four gates and a CTR gap, with no invented length rule.
Tell real ownership conflicts from normal sibling pages with four gates and choose differentiate, merge, redirect or canonical, with Google’s own warnings.
Build a baseline from your own site, size the click gap for one pair, learn what Google documents about snippets and run one bounded test.
Turn one coverage total into a queue: define the working set, drop expected exclusions, inspect representative URLs and fix one cause at a time.
Two discovery channels, the verification-fetch rules and robots.txt traps, with what Brave documents kept apart from what a code analysis found.
What a connection really is, what OpenAI documents for developer mode and the API, Google row limits and how to check the numbers.
Export, custom action, self-hosted server, hosted app and BigQuery compared by row limits, live data, who runs it and trust.
Add an annotation, define an equal comparison window and use experiments or change-point reports to test the result.
What Search Console can and cannot show about AI Overviews on brand searches, and how many queries to sample.
Ten rules for scopes, skills, secrets, untrusted pages and approvals, plus a call-budget check.
Four questions for any server and what Google Analytics, Ahrefs, Semrush, DataForSEO, Screaming Frog and Chrome DevTools document about data, sign-in and limits.
Data windows, a daily health check, weekly movers, monthly decisions, failure alerts and an output contract for scheduled reports.
Looker Studio, BigQuery export, the API and manual export compared by documented limits, why site and URL tables differ and how to reconcile a report.
Google’s built-in AI, assistants, answer trackers and AI visits separated by what each measures, with documented limits and a page-level join.
A vetting workflow from the documented commands: reading before enabling, name shadowing, lock files, transport settings and read-only tool filters.
What OpenAI documents: the four permission settings, what apps can see, training use by plan and a checklist before you connect.
Move from one-off checks to monitoring, reporting and shared decisions.
Use saved filters, annotations, index tracking and alerts so important changes surface automatically.
Keep Search Console clicks separate from Analytics sessions while using both sources to explain landing-page outcomes.
Invite users, share saved reports and export the right grain without exposing unrelated properties.
Connect through MCP with explicit scopes and ask source-aware questions without copying credentials into prompts.
METHOD & LIMITS
Each lesson separates documented behavior from an interpretation, names the data source and ends with a check you can repeat. Examples are educational, not live findings about your site; verify decisions against the affected URLs and your own GSC or GA4 property.
FAQ
Start with the fundamentals track, then apply one lesson to a site you control. Move to a playbook only after you can read the underlying metric.
All materials linked from this hub are available without payment. Some practical reports require your own Search Console or Analytics data, but the lessons themselves are public.
Use a test site or a site you are authorized to change. Record a baseline, make one bounded change, wait for enough data and compare like-for-like periods.
Keep search impressions, clicks, CTR and position in Search Console separate from sessions, engagement and conversions in GA4. Join them only at a shared page and date grain.
Connect Search Console and use the same reports described in every learning track.