WEBCETRA

Article

On-Page SEO Checklist

On-page SEO is how a single URL explains itself to people and to search engines. It is titles, headings, first paragraphs, internal links and media — aligned with the query the page is supposed to answer. It is not repeating a phrase until the copy becomes unreadable.

WEBCETRA Editorial · · · 11 min read

Work page by page. A homepage cannot rank for every service, city and product. Google’s starter material at https://developers.google.comsearchdocs still holds: make a page for a purpose, then make that purpose obvious. Technical blockers belong on blog/technical seo checklist; this article assumes the URL can be crawled.

Contents

  1. Pick the intent before you edit
  2. Title, H1 and meta description
  3. Headings, first screen and copy structure
  4. URLs, internal links and breadcrumbs
  5. Images, media and accessible text
  6. Experience and trust on the page, without theatrics
  7. Thin, duplicate and overlapping pages
  8. A repeatable page QA pass

Pick the intent before you edit

Write one sentence: this URL exists so that a specific audience can do or learn a specific thing. If you cannot, the page is a dump. Search queries are informational, commercial, transactional or navigational. Mixing all four on one URL usually means none of them is done well.

Check Search Console for queries the page already attracts. If it attracts the wrong ones, the title and H1 are probably mis-selling the content. If it attracts nothing, the page may be new, blocked, or targeting a phrase nobody uses.

Title, H1 and meta description

The title element should be unique, readable, and include the topic naturally. Do not end every title with the same slogan. The H1 should match the page the user thought they clicked — close to the title, not a cryptic brand line.

Meta descriptions do not directly rank, but they influence clicks. Aim for a complete thought around 150–160 characters. Repeat the offer, not the keyword seven times. If Google rewrites your description, your snippet may not match the page; tighten the first paragraph.

Headings, first screen and copy structure

Use one H1. Use H2s for real sections, not for styling. The first screen should state what you offer and who it is for. Buried value below a carousel is a conversion problem that also confuses snippet generation.

Write for the reader. Include the words people search if they are the words you would say in a sales call. Do not bolt them onto every sentence. Specificity (material, size, process, city) beats adjectives.

URLs, internal links and breadcrumbs

Prefer stable, readable paths. Changing URLs for SEO keywords is usually a downgrade once you have links and history. If you must change, 301 and update internals.

Link from related pages with anchors that describe the destination. A service page should point to proof, FAQ and contact. A guide should point to the service that implements it — for example this checklist pointing to services/seo. Breadcrumbs help users and can feed structured data if they match the visible trail.

Images, media and accessible text

Compress images. Give them descriptive file names and alt text that explains the image, not a keyword list. Decorative images can have empty alt. Captions help people; they are not a ranking cheat.

Do not put essential offers only inside images or videos. Search and screen readers need text. Transcripts and captions are good practice and match WCAG guidance at https://www.w3.org/WAI/WCAG22quickref.

Experience and trust on the page, without theatrics

Google’s quality language around experience, expertise, authoritativeness and trust is not a plugin. On a business site that means accurate claims, visible contact details, an organisation byline that exists, and no invented awards.

WEBCETRA articles are bylined WEBCETRA Editorial for that reason — practical company writing, not a fake personal guru. Do not add reviewer names you cannot stand behind. Healthcare topics need extra care; do not publish medical advice you are not qualified to give.

Thin, duplicate and overlapping pages

If two URLs target the same intent, merge them. Location pages need unique proof (address, hours, team, local service list), not a city name swapped in a template. Product variants may need canonicals rather than twenty near-duplicate descriptions.

Ecommerce overlap is its own problem — faceted navigation, manufacturer pages, and thin tags. See blog/ecommerce seo guide. International overlap is blog/international seo guide.

A repeatable page QA pass

Before you publish or re-publish, walk the page on a phone. Check title, H1, first paragraph, headings, one internal link up, two internal links across, images, form or phone, and that the canonical is self-referencing.

Then wait. Rankings move slowly. If nothing happens after a genuine improvement, look at technical access and demand for the query — not at whether you used the phrase one more time.

  • Unique title and H1 aligned with intent
  • Description that would make you click
  • Copy that answers the query in the first screen
  • Working internal links, not click-here soup
  • No keyword stuffing, no fake testimonials

Questions

How often should I rewrite titles?

When the intent is wrong or the snippet is misleading. Weekly title churn for the same URL rarely helps and makes testing impossible. Change, measure in Search Console over weeks, then decide.

Do I need a blog to do on-page SEO?

No. Service, product and location pages are on-page work. A blog helps when you have questions worth answering that should not live on a sales page. Thin posts published for freshness usually add noise.

Is keyword density a real metric?

Not as a target. If a reader can tell you were writing for a density number, you overshot. Use the language of the customer, once clearly, and again where a new section needs it.

Author

WEBCETRA Editorial. Practical articles from WEBCETRA on websites, SEO and digital systems. Written for business readers, not for ranking tricks.

Further reading on Google Search Central (developers.google.com/search/docs), Core Web Vitals on web.dev, and accessibility on the WCAG 2.2 quick reference.

Ready to talk through a project?

Share your goals, constraints and timeline. WEBCETRA will respond with questions that help scope a realistic next step — not a generic sales script.