On-Page & Technical SEO: A Checklist for Business Owners
Most business owners don’t need to do technical SEO. They need to know enough to tell whether it’s being done — and to hand their developer a clear list instead of a vague “make the site more SEO-friendly.” That’s what this guide is: the on-page and technical fundamentals in plain language, arranged as a checklist you can actually use.
We’ll start with the on-page things you can influence directly, then move to the technical layer under the hood. None of it requires code from you. All of it decides whether the rest of your SEO has a foundation to stand on.
On-page SEO: the parts you control on each page
On-page SEO is everything on a given page that helps Google understand what it’s about and helps a human decide to stay. Get these right on every important page:
The title tag. This is the clickable headline in Google’s results and the single most important on-page element. It should contain the main thing the page is about and, for a local business, the location — “Web Development Company in Jaipur,” not “Home” or “Welcome.” One page we audited literally had the title “Home”; it was targeting nothing, and ranking for nothing. Keep it under about 60 characters so it doesn’t get cut off.
The meta description. The grey text under the title in search results. It doesn’t directly affect rankings, but it decides whether people click. Write it like an ad for the page — and never leave it blank or, worse, filled with a stray fragment like “HR Manager” (a real bug we’ve found on live sites where the field pulled the wrong content).
One clear H1. The main on-page heading. Each page should have exactly one, and it should say what the page is about. A surprising number of sites either have no H1 or several fragmented ones — often because a slider or page builder splits the headline into pieces. Google reads that as confusion.
A logical heading structure. H2s for main sections, H3s for sub-points, in order. It’s how both Google and screen readers understand the shape of your content — and increasingly, how AI answer engines decide which passage to quote.
Genuinely useful content. Enough depth to actually answer the query, written for a person first. Thin pages — a couple of hundred words of filler — don’t rank and don’t convert. Depth doesn’t mean padding; it means completely answering the question someone came with.
Internal links. Links from one page of your site to another, using descriptive anchor text. They help Google find and understand your pages, and they guide visitors toward the pages that make you money. Every blog post should link to a relevant service page; every service page should link to related services.
Image basics. Descriptive file names and alt text (the text describing an image), so Google understands them and the page is accessible. Compressed file sizes, so they don’t slow the page down.
A clean URL. Short, readable, keyword-relevant — /web-development-jaipur/ beats /?p=1487. Set it once and don’t change it casually; changing URLs without redirects breaks links.
Technical SEO: the layer under the hood
This is the part your developer owns, but here’s what to check for.
Speed, and Core Web Vitals. Google measures real-world loading experience through three metrics: how fast the main content appears (LCP — target under 2.5 seconds), how quickly the page responds to interaction (INP), and how much the layout jumps around while loading (CLS). Slow sites get suppressed, especially on mobile. We’ve measured business sites taking nine seconds to show their main content on a phone — usually the culprit is a bloated theme loading dozens of stylesheets and un-compressed images. Fixes are mechanical: compress and lazy-load images, defer scripts that block rendering, cache static files. A fast server isn’t enough if the page itself is heavy.
Mobile-friendliness. Google ranks the mobile version of your site, not the desktop one. If it’s awkward on a phone, that’s the version being judged.
Crawlability. Google has to be able to find and read your pages. That means a working XML sitemap, a robots.txt that isn’t accidentally blocking important pages, and no stray “noindex” tags on pages you want ranked. It also means your server should return your pages to Google’s crawler cleanly — we’ve seen security settings accidentally block legitimate crawlers, which makes a live site look dead to Google.
HTTPS. The padlock. A basic trust and ranking requirement; non-secure sites are flagged to visitors.
Structured data (schema). Code that tells Google explicitly what your content is — a local business, a service, an article, an FAQ. It doesn’t change how your page looks to visitors, but it helps Google understand you and can earn richer search listings. Most sites either skip it or, running two SEO plugins at once, output conflicting versions — pick one source of truth.
No duplicate content. The same content on multiple URLs splits your ranking signals. Common causes: www vs non-www versions both loading, printer-friendly pages, or near-identical location pages. Canonical tags and redirects sort this out.
The checklist to hand your developer
Copy-paste this:
- Unique, descriptive title tag (with location) on every page, under 60 characters
- A written meta description on every page — no blanks, no stray fragments
- Exactly one clear H1 per page; logical H2/H3 structure below it
- Core Web Vitals in the green — LCP under 2.5s on mobile especially
- Images compressed, lazy-loaded, with alt text
- Working XML sitemap submitted to Google Search Console
- robots.txt reviewed — nothing important blocked; crawlers not firewalled
- HTTPS enforced across the whole site
- One SEO plugin only, outputting clean schema (LocalBusiness/Service/Article)
- Redirects for any old or changed URLs; one canonical version of the site
Work down that list and you’ve fixed the foundation most competitors never bother with.
Why on-page comes before link building
A quick word on order. On-page and technical work should come before you spend a rupee on links or content promotion. Links pointing at a slow, poorly-structured site are effort poured into a leaky bucket. Google can’t reward a page it struggles to read, no matter how many sites vouch for it. Fix the foundation first; everything else compounds on top of it. (If you’d rather not audit this yourself, that’s exactly what our SEO service starts with.)
Frequently asked questions
What is on-page SEO? Everything on an individual page that helps it rank and convert — title tag, meta description, headings, content, internal links, images, and URL. It’s the part of SEO you have the most direct control over.
Why is on-page SEO important? It’s how Google understands what your page is about, and it’s the foundation everything else builds on. Even the best links won’t rank a page Google can’t read or a visitor won’t stay on.
What’s the difference between on-page and technical SEO? On-page is content-level: titles, headings, copy, internal links. Technical is site-level: speed, crawlability, mobile, HTTPS, structured data. They overlap, and you need both.
How do I make an SEO-friendly URL? Keep it short, readable, and descriptive of the page — lowercase, words separated by hyphens, no random numbers or parameters. Set it once and use redirects if it ever has to change.
What are Core Web Vitals? Google’s measures of real-world page experience: loading speed (LCP), responsiveness to interaction (INP), and visual stability (CLS). Poor scores, especially on mobile, hold rankings back.
Do I need schema markup? It’s not mandatory, but it helps Google understand your content and can earn richer listings. For a local business, LocalBusiness/ProfessionalService schema with your NAP is one of the easiest wins available.
Want this foundation checked and fixed properly? Our SEO services begin with exactly this audit, and our web development team builds sites that pass these checks from day one. Get a free assessment.