On Page SEO Checklist: 13 Checks for Search, AI, and Core Web Vitals

This checklist gives you a practical, ordered set of tasks to optimize a single page for search and AI discovery: metadata, headings, URLs, content, images, links, schema, and Core Web Vitals. Before touching any of it, confirm the page’s target keyword and the search intent behind it. The same sequence works whether you are building a new page or auditing one that already ranks.

TL;DR:

• Keep titles under roughly 60 characters, lead with the primary query, align each title’s meaning with its single H1, and write a unique meta description.
• Add information competitors lack and answer the main query in the opening paragraph; repeated keywords cannot replace useful, specific content.
• Meet the Core Web Vitals targets: LCP at 2.5 seconds or less, INP at 200 milliseconds or less, and CLS at 0.1 or less.
• If a ranked URL must change, use a direct 301 redirect from its old address to the new one, then check for redirect chains.
• Prioritize accidental noindex directives and mobile usability failures, because either can remove a page from search results; check both after redesigns or migrations.

Snapshot Checklist: What to Fix First on Any Page

Run through these items in order. Each one includes why it matters and a quick way to check whether you passed.

1. Keyword and intent: confirm the page targets one primary query and matches what searchers expect to find. Pass/fail: does the page answer the query in the first paragraph?
2. Title tag: include the primary keyword near the front. Pass/fail: is it under roughly 60 characters?
3. Meta description: write a unique summary for the page. Pass/fail: no two pages share the same description.
4. H1: one per page, matching the title’s intent. Pass/fail: exactly one H1 in the rendered HTML.
5. Heading hierarchy: H2s and H3s break up sections logically. Pass/fail: no skipped levels (H1 to H3 with no H2).
6. Body content: covers the topic with specifics, not filler. Pass/fail: would a reader learn something new in the first 100 words?
7. URL slug: short and descriptive. Pass/fail: no session IDs, dates, or random strings.
8. Images: descriptive filenames and alt text. Pass/fail: no “IMG_2031.jpg” in production.
9. Internal links: relevant anchors pointing to related pages. Pass/fail: at least two contextual links per 1,000 words.
10. Structured data: schema matches visible content. Pass/fail: validates in the Rich Results Test.
11. Core Web Vitals: LCP, INP, and CLS within target. Pass/fail: green in PageSpeed Insights.
12. Mobile usability: no overlapping elements or tiny tap targets. Pass/fail: passes Google’s mobile-friendly test.
13. Indexing: no accidental noindex or robots.txt block. Pass/fail: page shows as indexed in Search Console.

• Treat items 1 through 4 as the fastest wins; they take minutes per page.
• Treat items 10 through 13 as technical checks worth batching across the whole site.

Getting Title Tags and Meta Descriptions Right

The title tag is still the single most direct lever you control for a page’s search appearance. Google’s own SEO Starter Guide recommends descriptive, specific titles and notes that titles are commonly kept under roughly 60 characters because longer ones risk truncation in results. Put your primary keyword early in the tag, write it the way a person would actually search, and skip the boilerplate.

A few rules that hold up across most pages:

• Lead with the keyword or core topic, not the brand name.
• Keep the brand name at the end, and only when there is room for it.
• Write a different title for every page; duplicate titles blur which page Google shows for a query.
• Avoid stuffing the same word twice just to “cover” variants.

Google’s guidance on influencing title links adds a detail many checklists skip: the visible on-page title (your H1 or main heading) also factors into what Google displays as the clickable title link. If your H1 reads completely differently from your title tag, you lose some control over how your page shows up. Keep the two aligned in meaning, even if the wording is not identical word for word.

Meta descriptions do not influence ranking directly, but Google’s documentation on how Search generates snippets confirms that a well-written, unique meta description is sometimes used as the snippet when it describes the page better than the surrounding content would. Write one per page. Summarize the actual value of the page in plain language, include the primary keyword naturally, and stop trying to cram in every secondary keyword you can think of.

Pro Tip: Open an incognito window and search your own page title to see exactly how Google renders it today; titles get rewritten more often than most site owners realize.

For QA, pull up Google Search Console’s Performance report filtered by page, and compare impressions against click-through rate. A page with high impressions and low clicks usually has a weak or mismatched title or description, even if rankings look fine.

A page without a unique meta description risks Google auto-generating a snippet from body text that may not represent the page’s main value, which can quietly depress click-through rate on otherwise well-ranked pages.

One H1, Clear Subheads, and Content That Actually Says Something New

Every page needs exactly one H1, and it should match the intent behind your title tag and target query. If your title promises “a checklist,” your H1 should not pivot to “why SEO matters,” because that mismatch confuses both readers and crawlers trying to confirm relevance.

From there, headings exist to help a reader skim and find the part they need. Use H2s for main sections and H3s for sub-points inside them, and never skip a level just because a smaller heading looks tidier in your CMS. A page with ten H2s and no H3s is usually a page that needs tighter grouping, not more headings.

Content quality is where most on-page checklists get vague, so get specific:

• Does the page say something a competing page does not already say? That is information gain, and its absence is the most common reason a well-optimized page still underperforms.
• Are claims backed by a specific example, number, or named source rather than a vague assertion?
• Does the first paragraph answer the main question, or does it warm up with throat-clearing before getting to the point?
• Are keyword variants and related terms (what some call LSI terms) woven in naturally, the way a subject-matter expert would actually phrase things, rather than mechanically repeated?

Industry guidance on on-page SEO for 2026 frames a newer layer on top of the traditional checklist: pages increasingly need to be readable by AI systems and agents, not just by human visitors and crawlers. That means semantic HTML (using actual <h2>, <ul>, and <article> tags instead of styled <div> soup), clear author attribution, and visible expertise signals. These are the practical ingredients of what is commonly called E-E-A-T: experience, expertise, authoritativeness, and trust, expressed through real bylines, clear sourcing, and content that reads like it was written by someone who has actually done the thing.

Pro Tip: Read your page out loud. If you stumble over a sentence or lose the thread, an AI summarization system will likely struggle with that same passage too.

Over-optimization still happens, even now. If your primary keyword appears in every single heading and every other sentence, dial it back. Write for the person asking the question first, and let keyword variants fall into place naturally as you explain the topic in full.

Clean URLs and Internal Links That Actually Help Navigation

A URL slug should tell a person (and a crawler) what the page is about before they even click. Keep it short, use hyphens between words, include the primary keyword when it fits naturally, and skip dates unless the content is genuinely time-bound, like a yearly report.

1. Write descriptive slugs: /on-page-seo-checklist beats /post-4471 or /blog/2026/09/article-title-here.
2. Avoid changing URLs casually: once a page ranks, a URL change risks losing that equity unless handled correctly.
3. Use a 301 redirect from the old URL to the new one whenever a slug must change, and verify the redirect resolves directly without chaining through two or three hops.
4. Apply rel=canonical when similar content exists at multiple URLs (common with filtered or parameterized pages), pointing search engines to the version you want indexed.
5. Audit internal links quarterly: look for orphan pages with zero internal links pointing to them, broken links returning 404s, and redirect chains that slow crawling.

For internal linking itself, anchor text should describe the destination page, not just say “click here” or “learn more.” Link to genuinely related content where it helps the reader go deeper, and resist the urge to repeat the same five links in every blog post footer. A tool like Screaming Frog will surface orphan pages and redirect chains in minutes, and Siteimprove’s guidance on technical SEO during migrations points out that leftover noindex tags and broken redirect chains are among the most common things to break after a URL or site structure change, so a post-launch crawl is worth the time every single time.

Images and Media: Small Files, Clear Descriptions

Images carry more SEO weight than most checklists give them credit for, and they are often the easiest wins on a page.

• Name image files descriptively before upload: blue-lake-website-redesign-before-after.jpg tells Google (and you, six months later) far more than DSC_0294.jpg.
• Write alt text that describes what the image actually shows and how it relates to the surrounding content, following Google’s own guidance on image placement and alt text.
• Compress images before upload and serve responsive sizes using srcset, so a phone is not downloading a desktop-sized hero image. This is one of the most reliable levers for improving LCP, the Core Web Vitals metric most sensitive to large above-the-fold media.
• Use WebP where your platform supports it, lazy-load images below the fold, and never autoplay video with sound.
• Add captions and a transcript for video content; it helps accessibility and gives crawlers text to index that the video itself cannot provide.

Further detail on naming conventions and alt text structure is available from WSU’s guidance on SEO alt text and file naming, which breaks down how to write alt text that serves both accessibility and search.

Pro Tip: If an image is purely decorative and adds no information, give it an empty alt attribute (alt="") rather than stuffing it with keywords it has no relevance to.

Structured Data: What to Add and How to Validate It

Structured data will not rewrite your rankings on its own, but it gives search engines a clearer map of what is on the page, and it can unlock rich results that take up more visual space in the results. Google’s documentation on structured data recommends JSON-LD as the preferred format and is explicit that markup should describe content actually visible on the page, never information a visitor cannot see.

For most content pages, a short list covers the common cases:

• Use Article schema for blog posts and guides.
• Use BreadcrumbList schema when your site has a clear navigation hierarchy.
• Use FAQPage schema only when the page contains an actual visible FAQ section.
• Skip schema types that do not match your content type; irrelevant markup adds risk without adding benefit.

Validate every implementation with the Rich Results Test before publishing, then monitor the Enhancements reports in Search Console afterward. Google’s own guidance suggests running a before and after comparison on a sample of pages and watching the Performance report to judge whether a structured data change actually moved the needle, rather than assuming it worked.

Core Web Vitals, Mobile Readiness, and Avoiding Indexing Mistakes

Page experience signals round out the technical side of on-page SEO, and they are measured, not guessed at. Core Web Vitals set specific thresholds at the 75th percentile of real user visits: Largest Contentful Paint (LCP) within 2.5 seconds, Interaction to Next Paint (INP) at 200 milliseconds or less, and Cumulative Layout Shift (CLS) at 0.1 or less. These three numbers function less like raw speed scores and more like user experience benchmarks: they measure whether a page feels fast, stable, and responsive to an actual visitor.

• Test with PageSpeed Insights for both lab and field data, and cross-check with the Core Web Vitals report in Search Console for real-world numbers across your whole site.
• Run Lighthouse audits in Chrome DevTools for a deeper breakdown of exactly what is slowing a specific page down.
• Confirm mobile usability separately; a page can pass Core Web Vitals and still have tap targets too small or text too tiny to read on a phone.
• Check robots.txt and page-level meta tags for accidental noindex or disallow directives, which are a common and costly mistake after a redesign or migration.

Pro Tip: Fix layout shift before chasing load speed. A page that loads fast but jumps around as ads and images pop in will frustrate visitors and still fail CLS.

When a page fails multiple checks, prioritize by impact. Fixing a render-blocking script or an oversized hero image usually moves LCP the most for the least effort, so start there. INP issues, often caused by heavy JavaScript execution, tend to need more engineering time. For a deeper walkthrough of server-side and caching fixes, this practical hosting and speed guide covers caching, CDN setup, and server-level changes that complement the front-end fixes covered here. Mobile usability problems and accidental noindex tags should jump to the front of the queue regardless of effort, since either one can remove a page from search results entirely.

A Repeatable Audit Workflow You Can Run on Any Page

Work through the checklist in the same order every time, so nothing gets skipped under deadline pressure.

1. Confirm intent and keyword before changing anything else; every other fix depends on this being right.
2. Fix metadata: title tag and meta description.
3. Fix structure: H1, heading hierarchy, and content gaps.
4. Fix images: filenames, alt text, and compression.
5. Add or validate schema where it genuinely applies.
6. Check speed and mobile UX using PageSpeed Insights and Search Console’s field data.
7. Review internal links pointing to and from the page.
8. Confirm indexing status in Search Console after publishing changes.

For tooling, Google Search Console and PageSpeed Insights cover most of the technical checks for free. A crawler such as Screaming Frog finds broken links, orphan pages, and duplicate titles across an entire site in one pass. The Rich Results Test validates structured data before it goes live. Keep a simple content editor checklist (a shared document or spreadsheet) so writers apply the same metadata and heading rules before a page is ever published, rather than fixing it after the fact.

Prioritize by impact versus effort: metadata and alt text fixes take minutes and often show up in Search Console within weeks. Core Web Vitals and schema fixes take longer but tend to affect every page on a template at once. Measure success through the Performance report (impressions, clicks, average position) and the Core Web Vitals report, checked monthly rather than daily, since search data is noisy in short windows.

Real-World Application Notes From Blue Lake Web Design

We apply this exact sequence on every site we build, because the order matters as much as the individual tasks. Blue Lake Web Design is a web design and SEO agency based in Michigan, and we built our process around delivering affordable, lead-generating websites that combine fast-loading, visually appealing design with SEO built in from the start, rather than bolted on afterward.

• We typically deliver a completed, operational website relatively quickly, without locking clients into long-term contracts.
• Every project comes with a pricing quote up front, so there are no surprise fees once the build is underway.
• We build on modern frameworks and techniques aimed at helping businesses, from new startups to established companies, turn more site visitors into paying customers.

The checklist above is not theoretical for us. It is the same sequence our team runs on every page we launch, adjusted for the specific industry and goals of each client.

When to Handle This Yourself and When to Bring in Help

Some items on this checklist take five minutes and no special skill: writing a unique meta description, naming an image file correctly, or fixing a missing H1. Any site owner can knock those out in an afternoon with a simple spreadsheet and a bit of discipline.

Others sit on the other end of the spectrum. Diagnosing an INP problem buried in third-party JavaScript, structuring Article and BreadcrumbList schema correctly across a templated site, or rebuilding a page’s information architecture to fix chronic layout shift all require a level of technical fluency most business owners have not built up, and understandably so; running the business itself is a full-time job.

The honest framework is this: handle the low-skill, high-frequency items yourself as part of routine publishing. Bring in outside help when the fix touches site-wide templates, performance engineering, or structured data at scale, or when the cost of getting it wrong (a page accidentally deindexed, a migration that tanks rankings for a month) outweighs the cost of paying someone who does this daily. Speed of needed results matters too: a checklist run solo might take a small business owner a month of evenings, while a team that does this full time can usually clear the same list in days.

For readers who want this checklist implemented rather than self-managed, a done-for-you build is often the faster path, and it is the kind of work we focus on.

— Eric

How We Can Put This Checklist to Work on Your Site

Running this entire checklist yourself takes real time, and getting the technical parts wrong (schema, Core Web Vitals, indexing) can cost you more than it saves. We handle the full list for you, built into the site from day one rather than patched on after launch.

Our services map directly to what this checklist covers:

• Web Design and Website redesign for a new or rebuilt site with on-page SEO structured in from the start.
• Search Engine Optimization for ongoing metadata, content, and technical maintenance after launch.
• Local SEO and Google Maps for business pages that depend on local search visibility.
• Google Ads and Facebook Ads for paid traffic alongside organic improvements.
• Content Creation for pages that need the information gain this checklist calls for.

Every project comes with a pricing quote and typically launches relatively quickly, with no long-term contract attached. If you want a site built with this checklist already applied, check our website design pricing to see current packages and get started.

FAQ

What does on-page SEO include?

On-page SEO covers everything you control directly on a page: title tags, meta descriptions, heading structure, URL slugs, body content, images, internal links, and structured data. It also includes technical factors tied to the page itself, like Core Web Vitals and mobile usability, as outlined in Google’s own SEO Starter Guide.

How do I do proper on-page SEO?

Start by confirming the page’s target keyword and the intent behind it, then work through metadata, headings, and content before moving to technical checks like images, schema, and Core Web Vitals. Following a consistent order, rather than fixing items at random, catches gaps that a scattered approach tends to miss.

What are the three most important factors for on-page SEO?

Title tags, content that genuinely answers the search intent, and page experience signals like Core Web Vitals tend to carry the most weight. A title tag under roughly 60 characters helps avoid truncation, while Core Web Vitals targets of 2.5 seconds for LCP, 200 milliseconds for INP, and 0.1 for CLS cover the technical side.

How long does it take to see results from on-page SEO changes?

Metadata and content changes can show up in Search Console within a few weeks, though full ranking shifts often take longer depending on competition and how often the page gets recrawled. Technical fixes like Core Web Vitals improvements tend to show measurable change in field data within four to six weeks as more real users are sampled.

Sources

• Search Engine Optimization (SEO) Starter Guide — Google Search Central
• Web
• Intro to structured data — Google Search Central