Discourage search engines, still checked
Settings → Reading is the classic launch bug. The scan flags noindex on the homepage before Google does.
For WordPress sites
Most WordPress sites lose points in the same five places.
A theme can look finished and still be slow, set to noindex, missing a tap-to-call link, and answering on xmlrpc.php. WebFixScore reads the public site and writes the fixes as WordPress admin steps: which screen, which plugin path, what to check after.
Speed from plugins and heroes
We use Google PageSpeed when it responds, and we sample image weight. The fix is usually cache, one hero image, and fewer plugins, not a new theme.
Local pages with no local signals
No phone, no address, no LocalBusiness schema, no Maps link. That is how a contractor site loses the map pack.
What the scan looks for
- HTTPS, HSTS, and headers
- xmlrpc.php and public backups
- Titles, sitemap, and noindex
- Local schema and tap-to-call
- Mobile PageSpeed
Do you need a WordPress login?+
No. The scan is read-only and uses the public URL. You tick a box that you own the site or may test it.
Are the steps written for the editor I actually use?+
The paid report has WordPress steps, and also Wix and Squarespace steps, plus a prompt if a developer is fixing it in Cursor or a similar tool.