Website and SEO
Fix suggestions and the work queue
Per-issue guidance with paste-ready snippets, the AI fix plan for a whole domain (a human version and an agent brief), the work queue, and the developer brief.
Updated · 3 min read
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: SEO, Issues; 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.
AI suggestions (Starter and up)
POST /api/ai/seo-suggestions and POST /api/ai/seo-page-fixes write a suggested title, description or heading for a page. The rules the writer follows, after a round of bad output was fixed in September 2026:
- It 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 suggestion clipped to fit a search result does not end on a dangling word.
If a suggestion still reads as nonsense, tell support; that is the feedback the team asks for.
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: SEO, 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 writes text for you to paste. 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.
Keep reading
Related articles
- Mailbox exposure monitoringAdd an address at your own domain, choose a cadence, run a check now, and understand the plan limits, the upstream rate limit, and hashed storage.Dark web ·Updated
- A domain says "on demand" or "past your plan limit"What happens to a domain over the plan's automated allowance: it stays, it scans when you ask, it accepts edits, and the oldest domains keep the automation.Troubleshooting ·Updated
- API and MCP: 401, 402, 403, 429, or a missing toolWhat each response means when a key or an MCP client is refused, and the one fix that usually applies: mint a key with the right scope on the right plan.Troubleshooting ·Updated