From your website to your next step
Make your business clear.
Then put it to work.
You know your business. Legible helps you organise the facts, find the words and review what belongs on your website. One record carries the work forward.
1 · Read
Start with what your site says.
Read the evidence behind your business description. Correct what is missing or misunderstood before you build on it.
2 · People
Put the right people behind it.
Review names, roles and the people connected to your business. Keep each person’s official profiles attached to that person.
3 · Your record
Confirm the business you mean.
Bring your business facts together. Reuse the information already found, and fill in the details only you can confirm.
4 · Three truths
Give your brand a clear idea.
Shape your category truth, buyer truth and brand truth. Get help with concise wording, then review your brand idea, search description and buyer answers.
5 · Publish
Review the changes. Choose how they go live.
Connect services, buyers, pages and profiles. Prepare your approved record, choose a supported website connection or developer download, then check the published changes.
6 · Results
See the assessment and what comes next.
Return to your business report and remaining findings. A live website check and later search or AI discovery measurements each need their own evidence.
Preparing a record does not change your live site. The Publish page shows the installation options for your platform. Changes outside those options need a separate website edit.
Resolution
Green only after we
re-crawl and prove it.
Follow a supported change from review to installation, then check the published page. The sequence below illustrates those separate steps; it is not a completed installation for your site.
Review what we suggest
See the exact change before anything moves.
Review the existing business record beside the proposed value. In this illustration, the saved audit found an Organization record with no website URL. Confirm the correct URL before installing it.
Approve it, on brand
Nothing is applied without you.
The engine proposes; you decide. Edit the wording, approve it as drafted, or reject it outright. There is no autopilot and no bulk-apply, because a machine writing your identity unread is the failure this product exists to prevent.
Watch a dry run
The whole thing, with nothing written.
For supported changes, a dry run checks the proposed values and destination before applying them. Review the result and any blocked items. The available installation and rollback steps depend on the change and the connected platform.
Apply it for real
Written to your platform through a real adapter.
Your connected platform determines which changes can be applied. Framer and Webflow support selected fields and installation methods. For other changes, download the prepared code and instructions for your developer.
Publish to your platform
A separate, deliberate step.
Applying and publishing are kept apart on purpose. A change can sit staged while you look at it in context, and going live stays an act you perform rather than a side effect of approving something.
Validate and reconfirm
We re-crawl the live site and check.
The engine fetches your published page again and looks for the change in the delivered HTML. Present, and the finding turns green. Absent — a cache, a failed deploy, a theme that stripped it — and it stays open and tells you why.
What the live check needs to confirm.
Before · recorded in the saved audit
Organization markup is missing its website URL.
The saved audit dated 15 August found this on 58 pages of redsxp.com.
Proposed · installation not demonstrated here
Organization website URL: https://redsxp.com
After installation, fetch the live page and check that its Organization record contains the approved URL.
The missing URL is a finding from the saved audit. The proposed value and walkthrough illustrate the next steps; they are not evidence of a completed installation or a search result.
Why you can check us
Your changes should be checkable.From the source to the live page.
Every finding carries its evidence
Open the affected page and inspect the supporting evidence. Findings give you a place to start and a way to check the proposed fix.
Service markup: missing providerFixed means re-crawled, not ticked
Installation and verification have separate results. Re-read the live page to check that an approved change is present; saving the record is not that check.
We never invent your identity
The words that go into your schema are the ones you approve. The engine proposes and shows its reasoning; you confirm or edit.
Choose your installation route
Saved audit example: redsxp.com · 58 pages · 39 findings, each with evidence
Need some help?
Write to hello@sensate.design and one of us replies — usually the same day, always a person.