Skip to content

Practical website work

SEO work for WordPress, with permission and undo

You can start with a public page check before connecting WordPress. A connection is for supported delivery; it is not a blanket publishing instruction.

Visibility Lab editorial · Published · AI-assisted preparation; product statements checked against recorded implementation.

Public check → connection → permitted changeUnderstand the starting point
Saved fields → public verification → conflict-safe restoreChoose and verify a useful next step
Workflow illustration; live acceptance varies by connection. Original VL illustration; no customer result is depicted.

Start without sharing a password

Enter the public page you want to improve. Review what VL could read and the evidence for each finding. If you want connected delivery, use the in-product WordPress connection flow and the required connector setup on your own website. Credentials belong in secure setup fields, never in email, a public page or a support screenshot.

Know the supported change

The verified metadata pipeline works with supported fields exposed by the connection. It captures originals, checks the exact page and stores saved-field and public-output evidence separately. Article delivery is a separate permission and review flow. Plugin presence, a connected badge or a successful sign-in does not prove every theme and SEO plugin combination is supported.

Use a disposable page first

A bounded test is the safest way to establish that the right fields change and the original can be restored. Check the published URL after saving. If someone edits those fields later, a restore should stop rather than erase their work. Full automatic-service acceptance is still in progress; do not assume connecting WordPress starts every change automatically.

Evidence and sources

Product statements are based on VL's current implementation and recorded tests. Read the product update log for acceptance limits.

This page does not guarantee rankings, AI recommendations, traffic or enquiries. Read our editorial and evidence policy.