THE RESULT YOU'RE WORKING TOWARD
Done means it works.
The intended property is verified and the responsible owner is documented.
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
- Complete the previous lesson or use an equivalent prepared demo project.
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 the appropriate property type and confirm you are authorized to verify the site. Record the exact domain or URL scope.
- 02
Step 2
Follow Search Console's offered verification method. Get approval before changing live DNS and preserve existing unrelated records.
- 03
Step 3
Complete verification and check the property selected in the interface. Give collaborators only the access their role requires.
- 04
Step 4
Record who owns verification and how to recover access. Do not remove the verification mechanism immediately after it succeeds.
04 / GET UNSTUCK
If something goes wrong.
Start with the likely cause
If verification fails, compare the property scope and the exact record or file location; do not reuse a token from another property.
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 intended property is verified and the responsible owner is documented.
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.