On-page SEO helps one page answer a search intent clearly through its title, headings, copy, links, and images. This checklist covers the elements teams most often miss before publishing or refreshing an existing page.
Quick summary
What you get from this article
- One page should cover one main topic and carry a single H1.
- Make titles concise, unique, and accurate without treating character count as a fixed rule.
- Meta descriptions do not affect ranking but strongly affect click-through.
- Open sections with direct answers for reader clarity, not to chase an AI formula.
- Structured data must match what the page actually shows.
One page, one primary topic
Before touching technical details, answer what question this page is meant to answer and for whom. A page that tries to cover three topics at once often ranks for none, because the content is not deep enough in any of them.
Write down one primary phrase and a few related terms before drafting, then make every heading on the page support that main topic.
If an existing page already receives traffic for mixed intents, clarify or split the content before adding more keywords.
Example case (name withheld): a service page title focused on the company name. After rewriting the title to match search intent and moving the primary phrase to the front, click-through rate from search rose roughly 22% in five weeks — rankings may still fluctuate, but CTR showed the headline communicated better.
Image slot prepared — artwork to follow
Image slot — old vs intent-aligned title in search results
Titles and meta descriptions that work
The title is an important on-page signal. Make it accurate, concise, and unique. Put the primary phrase near the front when it reads naturally, but do not treat 50–60 characters as a fixed Google limit; title links may be generated from several page elements.
The meta description is not a direct ranking factor, but it can communicate the reason to click. Summarise what the page delivers without treating 155–160 characters as mandatory because snippets vary by query and device.
Review title and meta as a pair against intent. If the title promises sales copy but the page teaches, people bounce and CTR suffers over time.
- One unique title per page across the site
- Primary phrase near the front in natural language
- Meta description describes the page outcome, not the company pitch
- Bilingual sites need separately written Thai and English copy
Image slot prepared — artwork to follow
Image slot — title and meta description examples aligned with search intent
Heading structure and answer-first writing
Use one H1 as the page title, H2 for main sections, and H3 for detail under each H2 without skipping levels. Screen readers and search systems both rely on that order to understand structure.
Answer in the first two sentences
Start with the direct answer, then expand with detail so readers get the point quickly and the structure stays clear. Google says no special writing format or artificial chunking is required for AI Search.
Add a visible FAQ section
Questions customers repeat in chat or on calls are useful source material. Add concise visible answers when they help decisions, but do not do this only for an FAQ rich result: Google stopped showing that feature on 7 May 2026.
Image slot prepared — artwork to follow
Image slot — H1 H2 H3 structure with answer-first opening paragraphs
Links, images, and details teams skip
Internal links signal which pages matter. Use anchor text that describes the destination instead of click here. Meaningful images need alt text for screen readers and descriptive file names.
Unoptimised image weight is a leading cause of slow mobile pages, which hurts both experience and Core Web Vitals.
- Anchor text describes the destination
- Meaningful images include alt text
- Decorative images are hidden from screen readers
- Compress and use modern image formats before upload
- URLs are readable, short, and free of random IDs
Technical basics every page should pass
Strong copy with broken technical setup may never get indexed. Check that each page has a self-referencing canonical, is not accidentally blocked, and that bilingual sites declare hreflang in both directions.
Finish with real-user mobile performance data, because lab tests often look better than the field.
- Correct canonicals with no cross-page conflicts
- Complete hreflang for Thai and English
- Pages in the sitemap and not accidentally noindexed
- Structured data matches visible content
- Core Web Vitals pass on mobile
Image slot prepared — artwork to follow
Image slot — technical on-page checklist for canonical, hreflang, and schema
Preparation
Information to prepare before you start
- Primary and related queries for every page
- Titles and meta descriptions written separately per page and language
- Heading order from H1 to H3 without skipped levels
- Image alternative text and compressed file sizes
- Canonical, hreflang, sitemap, and structured data
Related services
