Search Engine Optimization

01Purpose and scope

• This manual supports the course Search Engine Optimization. It describes how practitioners who manage websites, content teams, and reporting for clients or internal products actually carry out the work, from the first crawl of a site to the monthly review of organic results.
• The scope covers the work a team controls on its own properties: technical health, page content, internal structure, and the outreach needed to earn references from other sites. It does not cover paid search campaigns in detail, although the two channels share keywords and landing pages and need coordination. Paid media is a separate discipline with its own budgets and platform rules.
• Practice changes with context. A local service business relies heavily on its business listing, location pages, and reviews. An ecommerce catalog contends with faceted navigation, duplicate product variants, and seasonal demand. A publisher depends on freshness and editorial quality. A business-to-business firm often has long sales cycles, so organic conversions are fewer and harder to attribute. The same methods apply in each case, but priorities and measures differ.
• No one can guarantee a ranking position. Search engines change their systems without notice, competitors move, and a result that was stable for months can shift in a week. A good practitioner promises a process, a measurable baseline, and honest reporting of what changed and what did not.

02Core principles

• Search engines try to match a query with pages that satisfy the intent behind it. Someone typing a question about a product's installation steps wants instructions, not a sales page. Start every decision by asking what the searcher is trying to do, then judge whether the page does that job better than alternatives.
• Crawlability and indexability come before ranking. A page that cannot be fetched, rendered, or stored in the search index cannot appear in results at all. Many lost organic traffic cases trace back to a misplaced noindex directive, a broken canonical tag, or a robots rule that blocked a whole directory after a release.
• Relevance is judged at the page level and at the site level. A page about running shoes gains credibility when the site consistently covers footwear, fit, and running topics with accurate detail. Thin pages scattered across unrelated subjects dilute that signal.
• Measure changes against a baseline and, where possible, change one major variable at a time. Testing one thing at a time is slower, but it tells you what worked. Bundling a title change, a new template, and a site migration into one release makes the results impossible to interpret.
• Stay within the published guidelines of the major search engines. Cloaking, hidden text, purchased link networks, and automatically generated pages with little value carry real penalty risk. Shortcuts that work for a few weeks often cost months of recovery work.

03Planning and preparation

• Begin by defining the business outcome. Leads, product sales, subscriptions, donations, and readership each point to different pages and different success measures. Agree on these with the people who own revenue or mission, because an organic traffic target by itself tells you little about value.
• Next, gather keyword and demand data. Export queries from the search engine's own webmaster console, which shows the impressions and clicks your site already receives. Add keyword research tools for estimated volume and related terms, and review internal site search logs, which show what visitors looked for after arriving. Group the terms by intent: informational, navigational, commercial investigation, and transactional. Each group usually calls for a different page type.
• Establish a baseline before changing anything. Record organic clicks, impressions, click-through rate, indexed page counts, and conversions for the pages in scope, using at least several months of history where it is available. Save screenshots or exports so later reports can be compared with the same definitions.
• Assemble the tools and roles. A typical setup includes a webmaster console, a web analytics platform, a site crawler that reports status codes, titles, canonicals, and internal links, a log file analyzer for large sites, and a rank tracker for a fixed set of queries. The SEO lead sets priorities and reviews results. A developer handles templates, redirects, and performance. A content editor writes or revises copy. An analyst maintains the reporting. On small teams one person may hold several of these roles, which is workable but makes review harder.
• Decide what is in scope and what is not before work starts. A site with fifty thousand product pages cannot be optimized page by page in one pass, so set a priority set of templates or categories first. Clarify who approves changes to navigation, URLs, and page templates, since those changes have the largest effects and the highest risk.

04Recommended workflow

1. 1
   : Audit the current state. Crawl the site with a tool that reports response codes, redirect chains, canonical tags, meta robots directives, and internal link counts. Compare the crawl with the indexing report from the webmaster console to find pages that are submitted but not indexed, or indexed but not wanted.
2. 2
   : Prioritize the findings. Rank issues by the traffic and revenue of the affected pages and by the effort required. A redirect chain on a page that earns almost no traffic can wait, while a template-level noindex on category pages should be fixed immediately.
3. 3
   : Map keywords to pages. Assign each priority query group to one primary page. Where two pages target the same intent, decide whether to merge them, differentiate them, or point one canonical to the other. This step prevents the internal competition that confuses both readers and search systems.
4. 4
   : Update on-page elements. Revise title tags, headings, and meta descriptions so they describe the page accurately. Make sure the opening section answers the core question directly. Add internal links from related pages using descriptive anchor text, and check that images have useful alternative text. Write for the reader first, then confirm that the page covers the terms a searcher would expect to see.
5. 5
   : Fix technical issues. Address slow templates, pages that render poorly on mobile devices, broken internal links, and missing or outdated XML sitemaps. Apply structured data only where it matches visible page content, and test it with the validation tools that search engines provide. Confirm that robots directives block only what should be blocked.
6. 6
   : Build authority through legitimate means. Original research, data sets, tools, and expert commentary attract references naturally. Outreach works best when it offers something useful to the other site, such as a correction, a resource, or a quote from a named expert. Avoid paid link placements that are not disclosed, and avoid mass requests that offer nothing in return.
7. 7
   : Release in controlled batches and log each change. Record the page, the change, the reason, and the expected effect in a change log. Releasing in batches lets you compare changed pages against a comparable group that did not change, which gives a rough control for judging impact.
8. 8
   : Review results after the search engine has recrawled the changes. Recrawl timing varies from days to several weeks depending on site size and crawl priority. Judge the change against the baseline and the control group, and note any algorithm updates or seasonal shifts that may have affected the results.

05Quality checks, risk controls and compliance

• Run a pre-release check on every change set. Confirm that no page carries an accidental noindex, that canonical tags point to the intended URL, that internal links do not return errors, and that key content renders when JavaScript is limited or delayed. Check that pages meet the Web Content Accessibility Guidelines at the level your organization has adopted, since accessible pages tend to be easier to parse for both people and machines. Keep a short written checklist so the same items are checked every time.
• Site migrations carry the highest risk. Changing domains, moving to HTTPS, or restructuring URL paths can cut organic traffic sharply if redirects are incomplete. Map every old URL that has traffic or links to a specific new URL, avoid redirecting large numbers of unrelated pages to the home page, and monitor coverage and clicks daily for several weeks after launch. Keep the old site's analytics and webmaster property available for comparison.
• Privacy and tracking rules affect measurement. Consent requirements for cookies and analytics differ by jurisdiction and change over time, so check the current rules with your privacy or legal team and the authoritative sources in each market you serve. Data that cannot be collected cannot be reported, and reports should say so instead of filling gaps with estimates presented as fact.
• Disclosure rules apply to sponsored content and to affiliate or paid placements in many places. Where such content is published, follow the disclosure requirements that apply in the relevant jurisdiction and ensure that the link attributes used match the agreement with the partner.
• Topics such as health, finance, legal matters, and tax carry higher stakes for readers. Guidance in this manual does not replace qualified professional judgment, approved editorial procedures, or required authorization. Content in these areas should go through review by a qualified subject matter expert and any required approval process before publication.

06Collaboration and documentation

• Keep three shared records: a keyword and page map, a change log, and a prioritized backlog. The keyword map shows which page owns which intent. The change log lets anyone answer what changed on a given page and when. The backlog holds technical and content tickets with clear acceptance criteria, so developers and writers know what done looks like.
• Briefs make content work faster and more consistent. A useful brief names the target query group, the search intent, the questions the page must answer, the related entities or terms that should appear naturally, the internal links to include, and the pages it must not compete with. Writers who receive this kind of brief can produce copy that is specific enough to be useful, rather than generic copy padded with repeated keywords.
• Coordinate with product, sales, support, and legal early. Product teams control templates and URLs. Sales and support teams often know the questions customers ask, which are excellent sources for page topics. Legal teams need to review claims and comparisons before publication. Agree on shared definitions of an organic conversion and a qualified lead so every report uses the same numbers.
• Set a review cadence. A short weekly meeting can cover releases, crawl errors, and any ranking or traffic anomalies. A monthly review can look at trends, progress against the backlog, and decisions that need sign-off from leadership. Keep the dashboard small enough that people read it.

07Measures and continuous improvement

• Track indicators that connect to the business outcome. Useful measures include impressions and clicks by query group and by page, click-through rate for priority pages, the count of submitted pages that are indexed, organic conversions and their value, and the share of priority queries where a site's page appears on the first results page. Average position is useful for trend reading but is an average across queries and impressions, so it hides more than it shows.
• Recognize the limits of attribution. Organic visits often precede a purchase made through a direct visit, a branded search, or a paid click. Use assisted conversion reports where the analytics platform supports them, and state the attribution model in every report. Avoid claiming that a single change caused a traffic gain when seasonality, competitor changes, or search engine updates could explain it.
• Use the change log and control groups to learn. After each release batch, compare the changed pages with a comparable set that was not changed. Record what worked and what did not, and update the playbook so the next team does not repeat the same test without knowing the result. Revisit the priority list at a fixed interval so the work follows current business needs rather than last year's plan.
• Accept trade-offs. Aggressive technical cleanup can break working URLs in the short term. Expanding content quickly increases the risk of thin or repetitive pages. Heavy reliance on one referral partner or one search feature exposes the site to sudden loss. Good practice names these risks in advance and sets a rollback plan for each major change.

08Common mistakes and how to prevent them

• Chasing high-volume terms that have little commercial value. A page that ranks for a term with no buyers adds reports but not revenue. Prevention: score each query group by conversion potential before assigning it to a page, and include that score in the priority list.
• Creating several pages for the same intent. Competing pages split links and signals and confuse both readers and search systems. Prevention: maintain the keyword and page map, and check it before any new page is created.
• Blocking important pages by accident. A robots rule or noindex tag copied from a staging environment can remove a site from search results within days. Prevention: add an automated check to the release process that flags robots directives on priority templates, and confirm the result in the indexing report after each deployment.
• Changing URLs without redirects. Old links, bookmarks, and external references then lead to error pages, and the accumulated authority is lost. Prevention: maintain a redirect map as a required deliverable for any URL change and test sample redirects before launch.
• Filling pages with repeated keywords. Copy written to hit a term count reads poorly and rarely earns links or engagement. Prevention: require an editorial review that asks whether the page answers the question better than the pages already ranking, and cut any sentence that exists only to repeat a phrase.
• Reporting ranking changes without context. A position change reported alone invites false conclusions. Prevention: report traffic, conversions, and the control group alongside any ranking movement, and label estimates clearly.

09Practical checklist

• Confirm the business outcome and the pages that support it before selecting keywords.
• Record a baseline of clicks, impressions, indexed pages, and conversions with clear definitions.
• Crawl the site and reconcile the crawl with the indexing report for every priority template.
• Map each query group to one primary page and resolve any overlapping targets.
• Check titles, headings, internal links, and the opening answer on each changed page.
• Test redirects, canonicals, robots directives, and structured data before release.
• Log every change with the page, the reason, the expected effect, and the release batch.
• Compare changed pages with a control group and note any search engine updates in the same period.
• Review consent and disclosure requirements with the responsible team for the markets served.
• Hold a regular review to decide what to change next and to retire tasks that no longer matter.

★Learning sources

• Micro Degree: Search Engine Optimization
• Micro Degree: Marketing Strategy Development
• Micro Degree: Programmatic Advertising Management
• Micro Degree: Lead Generation Operations