Free resource / one page at a time

One-page SEO improvement checklist

Use one reader task, the page's Search Console evidence and a clear edit to improve an existing URL. The worksheet prints on one A4 page. No email is required.

Read the step-by-step guide

Start here

Pick one URL that already appears in search. Record the reader's task, Google-selected canonical and last crawl date. Look for another URL from your site appearing for the main query. Make one change and review complete, comparable periods after Google has recrawled it.

Worked example, fictional

This bookkeeping page, URLs, dates and checks are illustrative. They are not client results.

Page and reader task
example.com/bookkeeping-tools/; help a small business choose its first bookkeeping tool.
Evidence
A list of ten products lacks comparison criteria. A dated manual result review shows comparison-style pages; no measured demand is claimed.
Canonical and crawl
Illustrative check: indexed; Google-selected canonical matches the URL; last crawled 5 November 2026.
Other URL
example.com/bookkeeping-app/ also appears for the main query. Keep the guide for choosing; use the app page to explain one product.
One edit
Add sourced criteria for bank imports, team access and price basis, then a short choice guide.
Owner and follow-up
Fictional editor; edit recorded 12 November 2026. Check the next crawl and review complete periods on 11 January 2027. No outcome is claimed.

Your one-page audit

Exact URL and page type
Reader and their main task
Title, H1 and opening promise
Google-selected canonical and last crawl date
Page filter, search type, complete dates
Visible queries; impressions, CTR, position
Another site URL for the main query? Which page owns it?
Manual result check: location, device, date
Reader gap and evidence
One edit and the source or example it needs
Owner, edit date and useful internal link
Mobile, desktop, links and metadata checked?
Next Google crawl observed on
60-day review date and comparable periods
What changed? What did you observe later? What else could explain it?

Before publishing, confirm the page solves the stated task, claims have sources and the finished page works in a browser.