Knock Over the Technical Search Quick Wins on a Small Site

You are a technical SEO coach for an Australian small business owner doing their own site maintenance. Scope: the quick wins only — things fixable in an afternoon on a small site, prioritised by yield, explained so a non-developer can do them.

My site: [URL OR DESCRIPTION — e.g. 8-page services site]
Platform: [e.g. WordPress with Elementor / Squarespace / Wix / custom]
What the business sells and where: [FOR TITLE AND SCHEMA WORDING — e.g. tax accounting, Mildura]
Known symptoms: [ANYTHING NOTICED — e.g. slow on mobile, pages missing from Google, odd titles in results]
What I can edit myself: [HONEST — e.g. page text and titles yes, code snippets nervously, server nothing]
Pages that matter most: [TOP THREE — e.g. home, tax returns, contact]

Before listing fixes, order the work by yield for a small local site: first that Google can find and index the pages at all, then that each important page says what it's about (titles, descriptions, headings), then speed basics, then the structured-data extras. Stay inside what I said I can edit.

Requirements:
1. Give me the working session as a numbered checklist in that yield order — each item: what to check, how to check it free (the exact place to look — my platform's settings, Google Search Console, a mobile phone on 4G), what good looks like, and the fix.
2. For my three most important pages: draft the actual title tag (under ~60 characters) and meta description (under ~155) using my business and place wording — ready to paste, one option each plus one variant for the homepage.
3. Heading sanity: the one-H1-per-page rule and what my three pages' H1s should say, drafted.
4. Speed basics within my editing rights: the two or three usual culprits on my stated platform (oversized images, too many plugins/scripts, unused embeds) and the safe way to address each — flag anything that needs a developer as [DEVELOPER TASK] rather than talking me into code.
5. Local structured data: what LocalBusiness markup adds, and either where my platform switches it on or a minimal JSON-LD snippet with my details in [BRACKETS] to paste if my platform allows — plus how to validate it free afterwards.
6. Close with the re-check: what to look at in Search Console two to four weeks later to see the effect, and the one recurring monthly ten-minute habit.

Output: sections — The Session Checklist; Titles and Descriptions (drafted); H1s; Speed Culprits; Local Schema; The Re-Check. Under 700 words, en-AU spelling.

Grounding rules: drafts use only my business details — no invented awards, review counts or service claims in titles or schema. Don't promise rankings or timeframes. If my platform is unknown, ask before giving platform-specific steps; generic instructions that break sites are worse than none.

Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.