Add basic search engine information

Outcome

You will revise the WordPress site so each route gives people and search systems clear, page-specific information. You will inspect the rendered HTML and record evidence without claiming that the private Playground site is indexed or ranked.

Why this matters

Search engine optimization, or SEO, begins with a site that people can access, understand, and navigate. Titles, headings, content, links, URLs, and image alternatives help describe each page. They do not guarantee a position in search results.

What you will practice

Distinguish discovery, crawling, indexing, and serving a search result.
Explain how page titles, visible headings, URLs, content, links, and image alternatives can provide search signals.
Write unique, accurate page titles and opening summaries for a specific visitor need.
Inspect the rendered title element and visible page structure in the browser.
Separate verified page improvements from unverified claims about indexing or ranking.

What is new and what is reused

New: SEO, search intent, discovery, crawling, indexing, serving, title link, snippet, page-specific summary, and a search-signal audit.
Reused: Site purpose, page hierarchy, slugs, headings, descriptive links, alternative text, visitor testing, developer tools, and complete CMS exports.

Starting point

Before you start

The saved WordPress Playground site from the navigation lesson, or cms-navigation-checkpoint.zip.
The cms-site-map.txt plan and five connected published pages.
A current browser with developer tools.

Current state: The site has a logical hierarchy and working navigation. Some page titles and opening text are still generic, and no page-specific SEO audit exists.
First action: Open the saved Playground site or import cms-navigation-checkpoint.zip, then create seo-audit.txt beside the checkpoint files.
First checkpoint: The visitor view shows all five connected pages, and seo-audit.txt is ready to record one section per page.
Help trigger: Use the recovery note or ask for help if the restored pages are missing, the rendered title is hard to locate, a title change breaks a menu link, or you are unsure whether a statement is a verified page fact or an unverified search-engine outcome.

Required result

You have completed the lesson when:

seo-audit.txt records the visitor need, title, path, opening summary, incoming link, and image-text decision for all five pages;
the project detail page title is Responsive Profile Page while its stable path remains /projects/profile-page/;
every page has one unique, accurate visible page title;
every page begins with a page-specific summary that helps a visitor decide whether the page meets their need;
headings describe the sections that follow and preserve a logical order;
internal link labels describe their destinations;
the Home image keeps context-appropriate alternative text near relevant content;
the rendered HTML title for each inspected route is accurate and page-specific;
no text contains repeated keyword lists, false claims, hidden text, or a promise of ranking;
the visitor view still passes navigation, narrow-width, 200% zoom, and keyboard checks; and
a new complete export exists as cms-seo-checkpoint.zip.

Understand the search process

A search system can perform several separate actions:

Discover: Find a URL through links, a sitemap, or another known source.
Crawl: Request the URL and receive a response.
Index: Analyze and store information from the page when the system chooses to include it.
Serve: Select and present results for a query.

A page can be crawlable but not indexed. An indexed page can be irrelevant to a particular query. A technically correct page can rank below other useful pages. Treat each state as separate evidence.

Read a search result as an automated output

A typical text result can contain a site name, URL or breadcrumb, title link, and snippet. A search system chooses the final presentation and can change it for a query or device.

Search appearance model

Page signals can inform a search result, but they do not fix its final wording

Read the page signals first, then the possible result on the right.

Clear, page-specific signals help people and search systems interpret a route. The displayed search result remains an automated output, not a preview you can guarantee.

The page can influence the result through clear source information:

the HTML title element;
the visible page title and headings;
the URL path;
the page content;
descriptive internal and external link text;
image alternative text and nearby relevant content; and
references to the page from elsewhere.

A title link is the clickable result title. It can use the HTML title or other page and link signals. A snippet is the descriptive result text. It can come from page content and can differ between queries. A search system can sometimes use a meta description when it describes the page well, but it does not have to display that text.

Do not treat a search-result preview tool as a guarantee. Use it to inspect wording and likely truncation, then verify the real page source and content.

Record search intent and current evidence

Search intent is the need behind a search. This lesson uses visitor questions rather than a list of target keywords.

Add this structure to seo-audit.txt once for each page:

Page:
Visitor need:
Visible page title:
URL path:
Opening summary:
Incoming internal link:
Image text decision:
Rendered HTML title:
Evidence or change needed:

Use this table to define the visitor need:

Page	Visitor need
Home	Identify the portfolio and choose the next route
Projects	Find a list of selected web work
Responsive Profile Page	Review one responsive project and its decisions
About	Understand the role and current focus behind the work
Contact	Find a safe way to make contact

Audit before editing

Open each route in the visitor view. Record the current title, path, first paragraph, one incoming link label, and any image alternative text. Mark Evidence or change needed with a concrete observation such as:

The project page title is Profile Page. It does not state that the project is responsive.

Do not write a score. A score hides which page signal needs work and which evidence will prove the change.

Checkpoint: The SEO starting state is recorded

What now works: seo-audit.txt contains one evidence section for each published route and states the visitor need and current page signals.
Files changed: seo-audit.txt
What remains: Revise page titles, opening summaries, headings, links, and image context, then inspect the rendered HTML.
Next action: Open the Profile Page editor and change only its visible title first.
If it does not work: If a field is unclear, inspect the visitor view and record what a person can actually see before interpreting search behavior.

Make the project page specific

Open the existing Profile Page in WordPress Admin.

Change the page title from Profile Page to Responsive Profile Page.
Keep its parent set to Projects.
Keep its slug as profile-page.
Replace the opening paragraph with:

This project combines semantic HTML, reusable CSS, responsive layout rules, and prepared web images in one profile page.

Keep the Key decisions and Result sections.
Update the page.

A published title can change without changing its stable slug. The URL remains /projects/profile-page/, so existing links can continue to work.

Update labels that name the page

Edit the Projects content link so its label becomes:

Read the responsive profile page project

Update the submenu label to Responsive Profile Page if the menu does not update automatically. Keep it nested under Projects.

Update cms-site-map.txt so the child title becomes Responsive Profile Page while the path remains unchanged.

Check

Start at Projects in the visitor view. Follow the revised content link and confirm that the visible title is Responsive Profile Page and the address still ends in /projects/profile-page/.

Write useful opening summaries

The first visible paragraph should tell a visitor what the page provides. It should also give a search system relevant page content from which it can select a snippet.

Use or adapt these summaries:

Home

Studio Profile presents selected web projects built with clear structure, responsive layout, and web-ready visual assets.

Projects

Browse selected web projects and review the purpose, technical decisions, and result of each project.

About

Studio Profile documents a developing web practice focused on semantic structure, responsive design, accessible interaction, and clear project communication.

Contact

Contact Studio Profile through the reserved practice address to discuss a project or request more information.

Update each page so its summary appears directly after the page title and before the first section heading.

The wording should be natural and page-specific. Do not repeat the same phrase in every sentence. Do not add unrelated terms because you think they might attract searches.

Check headings and visible content

For each page:

keep one visible page title supplied by the CMS and theme;
use H2 for major sections inside the page;
use H3 only for a subsection inside an H2 section;
make each heading describe the content that follows; and
remove empty headings used only to create large text.

SEO does not replace semantic correctness. A heading must still help visitors and assistive technology understand the page.

Checkpoint: Each route states its distinct purpose

What now works: Every page has a unique visible title, a page-specific opening summary, descriptive section headings, and updated link labels that agree with the content.
Files changed: seo-audit.txt, cms-site-map.txt
What remains: Inspect rendered HTML titles, verify links and image context, record evidence, and export the new checkpoint.
Next action: Open Responsive Profile Page in the visitor view and inspect its head element in browser developer tools.
If it does not work: If two pages still sound interchangeable, compare their visitor needs and rewrite the first sentence to name the different result each page provides.

Inspect the rendered HTML title

Most CMS themes combine the page title and site title into an HTML title element. Inspect the output rather than assuming the pattern.

Open Responsive Profile Page in the visitor view.
Open browser developer tools and select Elements or Inspector.
Find the document’s head element.
Find the title element inside head.
Record the complete text in seo-audit.txt under Rendered HTML title.
Repeat the inspection for Home, Projects, About, and Contact.

Depending on the active theme and WordPress settings, the result can resemble:

<title>Responsive Profile Page – Studio Profile</title>

The separator and order can differ. The required result is accurate, unique page information—not one exact punctuation mark.

If two different pages produce the same HTML title, confirm that both visible page titles are saved, then inspect whether the theme or an installed extension replaces titles globally.

Understand meta descriptions without inventing a field

WordPress core does not give every page a universal meta-description field in the workflow used by this lesson. Do not paste description markup into a page’s visible content and assume it will enter head.

This is the HTML pattern a CMS setting or suitable extension would need to generate:

<meta
  name="description"
  content="Review a responsive profile page built with semantic HTML, reusable CSS, responsive layout rules, and prepared web images."
>

The core lesson improves the visible opening summary because search snippets are primarily generated from page content. If a future production CMS provides a page-specific SEO field, write a unique summary there and inspect the rendered meta element afterward.

Do not publish one identical description across every route. Do not promise that a search system will display the description unchanged.

Assistance 3 — Separate page evidence from search outcomes

Use these statements as a model:

Verified: The rendered HTML title contains Responsive Profile Page and Studio Profile.
Verified: The first paragraph accurately summarizes the project’s content.
Verified: Projects links to the page with descriptive anchor text.
Not verified: A search engine has indexed this Playground page.
Not verified: The page ranks for a phrase.
Not guaranteed: A search result will display the exact title and summary that you wrote.

Record only the first three as completed page evidence. Keep the remaining statements as explicit limits.

Check links and image information

Search discovery and human navigation both depend on usable connections.

Start at Home and follow View the selected projects.
Follow Read the responsive profile page project.
Confirm that the browser reaches the expected stable path.
Use the menu and submenu to reach the same pages.
Confirm that link text remains specific when read without the surrounding paragraph.

On Home, inspect the workspace image:

keep the image near text about the work it supports;
keep its visible caption;
keep alternative text that describes its purpose in context; and
do not add search phrases that the image does not communicate.

Alternative text is an accessibility requirement first. Accurate image context can also help search systems interpret the image. Do not turn alt into a hidden keyword list.

Test the visitor result

Test every route in the visitor view:

about 320px viewport width;
200% zoom;
keyboard navigation and visible focus;
mobile menu and submenu operation without hover;
browser Back and Forward; and
image unavailable or blocked.

SEO work does not justify breaking usability, accessibility, or the information architecture. A search visit still ends on a page that a person must be able to use.

Update each seo-audit.txt section with the final values and one evidence statement. Use No image on this page when a page has no image. Do not leave a blank field that another reader could mistake for an incomplete audit.

Export the search-ready checkpoint

Open Export in the WordPress Playground Dock and select Download as .zip. Rename the complete-site export:

cms-seo-checkpoint.zip

Store it beside seo-audit.txt, cms-site-map.txt, and the earlier ZIP checkpoints. Confirm that the new ZIP is greater than 0 bytes before closing the tab.

Self-check

Complete these checks against the required result.

Open seo-audit.txt and confirm that all five pages have a visitor need, title, path, opening summary, incoming link, image-text decision, rendered HTML title, and evidence note.
Open Responsive Profile Page and confirm that its visible title changed while its stable path remains /projects/profile-page/.
Confirm that Projects and the submenu use the updated descriptive project-page label.
Read each opening summary and confirm that it accurately distinguishes that page from the other four routes.
Inspect each page structure and confirm that it has one page title and logically ordered section headings.
Inspect the rendered title element on every route and confirm that each title is accurate and unique.
Follow the internal link route from Home to Projects to Responsive Profile Page and confirm that each label predicts its destination.
Inspect the Home image and confirm that its alternative text is accurate, contextual, and not a keyword list.
Search the visible content for repeated keyword lists, false ranking claims, hidden text, and identical page summaries. Confirm that none remain.
Test every route at about 320px width, 200% zoom, and with keyboard navigation. Confirm that the SEO revisions did not break the visitor experience.
Explain why the current evidence does not prove that the Playground site is indexed or ranked.
Find cms-seo-checkpoint.zip and confirm that it is greater than 0 bytes.

What basic SEO can and cannot establish

Basic SEO can make page meaning clearer, connections more usable, URLs more readable, and rendered source more descriptive. It can remove avoidable barriers to discovery and interpretation.

It cannot guarantee crawling, indexing, traffic, or a ranking position. Those outcomes depend on public access, technical configuration, competition, relevance, authority, search-system decisions, and change over time.

Use evidence at the right level: inspect the page for page claims, server and crawl tools for crawl claims, index reports for index claims, and search-performance data for traffic and query claims.

Optional SEO investigations

The required lesson is complete before these investigations. Choose one route that adds a separate kind of evidence.

Add page-specific meta descriptions in a supported environment

Use a teacher-approved SEO field or extension in a non-production copy. Add a unique description for Home and Responsive Profile Page. Inspect the rendered meta name="description" elements and confirm that the values differ. Do not claim that a search system will display either value unchanged.

Compare two title candidates

Write two accurate title candidates for Responsive Profile Page. Ask another person which candidate better predicts the page content and why. Keep the title that gives clearer information without repeating the site name unnecessarily in the visible page heading.

Prepare a public-deployment checklist

Create a checklist for a future public site: stable HTTPS URL, crawlable links, no accidental noindex, XML sitemap location, canonical URLs, responsive pages, server status checks, and a verified search-console property. Do not apply production settings to the private Playground site.

Optional references

Google’s SEO Starter Guide explains title links, snippets, site structure, links, and image context.
Google’s snippet documentation explains how page content and meta descriptions can contribute to query-specific snippets.
Google’s title-link documentation lists the page and link sources that can influence an automated title link.
WordPress SEO documentation provides WordPress-specific context for content, permalinks, links, and crawlability.

Next step or safe stopping point

The required lesson is complete when every page presents clear, unique, connected information, the audit records rendered evidence and limits, visitor behavior still works, and the new ZIP checkpoint exists.

Continue to Practice: Build a small CMS site to build the complete CMS, navigation, media, and basic SEO result from a new starting state.

If you stop here, leave yourself this resume note beside the audit: Page signals are verified; indexing and ranking are not claimed. Next, preserve this reference site and start the CMS assignment from its required independent copy.