Find the next useful step when something breaks

Check the signed-in account first. A site can belong to another account, require collaborator access, or be in Archive.

A visible feature can also require a specific role or the owner's paid plan. Editors do not have Email or Environment variables access.

1. Check the account email in Settings.
2. Check the site's collaborator role.
3. Check Archive for a retired site.
4. Open Usage in the owner's account for plan limits.

• Permissions matrix

Keep the editor open until the save state is clear. A local preview or browser-held post draft is not proof of a server save.

1. Read the save or conflict message.
2. Check the connection and resolve the named source or field error.
3. If another version changed, preserve needed text before following Reload latest.
4. Retry the save and wait for confirmation.
5. Use Help if the same error remains.

Do not close a tab that says the browser cannot keep a copy of unsaved changes.

Check whether the edit was saved, whether Publish succeeded, and which build has the Live marker.

Also check the address. A different site or an old domain can make a correct publish look missing.

1. Confirm the latest save.
2. Check History → publishes or Hosting → Deployments.
3. Open the live address from the site menu.
4. Check the affected page in a fresh tab.
5. If a custom snippet differs, test the custom domain instead of webrenew.app.

• Publishing and rollback

Domain routing, search visibility, and search-engine indexing are separate steps. A working website can still be hidden or not yet indexed.

1. Check Domains and the exact DNS records.
2. Check SEO & Social visibility and Crawling.
3. Publish any saved metadata or crawling changes.
4. Inspect the live custom domain before investigating a search result.

• Domain checks
• Search Console checks

First check the saved submission. Then investigate the notification or visitor follow-up separately.

An email draft, a queued send, a provider handoff, and a delivered message are different states.

1. Find the enquiry in Leads or Forms.
2. For a team alert, check the recipient's confirmation and alert status.
3. For a visitor follow-up, check the flow trigger and Activity.
4. For a campaign, check subscriber eligibility, schedule, sender, and plan.
5. For a reply, check Inbox and the sender's receiving records.

• Form troubleshooting
• Email delivery reference

Open Help and include a short sequence that another person can repeat. A precise symptom is more useful than a large unfiltered log.

Site name:
Affected URL:
Approximate time and time zone:
Device and browser:
What I tried:
What I expected:
What happened instead:
Visible error:
Last known working version or recent change:

Remove passwords, API keys, private customer messages, and unrelated account information before sending the report.