On-Page SEO Checklist for Developers: Titles, Headings, Schema, Images and Technical Basics

On-page SEO is often treated as a marketing task, but most of it lives in the HTML a developer writes. Titles, headings, canonical tags, image attributes, structured data, links and rendering are all code. When they are wrong, no amount of content work will fully fix the problem. This checklist is written for developers: each item says what to do, why it matters and how to verify it, with code you can copy.

It pairs with Mobile-First Indexing: A Developer Checklist, Core Web Vitals on Mobile and the Responsive Web Design Testing Checklist. You can test layouts on real screen sizes with the Dev Browser app.

1. Title tag

The title is the strongest on-page signal you control and usually the clickable headline in search results.

  • One unique <title> per page, describing that page specifically.
  • Put the main topic first and the brand last: “Step-Up SIP Explained | Brand”.
  • Aim for roughly 50–60 characters. Display is limited by pixel width, not a fixed character count, so longer titles may be truncated. Google may also rewrite titles it considers poor.
  • Avoid keyword stuffing and the same title across templates.
<title>On-Page SEO Checklist for Developers | My Advisers</title>

2. Meta description

The meta description is not a direct ranking factor, but it often becomes the snippet and affects click-through. Write a unique summary of about 120–160 characters that matches what the page delivers. Search engines may replace it with text from the page when they think it fits the query better. The old meta keywords tag is ignored by Google, so do not spend time on it.

<meta name="description" content="A developer-focused on-page SEO checklist covering titles, headings, canonicals, schema and images.">

3. Headings and semantic structure

  • Exactly one <h1> that states the page topic.
  • Use <h2> and <h3> in logical order. Do not pick heading levels for their font size; control size with CSS.
  • Use <main>, <nav>, <article>, <header> and <footer> instead of anonymous <div> blocks. This also helps accessibility.
  • Use real <ul>, <ol> and <table> elements for lists and data.

4. URLs

  • Short, lowercase, hyphen-separated and readable: /on-page-seo-checklist-for-developers/.
  • Avoid session IDs and needless parameters. If filters create many URL variations, decide which are indexable.
  • Pick one trailing-slash convention and one host (www or non-www) and redirect the rest with a 301.
  • Do not change URLs without redirects, because you lose accumulated signals.

5. Canonical tags

A canonical link tells search engines which URL is the preferred version when the same or very similar content exists at several URLs (tracking parameters, print versions, HTTP and HTTPS).

<link rel="canonical" href="https://example.com/on-page-seo-checklist-for-developers/">
  • Use absolute URLs and make each page self-canonical by default.
  • The canonical must point to an indexable, 200-status page. Do not canonicalise to a redirect or a noindex page.
  • Treat it as a strong hint, not a command. Search engines may choose a different canonical.

6. Robots directives and indexability

Use <meta name="robots" content="noindex"> for pages that should stay out of search results (internal search results, thank-you pages). Remember the difference: robots.txt controls crawling, while noindex controls indexing. If robots.txt blocks a page, crawlers cannot see its noindex tag. Always check that staging-site noindex or password settings are not carried into production, a classic launch-day mistake.

7. Mobile viewport and responsive basics

<meta name="viewport" content="width=device-width, initial-scale=1">

Google primarily indexes the mobile version of a page, so content, links, structured data and metadata that appear on desktop must also appear on mobile. Test breakpoints with the guide on CSS breakpoints and container queries and the notes on viewport units on mobile.

8. Images

<img src="/img/hero-800.webp"
     srcset="/img/hero-400.webp 400w, /img/hero-800.webp 800w, /img/hero-1600.webp 1600w"
     sizes="(max-width: 600px) 100vw, 800px"
     width="800" height="450"
     alt="Developer testing a responsive layout on a phone"
     loading="lazy">
  • Alt text that describes the image for people who cannot see it. Leave it empty (alt="") for purely decorative images.
  • Width and height attributes to reserve space and prevent layout shift (CLS).
  • Lazy-load below-the-fold images, but not the main above-the-fold hero image, which should load promptly because it is often the Largest Contentful Paint element.
  • Use modern formats such as WebP or AVIF with a fallback where required, and descriptive file names.
  • Use real <a href> links. Crawlers do not reliably follow click handlers or onclick navigation without an href.
  • Write descriptive anchor text (“mobile-first indexing checklist”), not “click here”.
  • Make sure important pages are reachable within a few clicks from the home page, and that no valuable page is an orphan.
  • Add rel="nofollow", sponsored or ugc on paid or user-generated links as appropriate.

10. Structured data (schema.org)

Structured data helps search engines understand the page and can make it eligible for rich results. JSON-LD is the format Google recommends. The markup must match content that users can actually see.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "On-Page SEO Checklist for Developers",
  "author": { "@type": "Person", "name": "Biswajit Barman" },
  "datePublished": "2026-11-18",
  "image": "https://example.com/img/hero-1600.webp"
}
</script>

Common useful types are Article, BreadcrumbList, Organization, Product, LocalBusiness and SoftwareApplication. Note that Google has limited FAQ and HowTo rich results to a narrow set of sites, so do not add that markup expecting special results. Validate with Google’s Rich Results Test and the Schema Markup Validator.

11. Open Graph and social tags

<meta property="og:title" content="On-Page SEO Checklist for Developers">
<meta property="og:description" content="Titles, headings, canonicals, schema and images.">
<meta property="og:image" content="https://example.com/img/og.jpg">
<meta property="og:url" content="https://example.com/on-page-seo-checklist-for-developers/">
<meta name="twitter:card" content="summary_large_image">

These do not affect rankings directly, but they control how your page looks when shared, which affects clicks and links.

12. Rendering and JavaScript

Google can render JavaScript, but rendering is queued and fragile. For content that matters, serve the main text, links, title and canonical in the initial HTML through server-side rendering or static generation. Client-only apps risk delayed or missed indexing. Verify with the URL Inspection tool in Search Console and by viewing the rendered HTML. Fix runtime errors that stop rendering; see debugging JavaScript console errors on mobile.

13. Performance and Core Web Vitals

Page experience is one of many signals, and relevance still comes first, but slow pages lose users regardless. Watch LCP, INP and CLS and follow the fixes in Core Web Vitals on Mobile. Compress text with gzip or Brotli, cache static assets and avoid render-blocking scripts.

14. Status codes, redirects and sitemaps

SituationCorrect response
Page moved permanently301 redirect to the new URL
Page removed for good404 or 410
Temporary move302 or 307
Server problem503 with Retry-After
Soft 404 (error page returning 200)Fix to return a real 404

Avoid redirect chains and loops. Publish an XML sitemap that lists only canonical, indexable, 200-status URLs, reference it in robots.txt and submit it in Search Console.

15. Pre-launch quick audit

  1. Unique title and meta description on every page template.
  2. One h1, logical heading order.
  3. Self-referencing canonical on indexable pages.
  4. No stray noindex or robots.txt block from staging.
  5. Viewport tag present and mobile content parity confirmed.
  6. Images with alt, dimensions, responsive sources.
  7. Valid structured data with no errors.
  8. Redirect map for any changed URLs and sitemap updated.
  9. Key content visible in the rendered HTML.
  10. Core Web Vitals checked on a mid-range phone.

Common mistakes

  • Launching with staging noindex still on.
  • Duplicate titles generated by a template with no page-specific variable.
  • Blocking CSS or JS in robots.txt so Google cannot render the page.
  • Using images for important text.
  • Hiding content behind tabs that only load on interaction.
  • Adding schema for content that is not on the page.

Where Dev Browser fits

Many on-page problems appear only at certain screen sizes: hidden content, overflowing tables, tap targets too close together. Dev Browser lets you load a page at phone, tablet and desktop widths on your own phone, so you can confirm that the mobile view carries the same content and links as desktop. Get it on Google Play, and see the full range on the products page.

Frequently asked questions

How long should a title tag be?

Roughly 50–60 characters is a safe target, but truncation depends on pixel width. Put the key words first.

Do meta descriptions affect rankings?

Not directly, but a clear description can improve click-through rate, and search engines may rewrite it anyway.

Is one h1 per page required?

HTML allows more, but one clear h1 is a simple, safe convention that helps users and assistive technology.

Should I lazy-load every image?

No. Lazy-load images below the fold, and load the main visible image eagerly.

Does JavaScript hurt SEO?

It can if critical content depends on client-side rendering. Server-rendered or static HTML is the safest option for important pages.

Conclusion

On-page SEO is mostly disciplined HTML: clear titles, logical headings, correct canonicals, accessible images, valid schema and content that is present in the rendered page on mobile. Build these into your templates once and every new page inherits them. Run the quick audit before every launch, then check your mobile layouts in Dev Browser.

Disclaimer: Search engine behaviour changes over time and no checklist guarantees rankings. Verify current guidance in Google Search Central documentation.

Leave a Reply

Share Your Love