How to Do On-Page SEO: A Step-by-Step Page Review
Review one page from title and headings to images, internal links and mobile usability using a practical on-page SEO checklist.
By New Delhi Website Technologies · Practical SEO learning series
Start with a website you own or are authorised to edit. Examples are teaching exercises; search rankings and traffic results are not guaranteed.
What you will learn
On-page SEO is the work you can review directly on a page: its purpose, written answer, title, headings, images, links and supporting metadata. It works best as a connected editorial review rather than a list of keyword placements. In this lesson you will inspect one service page or guide from top to bottom, record evidence and publish a focused improvement. Keep a backup of the original page so you can compare the result and recover if a shared template changes unexpectedly.
1. Start with the purpose and visible answer
Write down the main visitor question, then read the page without looking at its metadata. Can you find the answer quickly? Does the page explain the offer or procedure in terms a beginner can understand? Mark vague claims and replace them with useful facts you can support. For a website service page, that may mean describing what is included, what the customer provides and what happens after an enquiry. For a tutorial, it may mean adding prerequisites and a finished example. Improve the answer before concentrating on small tag changes.
2. Align the title, main heading and introduction
The browser title, visible headline and opening paragraph should describe the same subject. They do not need identical wording, but they should not promise different things. If the title says “HTML contact form tutorial” while the page only sells development packages, rewrite the page or change the promise. Use headings to show the structure of the explanation. A useful section heading tells readers what they will find underneath it. Avoid turning headings into lists of city names or repeating a phrase simply to reach an arbitrary keyword count.
3. Add enough evidence to make the page useful
Replace generic statements with worked examples, screenshots, scope tables or clearly labelled demonstrations. If a code example is incomplete, explain what still needs a server or service before it can work in production. If a cost is illustrative, label it as an example rather than a current quotation. Review every important claim as an editor: how would the visitor verify this? Use accurate captions and disclose material limitations. A short original explanation with evidence can be more useful than a long page assembled from repeated definitions.
4. Review links and the next useful action
Open each important link and confirm that it reaches the intended page. Use descriptive anchor text where it helps explain the destination. Link a beginner to the prerequisite lesson before a difficult step and to the next task when they finish. For a service page, give an appropriate enquiry route after the scope is clear. Keep navigation accessible on mobile and keyboard. A page should not depend on a hover-only control for an essential destination. Do not add large unrelated link blocks merely to create more internal links.
5. Check images and mobile reading
Use an image because it explains a concept, demonstrates a result or shows relevant work. Add concise alternative text for informative images and avoid filling it with marketing phrases. Set useful dimensions so the layout can reserve space, and serve appropriately sized files. On a phone, inspect line length, contrast, spacing, tables and buttons. Make sure important instructions are not hidden behind decorative effects. If a screenshot contains small text, explain the important point in the article as well so the lesson remains useful without zooming into the image.
6. Verify the published page as a complete experience
After publishing, reload the actual URL and confirm the title, description, links and visible content. Check that a shared layout update did not duplicate headings or insert a second description tag. Inspect the intended indexing state without changing private or duplicate pages indiscriminately. Keep a brief change log describing the page problem and correction. Then allow enough evidence to accumulate before judging search performance. One-page optimisation is an iterative task: fix the largest weakness, validate it, and use later observations to choose the next improvement.
Worked example
An imaginary services page says “best solutions for everyone” but omits deliverables. Improve it with a scope list, a short explanation of the design process, a sample project image and a clear enquiry link. Retain a concise topic-specific title. Your immediate success criteria are that a visitor can understand the service and complete the next step; any future traffic outcome needs separate measurement.
Your practical exercise
- Review one page using purpose, headings, evidence, links and mobile checks.
- Choose three changes that address actual visitor problems.
- Publish and verify the live URL on two screen sizes.
- Record what changed and which future metric could show whether it helped.
Save the page URL, the observed problem, your proposed change, the publication date and the check you performed. Record real report data separately from examples or expectations.
Frequently asked questions
Is there an ideal keyword density?
Do not write to a fixed repetition percentage. Use natural terminology and make sure the page explains the topic clearly.
Should every image contain the target keyword in alt text?
No. Alternative text should communicate the image information needed in its context. Decorative images may need empty alternative text.
Continue learning on this website
Explore our original practical guides below. Each page includes explanations, examples and checks you can apply to your own project.