This module owns organic-search diagnosis and optimization. Module 08 owns the editorial production system, Module 06 owns the underlying information architecture, and Module 10 owns measurement implementation and reporting. SEO uses those systems; it should not duplicate or replace them.
START WITH THE SYSTEM
SEO is a chain. A weak link can make excellent content invisible.
A page can fail for very different reasons: Google may not know the URL exists, may be unable to crawl it, may crawl but not index it, may index the wrong canonical, may understand the page but consider another result more relevant, or may rank it yet attract few clicks because the search presentation is weak. Calling all of these “ranking problems” leads to random work.
| Layer | Question | Typical evidence |
|---|---|---|
| Discovery | Can Google find the URL? | Internal links, sitemap, external links, URL Inspection. |
| Crawl | Can Googlebot request the page and required resources? | Status codes, robots.txt, server logs, URL Inspection. |
| Index | Is the canonical page stored in Google’s index? | Page Indexing report, URL Inspection, noindex/canonical checks. |
| Understand | Is the topic, entity, purpose and structure clear? | Visible copy, headings, links, structured data, rendered HTML. |
| Compete | Is this result sufficiently useful, relevant and authoritative for the query? | SERP comparison, content quality, links, reputation, freshness where needed. |
| Attract | Does the result earn the right click? | Title link, snippet, rich-result eligibility, query-specific CTR. |
| Convert | Does organic traffic create a useful outcome? | Engagement, assisted actions, leads, affiliate clicks, revenue. |
Do not rewrite a page because rankings are weak until you know the page is discoverable, crawlable, indexable and canonical. Likewise, do not spend days on technical SEO when the real problem is that the page does not satisfy the query better than existing results.
THE BASELINE
Google Search Essentials define eligibility; SEO starts after the basics are satisfied.
Google groups its foundation into technical requirements, spam policies and key best practices. Meeting them does not guarantee ranking or even indexing, but violating them can make optimization irrelevant. The practical lesson is simple: first make the site eligible and trustworthy, then improve relevance and competitiveness.
Technical eligibility is surprisingly small
Most ordinary WordPress sites meet the minimum technical bar automatically. The harder work is ensuring important URLs return usable content, are accessible to Googlebot, and are not accidentally blocked, redirected or marked noindex.
People-first content is not separate from SEO
Useful content, clear language, real expertise, transparent sourcing and a coherent site purpose are part of sustainable search visibility. The goal is not to “write for Google” and then polish the text for people. Build a page that genuinely solves the task and make that page technically easy to discover and understand.
UNDERSTAND THE PIPELINE
Discovery, crawling, indexing and serving are different stages.
Google’s systems discover URLs, crawl accessible resources, process and index content, then rank eligible results for individual searches. A page can succeed at one stage and fail at the next. This distinction is fundamental when troubleshooting.
Google primarily discovers pages through links
Internal architecture matters because every important page should be reachable through crawlable links from another findable page. A sitemap can help discovery and monitoring, but it does not replace navigation or internal linking.
Google renders JavaScript, but do not make discovery unnecessarily dependent on it
Server-rendered or otherwise directly accessible HTML remains the safest baseline for critical text and links. If navigation or meaningful content exists only after client-side scripts run, test the rendered result with URL Inspection and ensure each meaningful screen has a real URL.
DEMAND RESEARCH
Keyword research should reveal user problems, language and opportunity — not dictate pages one phrase at a time.
A professional keyword workflow combines multiple signals: first-party queries, keyword tools, Google Trends, SERP inspection, customer questions, competitor coverage and commercial evidence. Search volume is only one input. A low-volume query can be strategically valuable if it represents a qualified problem close to a decision.
Build query families
Group terms that represent the same underlying task. For example, “how to choose web hosting,” “choosing hosting for WordPress,” and “what hosting do I need” may belong to one strong guide rather than three near-duplicate pages. Split only when the user task, evidence or depth meaningfully changes.
Score opportunity instead of chasing volume
| Factor | Question |
|---|---|
| Audience fit | Does this query come from the people the site is designed to help? |
| Intent value | Is the user learning, comparing, solving or buying something relevant? |
| Demand evidence | Is there enough evidence that the problem exists? |
| Competitive feasibility | Can we produce something materially more useful or differentiated? |
| Business fit | Does the topic support trust, acquisition, conversion or monetization? |
| Maintenance cost | Will the page require constant updates to remain accurate? |
MATCH THE JOB
Search intent is the task Google is trying to satisfy for a specific query.
Broad labels such as informational, commercial and transactional are useful, but they are not enough. Inspect what the user must decide, how much they likely know, what format dominates the results, and which evidence successful pages provide.
One modifier can change the required page
- “what is affiliate marketing” — foundational explanation.
- “best affiliate programs for SaaS” — commercial comparison with current program terms.
- “Hostinger affiliate program commission” — factual product/program information with current source verification.
- “Hostinger vs SiteGround” — comparative decision support.
- “Hostinger DNS not working” — troubleshooting workflow.
If the same person could read one page and feel the exact same task was solved, the queries probably belong to one owner URL. If the decision, evidence or format changes substantially, a separate page may be justified.
READ THE MARKET
SERP analysis tells you what Google currently considers relevant — but it is not permission to copy.
Inspect the live results before creating or substantially rewriting an important page. Look for dominant formats, recurring subtopics, freshness expectations, brand concentration, forum/video/image presence, rich-result features and the level of evidence required.
Ask four questions
- Intent: what task do the top results actually solve?
- Standard: how much depth, proof and usability does the query appear to require?
- Gap: what important question, workflow, comparison or evidence is missing?
- Advantage: what can we add that is genuinely better than another summary?
The goal is not to reproduce the headings of the first ten results. That creates commodity content. Use the SERP to understand expectations, then build a more useful answer around your own structure, examples, research and decision support.
ONE PRIMARY DESTINATION
Assign one primary URL to each meaningful query family.
The content-strategy module introduced query ownership. SEO operationalizes it. When several pages compete for the same task, internal links, titles and content updates can send mixed signals and split backlinks, engagement and maintenance effort.
Use a keyword-to-URL map
For every strategically important page record: primary topic, query family, search intent, page type, target audience, parent hub, commercial role, canonical URL and competing internal URLs. This map is a practical defense against accidental cannibalization.
Do not force exact-match keywords everywhere
Google can understand language beyond literal phrase matching. Use the vocabulary that naturally helps the reader understand the topic. Titles and headings should be descriptive, not repetitive containers for every keyword variation.
MAKE THE PAGE LEGIBLE
On-page SEO is clarity, not keyword density.
Strong on-page SEO makes the page’s purpose obvious to a reader and a search engine. The major signals are straightforward: a descriptive title, one clear primary heading, logical subheadings, useful body content, descriptive links, relevant media, an intentional URL, and metadata that accurately represents the page.
Place important language where it is naturally prominent
Google’s Search Essentials recommends using words people would use to find the content in prominent locations such as the title, main heading, alt text and link text where appropriate. This is not a requirement to repeat one phrase mechanically. It is a requirement to avoid vague pages whose subject is hard to identify.
Optimize for information gain
Ask what the page gives a reader that they would not get from five generic summaries: an original framework, screenshots, calculations, first-party observations, current source verification, decision criteria, failure scenarios, a worksheet, a comparison method or practical implementation steps.
SEARCH PRESENTATION
Write title elements and meta descriptions for accuracy first, click appeal second.
Google can generate title links and snippets from several sources, so the exact text you write is not guaranteed to appear. Your job is to provide strong source material: concise, descriptive titles and page content that clearly communicates what the result offers.
Title checklist
- Unique to the page.
- Describes the actual topic and intent.
- Avoids repetitive boilerplate and keyword stuffing.
- Uses the brand where it helps recognition, not at the cost of clarity.
- Matches the visible page purpose and H1 closely enough to avoid conflicting signals.
Meta description checklist
- Summarize the specific page, not the entire website.
- Include the most persuasive factual value, not hype.
- Do not fabricate urgency, ratings, savings or guarantees.
- Expect Google to use different text when another passage better matches a query.
CONTENT STRUCTURE
Headings should help a reader scan the argument, not serve as an SEO decoration layer.
Use one visible primary H1 for the main topic, then H2/H3 levels to express real hierarchy. There is no professional value in inserting a keyword into every heading. A long guide can have many headings because it has many meaningful sections; a short page may need only a few.
Answer the difficult parts, not only definitions
For competitive topics, basic definitions are table stakes. Add trade-offs, exceptions, failure modes, examples, diagnostic steps, costs, implementation detail and explicit decision rules. This is where a guide becomes useful enough to deserve links, mentions and repeat visits.
DISTRIBUTE CONTEXT & DISCOVERY
Internal links are one of the highest-control SEO assets you own.
Google uses links to discover pages and understand relevance. Important pages should be reachable through normal crawlable <a href> links from relevant pages. A sitemap alone is not a substitute for a coherent internal-link graph.
Use descriptive anchor text
“Read our complete WordPress security guide” gives more useful context than “click here.” Anchor text should be concise and relevant, without forcing exact-match phrases into every link.
Link according to relationship
- Parent → child: hub to detailed module.
- Child → parent: module back to the broader learning path.
- Sibling: related guides where a reader naturally continues.
- Contextual: from a paragraph to a deeper explanation of a concept.
- Commercial assist: from education to a relevant comparison or product page only when the next step makes sense.
Can every important page be reached from the homepage through a reasonable number of normal links without relying on site search, JavaScript-only controls or an XML sitemap?
VISUAL DISCOVERY
Image SEO starts with useful images on useful landing pages.
Use standard HTML image elements, descriptive context, sensible filenames and meaningful alt text where the image conveys information. Do not stuff keywords into alt attributes. Decorative images can use empty alt text when appropriate for accessibility.
Make images discoverable and representative
Google’s image guidance recommends standard <img> elements, responsive implementations and relevant high-quality images. Images referenced only as CSS backgrounds are not treated the same way for image discovery. For important original visual assets, consider image sitemap support where discovery is otherwise difficult.
Optimize the landing page too
An excellent image on a weak, irrelevant page is not a complete image SEO strategy. Surround visuals with context, captions when useful, descriptive page titles and content that explains what the image represents.
TECHNICAL SEO · CRAWL
Crawling asks whether Googlebot can request and render the resources required to understand a page.
Start with the basics: DNS works, the server responds, the URL returns an appropriate HTTP status, important CSS/JS resources are accessible, and robots.txt is not blocking something Google needs to see.
Use server logs when Search Console is not enough
For larger or technically complex sites, access logs show which URLs Googlebot requests, how often, which status codes it receives and whether crawl effort is being wasted on parameters, duplicate paths or errors. Logs are especially useful for diagnosing crawl patterns at scale.
Crawl budget is not a universal emergency
Small and medium sites usually gain more from fixing architecture, duplicate URLs and server errors than from obsessing over crawl budget. Treat crawl optimization as a scaling problem when the site is genuinely large, highly dynamic or generating substantial low-value URL combinations.
TECHNICAL SEO · INDEX
Indexed is not the same as ranked, and not every URL should be indexed.
Google’s Page Indexing report distinguishes indexed and non-indexed URLs. Your goal is not 100% index coverage. The goal is for the canonical version of every important public page to be indexed while duplicates, temporary URLs, filtered variants and intentionally private/low-value pages are handled appropriately.
Diagnose a missing page in order
- Does the URL return a successful and indexable response?
- Can Googlebot crawl it?
- Is there a noindex rule?
- Does it canonicalize elsewhere?
- Is it discoverable through links or sitemap?
- Is it a duplicate or near-duplicate of another page?
- Does Google consider it useful enough to index?
Use URL Inspection for the specific page and Page Indexing for broader patterns. Do not interpret “Not indexed” as automatically broken; many exclusions are intentional or healthy.
CONTROL ACCESS CORRECTLY
robots.txt controls crawling; noindex controls search indexing.
This distinction prevents a common technical mistake. A robots.txt rule tells compliant crawlers which URLs they may request. It is not the correct tool for guaranteeing that an HTML page stays out of Google Search. A URL blocked from crawling can still be known from external links and potentially appear with limited information.
Use noindex only where the crawler can see it
A noindex meta directive or X-Robots-Tag can remove an eligible resource from Google’s index, but Google must be able to crawl the resource to read the directive. Do not simultaneously block the same page in robots.txt and expect Google to process its noindex tag.
Use authentication for genuinely private information
SEO directives are not security controls. Admin areas, client documents and private records should be protected by proper access control, not merely robots.txt or noindex.
DISCOVERY & MONITORING
An XML sitemap is a discovery signal and monitoring aid, not a ranking button.
Include canonical URLs you actually want indexed. Exclude redirects, 404s, noindex pages and accidental parameter variants. Submit the sitemap in Search Console so you can monitor whether Google can read it and compare indexing for submitted URLs.
Keep sitemap hygiene aligned with canonical strategy
If a URL is in the sitemap but points canonical elsewhere, the site is sending conflicting signals. The cleanest implementation is consistent: internal links, sitemap, canonical and redirects should all favor the same preferred URL.
DUPLICATE CONSOLIDATION
Canonicalization helps consolidate duplicate or very similar URLs around a preferred version.
Google currently describes redirects and rel="canonical" as strong canonical signals, while sitemap inclusion is weaker. Signals can reinforce one another, but Google may still select a different canonical if it believes another URL is a better representative.
Do not canonicalize unrelated pages
A canonical is for duplicate or very similar content, not a way to “send authority” from weak pages to a stronger page. If two pages solve different tasks, they should normally remain independent and self-canonical.
Use one preferred URL consistently
Choose HTTPS, hostname, trailing-slash and parameter conventions deliberately. Link internally to the preferred version. Redirect obvious alternates where appropriate. Put the preferred canonical in the sitemap. Consistency reduces ambiguity and maintenance cost.
URL LIFECYCLE
Redirects and HTTP status codes should communicate what actually happened.
| Situation | Preferred response | Reason |
|---|---|---|
| Page permanently moved to a relevant replacement | 301/308 redirect | Users and crawlers reach the new canonical destination. |
| Temporary move | 302/307 when truly temporary | Signals that the original URL may return. |
| Page removed with no suitable replacement | 404 or 410 | More honest than redirecting to an irrelevant homepage. |
| Server error | 5xx while the failure exists | Do not return a fake 200 page for an outage. |
| Soft 404 | Fix content/status behavior | A “not found” message with 200 status can confuse systems and users. |
Update internal links after migrations
Redirects are safety nets, not a reason to keep linking to old URLs forever. After a migration, update navigation, contextual links, canonicals, sitemaps and structured data to the final destination.
MACHINE-READABLE CONTEXT
Structured data can make content eligible for supported search features, but it does not guarantee a rich result.
Google recommends JSON-LD when practical because it is relatively easy to implement and maintain. Use a schema type that matches the visible main content and follow the specific feature requirements. Do not mark up information that users cannot see or fabricate ratings, prices, reviews or entities.
Validation is necessary but not sufficient
A Rich Results Test can catch many technical errors, but technically valid markup can still violate content policies or misrepresent the page. Test the markup, inspect the live URL, and ensure the structured data remains synchronized when the visible content changes.
Do not add schema “because SEO”
If a page is not eligible for a supported feature, adding random schema types creates maintenance burden without a clear benefit. Use Organization/WebSite where appropriate at the site level, Breadcrumb where it reflects real hierarchy, and content-specific types such as Article or Product only when the page truly qualifies.
RENDERING & DEVICES
Build pages so critical content, links and state remain understandable across mobile and rendered HTML.
Google can process JavaScript, but SEO should not depend on fragile client-side behavior. Important links should be real anchors, meaningful content should render predictably, and client-side applications should expose unique URLs for distinct indexable content.
Mobile is not a separate SEO project
Responsive layouts, readable typography, usable controls and equivalent primary content are part of the same page quality. Do not hide important text or links from mobile users simply to simplify the visual design.
Test what Google sees
Use Search Console’s URL Inspection and live test for important pages after major JavaScript, rendering, navigation or template changes. A browser looking fine to you does not prove the crawler received the same meaningful page.
AVOID SHORTCUTS
SEO tactics that work only if a search engine is fooled are strategic liabilities.
Google’s spam policies cover practices such as link spam, scaled content abuse, doorway abuse, cloaking, hacked content and site reputation abuse. Policies evolve, so important commercial SEO decisions should be checked against the current Search Central documentation rather than old forum advice.
Common high-risk patterns
- Buying links or exchanging products/services primarily for ranking credit without appropriate qualification.
- Mass-producing near-duplicate AI pages for keyword variants without meaningful added value.
- Publishing third-party content primarily to exploit the host site’s reputation.
- Creating doorway pages that funnel users to substantially the same destination.
- Hiding text or links from users while exposing them to crawlers.
A robust rule is to ask whether the tactic would still make sense if search engines ignored the link or page entirely. If the answer is no, examine the risk carefully.
COMMERCIAL CONTENT
Affiliate pages need more independent value, not more affiliate links.
AffiliateBest should never become a catalogue of merchant descriptions with buttons added. Commercial pages should help a reader make a better decision than the merchant’s own landing page can provide.
Build decision-support content
- Who the product is for — and who should choose something else.
- Current pricing/commission terms verified against primary sources.
- Material limitations and trade-offs, not only benefits.
- Alternatives and comparison criteria.
- Real screenshots, workflows, calculations or tests where available.
- Clear affiliate disclosure and appropriate sponsored-link attributes.
Separate editorial judgment from commission size
The highest-paying offer is not automatically the best recommendation. Audience fit, conversion quality, retention, refunds, product quality, support and long-term reputation can matter more than headline commission percentage.
SEO IN GENERATIVE SEARCH
Google’s current guidance for AI-powered Search still starts with strong SEO fundamentals.
Google’s 2026 guidance for generative AI features emphasizes valuable, unique, non-commodity content and explicitly states that established SEO best practices remain foundational. There is no separate magic “GEO” tag that replaces crawlability, indexability, clear content, structured data or site quality.
Design for citation-worthy information
Make facts easy to verify, use clear headings, explain decisions precisely, publish original data or examples when possible, and keep volatile facts current. This helps both traditional search users and systems trying to understand and summarize useful information.
Do not create dozens of pages for every conversational wording
Generative interfaces broaden how people ask questions. The scalable response is deeper topic coverage and strong page ownership, not manufacturing a URL for every prompt variation.
Measure generative-AI visibility with the dedicated Search Console report
As of August 31, 2026, Google says its dedicated Search Generative AI performance insights have rolled out worldwide. The Search report isolates impressions from supported generative-AI experiences such as AI Overviews and AI Mode and can be segmented by page, country, device and date. Treat this as a visibility signal, not a standalone success metric: connect AI-feature impressions to qualified visits, landing-page behavior, conversions and business value before changing strategy.
Do not confuse participation controls with ranking optimization
Search Console now also provides a Search generative AI control. Inclusion is the default; exclusion prevents a site's links/content from appearing in the covered generative-AI Search and Discover experiences and removes traffic/impression opportunities from those features. Google states that this control is not a ranking or inclusion signal for other parts of Search. Use it as a publishing/participation decision, not as a supposed GEO shortcut.
MULTILINGUAL SITES
International SEO needs separate URLs and explicit language/region signals.
If AffiliateBest later adds Lithuanian or other language versions, each version should have its own stable URL. Avoid changing the same URL’s primary content only based on browser language or IP location because crawlers and users need predictable, linkable destinations.
Use hreflang when there are equivalent language or regional versions
Hreflang annotations can help Google understand equivalent versions. Implement reciprocal annotations consistently and avoid pointing several unrelated pages at one translation. Canonical and hreflang strategies should not contradict each other.
Translate the experience, not only the words
Currency, legal disclosures, examples, product availability and search behavior may differ by market. A literal translation can be technically multilingual yet commercially irrelevant.
PRIORITIZE WITH EVIDENCE
SEO measurement should identify bottlenecks, not produce dashboards for their own sake.
The next module covers Search Console and GA4 in depth. For SEO operations, use data to distinguish four common situations:
| Pattern | Likely question | First investigation |
|---|---|---|
| No impressions | Is the page indexed and relevant to any demand? | Indexing, internal links, query targeting. |
| Impressions but poor average position | Is the page competitive for the intent? | Intent match, content quality, authority, internal links. |
| Good position, low CTR | Is the result presentation weak or the query mismatched? | Title/snippet, SERP features, brand recognition. |
| Clicks but no business outcome | Is the traffic qualified and the page experience aligned? | Intent, CTA, offer fit, conversion UX. |
Use change logs
Record major SEO changes with date, URL set, hypothesis and expected effect. Without a change log, teams often attribute traffic changes to the most recent visible action even when seasonality, competition, indexing or ranking-system changes were responsible.
PROFESSIONAL AUDIT WORKFLOW
Audit in dependency order so you fix the strongest constraint first.
- Define scope: business objective, site section, critical pages and time horizon.
- Verify access: DNS, HTTPS, status codes, robots.txt, rendering and important resources.
- Verify indexing: canonical URLs, noindex, duplicates, Page Indexing patterns, sitemap consistency.
- Map architecture: crawl depth, orphan pages, internal links, breadcrumbs, parameter spaces.
- Map query ownership: target intent, competing internal URLs, page types and content gaps.
- Evaluate content: accuracy, completeness, originality, evidence, freshness and commercial bias.
- Review on-page signals: titles, H1, headings, URLs, anchor text, images and metadata.
- Review structured data: eligibility, accuracy, validation and visible-content match.
- Review authority: legitimate links, mentions, link-worthy assets and risky patterns.
- Review SERP presentation: CTR patterns, titles, snippets and supported search features.
- Prioritize: impact × evidence × confidence ÷ effort, adjusted for risk.
- Verify after release: live HTML, Search Console, logs and business outcomes.
Classify findings by severity
Site/section inaccessible, deindexed, compromised or technically broken.
Canonical/indexing failures, major architecture defects, severe content mismatch.
Content gaps, internal-link improvements, title/snippet opportunities, structured data.
Low-impact metadata cleanup, minor wording, cosmetic SEO changes.
A 200-line SEO checklist is not automatically a better audit. The deliverable should explain what is wrong, why it matters, evidence, affected URLs, risk, recommended fix, verification method and priority.
IMPLEMENTATION ROADMAP
A 90-day SEO plan should remove technical risk first, then build compounding content and authority.
Days 1–30: establish technical and strategic control
- Verify Search Console, sitemap, canonical and indexation status.
- Crawl the site and fix critical 4xx/5xx, redirect loops, noindex/robots mistakes and orphan pages.
- Create the keyword-to-URL ownership map for priority topics.
- Audit title/H1 consistency and duplicate page intent.
- Identify the 10–20 URLs with the strongest current opportunity.
Days 31–60: improve the pages closest to results
- Upgrade high-impression pages with weak intent match or insufficient evidence.
- Strengthen internal links from relevant authoritative pages.
- Consolidate cannibalizing URLs and update redirects/canonicals.
- Implement supported structured data where it creates legitimate eligibility.
- Build one or two genuinely link-worthy assets instead of mass-producing generic articles.
Days 61–90: expand strategically
- Publish missing high-value cluster pages based on the content map.
- Promote original assets to relevant communities and partners.
- Review indexing and query growth by page group.
- Run an internal-link refresh across newly connected modules.
- Document what worked, what did not and the next highest-confidence experiments.
PRACTICE
Do these exercises before moving to Search Console and GA4.
Exercise 1 — diagnose one invisible page
Choose a page with little or no organic visibility. Check discovery, crawl, indexing, canonical, intent, content quality, internal links and SERP competitiveness in that order. Write the first bottleneck you can prove.
Exercise 2 — build a 20-query ownership map
Group 20 related queries into query families and assign one owner URL to each family. Mark queries that do not deserve a separate page.
Exercise 3 — run a title/snippet review
Take 10 important pages. Compare the title element, visible H1, current Google title link and likely search intent. Rewrite only the pages where you can state a concrete presentation problem.
Exercise 4 — technical control test
For five URLs, record status code, robots access, indexability, user-declared canonical, Google-selected canonical, sitemap inclusion and internal-link source.
Exercise 5 — create one link-worthy asset concept
Design a resource worth citing without asking for a ranking favor: calculator, benchmark, original dataset, template, research summary, diagnostic checklist or tool. Define who would naturally reference it and why.
PRIMARY / AUTHORITATIVE ENGLISH SOURCES
Use these references when implementing or auditing SEO.
Search systems and policies change. Re-check current primary documentation whenever a technical or commercial decision depends on Google’s latest behavior or policy.
Source review: . Time-sensitive product, legal, analytics and platform details should still be re-checked at the source immediately before implementation.
MODULE 09 COMPLETE
Next: turn SEO visibility into measurable evidence with Search Console and GA4.
Module 10 covers property setup, Search Console Performance and Page Indexing reports, URL Inspection, GA4 events and key events, traffic acquisition, attribution limits, UTM governance, dashboards and a measurement workflow for diagnosing real growth bottlenecks.