On-Page SEO and Content Optimization

On-page SEO is the work of improving a published page’s content and presentation. It helps readers complete a task and helps search engines understand the page’s subject.

Compare what the page offers with what the reader needs. Review the title and search snippet, headings, main content, evidence, internal links, images, author and source information, structured data, and facts that changed after publication. Each edit should solve a specific problem: clarify a title, add a missing fact, explain a step, support a claim, or link to useful detail. Extra paragraphs that repeat keywords do not make the page more useful.

Clear, accessible content gives search systems better information about the page. Google’s guidance for AI features in Search states that pages must meet existing Search eligibility and technical requirements. Meeting those requirements does not guarantee appearance in an AI feature. A revised title does not guarantee higher rankings or more clicks, and valid structured data does not guarantee a rich result or AI citation.

Do not build a content plan around a fixed word count, keyword-density target, or list of “LSI” terms. Search engines do not publish universal targets for these measures. Use E-E-A-T - experience, expertise, authoritativeness, and trustworthiness - to ask whether readers have reason to trust the page. It is not a universal score to optimize. Judge each change by the reader problem it resolves, then review the available evidence.

Start with the reader’s task

Before changing the wording, write one sentence that defines the page’s job: “For [reader], this page helps them [task] so they can [decision or next step].” Use that sentence to decide whether each section helps the reader complete the task.

Where data is available, review the page’s queries and performance in Google Search Console’s Performance report. Compare those patterns with the page and with current results for several relevant queries. Search results offer clues about what people expect from a query, but they do not prove search intent, the goal a person has when entering a query. Impressions and average position also do not show whether the page meets that goal.

Then check the page against its stated task. Mark unanswered questions, unclear claims, missing steps, outdated facts, and passages that distract from the reader’s goal. Confirm that each issue matters to the page’s purpose before rewriting.

Check the page against intent

For an instructional query, provide the steps, prerequisites, likely problems, and a way for readers to confirm success. For a comparison query, state the criteria, explain the comparison’s limits, and support each claim with evidence. How to Build Comparison Pages With Explicit Criteria and Limitations covers this work in more detail.

For a product query, make decision-relevant facts easy to find before adding promotional copy. What Product Facts to Make Clear Before Adding More SEO Copy addresses that task.

Keep related questions on one page when the page can answer them clearly without losing focus. Creating a page for every wording variation fragments the answer and creates unnecessary overlap. How to Map Customer Questions Without Creating a Page for Every Query Variation provides a method for grouping related questions.

When an existing page serves mixed purposes, choose the change that best supports the reader’s task. Narrow the scope if unrelated material distracts; reorganize the page if the answer is hard to find. Link to a separate page when a related question needs different treatment.

If the URL does not appear in Google Search, investigate indexing separately. URL Inspection reports indexing status and crawl information. Editing content does not establish that Google indexed the URL or selected it for search results.

Write accurate titles and descriptions

Key takeaways: Write titles and descriptions that match the landing page. They give Google useful signals, but Google chooses the title link and snippet displayed in search results.

Check the HTML <title>, visible main heading, prominent headings, and social-sharing title, often set with og:title. Google lists these signals, along with page text and links to the page, among the information it uses to generate title links. Keep them accurate and consistent with the page’s subject.

Write a distinct, concise title that states what the page covers. Avoid vague labels, repeated boilerplate, and keyword stuffing. Google truncates title links to fit available screen space, but it does not set a universal character limit for HTML titles. A precise title improves the signals Google evaluates; it does not guarantee the exact wording shown in search results. Follow Google’s current title link guidance.

Write a page-specific meta description that previews useful content. Google may use the description or generate a snippet from page text that better matches the query. The meta description does not control the wording shown in results. Do not include changing prices, unsupported claims, repeated keywords, or clickbait promises the page does not fulfill. Google explains these choices in its snippet guidance.

Diagnose a rewritten title

A changed Google title link alone does not indicate a ranking problem. Compare the displayed title with the HTML <title>, visible main title, prominent headings, page text, link text, and relevant structured data.

Check whether any of these sources are empty, incomplete, outdated, inaccurate, generic, unclear, or in a different language from the page’s main content. Fix the mismatch before changing the HTML title.

Google must recrawl and reprocess the page before revised title signals appear. Google states that this can take a few days to a few weeks, with no fixed timing for a particular URL. A title-link change does not show which source Google used, whether rankings changed, or whether clicks increased.

Make the main content answer the query

Put the answer, decision, or first useful action near the top of the page. Follow it with the steps, explanation, conditions, and exceptions readers need to act. Someone searching for router reset instructions needs the reset steps and a warning that the reset erases saved settings before a history of wireless networking.

Use one clear, visible main heading and section headings that state what each section covers. In the HTML, use heading elements such as <h1>, <h2>, and <h3> to mark the page structure, then use CSS to control their appearance. W3C guidance on headings explains how structured headings help people navigate and understand a page.

Organize sections around the reader’s task. Present instructions as steps and organize comparisons by their criteria. Put conditions or exceptions that change the answer in separate sections. Define unfamiliar terms before relying on them.

Replace broad claims with details readers can verify or use. “Setup is easy” does not tell a reader what to do. State the prerequisites, required steps, and how to confirm that setup worked. Remove repeated introductions, boilerplate, and keyword insertions that do not clarify the answer. Add text to supply a missing fact or explanation, not to reach a length target. Use lists for steps and comparisons. Use prose when readers need to understand how facts or ideas relate.

Google’s guidance on helpful, reliable, people-first content offers a useful check: does the page give its intended reader a useful answer? The guidance does not provide a score or guarantee rankings.

Add evidence readers can assess

Match the evidence to the claim. Link product behavior to current product documentation, technical requirements to the relevant standard, legal claims to the applicable law, and reported findings to the original research. State the source, date, scope, and limitations when they affect the conclusion.

Make clear what each statement represents. A documented fact, an illustrative example, an interpretation, and a recommendation require different wording. Do not present an example as a test result or imply firsthand experience that did not occur.

On product pages, make specifications, availability, pricing conditions, and other decision-relevant facts easy to verify before adding general SEO copy. See what product facts to make clear when that is the immediate problem.

Clear facts help readers check and use the information. Better content does not by itself establish a ranking change or inclusion in an AI search result.

Improve links and images

Add a link when readers need a related answer, definition, or next step. Use linked words, called anchor text, that describe the destination. “How to find important pages with no useful internal links” tells readers what they will find; “click here” does not. Links give Google a way to discover pages and understand how they relate, but adding one does not automatically improve rankings. For a site-wide audit, see How to Find Important Pages With No Useful Internal Links.

Use standard HTML links with the destination in the href attribute. Google generally crawls these links. Links without an href value, and script-based controls that do not expose a destination, may not provide a crawlable path. Avoid repeated exact-match keyword anchors added only to place keywords. Write wording that fits the sentence and accurately describes the destination.

Make important pages reachable through internal links that readers would reasonably follow. Each link should help readers reach the next relevant information.

Keep images that explain, identify, compare, or demonstrate information readers need. Remove images that merely repeat nearby text or serve no reader purpose. For meaningful images, write alternative text, or alt text, that conveys the relevant information or function to people who cannot see the image. Use empty alt text (alt="") for decorative images so screen readers skip them. The W3C image decision tree helps distinguish decorative images from images that need text alternatives.

When an image is the only content in a link, its alt text should describe the link’s purpose or destination. Google may use that alt text as anchor text. Put essential information from charts, diagrams, and other visuals in the page text when readers need it to complete a task.

Identify authors and sources

Identify the person or organization responsible for the content when readers would reasonably expect that information. List an editor, reviewer, or fact-checker only when that person performed the work, and describe the role accurately.

Google’s guidance on helpful, reliable, people-first content recommends clear information about who created a page when readers would reasonably expect it. A byline establishes accountability for the content. It does not create a universal author score or guarantee rankings.

Support consequential, technical, time-sensitive, and disputed claims with sources readers can verify. Put each link close to the claim it supports. Prefer a primary document, standard, law, official record, or original research. State the source’s date and scope when those details limit what the evidence establishes.

When a page reports an original audit or observation, give the date, method, scope, and limitations. An audit of selected pages records what those pages showed at that time. It does not establish effects on traffic, rankings, citations, or revenue.

When the goal is to publish and explain a useful public reference, see How to Turn Existing Business Data Into a Useful Public Reference.

Use structured data only when it fits

Structured data adds machine-readable labels to facts already visible on a web page. Add it only when the markup accurately describes that content and the page meets the current requirements for the relevant search feature. Product markup, for example, should match the product name, price, availability, and other details shoppers see on the page.

Before adding markup, check Google’s structured data guidance and the documentation for the specific feature. Google’s structured data policies require marked-up content to be visible and accurate. Mark only facts readers can find on the page. Markup cannot supply missing facts, clarify vague wording, or substantiate unsupported claims.

Test the markup with the relevant validation tool after adding it. A passing test means the tool found no technical error within its checks, but it does not establish eligibility for a Google Search feature or guarantee a rich result. Google decides whether to show one under its current requirements and search systems.

FAQ content still serves readers when Google does not show an FAQ rich result. Google limits FAQ rich results to well-known, authoritative government and health sites. Useful FAQ Content and Structured Data: Which Problem Does Each Solve separates the value of clear on-page answers from the role of markup that describes those answers to search engines.

Check access and AI search

Clear, accessible content helps readers and search systems understand what a page says. It does not show that a search provider fetched or indexed the page. Nor does it show that an AI feature retrieved or quoted it, linked to or recommended it, or summarized it accurately.

Google states that a page must be indexed and eligible to show a search snippet before it qualifies as a supporting link in AI Overviews or AI Mode. These features use Google Search systems, but meeting the technical requirements does not guarantee inclusion. Google’s AI features documentation sets out the current requirements.

Keep the outcomes separate: crawler access, a recorded fetch, indexing, a search appearance, an AI source link, a brand mention, a recommendation, a visit, and a sale are distinct events. Each requires its own evidence.

Check the page response and browser display when important content seems absent. Review the site’s robots.txt rules as part of the access check, but do not treat them as proof that a particular crawler visited the page or followed those rules. Google explains that robots.txt controls crawling and does not guarantee that a blocked URL stays out of search results; Google can index a URL without crawling its content. See Google’s robots.txt guidance.

For source-selection factors, see How AI Search Finds and Selects Website Sources. For the separate question of search access and training permissions, see How to Separate AI Search Access From Training Permissions.

A dated page check

On November 11, 2026, an unauthenticated HTTP response for the sitemap-audit article was compared with the page’s visible browser content. After excluding the comment form, all 15 selected visible paragraphs longer than 60 characters appeared in normalized response text.

That check establishes that the selected paragraphs were present in the page’s response HTML at that time. It does not establish crawler access, indexing, ranking, AI selection, citation, recommendation, or the behavior of other pages on the site.

When the response text differs from the browser display, identify the exact content you compared, check for authentication differences, and investigate rendering before deciding what the discrepancy means. How to Check Whether Important Content Exists Without JavaScript covers that narrower rendering check.

Maintain and measure the page

Fix factual errors, missing answers, broken links, misleading titles, and inaccessible content before making cosmetic keyword edits. For time-sensitive pages, review facts and cited sources that may have changed. Update the content where needed, and explain meaningful revisions so readers understand what changed. See How to Update Time-Sensitive Guides Without Merely Changing Their Dates.

Check the published page

After publishing an update, inspect the rendered page - the version a browser and Google receive. Confirm that the main content and visible heading appear correctly. Check the HTML title, meta description, links, images, and structured data.

Also verify the canonical URL, which identifies the version you want Google to treat as the main page, and indexing directives such as noindex. A publishing error, incorrect canonical, or indexing directive can prevent an improved page from appearing in Google Search.

Read performance data carefully

In Google Search Console’s Performance report, compare impressions, clicks, queries, and pages across periods that fit the topic. Use comparable dates where possible. Seasonal interest, changes in search demand, ranking movement, and other site updates affect the numbers. Search Console clicks also differ from analytics sessions, and Google may attribute data to a canonical URL other than the URL you expected.

Record each meaningful change and its publication date. If you rewrite the page, change the title, and add sections at once, later movement cannot identify which edit produced the outcome.

A rise or fall after publication shows a change in performance, but alone it does not establish that one edit caused it.

Request a recrawl when needed

After substantial changes, follow Google’s recrawl request guidance when appropriate. A request does not guarantee when Google will recrawl or index the URL, improve its ranking, or show it in a search feature. A successful live test or fetch confirms that Google could retrieve the page at that time. It does not confirm that Google indexed the URL.

FAQ: What if Google crawls the page but does not index it?

Crawling and indexing are separate steps. Check the page content, canonical URL, indexing directives, and technical accessibility. Then review the specific exclusion reason in Search Console. See What to Investigate When Google Crawls a Page but Does Not Index It.

Why more SEO copy can fail

Add detail when it fills a gap in the reader’s task. A missing step, verified fact, comparison criterion, source, or caveat leaves the answer incomplete. Put the material where readers need it and explain why it affects the decision or action.

Extra paragraphs do not improve a page simply because they raise the word count, repeat a target phrase, cover loosely related topics, or imitate pages that rank. Google’s title-link guidance warns against keyword stuffing and repeated boilerplate in titles. That guidance does not establish that every repeated phrase in body copy harms rankings. It supports the same editorial discipline: keep repetition that improves understanding and remove repetition that adds clutter. Google’s people-first content guidance likewise asks whether content serves readers rather than a search-engine-first publishing goal.

A longer page is justified when each added section completes the answer. When readers need to know which option fits a use case, what evidence supports a claim, or which exception changes the recommendation, include that information. Use headings and semantic HTML when they make the page easier to scan and use with assistive technology. Structured data belongs only when it accurately describes information already visible on the page.

Do not infer a universal ranking formula from another page’s word count, heading count, keyword pattern, or structured data. Those visible features do not show why the page appears in search results or whether they contributed to its ranking.

Before adding a section, ask:

• Which reader question does it answer?
• What new, verified information does it provide?
• Does it make the answer easier to find and use?

If the proposed copy fails those tests, it does not complete the page’s job.

On-page SEO essentials

• Start with the reader’s task: State what the page should help someone do, then fix unanswered questions, unclear claims, missing steps, and outdated facts.
• Make useful information easy to find: Write an accurate title and description, organize the page with clear headings, lead with the answer, support important claims with evidence, and add relevant links and accessible images.
• Add only what completes the answer: Skip fixed word counts, keyword-density targets, and SEO filler. Use accurate author and source details, and add structured data only when it describes visible information.
• Check changes without overclaiming: Verify the published page and review search data over comparable periods. A content edit does not prove a ranking gain, rich result, indexing, or AI citation.

FAQ

How long should an SEO page be?

Use the length needed to answer the reader’s task, including necessary steps, facts, and caveats. There is no universal ideal word count.

How many times should I use a keyword?

Use the words that describe the page clearly and naturally. A fixed keyword-density target or repeated phrase does not make a page more useful.

How do I decide whether to add more content?

Add material when it answers an unanswered reader question, supplies a verified fact, or explains a necessary step or limitation. If a paragraph only repeats existing information or inserts related keywords, it is SEO filler.

What if Google shows a different title or description?

Google generates title links and snippets automatically, so its displayed wording can differ from the page’s title tag or meta description. Compare the displayed text with the page’s visible title, headings, content, and other prominent references. Fix inaccuracies or mismatches, but do not expect an edit to guarantee a particular search display.

Does structured data guarantee a rich result?

No. The markup must accurately describe visible page content and meet the current requirements for a supported search feature. Valid markup still does not guarantee that the feature will appear.

Does clear page content guarantee an AI search citation?

No. Clear, accessible facts help explain what a page says, but they do not guarantee that an AI search feature will retrieve, select, quote, or link to it. Access, indexing, and citation are separate outcomes.

What if the page still does not appear in search after I edit it?

A content edit does not establish that a page has been indexed or selected to appear in search. Check indexing and technical access separately. A recrawl request or successful fetch establishes neither indexing nor improved rankings.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com