On-page SEO checklist to boost rankings and UX

What you’ll get from this checklist

This checklist gives concise, actionable on-page SEO tasks you can run immediately: technical checks that affect crawling and indexing, content and metadata best practices, internal-link structure, performance and Core Web Vitals, and a verification/troubleshooting section with exact tools and commands.

How to think about on-page SEO (crawl, index, rank)

Separate three phases when you evaluate a page: crawling (discovery and fetch), indexing (what Google stores about the page) and ranking (how results are ordered). Fixes at the crawl/index stage make content available for ranking signals, but they do not automatically change rank. Since July 2024, Google crawls sites for Search with Googlebot Smartphone by default — treat the mobile view as the primary source for what Google sees.

Core technical checks

Run these checks first. They address visibility and basic site health.

• Robots and meta robots: ensure pages you want indexed allow crawling and indexing. Look for missing or conflicting directives in your HTML <meta name="robots"> and in your server-side X-Robots-Tag headers.
• Canonical tags: use a single rel="canonical" pointing to the preferred URL and verify it’s self-consistent across mobile and desktop versions; canonical conflicts can prevent indexing.
• Sitemap: include canonical URLs only and make sure your XML sitemap is referenced from robots.txt. For large sites, split sitemaps according to the sitemap protocol.
• Mobile rendering: test representative pages with the Google Search Console URL Inspection tool and with a smartphone user-agent to confirm mobile HTML equals the content you want indexed.
• HTTP status and redirects: ensure canonical and important pages return 200 and that redirects are 301 (or 302 where appropriate). Avoid redirect chains.

Content and on-page elements

Content quality and structure remain central. These items improve both user experience and the signals search engines observe.

• Title tags: write unique, descriptive titles for each page that reflect the page’s topic and primary search intent.
• Meta descriptions: craft helpful summaries that accurately describe the page; they don’t directly determine rank but affect click-through rates.
• Headings and content hierarchy: use H2/H3 to reflect logical sections. Keep content scannable with short paragraphs, lists and clear subheads.
• Unique, useful content: focus on content that answers user intent and provides value beyond thin or duplicated material. Avoid copying large blocks from other pages.
• Images and alt text: compress images, use responsive srcset where helpful, and add concise alt text that describes the image function or content.

Internal linking and URL structure

Internal links help users and help search engines discover and prioritize pages. Treat internal links as editorial signals and keep anchor text descriptive and relevant.

• Flatten deep pages where appropriate by adding contextual internal links from relevant hubs to important posts.
• Consistent URLs: use readable, stable URLs and avoid query strings for canonical content when possible.

UX, performance and Core Web Vitals

Performance affects engagement and can influence how search engines interpret a page’s value. Treat Core Web Vitals as user-focused KPIs: LCP (loading), INP (interaction), CLS (visual stability).

• Server and hosting: if resources are constrained, move to a plan or provider that matches your traffic and application needs. Shared hosts can cause noisy-neighbor problems; managed platforms can reduce operational overhead.
• Asset optimization: use modern image formats where applicable, enable text compression, and implement critical CSS/async JS strategies to reduce blocking time.
• Caching and CDN: leverage CDNs for geographically distributed delivery and tune cache headers for static assets.

Outgoing links, rel attributes and paid placements

Use rel attributes to clarify link intent. There is no rel="dofollow" attribute — a normal link is simply a link without rel=nofollow, rel=sponsored or rel=ugc. For paid or sponsored links include rel="sponsored"; for user-generated links use rel="ugc"; to flag a link as a hint to search engines use rel="nofollow".

Inline examples: a standard link without a special rel value: example. For sponsored content: example. For user-generated links: example.

Google’s linkspam policy applies when links are used primarily to manipulate rankings. Paid placements should use rel="sponsored" or rel="nofollow" and the editorial context, indexability and publisher quality determine the placement’s SEO value.

Verification and troubleshooting (tools and commands)

Use the following tools and commands to verify how pages render and how search engines see them. For pages you own, Google Search Console’s URL Inspection is authoritative for inspection and live testing.

• Fetch headers only (quick status): curl -I https://example.com/page — this returns response headers without the body.
• Fetch HTML as a smartphone UA: curl -A "Mozilla/5.0 (Linux; Android)" https://example.com/page — use this to compare mobile vs desktop HTML when testing mobile-first rendering.
• Rendered DOM checks: open the page in Chrome, use DevTools Elements and Network panels to confirm that critical content isn’t injected later by JS and that resources return 200. Lighthouse in DevTools helps surface performance issues and Core Web Vitals.
• Rich Results Test and Schema: validate structured data with the Rich Results Test and the Schema Markup Validator at schema.org for correctness and eligibility.

Indexation checks from the outside: the site: operator can indicate whether Google is surfacing pages publicly, but it is not definitive. For owned pages, prefer URL Inspection in Search Console for authoritative indexation and coverage details.

Quick audit checklist (run this on a sample of pages)

• Confirm HTTP status, canonical and robots directives.
• Check that mobile HTML contains the same primary content you want indexed.
• Validate title, meta description and heading structure.
• Run Lighthouse for performance and inspect LCP/INP/CLS metrics.
• Check structured data with the Rich Results Test.

When to escalate to engineering or product

If fixes require server configuration, canonical logic changes, or major frontend refactors (rendering changes, critical CSS, or client-side rendering issues), involve engineering. Prioritize based on pages that drive business traffic and conversions.

Read the Technical SEO Guide

FAQ