Fix suggestions and the work queue

Every finding in DomainGuard ends in a next action. For website and SEO findings that action comes in three sizes: the issue's own guidance, an AI-written suggestion for one page, and a fix plan for everything wrong with a domain.

Issue guidance

Tapping an issue (web: a domain's SEO & search tab, Overview; iOS: SEO & accessibility, an issue row) opens why it matters in the scanner's own words, the next action with a paste-ready snippet where there is one (a title tag, a meta description, an alt attribute, a header value), and the affected pages with their word counts.

The guidance is written for the page it is about. It quotes the title, description or tag that is there now, says what to change, and includes a snippet with the page's real values: the real site address in an og:image tag, the real image found on the page, the page's own tag with one attribute added. Where the page gives enough to write a replacement (a title, a description, a label for an unnamed button, alt text from a file name or caption) the snippet is a draft, labelled as one with what it was built from, and it is never presented as final. When nothing in the page gives a basis, the guidance says a person has to write it. Findings from the homepage scan, the crawl and the whole-site audit all use the same wording, and the fix names the admin screen when the site runs on a recognised builder.

Items are listed in the order that matters for being found: a noindex, a robots.txt block, a missing HTTPS redirect and a broken canonical first, then titles and descriptions, then accessibility, and cosmetic findings last. A finding two checks would report twice (an icon-only button, the viewport tag) appears once.

The drafts are built by the scanner from your page, not by an AI model. The rules they follow, after a round of bad output was fixed in September 2026:

• A draft reads the page's own title, headings and URL, in that order, and skips routing words like "category" and "items".
• When the page genuinely never says what it is about, it shows no draft rather than inventing one.
• It keeps the capitals the site chose ("Akron, OH", "LLC") and never appends your office town to a page about somewhere else.
• A draft clipped to fit a search result does not end on a dangling word.

If a draft still reads as nonsense, tell support; that is the feedback the team asks for.

AI suggestions (Starter and up)

POST /api/ai/seo-suggestions (the AI fix summary) and POST /api/ai/seo-page-fixes (fixes per page) turn the scan's findings into ordered steps. Since October 2026 every AI feature that advises on a website follows the same rules, taken from Google's guidance on AI-generated content: it describes each edit and never writes the replacement title, description, heading, alt text or structured data itself; it never suggests a page per town or per phrase; and it never suggests markup for anything the page does not show. Anything you publish, check against the facts first. The reasons are in AI-written content and location pages.

The domain fix plan

POST /api/ai/domain-fix-plan (the "Get help using AI" action on a domain's page) reads the stored findings across SEO, mail authentication, TLS, exposure and uptime, never the request body, and writes one ordered plan. Two audiences:

• Human: what is wrong, why it matters, and what to do, in plain words, with the unavoidable terms explained.
• Agent: a handoff brief for a coding agent, ordered, with acceptance criteria and explicit "do not guess" boundaries.

The Enterprise portfolio summary

POST /api/ai/enterprise-portfolio-summary produces the Overview's verdict, score, facts and numbered fix list across every domain. Every count comes from your scan results; the model only orders and words them.

The work queue

Issues can be added to a work queue (web: a domain's SEO & search tab, Work queue; iOS: "Add to work queue" on an issue). The queue is the list you hand to whoever edits the site. The developer brief turns the queue into one document; in the app it is copied to the clipboard, on the web it can be downloaded.

Ask NHM

Every issue has Ask NHM, which opens a support thread with the finding attached. On Enterprise that thread is with a person who will work through it with you; on other plans the button explains what Enterprise adds and the explanation of the finding stays where it is.

Common questions

Does the AI change my site? No. It describes what to change; any draft text comes from your own page and is yours to check before you publish it. DomainGuard never edits a website.

Where do the AI features run? On Cloudflare Workers AI, inside the same account as the scan data. Findings are sent as structured data, not as your page content.