First Explorer scan

What you see

• Empty project — you need a quick health check before a meeting.
• Client sent a domain without WP access.
• Explorer returns score 0–100, grade A–F, and a findings list.
• Some items may be blurred until unlock — on the first scan everything is visible (free).

Why it happens

Explorer is the door into the Puluno family — not a full-site audit. It typically checks homepage (optional sitemap sample).

By design:

• fast technical signal (robots, canonical, CWV hints, OG)
• same finding codes as Center
• path to the plugin when the site is WordPress

It is not Ahrefs — no backlinks or keyword volume.

What Puluno does

Output	Meaning
Score + grade	orientation, not a contract KPI
Coded findings	map to Guide and Apply packs
Action plan (max 5)	same logic as Today in Center
Shared report	/pruzkumnik/r/id for the client

WordPress: after installing the plugin, Center continues on the full site (products, posts).

Step by step

1. Open Explorer — enter the domain; use the client’s canonical host (www vs non-www).
2. Wait for completion — timeout may mean hosting blocks the scan.
3. Read Do this today (max 5 steps) — not the full list at once.
4. For findings with Guide →, open the playbook.
5. If WordPress: Download plugin → Center for Apply.
6. After first fixes: Apply → Verify → rescan.
7. Optional: connect GSC (docs) — not required for the first scan.

Rollback — undo the change

The first scan changes nothing — no rollback.

After Apply in the plugin, use Verify and per-module rollback.

When it is not Puluno

• You need a 500-URL audit — Explorer Pro / Center crawl, not one free scan.
• SPA without JS render — default scan may miss rendered React; use Lab + JS render (credits).
• Client wants a ranking guarantee — Explorer shows technical health, not a commercial promise.