How to use this manual: Every conclusion carries a confidence label——Officially confirmed from official Google documentation;Industry consensus is third-party practice with a methodology, but not a Google rule;Needs verification is a single-source claim — verify it yourself before acting.Do not present fixed ranking weights, an overall SEO score, keyword density, title character counts, backlink counts or recovery timelines as Google rules — none of them are officially supported.
Ten global boundaries
- Crawl ≠ Index.
- Index ≠ Rank.
- Rank ≠ Click.
- Structured Data ≠ Ranking Boost.
- Valid Schema ≠ Guaranteed Rich Result.
- AI Content ≠ Spam; low-value manipulation at scale is the real risk boundary.
- E-E-A-T ≠ a numeric Google score.
- Third-party metrics (DA/DR etc.) ≠ Google PageRank.
- A traffic drop ≠ a penalty; diagnose by layer before assigning a cause.
- Correlation ≠ causation.
Search processing chain
Before diagnosing any SEO problem, locate which layer of the chain it occurs in:
Query / User Context
↓
Technical Eligibility
↓
Discovery → Crawling → Rendering → Indexing
↓
Canonicalization / Understanding
↓
Content Quality / People-first / Relevance
↓
Site Architecture / Internal Relationships
↓
Ranking Systems → Search Eligibility
↓
Search Appearance
↓
Web / Images / Video / Products / Local / Discover / Generative AI
↓
Impressions → Clicks / CTR / Position
↓
Landing Page Behaviour → Business Outcome
↓
Measurement → Diagnosis → Improvement → Re-evaluation
01｜Google Search Fundamentals and the SEO Rule System Slow-changing
Google Search EssentialsOfficially confirmed
Search Essentials is the entry point to the whole rulebook: technical requirements, spam policies and key best practices. Meeting the requirements does not guarantee crawling, indexing or display.
Source:Google’s official Search Essentials and SEO Starter Guide.
Action:Sort every SEO recommendation into technical eligibility, spam policy or best practice first, then judge whether it is an official Google requirement.
Risk:The basic framework is stable; official documentation wording still needs periodic re-checking.
Layers of the search processing chainOfficially confirmed
Understand search as the chain Discovery/Crawling → Rendering → Indexing → Serving/Ranking, and do not blur “crawling, indexing, ranking” into a single concept.
Source:Google Search Central official documentation (how Google Search works, crawling and indexing).
Action:When diagnosing, establish which layer the problem sits in first, then pick the tool and the fix.
Risk:Stable; individual pages are not guaranteed to pass through every stage.
Ranking system boundariesOfficially confirmed
Google uses multiple ranking systems and signals; no fixed SEO factor weighting formula is published. Discard fixed weighting models such as “content 30%, backlinks 25%”.
Source:Google Search ranking systems guide.
Action:Use “systems + signals” thinking instead of scoring authority.
Risk:Ranking systems change; the status of specific systems needs re-checking.
02｜Crawling, Rendering and Indexing Slow-changing
robots.txt and noindexOfficially confirmed
robots.txt mainly controls crawling, it is not a reliable de-indexing tool; Disallow is not the same as noindex. When you need to prevent indexing, use an index-control method Google supports.
Source:Google robots.txt and robots meta tag documentation.
Risk:Configuration errors can cause crawling or indexing anomalies.
SitemapOfficially confirmed
A sitemap helps URLs get discovered and understood, but submitting one does not guarantee indexing. Only submit canonical URLs you want discovered, and keep lastmod truthful.
Source:Google sitemap documentation.
Risk:A sitemap is a discovery signal, not an indexing command.
JavaScriptOfficially confirmed
Google can render JavaScript; loading content with JS does not by itself mean it is harder for Google to crawl. Verify HTTP status, resource access, rendering and indexing results instead of declaring an SEO risk the moment you see JS.
Source:Google JavaScript SEO basics; 2026-03 documentation update log.
Risk:Complex rendering can still fail because of resource, status code or implementation issues.
CanonicalOfficially confirmed
Canonical is a normalisation signal or hint, not an absolute command; Google may choose a different canonical. Keep your normalisation signals consistent across redirects, rel=canonical, sitemaps and internal links.
Source:Google canonicalization documentation.
Risk:Conflicting signals make it more likely that Google picks a different canonical.
03｜Content Quality and E-E-A-T Slow-changing
People-first contentOfficially confirmed
Google encourages helpful, reliable, people-first content; content quality cannot be measured by a single mechanical metric such as word count or keyword density. Do not mechanically change dates or rewrite in bulk just for “freshness”.
Source:Google creating helpful, reliable, people-first content.
Action:Be clear about the page’s purpose, target users, original value and practical usefulness.
E-E-A-TOfficially confirmed
E-E-A-T is a quality evaluation framework, not a readable numeric Google score; trust is the core of the framework. Quality rater scores do not directly change an individual page’s ranking.
Source:Google Search Quality Rater Guidelines and Search Central documentation.
Action:Strengthen author and company transparency, experience, expertise, sourcing and factual accuracy.
AI contentOfficially confirmed
Using AI to generate content does not automatically make it spam; producing low-value content at scale to manipulate rankings can cross into scaled content abuse. Judge the final content on whether it is original, helpful and accurate, not on the tool that produced it.
Source:Google AI content guidance and Spam Policies.
Risk:AI content at scale needs extra scrutiny of original value and manipulative intent.
04｜Search Intent, Keywords and Content Systems Slow-changing
Search IntentIndustry consensus
Search intent is a useful analytical framework for content planning, but the common four intent types (informational / navigational / transactional / commercial investigation) are not an official Google taxonomy. Do not treat an industry classification as a ranking algorithm label.
Action:Judge real demand from the SERP, Search Console queries and your business context together.
Keyword dataOfficially confirmed
Search Console queries are first-party data on real search performance, but they are not Google’s complete keyword database. Use GSC first to verify the query impressions you already have, then third-party tools to expand.
Source:Google Search Console Performance documentation.
Risk:Privacy, low-frequency queries and data limits all cause incompleteness.
Content clusters (pillar/cluster)Industry consensus
Pillar/cluster structures help organise content and internal links, but Google has published no such thing as a topical authority score. Build your content system around user tasks and topical relationships, and avoid mass-producing thin pages just to hit a “topical coverage” number.
Risk:The structure has value, but there is no official fixed cluster count.
05｜On-page SEO Stable
Title LinkOfficially confirmed
<title> is one important source Google uses to generate title links, but Google may also draw on other on-page text, anchor text, og:title and more. Write titles that are clear, unique and consistent with the content, then check how they actually appear in the SERP. Do not treat 50–60 characters as a ranking threshold.
Source:Google title links documentation.
Meta DescriptionOfficially confirmed
Google may use your meta description, or it may generate a snippet dynamically based on the query. Write descriptions that are accurate, unique and informative rather than stuffed with keywords. A fixed 150–160 characters is not a Google rule.
Source:Google snippets documentation.
HeadingsOfficially confirmed
Heading hierarchy helps organise content and understand page structure, but no H1/H2 ranking weight formula is published; “every page must have exactly one H1” is not a hard Google rule.
Source:Google SEO Starter Guide.
Alt textOfficially confirmed
Alt text describes an image and its context, helping Google understand it; it should not be used as a keyword stuffing slot. Handle decorative images according to accessibility needs.
Source:Google Image SEO best practices.
06｜Technical SEO Slow-changing
HTTP statusOfficially confirmed
Status codes should truthfully express resource state; soft 404s make it hard for Google to understand a page. Audit 2xx/3xx/4xx/5xx, redirect chains and soft 404s regularly — the risk is higher during migrations and redesigns.
Source:Google HTTP status codes and soft 404 documentation.
HTTPSOfficially confirmed
HTTPS is a security and infrastructure matter, not an “SSL SEO score”. Use HTTPS site-wide, get redirects right and avoid mixed content; when migrating protocols, sync canonical, internal links and the sitemap.
Source:Google HTTPS and site move guidance.
Crawl BudgetOfficially confirmed
Crawl budget matters mainly for large sites or those with complex URL spaces; small sites should fix content, indexing and internal linking first. Do not treat crawl budget as the primary SEO KPI for every site.
Source:Google crawl budget documentation.
Action:Large sites should focus on controlling worthless URL space, facets, duplicate URLs and server stability.
07｜Site Architecture and Internal Links Stable
Information architectureOfficially confirmed
A clear site architecture and crawlable links help Google discover pages and understand relationships. Design navigation around business topics, user tasks and page hierarchy. Note: there is no official ranking rule that “every page must be within 3 clicks”.
Source:Google SEO Starter Guide and links documentation.
Internal LinksOfficially confirmed
Internal links serve discovery, navigation, context and relationship signalling at the same time. Give important pages reasonable, natural, crawlable contextual links; do not work to a fixed internal link count or an exact-match ratio formula.
Source:Google links best practices.
Faceted NavigationOfficially confirmed
Faceted navigation can generate huge numbers of URL combinations and consume crawl resources. Decide which combinations should be indexed and control worthless parameter space — the risk is greater on large ecommerce and catalogue sites.
Source:Google faceted navigation guidance.
08｜Page Experience and Core Web Vitals Slow-changing
Current CWV metricsOfficially confirmed
The current Core Web Vitals are LCP, INP and CLS; the “good” reference values are LCP ≤ 2.5s, INP ≤ 200ms and CLS ≤ 0.1, assessed at the 75th percentile. Use real user data first to locate the problem, then lab tools to diagnose it.
Source:Google Core Web Vitals documentation.
Risk:Metrics and thresholds may be adjusted in future and need re-checking.
Field vs LabOfficially confirmed
CrUX/PSI field data and Lighthouse lab data are not the same kind of measurement: field data is for judging real user experience, lab data for reproducing and fixing issues. Do not substitute a single Lighthouse score for real user data.
Source:PageSpeed Insights, CrUX and Lighthouse official documentation.
Ranking boundariesOfficially confirmed
Core Web Vitals are used in ranking systems, but no single page experience score guarantees rankings; all-green does not automatically lift you. Evaluate performance work alongside content relevance and indexability.
Source:Google page experience / CWV guidance.
09｜Structured Data and Search Appearance Fast-changing · review quarterly
Structured data positioningOfficially confirmed
Structured data helps Google understand a page and may qualify it for specific display features, but it is not a ranking guarantee. Only implement types that match genuinely visible on-page content and that Google currently supports. Valid ≠ Eligible ≠ Displayed.
Source:Google structured data general guidelines.
Feature status managementOfficially confirmed
Schema.org support, Google Search support and rich result display are three different things; Google does retire search features. Keep a Supported / Limited / Deprecated / Removed status table with the last verified date.
Source:Google Search Central documentation updates.
Key points: From 2026-05-07 FAQ rich results stopped displaying; official documentation was removed in June.
Products and entitiesOfficially confirmed
Use Product, ProductGroup, Organization and similar types according to real entities and page roles; do not stack types on every page just because “more Schema is better”.
Source:Google product/organization structured data docs.
10｜AI Search Visibility (GEO) Fast-changing · review quarterly
SEO fundamentals still applyOfficially confirmed
Generative search experiences such as AI Overviews and AI Mode are still built on top of Google Search; there is no special AI Schema you must use. Keep prioritising crawling, indexing, content quality, page experience and comprehensibility.
Source:Google AI features / AI optimization guidance.
Query Fan-outOfficially confirmed
Generative search uses query fan-out to explore several related subtopics and sources. Content should cover real user tasks and sub-questions, but do not mass-produce thin pages for every potential fan-out, and do not derive a fixed “AI citation formula”.
Source:Google AI features documentation.
llms.txtOfficially confirmed
Google stated in 2026-06 that llms.txt is not required for Google Search and will neither positively nor negatively affect Google Search visibility or rankings. Maintain one if other systems need it, but do not list it as a must-do for Google SEO/GEO.
Source:Google Search Central 2026-06-15 documentation update.
Risk:Other AI services may handle this differently.
Generative AI measurementOfficially confirmed
In 2026 Google added more dedicated Search Console analysis for generative AI search performance; analyse classic web performance and generative AI visibility as separate layers. Verify the exact interface and availability against current official documentation.
Source:Google 2026 Search Central updates and AI optimisation guidance.
11｜Off-Page SEO, Backlinks & Authority Slow-changing
Links positioningOfficially confirmed
Links still help Google discover and understand pages, but modern rankings are decided by many systems and signals together. Earn links for genuine editorial value, brand spread and user discovery; do not predict rankings from a fixed link count or a DR threshold.
Source:Google ranking systems and links best practices.
Link SpamOfficially confirmed
Links created or acquired primarily to manipulate rankings may fall under link spam. Mark paid/sponsored links with the appropriate rel attribute and avoid scaled anchor-text manipulation. Spammy links do not automatically mean a manual action; look at the actual evidence.
Source:Google Spam Policies.
Third-party authority metricsIndustry consensus
DA, DR, Authority Score and Trust Flow are all third-party metrics, not Google PageRank or any official authority score. Use them for comparison and research, but do not write them up as Google ranking signals.
Source:Definitions of each tool’s metrics; Google 2026 third-party SEO tool guidance.
12｜Local SEO Fast-changing · review quarterly
Local ranking factorsOfficially confirmed
Google local results are best understood around factors such as relevance, distance and prominence; no fixed weights are published. Distance is a real factor and cannot be removed by ordinary SEO tricks. Keep your business information truthful, accurate, complete and continuously maintained.
Source:Google Business Profile local ranking help.
ReviewsOfficially confirmed
More reviews and positive ratings can help local rankings, but there is no official fixed review count threshold. Earn and respond to reviews genuinely; no fake or incentivised reviews.
Source:Google Business Profile local ranking help.
Regional search experienceOfficially confirmed
In 2026-09 Google added regional Search Experience documentation; some aggregator/supplier/carousel features are only available in specific countries or regions. Add a country/region feature availability check when doing international local SEO.
Source:Google Search Central 2026-09 documentation updates.
13｜International and Multilingual SEO Slow-changing
hreflang targetingOfficially confirmed
hreflang helps Google understand language/region alternative versions; it is not a ranking bonus. Configure correct language/region codes and reciprocal references for genuine alternate pages; errors or omissions may leave Google to pick the version itself.
Source:Google localized versions documentation.
How canonical and hreflang divide the workOfficially confirmed
Canonical handles the preferred version, hreflang expresses language/region alternates; they solve different problems and can be combined. Avoid canonicalising every international version that should compete independently into a single English page.
Source:Google canonicalization and localized versions docs.
URL architecture choicesOfficially confirmed
ccTLD, subdomain and subdirectory are all valid international site architectures; there is no official fixed ranking preference. Choose a stable structure based on your operations, technology, brand and maintenance capacity; do not rely on automatic IP redirects as your only internationalisation mechanism.
Source:Google multi-regional/multilingual guidance.
14｜Ecommerce and Product SEO Fast-changing · review quarterly
Product data systemOfficially confirmed
Manage ecommerce SEO as one consistent data system spanning Product Identity, URL, Variants, Category, Structured Data, Merchant Data, Shipping/Returns and Reviews. Keep core fields such as price and availability aligned across the page, the structured data and your Merchant data.
Source:Google ecommerce documentation.
Product / Merchant ListingsOfficially confirmed
Product structured data can help you qualify for product search features; Merchant Center matters for some Shopping surfaces, but ordinary organic inclusion does not depend on Merchant Center. Eligibility is not the same as display.
Source:Google product structured data and Merchant Center guidance.
Product variantsOfficially confirmed
Google supports expressing product variants via ProductGroup/Product and similar approaches; both single-page and multi-URL variant designs are valid. Express the product group, variant identity, canonical and URL relationships consistently; do not automatically treat every variant URL as duplicate content spam.
Source:Google product variants documentation.
15｜Images, Video and Vertical Search Fast-changing · review quarterly
Image SEOOfficially confirmed
Image SEO is about more than alt text; it also covers image crawlability, page context, quality, metadata and indexing. Use high-quality relevant images, descriptive context and sensible alt text. Google added preferred image metadata guidance in 2026-03.
Source:Google Image SEO best practices.
Video SEOOfficially confirmed
Design video SEO around watch pages where video is the primary content, video structured data and indexable video assets. Give core videos a dedicated page, title, thumbnail and VideoObject; merely embedding a third-party video does not mean video SEO is done.
Source:Google Video SEO best practices.
Google DiscoverOfficially confirmed
Discover does not require special Schema to be eligible; content needs to be indexed and comply with the relevant policies, and display is never guaranteed. Analyse Discover separately from Web Search. Discover-specific Core Updates appeared in 2026 and should be tracked on their own.
Source:Google Get on Discover documentation.
16｜Spam Policies and SEO Risk Fast-changing · review quarterly
Scaled Content AbuseOfficially confirmed
What matters is creating content at scale primarily to manipulate rankings with little original value; whether it was produced by AI, humans or a mix is not the deciding factor. Examine scale, purpose, original value and user value.
Source:Google Spam Policies.
Site Reputation AbuseOfficially confirmed
Third-party content that mainly exploits the host site’s existing ranking signals to manipulate results may fall under site reputation abuse; third-party content is not automatically a violation. Examine who controls the content, its purpose and its independent value. Enforcement practice in the EEA was updated in 2026-09 and should be re-checked per region.
Source:Google Spam Policies; 2026-09 site reputation policy update log.
Expired Domain AbuseOfficially confirmed
Buying an old domain is not automatically a violation; the real risk is using its historical reputation to host low-value content that manipulates rankings. Keep genuine business and content value when acquiring or migrating domains; do not treat domain age as an inheritable ranking asset.
Source:Google Spam Policies.
The difference between manual actions and algorithmic changesOfficially confirmed
Manual actions and algorithmic changes are different mechanisms; the absence of a manual action does not mean there is no algorithmic impact. When traffic drops sharply, check manual actions, security issues, algorithmic and technical causes separately — do not call every drop a penalty.
Source:Search Console Manual Actions documentation.
17｜Search Console and Measurement Fast-changing · review quarterly
Performance reportOfficially confirmed
Search Console provides Clicks, Impressions, CTR and Position plus first-party dimensions including Query / Page / Country / Device / Search Appearance / Date. Break the data down by dimension instead of looking only at site-wide totals; Query data is not a complete keyword database.
Source:Google Search Console Performance documentation.
URL InspectionOfficially confirmed
URL Inspection diagnoses indexing, crawling, canonical and rendering for a single URL; a live test and the indexed data are not the same state. Use it to verify when an important URL looks wrong; Request Indexing guarantees neither inclusion nor ranking.
Source:Google URL Inspection documentation.
Data AnomaliesOfficially confirmed
Search Console can suffer reporting or data-recording anomalies; a data anomaly does not necessarily mean real search traffic changed. When you see a sudden shift, check official data anomalies and Search Status first, then attribute causes.
Source:Google Search Console Data Anomalies.
Indexing KPI boundariesOfficially confirmed
Not indexed does not automatically mean a problem; the goal is that important, indexable URLs are indexed correctly and intentionally excluded URLs are excluded correctly. Do not treat a 100% index rate as an SEO KPI — large sites normally have many legitimately excluded URLs.
Source:Google Page Indexing report documentation.
18｜SEO Data Analysis and Diagnosis Slow-changing
Analysing the four metrics togetherIndustry consensus
Analyse clicks, impressions, CTR and position together; a drop in clicks is not the same as a drop in rankings. Work out which stage changed — impressions, position or CTR — first; average position does not represent a single site-wide ranking.
Source:Search Console metric definitions and diagnostic practice.
Layered diagnosisIndustry consensus
Localise anomalies layer by layer — Site → Directory → Page Type → Page → Query → Country → Device → Search Type / Search Appearance — find the pages and query groups actually driving the change, then form a hypothesis. Avoid drawing conclusions from site-wide percentages alone.
Source:The Google Search Console dimension system.
Demand change vs ranking changeOfficially confirmed
Seasonality and shifts in search interest can cause traffic to fall even when rankings have not visibly worsened. Combine GSC and Google Trends to judge demand changes; timing correlation is not algorithmic causation.
Source:Google’s guidance on debugging drops in search traffic and Trends.
How to validate changesIndustry consensus
Validate SEO changes with comparable time windows, affected/unaffected groups and year-on-year data where needed. Record the change date, what was changed, the expected result and your confidence level. Correlation ≠ causation.
Source:Data analysis methods and GSC metrics.
19｜Algorithm Updates and Recovery Fast-changing · review quarterly
Characterising a core updateOfficially confirmed
A core update is a broad adjustment to ranking systems, not a manual penalty aimed at a specific site. A ranking drop does not automatically mean a violation. Log the official start/end dates, then analyse the affected pages, queries and Search Surface.
Source:Google core updates guidance.
Analysis windowOfficially confirmed
Formally assessing a core update’s impact means waiting for it to finish, then comparing stable before/after windows as official guidance recommends. Monitor during the rollout, then run a systematic before/after analysis afterwards.
Source:Google core updates guidance.
Recovery expectationsOfficially confirmed
There is no fixed core update recovery cycle, and no guarantee that changes restore your previous rankings; Google keeps re-evaluating content and sites. Prioritise meaningful, long-term quality improvements rather than chasing an algorithmic “cure”. Never promise recovery in 7 or 30 days.
Source:Google core updates / debugging traffic drops guidance.
Multiple Search Surface updatesOfficially confirmed
Discover Core Updates appeared in 2026, so algorithm analysis can no longer revolve only around traditional Web Search. Update logs should add Surface, Start/End, Scope and Official Guidance fields; different Search Surfaces may behave differently.
Source:Google February 2026 Discover Core Update.
20｜The SEO Tool Ecosystem Fast-changing · review quarterly
First-party vs third-partyOfficially confirmed
SEO tools are data collection, diagnostic and research tools, not Google’s ranking system; first-party data and third-party estimates must be kept separate. For every metric, log the data source, what is being measured, whether it is an estimate, and its limitations.
Source:Google 2026 third-party SEO tools/services/advice guidance.
How GSC and GA divide the workOfficially confirmed
Search Console describes how you perform inside Google Search; Google Analytics describes what happens after visitors land on your site — the two sets of numbers do not have to match, so do not force Clicks and Sessions to line up. Build a Visibility → Acquisition → Website → Business Outcome data chain.
Source:Google Search Console + Analytics guidance.
PSI / CrUX / LighthouseOfficially confirmed
CrUX/PSI field data and Lighthouse lab data serve different purposes; the Lighthouse SEO audit is not a Google ranking score. Field data tells you about real user experience, lab data is for technical diagnosis.
Source:Google PSI, CrUX, Chrome Lighthouse docs.
All-in-one third-party toolsIndustry consensus
Ahrefs, Semrush, Majestic, Screaming Frog, Sitebulb, JetOctopus and similar tools are useful for research, crawling, link and visibility analysis, but their scores are not official Google metrics. Use third-party tools to surface problems, then verify with first-party data and the actual pages. Do not maintain a “best tool ranking” as a long-term reference.
Source:Google 2026 third-party SEO tool guidance plus each tool’s definitions.
Key changes after the 2026 full-library review
| Modules | Type | Verification results |
|---|---|---|
| 01 | Added | Fix the Technical Eligibility ≠ Indexing ≠ Ranking/Serving layering. |
| 02 | Added | Added the boundary note “Indexed does not necessarily mean the current body content has been fully crawled / rendered”. |
| 09 | Fixed | Manage structured data with Supported / Limited / Deprecated / Removed statuses; FAQ rich results stopped displaying in 2026-05. |
| 10 | Fixed | AI search continues to build on traditional SEO fundamentals; llms.txt is not required for Google Search and does not affect rankings. |
| 12 | Added | Regional Search Experience documentation was added in 2026-09; regional features need verifying per country/region. |
| 13 | Fixed | Canonical and hreflang have separate jobs; canonical is a signal, not an absolute command. |
| 15/19 | Fixed | Add Discover-specific core update / surface-specific update thinking. |
| 16 | Fixed | Keep tracking the 2026-09 EEA enforcement update on site reputation abuse. |
| 17/18 | Added | When diagnosing data anomalies, check Search Console Data Anomalies / Search Status first so you do not mistake a reporting problem for an SEO decline. |
| 20 | Fixed | Treat every third-party SEO tool metric as a third-party model, not as a Google ranking metric. |
Official core source index (for quarterly review)
- Google Search Essentials
- Google Search Central — Latest documentation updates
- SEO Starter Guide
- Ranking systems guide
- Crawling & Indexing documentation set
- Structured Data documentation set
- Search Console monitoring and debugging documentation set
Maintenance principles: Slow-changing modules are re-verified annually or when official guidance changes materially; fast-changing modules quarterly; an extra incremental check whenever Google ships a major update. This knowledge base supports SEO learning and project management and does not represent a ranking guarantee from Google — Google Search products, policies and documentation keep changing.
FAQ
- What is the difference between the 16-lesson path and this 20-module knowledge base?
- The 16-lesson path is a step-by-step course (from awareness through to GEO), best for learning from scratch; this manual is organised by topic for on-demand lookup, with a confidence label on every conclusion. Walk the path first, then use the manual to verify details.
- What do the “officially confirmed / industry consensus / needs verification” labels mean?
- Officially confirmed = from official documentation such as Google Search Central; Industry consensus = third-party practice with a methodology but not a Google rule; Needs verification = a single-source claim, verify before acting.
- How often is this manual updated?
- Slow-changing modules: re-verify annually or when guidance changes materially; fast-changing modules (structured data, AI search, local, spam policy, GSC, algorithms, tools): quarterly; major updates get their own incremental check. This edition verified through 2026-09-22.