How to Do on Page Seo

Most advice about how to do on-page SEO starts with a checklist long enough to require its own project manager. That's the wrong place to begin. Search visibility usually doesn't improve because someone changed every subheading, added an exact-match phrase to an image filename, or counted related terms like they're inventory.

The work that matters is more focused. Choose the right query, satisfy the intent behind it, make the page's purpose obvious in the HTML, and remove technical barriers that keep search engines or people from accessing it. Title tags deserve particular attention because a large analysis of 4 million Google search results found that titles between 40 and 60 characters earned the highest organic CTR, with 33.3% higher CTR than titles outside that range and an 8.9% better average CTR overall (Backlinko's Google CTR analysis).

This guide separates meaningful optimization from checklist theater, so a small business team can spend its limited time on decisions that affect rankings, clicks, and useful visits.

Why Most On-Page SEO Advice Misses the Point

On-page SEO is not a ritual that gives every page the same set of edits. It is a page-level relevance problem. A service page, product page, and educational article may all target search, but each needs a different structure, promise, and next action.

Searchmetrics research found that text relevance was the strongest correlate of higher search positions, while only 53% of top-20 URLs in 2016 included the exact keyword in the title (Search Engine Land's coverage of the Searchmetrics study). That finding cuts through the advice to repeat a keyword in every available field. Exact wording can clarify a topic, but relevance comes from answering the need behind the query.

Four decisions carry most of the weight

1. Query selection: Does the search need fit the business and justify a dedicated page?
2. Intent satisfaction: Does the page provide what visitors expect, such as an explanation, comparison, service option, or clear next step?
3. HTML clarity: Do the title, H1, headings, URL, and visible copy describe one subject without sending competing signals?
4. Technical eligibility: Can Google render, crawl, index, and retrieve the content that matters?

These decisions deserve attention before minor wording changes. Details such as formatting and image filenames can support accessibility, usability, and maintenance, but they rarely compensate for a page aimed at the wrong query or built around the wrong user need.

Practical rule: If an optimization does not improve relevance, comprehension, discoverability, or the visitor's next action, assign it a lower priority.

Google's guidance recommends descriptive titles, warns against keyword stuffing and repeated boilerplate, and says the main title should clearly describe the page (Google's title and snippet guidance). That standard is more useful than chasing an arbitrary audit score. A page can pass dozens of tool checks and still fail because its promise is vague or its content does not answer the search.

Use a checklist to diagnose gaps, then make a judgment about what deserves time. You can browse on-page optimization tips for additional ideas, but the page's query, intent, clarity, and access should determine the order of work.

The Page-Level Fundamentals You Have to Get Right First

On-page SEO does not require a 47-item checklist. A small set of page elements usually determines whether searchers understand the result and whether Google can connect it to the query. The rest can wait.

Start with the title tag. Write it for the search result, not for a character-count plugin. Put the primary topic near the front, add an intent modifier when useful, and make the promise specific. “Managed WordPress Security for Small Businesses” gives visitors a clearer reason to click than a string of disconnected service terms.

Google can rewrite publisher-supplied titles that are verbose, repetitive, or poorly aligned with the page. Analyses from Portent and Amsive have reported frequent title changes and a higher likelihood of rewriting for longer titles. The practical takeaway is simple: write concise, page-specific titles that accurately describe the page instead of chasing a perfect length.

Use each element for a distinct job

• Title tag: Aim for 50 to 60 characters when practical to reduce truncation, while prioritizing clarity over a rigid limit. Put the primary topic close to the beginning.
• Meta description: Treat it as ad copy, not a ranking lever. Yoast recommends roughly 155 characters, active voice, an actionable benefit, a call to action, and unique copy that matches the page (Yoast's meta description guidance).
• H1: Use one visible H1 that matches the title's intent. It can be more readable or slightly longer than the title tag, but it should not describe a different page.
• H2 and H3 headings: Use H2s for major sections and H3s for questions or subtopics within them. Do not skip heading levels to achieve a visual size.
• URL slug: Keep it short, descriptive, hyphenated, and focused on the topic. A practical limit is 60 characters. Avoid dates and unnecessary parameters, and preserve a stable structure.

The Google SEO Starter Guide recommends descriptive titles and meta descriptions. Its image guidance also favors useful, information-rich alt text written in context rather than stuffed with keywords.

Keep these elements aligned with the visible page. If the title promises “website security maintenance” while the H1 and opening copy focus on redesign services, visitors receive a mixed message and search systems have a less consistent page to interpret. Fix that mismatch before spending time on minor formatting details or image filenames.

Writing Content That Matches Search Intent

A keyword is a clue, not a content brief. Search the target query before drafting, then inspect the result types, page formats, and recurring questions. The results reveal how search systems currently interpret the query. Ignoring that evidence turns content planning into guesswork.

Informational queries usually need an answer-first structure. Define the subject quickly, explain the steps, then add examples and context. Commercial queries need comparisons, decision criteria, appropriate pricing context, and trust signals. Transactional queries need a clear action path, useful details, and answers to objections that could stop someone from contacting or buying.

Place the primary topic naturally

For a focused page, use the primary keyword or a close natural variation in the title, H1, opening copy, and at least one relevant subheading. That aligns the page with its topic without turning the copy into a repetition exercise.

Semantic depth means covering the entities, decisions, and related questions that make the subject useful. A page about website rebuilds may need migration, redirects, content preservation, accessibility, analytics, hosting, and post-launch maintenance. Do not force every related term into the copy. Answer the questions that belong to the reader's decision.

The shift from simple keyword matching toward relevance and semantic coverage makes topical completeness more useful than repeating one phrase. Search visibility still has limited value if visitors cannot find the answer quickly. Content that matches intent can support both clicks and engagement, while a page that makes visitors work too hard can disappoint after the visit begins.

Use answer-first formatting throughout:

• Lead with the answer: Put the direct response in the first sentence or paragraph under each heading.
• Expand with evidence: Follow the answer with explanations, qualifications, examples, and practical steps.
• Make sections stand alone: A reader should understand the point even after reaching a passage through a snippet or AI-generated summary.
• Match the format: Use comparison tables for comparisons, numbered steps for processes, and concise definitions for basic questions.

Word count should follow the query. A product page may need compact specifications and objections, while a broad educational topic may require more context. A long page that buries the answer is not more useful because it is longer.

AI-assisted drafting can organize research and generate alternatives, but editing determines whether the result deserves to rank. Guides such as write SEO content with AI can provide a starting point. A person still needs to verify accuracy, remove generic filler, and add information specific to the audience.

If two pages answer nearly the same query, consolidate them or give each one a sharply different purpose. Otherwise, keyword cannibalization makes performance harder to interpret because your own pages compete for the same intent. For practical guidance on the writing process, see Bruce and Eddy's guide to real SEO content writing.

Internal Linking, Schema, and Images That Tie It Together

Internal links help search engines interpret a site's topic relationships and help visitors choose a useful next page. Link broad guides to relevant service or topic pages, supporting articles back to a priority pillar page, and closely related pages to one another. The destination should answer the next question a reader is likely to have.

Use descriptive anchor text, such as “WordPress maintenance services,” instead of “click here.” The anchor gives visitors and search engines clearer context. Avoid forcing links into every paragraph. A few relevant connections usually serve the page better than a dense network added to satisfy a checklist.

Schema needs a reason to exist

Structured data clarifies what a page represents, but it does not automatically improve rankings or produce a rich result. Use JSON-LD when the visible content fits an eligible type:

• Article or BlogPosting: Editorial content with clear authorship and publication details.
• Product: Product information that follows Google's requirements.
• FAQPage: Genuine questions and answers displayed on the page.
• LocalBusiness: Accurate business details and applicable local service information.

Validate the implementation with Google's Rich Results Test. For a practical walkthrough of setting up markup correctly, see Bruce and Eddy's guide to structured data for SEO. Do not mark up content visitors cannot see, and do not activate every schema option a plugin provides.

One independent 2026 audit found structured data on only 17% of websites and Speakable schema on less than 3%, indicating an implementation gap rather than a reason to add irrelevant markup (Rank Nibbler's State of SEO 2026).

Images need useful descriptions and sensible files

Write alt text that explains what the image shows and why it matters in context. A screenshot of a title-tag audit should describe the interface or relevant finding, not repeat the target keyword. Decorative images can use empty alt text so assistive technology skips visual noise.

Compress images and use WebP or AVIF where the platform and browser support them. Set width and height attributes to reduce layout movement during loading. Google's image SEO documentation recommends useful, information-rich alt text instead of keyword stuffing.

Technical Checks That Decide Whether Any of It Matters

A page can have excellent copy and still fail before ranking becomes a meaningful question. Search engines need to render the page, crawl its important resources, and index the correct URL. These checks are less exciting than rewriting a title, but they protect every other investment.

Start with mobile rendering. Use Google Search Console's Mobile Usability report and inspect important templates on actual mobile devices. A responsive layout, readable content, usable navigation, and accessible primary content matter more than a decorative desktop experience that collapses on a phone.

Core Web Vitals provide specific performance gates. The benchmark table below uses the thresholds defined in Google's Core Web Vitals documentation.

These are field-oriented benchmarks, not permission to chase a perfect lab score while ignoring the page's purpose. Fix oversized media, blocking scripts, unstable layouts, and slow server responses before polishing minor details. Bruce and Eddy's Core Web Vitals guide offers a practical explanation of what each metric means for a working website.

Run an indexability check before editing copy

For each important page, verify the following:

• Renderability: Critical text and links should be available without depending on fragile JavaScript execution.
• Status: The intended URL should return a normal successful response, not a redirect chain or error.
• Canonical: Use a self-referencing canonical when the page is the preferred version.
• Indexing: Inspect the URL in Search Console and check a site: search for the specific address.
• Robots controls: Remove accidental noindex directives and avoid blocking important content.
• Sitemap hygiene: Keep the XML sitemap limited to preferred, indexable URLs and submit it through Search Console.

Parameter-heavy, duplicate, or thin URLs may not belong in the index. The goal isn't to index every URL your CMS can generate. It's to make the important pages easy to discover and the unwanted versions uninteresting to crawlers.

Measuring Whether Your On-Page SEO Actually Worked

Search rankings move around, and one position check can tell you almost nothing. Judge an on-page change against a baseline and a meaningful trend, not a screenshot taken after lunch.

Before editing a page, record its clicks, impressions, average position, and CTR in Google Search Console at both URL and query level. Add the date and describe the change, such as “rewrote title to clarify commercial intent” or “added comparison section.” Then review the page after the next crawl cycle and compare the surrounding period rather than reacting to a single day.

Read the pattern, not just the number

• Impressions increase while CTR stays flat: The page may be appearing more often, but the title or snippet isn't earning attention.
• Rankings remain stable while traffic disappoints: The page may target the wrong intent, attract an unqualified query, or make the answer difficult to find.
• Clicks rise without useful engagement: The title may promise something the page doesn't deliver, or the visitor may need a clearer next action.
• Important queries disappear: Check indexing, canonicalization, intent shifts, and major changes to the page before rewriting everything.

Google says snippets are previews of page content relevant to a query and may draw from the body rather than the meta description. It also provides nosnippet, max-snippet, and data-nosnippet controls (Google's snippet documentation). That's why the answer needs to appear in the visible copy, especially near the opening, instead of being hidden in metadata.

Use GA4 alongside Search Console to assess whether organic visitors engage, continue into the site, or complete the page's intended action. This SEO performance tracking guide can help structure the review. Don't declare victory because a vanity keyword moved. Ask whether the right people found the page and whether the page helped them make progress.

On-Page SEO Workflow and Common Questions

Small teams need a routine that survives busy weeks. Assign ownership to the person who publishes or manages the website, set a recurring calendar task, and keep the audit short enough that it happens.

Use this operating rhythm

Each week, audit every new or materially updated page with five checks:

1. Title and meta review: Confirm the title describes the page and the meta copy makes a clear, accurate promise.
2. Heading hierarchy: Check that the H1, H2s, and H3s reflect the page's actual structure.
3. Internal links: Add relevant links to useful next pages and confirm existing links still work.
4. Image accessibility: Review alt text, filenames, dimensions, and obvious performance problems.
5. Speed spot-check: Test the page on mobile and look for large media or scripts that make the opening sluggish.

Each month, review Search Console for drift. Look for changes in impressions, clicks, CTR, average position, and indexing on priority URLs. Validate schema, check broken links, inspect the current SERP format, and identify pages whose traffic is falling because the query or market expectation has changed.

Each quarter, refresh stale pages. Revisit titles, introductions, examples, outdated claims, internal links, and calls to action. Keep a change log so you know what changed and when. The person responsible should have enough access to the CMS, Search Console, and analytics to complete the work or escalate technical issues quickly.

Questions that deserve direct answers

Does on-page SEO still matter when AI Overviews summarize results?
Yes, but the emphasis is shifting toward explicit answers, clear entities, useful structure, and content that can be extracted without losing meaning. A page that hides its answer behind a long introduction is harder for both users and answer systems to use. The practical gap is machine readability, not a need to stuff in more keywords.

What should you do when a page suddenly drops?
Check whether the query's result format changed, whether searchers now want a different intent, and whether your page still matches the leading results. Then inspect indexing and technical changes before making content edits.

Does the H1 need the exact-match keyword?
No. It should clearly describe the page and naturally reflect the topic. Exact matching can help clarity, but a readable H1 is more valuable than awkward phrasing.

How thin is too thin?
A page is too thin when it fails to answer the visitor's reasonable next questions or offers no distinct value beyond another page on the site. Word count alone isn't the test.

What should a small team fix first?
Start with pages that already have impressions but weak CTR, important pages that aren't indexed, and high-value pages whose content doesn't match the current intent. Leave low-impact formatting cleanup for later.

If your team needs help turning this workflow into a functioning website process, Bruce & Eddy provides website strategy and rebuilds, WordPress development, hosting, security, maintenance, SEO, local visibility, and analytics support. Visit Bruce and Eddy to discuss which pages and technical priorities deserve attention first.