THE RESULT YOU'RE WORKING TOWARD
Done means it works.
The audit names specific changes and observable tests rather than a vague numerical SEO score.
Practice project: One published service page01 / GET READY
Before you start.
- Platform / editor
- Your website editor and Google Search Console
- Access & plan
- Permission to edit the selected site. Search Console lessons require authorized property access. Indexing and ranking changes are not guaranteed.
- Starting point
- Start in a separate demo project using fictional business information.
Keep a note of the exact account, project and version you use. Work with demo data and record the expected result before making changes. Never place passwords, verification codes or private customer records in your evidence.
02 / LEARN THE TOOL
Open the official walkthrough.
Use the publisher's instructions and available screenshots to locate the current controls. Then return here for the SETLY exercise and its result checks. These links open on the publisher's website.
Source credit belongs to the named publisher. These are external references, not SETLY recordings or a claim of affiliation. Screen names and plan availability can change.
03 / PUT IT INTO PRACTICE
Your task, step by step.
Use one labelled demo record or project so you can find your work again. Finish each action before continuing; if the screen differs, consult the matching official source rather than guessing.
- 01
Step 1
Choose one real page and record its URL, purpose and intended visitor action. Capture its current title and main heading.
- 02
Step 2
Read the content as a new customer. Note unanswered service questions, unclear next actions and unsupported claims.
- 03
Step 3
Inspect headings, images, internal links and the mobile view. Separate observed defects from ideas that need further investigation.
- 04
Step 4
Prioritize three changes by customer impact and effort, with a concrete verification test for each.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If an issue cannot be reproduced, record the conditions and uncertainty instead of presenting it as confirmed.
My screen is different from the guide
Check the product, editor, account role and selected project first. Open the credited official instructions for your version. Record the difference and pause any action whose effect you cannot verify.
The screen looks correct, but the result is missing
Inspect the saved record, published page or execution log that should prove the action. A preview, success message or draft is not always evidence that data was stored or a message was delivered. Retest with one unique demo value.
05 / PROVE THE RESULT
Check it before you call it done.
The audit names specific changes and observable tests rather than a vague numerical SEO score.
Keep useful evidence
Record the test date, project/version, expected result, observed result and a non-sensitive screenshot or record reference. Mark anything you did not test as untested. Your checkmarks do not certify an untested result.
Download the editable verification checklist ↓Guide status: original written practice exercise with credited external references. SETLY screen recording and independent learner reproduction are not yet complete.