Before Publishing Another Page, Check the One You Already Have

On-page SEO is the fastest SEO win because everything on it is under your control. You do not need to wait for links or for other sites. You only need to fix the page. This checklist covers twelve changes, grouped into four areas, and each has a one-line action. If you want the work done across your whole site, our AI SEO service includes an on-page review.

Content and keywords

1. Target one clear topic per page

Why it matters: pages that try to rank for everything rank for nothing. Fix: write down the single search each page should answer, and remove sections that drift.

2. Match the search intent

Why it matters: if people want a how-to and you offer a sales page, they leave. Fix: look at what currently ranks and format your page the same way, then do it better.

3. Put the keyword where it counts

Why it matters: clear placement helps search engines understand the page. Fix: include the main keyword naturally in the title, H1, first paragraph and URL.

Technical on-page

4. Write unique title tags

Why it matters: the title is the first thing searchers read. Fix: keep it specific, lead with the topic and make each page's title different.

5. Write meta descriptions that earn clicks

Why it matters: they do not set rankings but they influence whether people click. Fix: summarise the benefit in about 150 to 160 characters and end with a reason to visit.

6. Use a clean heading structure

Why it matters: headings let readers and crawlers scan the page. Fix: one H1, then H2s for main sections and H3s for detail, without skipping levels.

7. Use short, descriptive URLs

Why it matters: readable URLs are easier to understand and share. Fix: use lowercase words separated by hyphens, such as /services/seo, and avoid long strings of parameters.

Internal linking

8. Link to related pages with descriptive anchor text

Why it matters: internal links pass authority and help crawlers find pages. Fix: add two or three links per page using words that describe the destination, never "click here".

9. Link your key pages from your blog posts

Why it matters: your most important pages need the most internal support. Fix: from every article, link to the matching service page in the first few paragraphs.

User experience signals

10. Optimise images

Why it matters: heavy images slow pages, and missing alt text wastes a relevance signal. Fix: compress files, use modern formats and add alt text that describes the image.

11. Improve page speed

Why it matters: slow pages lose visitors before they read a word. Fix: test with PageSpeed Insights, then compress images, remove unused scripts and avoid heavy layout shifts.

12. Make the page work on mobile

Why it matters: most searches happen on phones. Fix: open the page on a real phone, check that text is readable, buttons are tappable and nothing overlaps.

A worked example: fixing one page

Suppose your "Web design for dentists" page has the title "Services | Company Name", three H1s, no internal links and a 4 MB hero image. Here is the fix, in order:

1. Rewrite the title: "Web Design for Dentists | Company Name".
2. Keep one H1 that says what the page is about.
3. Reorganise the sections under clear H2s: process, pricing approach, examples, FAQs.
4. Add links to two related pages and one case study.
5. Compress the hero image and add alt text.
6. Rewrite the meta description around the benefit.

That takes under an hour and often improves both rankings and conversions.

Mistakes that undo good on-page work

• Changing URLs without redirects, which breaks existing links.
• Writing titles for search engines only, so they read badly.
• Hiding important text in images that crawlers cannot read.
• Updating the page and forgetting to update the sitemap and internal links.
• Stuffing the keyword into every sentence, which makes the copy harder to read and does not help rankings.

A quick self-review before you publish

Read the page once as a stranger who arrived from Google, and answer these questions honestly:

1. Within five seconds, is it obvious what the page is about and who it is for?
2. Does the first screen contain the answer, or at least a clear promise of it?
3. Is there a next step, such as a related guide, a contact form or a service page?
4. Would you trust the page if you had never heard of the company, given the authorship, dates and examples shown?
5. Does it load without jumping around when opened on a mid-range phone?

If any answer is "no", fix that before you worry about fine-tuning the keyword. Pages that fail the stranger test rarely hold their rankings even if the tags are perfect.

How to prioritise

If you have dozens of pages, start with the ones closest to revenue, then pages already ranking on the second page of results, since small improvements there often bring the biggest jump. A simple scoring method helps: give each page one point for each of these that applies, being close to revenue, already getting impressions, outdated, or missing basics from this list. Work on the highest scores first and leave the rest for the next round.

How to measure whether the fixes worked

On-page changes are easy to make and easy to forget. Before you edit a page, note its current clicks, impressions and average position in Google Search Console for the last 28 days. After the changes, wait four to six weeks and compare the same period. Google needs time to recrawl, so judging after a few days will mislead you. Keep a simple log with the date, the page and what you changed, so you can tell which edits helped and repeat them elsewhere.

How to use this checklist

Do not try to fix every page at once. Start with the five pages that matter most to revenue: your homepage, main service pages and best-performing posts. Work through the list, then re-check Google Search Console after a few weeks to see what changed.

If you would rather hand it over, get a free SEO audit and we will list the fixes in priority order. For the technical side, read technical SEO for startups.

Information Gain

Record the problem, changed elements and intended reader benefit before applying the checklist. Review the combined change against that problem. If several elements changed together, report the result as evidence about the package, without attributing it to one title or heading alone.