Deterministic files
Paid access can generate JSON-LD, robots.txt and llms.txt from captured page data. Unknown values use REPLACE_ placeholders. Replace those with verified information before using the files.
See the handoff options03 / Repair guide
One repair.
Then the next.
We bring one finding forward, explain it in plain language, and give you generic steps you or your developer can follow.
The repair path / illustration
01
Read the evidence
Understand the condition and the page.
02
Make a reviewed change
Use generic steps or a developer brief.
03
Check fresh evidence
Confirm only what was actually rechecked.
Try the path
Follow an example repair.
Illustration with example.com data, not a customer result.
01 / Found
Missing canonical
The example page has no canonical tag. First decide which URL should represent this content. A canonical is a preference signal, not a command to Google.
02 / Choose platform
Generic guidance
Choose how you edit the page. These are generic steps, not WordPress, Shopify, Wix, Squarespace or Webflow tutorials.
03 / Make the change
One step you can review
1. Confirm that https://example.com/ is the preferred URL.
2. Add this tag inside the page’s <head>.
3. Save and publish the change.
<link rel="canonical" href="https://example.com/">
04 / Acknowledge
“I did this” is your note
An acknowledgement records that you followed a step in this session. It is not evidence that the condition passes, and it is not durable repair history.
05 / Recheck
Read the page again
The actual guide fetches fresh evidence for one supported condition on one page. This illustration makes no scan request. Choose an outcome to see both paths.
This condition passes on the page we rechecked
Only the named condition and page are confirmed. Other affected pages still need their own evidence.
Not confirmed: the page still fails or could not be inspected
Review the current evidence. A failed fetch or an unknown result never becomes a pass.
What is available today
Practical guidance, with boundaries.
- Generic steps
- Choose a platform context, then follow generic numbered instructions. Platform-specific WordPress, Shopify, Wix, Squarespace and Webflow tutorials are not built.
- Copy buttons
- Copy the available tag, text or brief. Review the proposed change against your own page before publishing.
- Session notes
- “I did this” is an acknowledgement in the current session. It is not durable repair history or a verified pass.
- One-repair handoff
- Copy, download or print a brief with the issue, affected location, evidence and verification steps.
- Owner access
- The guide is available to the report owner. The details it can show depend on the account’s access to that report.
What this does not tell youWe never edit your website automatically. The guide does not integrate Google’s response to your change.
Two kinds of generated help
Review before publishing.
AI-written drafts
A language model can draft text for failing checks when the model feed is available. Review before publishing. Model output can be wrong and never writes to your site.
Review generated suggestions