Start with what your site says.
Read the evidence behind your business description. Correct what is missing or misunderstood before you build on it.
How Legible works
From a live page
to a fix you can prove.
Read the evidence, confirm your business, approve the exact change, then check the published page again. One record carries the work forward.
01 · Your business record
Start with what is already true.
Legible reuses what it finds and asks you to confirm the rest. Nothing here changes your live website.
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.
Confirm the business you mean.
Bring your business facts together. Reuse the information already found, and fill in the details only you can confirm.
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.
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.
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.
02 · Review and publish
Four steps. One yes.
Read the proposal. Check the dry run. Approve the change. Read the live result. The six checks below keep each part separate and visible.
Your website connection determines which changes can be installed. Other changes come as a prepared download for your developer.
CRITICALOrganization record
Your website URL is missing.
Before
url: unknownThe fix:
url: yourcompany.comYes, publish thisUndo is free
Fixed means re-crawled.The live page is checked after publication.
Four steps. One yes.
Nothing changes until you approve it.
- 01ReviewSee the exact change.
- 02ApproveYou press yes.
- 03Dry runCheck without writing.
- 04ApplyPublish the approved change.
- 05Re-crawlRead the live page again.
- 06FixedEvidence closes the loop.
Before · a missing factAfter · found in the live source
And the loop closes. Undo is free.
01Review what we suggestSee 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.
02Approve it, on brandNothing 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.
03Watch a dry runThe 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.
04Apply it for realWritten 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.
05Publish to your platformA 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.
06Validate and reconfirmWe 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.
03 · Evidence behind the score
Each check carries its evidence.
A real saved reading, broken into separate dimensions. The score helps you scan; the finding and its source tell you what to do.
Saved redsxp.com audit · overall80/ 100
Identity98 / 100
Knowledge graph100 / 100
Metadata44 / 100
Structured data53 / 100
Claim consistency100 / 100
Semantic HTML77 / 100
AI readiness77 / 100
Content98 / 100
Template residue53 / 100
Index intent84 / 100
Validation93 / 100
Source · Saved audit dated 2026-08-15. Each score is out of 100. An unavailable check does not establish a result.
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.
Verification has its own result
Re-read the live page to check that an approved change is present. Saving the record does not establish that the website changed.
You approve your identity
The words that go into your structured record are the ones you approve. Legible proposes; you confirm or edit.
Start with your website
Start with a read. Leave with a next step.
See what your live pages say now. You decide what, if anything, changes next.