On-Page SEO QA Worksheet for Australian Websites

Start only after one page owner, page purpose and approval owner exist. The review can cover a draft, an approved refresh or a live page being checked before a new release, but every row must refer to one intended owner URL.

This is not keyword research, not CTR diagnosis and not a whole-site audit. Use the content brief when the page purpose or query theme is still being planned. Use the CTR guide when a published page has enough search evidence to diagnose visibility and presentation. Use a technical audit when the issue affects routes, templates or site-wide systems.

Quality assurance records whether the approved page meets its acceptance conditions. It cannot forecast or guarantee crawling, indexing, search appearance, rankings, clicks or enquiries.

The intended owner should be the one maintained URL that best fulfils this page purpose. Compare it with existing service, product, category, location and resource pages before approving new copy. If another page already serves the same reader and decision, choose HOLD until ownership is resolved.

Describe the real reader and the decision the page helps them make. Check that the approved query theme reflects that need without treating every wording variation as a separate page. A useful page can support a sale, enquiry or next step without making every section promotional.

Record the actual title element, meta description, visible H1 and opening answer. They should describe one page purpose and make an accurate promise that the body can fulfil. Check the wording in context rather than assigning a pass or fail from character count alone.

Google can generate title links and snippets from several page signals. Treat the title and description as accurate preferences, not controlled advertising copy. A supplied title or description can pass page-level QA even if a later search result uses different wording.

Escalate a price, location, result, testimonial, comparison or performance claim when current evidence and necessary qualifications are missing. Do not improve apparent relevance by adding a claim the business cannot support.

Identify what this page contributes beyond a generic summary. That may be first-hand experience, a named process, approved project evidence, original analysis, a useful working file, a calculation or a clear answer based on direct responsible sources.

For every material claim, record the evidence owner, source, source date, applicable geography or sample and any qualification the reader needs. Evidence should support the impression created by the page as a whole, not only one carefully limited sentence.

The ACCC says claims about products and services must be accurate, truthful and based on reasonable grounds. Choose ESCALATE when the content owner cannot verify an important price, service area, customer result, testimonial, comparison or performance statement. Choose HOLD when the unsupported claim is essential to the page proposition.

Confirm that relevant maintained pages link into the reviewed owner and that the page links out to the next useful service, proof, resource or primary source. Use real anchors with href values and descriptive text that makes sense in its surrounding sentence.

Review images and other media for a clear purpose, suitable dimensions and useful surrounding context. Write concise alt text when an image conveys information. Use empty alt text for a purely decorative image rather than repeating nearby copy or stuffing search phrases.

Test the primary customer action on the actual draft or live surface. Record whether the form, call, email, download or next step works with keyboard and pointer input and lands in the intended destination. A working action passes functional QA, but it does not guarantee conversion.

Observe the final response, crawl access, index directive, canonical target and any applicable structured-data output for the reviewed URL. A successful response with indexable content establishes basic eligibility, not a guarantee that Google will crawl or index the page.

Structured data should describe visible, relevant content on the page. Passing validation does not guarantee a rich result. A mismatch, unsupported property or hidden claim becomes a technical handoff with an owner and acceptance test.

Do not diagnose a template or whole-site cause inside this worksheet. Link the observation to a technical finding, record the affected page and choose ESCALATE when specialist review is required before release.

Choose exactly one outcome. READY means the approved acceptance conditions are met. REVISE means page-level content or presentation needs a defined change. HOLD means ownership, evidence or a release-critical condition is unresolved. ESCALATE means the issue sits outside the content owner's authority or needs specialist review.

Record the required changes, implementation owner, approval owner, acceptance test, production-verification method, release date and review condition. READY is not complete until the production URL, approved copy, links, customer action and declared technical signals have been checked live.

Later Search Console, analytics and business outcomes belong in the reporting record. Reopen this review when the page purpose, claims, service details, important links, technical signals or customer action change. Use the separate CTR workflow only when enough published search evidence exists to support that diagnosis.