Follow this step-by-step on-page SEO checklist to make any page search and AI ready in 2026, with two checks you cannot skip: Core Web Vitals and genuine E-E-A-T signals. The numbered list below is ready to run on your next page, whether it is a blog post, a service page or a landing page. We build sites against this exact list, and it holds up whether you are optimising for a human reader or an AI answer engine.
TL;DR:
- Ensuring a fast Largest Contentful Paint requires compressing hero images, as large unoptimized files are a common cause of slow load times.
- Selecting a single primary keyword should align with the page's search intent, as misaligned keywords waste optimization efforts.
- Structured data should be used selectively based on Google's supported subsets, to avoid penalties and maximize rich result chances.
- Updating core content, such as title tags and meta descriptions, offers quick improvements to click-through rates on existing pages.
- Regular reviews every six to twelve months help maintain content freshness, fix broken links, and ensure ongoing SEO effectiveness.
Table of Contents
- The complete on-page SEO checklist to run on every page
- How to prioritise and audit pages with limited time
- Practitioner notes: applying the checklist to real builds
- Balancing human writing with machine-readable structure in 2026
- How we help you put this checklist into practice
- FAQ
- Sources
The complete on-page SEO checklist to run on every page
This is the full sequence, in the order we check it on every page we build. Work through it top to bottom rather than jumping around: keyword decisions shape your title, your title shapes your heading, and your heading shapes how an AI system reads the page.
- Confirm search intent and pick one primary keyword. Decide whether the page should answer a question, compare options or sell something, then choose a single primary term that matches that intent. Search intent is the foundation of on-page work: tweaking titles and headings before intent is settled wastes effort, because you will rewrite the page anyway once you realise it answers the wrong question.
- Write a title tag that states the promise in under 60 characters. Lead with the keyword or its natural variant, then add a qualifier that separates your page from the ten others ranking for the same term. A title such as "On-page SEO checklist for small business sites" does more work than a generic "SEO tips".
- Write a meta description that earns the click, not the ranking. Google treats it as a suggestion rather than a guarantee: Search Central confirms it can replace your description with text pulled from the body when that matches the query better. Write one anyway, 150 to 160 characters, because a strong description still wins clicks when Google does use it.
- Set one H1 and a logical heading hierarchy. One H1 per page, H2s for main sections, H3s for sub-points, no skipped levels. A hierarchy that reads like a table of contents helps both a human skimming the page and an AI system parsing its structure.
- Build a short, descriptive URL slug. Strip stop words, keep the primary keyword, avoid dates and parameters:
/on-page-seo-checklistbeats/blog/post?id=4471. Shorter, stable slugs are easier to link to and easier to read in a search result. - Write body content that demonstrates real experience, not just keyword coverage. This is the E-E-A-T test: does the page show you have actually done the thing, with specifics, examples and a point of view, rather than summarizing what everyone else wrote? A comprehensive on-page checklist treats content quality and E-E-A-T as core ranking inputs alongside the technical items, not an afterthought.
- Place your primary keyword and its natural variants where they matter. Once in the opening paragraph, once in a heading, and then use synonyms and related terms through the rest of the page. Forcing the exact phrase into every heading reads as spam to a reader and flags as manipulative to a crawler.
- Add semantic and related terms naturally. Cover the vocabulary a reader or an AI model would expect around the topic, for example "meta description", "structured data" and "Core Web Vitals" on a page about on-page SEO, so the page reads as genuinely comprehensive rather than narrowly keyword-matched.
- Optimise every image for both users and crawlers. Use descriptive filenames, meaningful alt text, a responsive
srcsetand a fallbacksrc. Google's image SEO guidance recommends this combination for discovery and indexing, and an image sitemap helps on image-heavy pages. - Build internal links with descriptive anchor text. Link to related pages using the phrase a reader would click, not "click here" or "read more". A link such as "our website redesign process" tells both the reader and the crawler what the destination page covers.
- Add structured data that matches what Google actually supports. Schema.org documents hundreds of properties, but Google Search Central documents the specific subset it uses for rich results, so build your Article, FAQ or HowTo markup against that documentation rather than the full schema.org vocabulary.
- Pass Core Web Vitals at the 75th percentile. The recommended thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less, and a CLS of 0.1 or less. These are measured at the 75th percentile of visits, so a handful of fast loads will not mask a slow experience for most visitors.
- Format key answers for featured snippets and AI citation. Open the relevant section with a 40 to 60 word direct answer, then follow with a short list or table, and include the target phrase in the heading and opening sentence, a pattern the Ahrefs checklist recommends for snippet eligibility. The same structure helps agentic AI systems, which browse the web and generate answers by citing sources: clear headings and answer-first paragraphs are easier for these systems to extract and quote than long, meandering prose.
- Set canonical tags and robots directives deliberately. Every page should declare its own canonical URL, and any page you do not want indexed, such as a thank you page or a filtered listing, should carry a clear
noindexor be excluded through robots rules rather than left to chance. - Confirm mobile rendering and responsive behaviour. Check that text is readable without zooming, buttons are tappable, and layout does not shift as the page loads on a phone, since Google indexes and ranks primarily on the mobile version of your page.
- Review user experience signals that influence rankings indirectly. Intrusive pop-ups, slow interactive elements and confusing navigation increase bounce rate and reduce time on page, both of which undermine the quality signals the rest of this checklist is trying to build.
- Set a content review date and a maintenance plan. Stale statistics, dead links and outdated screenshots erode the trust signals you built in step 6, so put a six to twelve month review on any page covering a topic that changes.
- Audit for duplicate content across your own site. Near-identical service pages for different towns or product variants split ranking signals and confuse canonicalisation, so consolidate overlapping pages or differentiate them with genuinely distinct content.
- Check how the page reads out loud for voice search. Voice queries tend to be longer and more conversational, so a page that already answers questions in full sentences, as step 13 describes, tends to perform well here without extra work.
A few of these items need extra care because they are easy to get wrong even when you think you have covered them.
- Alt text that only repeats the filename ("IMG_4471.jpg becomes a photo of a kitchen") gives crawlers nothing useful: describe what the image shows and why it is there.
- A canonical tag pointing to the wrong URL variant (with or without
www, with or without a trailing slash) silently splits your ranking signals across two addresses. - Structured data copied from a template often references properties your page does not actually have, which risks a manual action rather than a ranking boost.
Pro Tip: Fix your Largest Contentful Paint before anything else on the Core Web Vitals list. It is usually the hero image or a render-blocking script, and it is the easiest of the three metrics to move in a single afternoon.
Pro Tip: When you cannot update every page on a template at once, apply the title, meta and heading changes site-wide first. They take minutes per page and compound across every URL using that template.
How to prioritise and audit pages with limited time
Not every page deserves the full nineteen-step pass today, so sort pages before you touch anything. New pages going live this week need the full checklist before launch, since fixing a published page is always more work than building it right the first time. Existing pages that already rank need a lighter audit focused on Core Web Vitals, content freshness and internal links, because a sudden rewrite risks losing rankings you already hold. Templates, such as a service page pattern used across a dozen locations, deserve the most attention of all: one fix there multiplies across every page built from it.
Once pages are sorted, these quick wins return the most value for the least effort:
- Rewrite the title tag and meta description, since this takes minutes and directly affects click-through rate.
- Rewrite the opening paragraph to answer the query directly, improving both snippet eligibility and AI citation odds.
- Compress and convert hero images to a modern format such as AVIF or WebP.
- Lazy-load images and embeds below the fold so they stop competing with the content users see first.
- Identify the heaviest third-party script, usually an ad tag, a chat widget or an old analytics snippet, and defer or remove it.
The measurement playbook is the same for every page: start in Google Search Console to see which queries and pages have the biggest gap between impressions and clicks, then run PageSpeed Insights on the worst-performing URLs to see which Core Web Vital is failing, then check real user data if you have it, since lab data from PageSpeed Insights can differ from what real visitors experience, and field data segmented by device is what Search Console and Chrome UX Report actually report against. Aim for the 75th percentile targets from the checklist above on both mobile and desktop, not just the average visit.
Here is a one-hour audit you can run on any single page:
- Open Search Console's Page Experience report and PageSpeed Insights side by side for the URL, and note which Core Web Vital, if any, fails.
- Read the page as if you were the target reader and mark the first sentence that does not directly serve the query.
- Check the title, meta description, H1 and URL against the keyword you actually want the page to rank for, not the one you chose a year ago.
- List every image without meaningful alt text and every internal link using "click here" or "read more", then fix both in one pass.
Practitioner notes: applying the checklist to real builds
We apply this exact checklist to every site we build at Webnora, and a few proof points map directly onto the items above. Because each site is custom-built rather than assembled from a recycled template, the markup is controlled closely enough to hit Core Web Vitals targets without fighting bloated theme code. Because the finished site is reviewed and approved by clients before payment, the incentive to ship a fast, correctly structured page is built into how we work rather than added as an afterthought.
Two anonymised examples from recent builds show what this looks like in practice:
- A trades business's homepage had a 4.8 second LCP because the hero image was an uncompressed 3MB JPEG; converting it to WebP and adding a responsive
srcsetbrought it under the 2.5 second target. - A services page was duplicating near-identical content across three location variants; consolidating them into one page with location-specific sections removed the internal duplicate content conflict and let one page accumulate the ranking signal.
Pro Tip: When you inherit a site you did not build, check the hero image's file size before touching anything else. It is the single most common cause of a failing LCP.
If working through this checklist across a whole site feels like more than your week allows, our services page outlines where a built-from-scratch approach saves that time.
Balancing human writing with machine-readable structure in 2026
The trade-off most teams get wrong is treating machine readability and genuine usefulness as competing goals. They are not. A page with a sharp, answer-first opening, clean headings and real first-hand detail reads well to a person and extracts cleanly for an AI system, because both want the same thing: the point, stated clearly, without padding. The mistake is over-formatting a page that has nothing original to say, stacking bullet points and bolded terms around content that is really just a summary of what already ranks. No amount of schema markup fixes thin content.
The audit mistake I see most often is fixing the technical checklist and never asking whether the page shows real experience with the topic. Get specialist help when the gap is structural, such as Core Web Vitals that will not move no matter what you compress, or a site architecture that fights every internal linking effort you make.
— Ar
How we help you put this checklist into practice
Running all nineteen items on every page, across an entire site, takes time most small business owners do not have alongside actually running the business. We build that work into the project itself: every Webnora site is custom built from scratch, which gives us direct control over the markup, image delivery and heading structure that Core Web Vitals and structured data depend on, rather than fighting an inherited template.
Here is how our services map onto the checklist above:
- Business Websites and Personal Websites cover the full build: title tags, heading hierarchy, URLs, schema and Core Web Vitals handled from the first line of code.
- Landing Pages are built for a single intent and a single keyword, which is the checklist's own first step.
- Website Redesigns target exactly the quick wins in the audit section: image compression, script cleanup and content consolidation.
- SEO Setup covers the ongoing items: sitemap, Search Console configuration, alt text and accessibility review.
| Checklist area | Matching service |
|---|---|
| Site build and Core Web Vitals | Business Websites, Personal Websites |
| Single-intent pages | Landing Pages |
| Fixing an existing slow or duplicated site | Website Redesigns |
| Sitemap, Search Console, alt text, accessibility | SEO Setup |
New clients often express concerns about paying upfront for a site that did not deliver. We let you review and approve the finished build before any payment changes hands, which removes that risk entirely and keeps the incentive on getting the checklist right the first time. Our services page lists each option in full if you want to see where your site needs the most work.
FAQ
What is the most important item on an on-page SEO checklist?
Core Web Vitals and genuine content quality (E-E-A-T) tend to matter most, because a slow page or thin content undermines every other optimisation. The recommended Core Web Vitals thresholds are an LCP of 2.5 seconds, an INP of 200 milliseconds and a CLS of 0.1, each measured at the 75th percentile.
How is on-page SEO different from technical SEO?
On-page SEO covers what is on the page itself (titles, headings, content, internal links and images), while technical SEO covers how the site is built and crawled (site speed infrastructure, indexing rules and canonicalisation). The two overlap at items like Core Web Vitals and structured data, which sit on the page but depend on technical implementation.
How do I optimise a page for AI search and featured snippets?
Open the relevant section with a direct 40 to 60 word answer, include your target phrase in the heading and opening sentence, and follow with a short list or table. Agentic AI systems browse the web and cite sources, and clear, answer-first structure is what makes a page easy for them to extract and quote.
Do I need structured data on every page?
Not every page benefits from the same markup, but any page matching a supported type, such as an article, FAQ or how-to guide, should carry the corresponding schema. Follow Google Search Central's documented properties rather than the full schema.org vocabulary, since Google only uses a defined subset for rich results.
How often should I update an existing page for SEO?
There is no single fixed interval, but a six to twelve month review catches outdated statistics, broken links and stale examples before they erode rankings. Pages covering fast-changing topics need more frequent review than evergreen reference content.