Automatic fixes (Auto-Fix): overview

How it works

1. Propose — in the “Issue resolution” panel, “Propose a fix” reads the current value on your site and drafts the fix from the page's real content, in its language (by a rule, otherwise by AI). Before and after are shown exactly; the after is editable.
2. Approve — a site manager (workspace Administrator or Strategist role) clicks “Apply”. Who, when and what are logged. For new text (FAQ, an added link) or a value changed on your site since the proposal, you must first tick “I have read this text”.
3. Apply — NeoRank first re-reads the live value. If it changed since the proposal, nothing is written and the fix goes back to “proposed”. Otherwise the old value is saved, then the new one is written (on a Git repository: a pull request is opened, see below).
4. Verify — a few minutes later, NeoRank reads the value back through the connector, then fetches the public page and checks the audit rule passes. If it fails, the original value is restored automatically.
5. Undo — for 30 days, “Undo” in the history puts the previous value back, unless someone changed it since (NeoRank never overwrites a change made after it).

The six platforms

Connect your site on the connectors page with one of these platforms. Each has its own step-by-step page:

What NeoRank can fix

• (1) Webflow: static pages with the “Fixed page” publishing; CMS items with no publishing.
• (2) Git: where the alt text is written in the code; otherwise a checklist item in the pull request.
• (3) Webflow: needs the “Whole site” publishing.
• (4) Shopify: in a NeoRank metafield, printed by the “NeoRank JSON-LD” app embed.
• (5) Git: in your redirects file.
• (6) Webflow: Webflow Enterprise plan only, with the “Whole site” publishing.

Settings that can break a whole site — canonical tags, hreflang, noindex, robots.txt, viewport, document language, speed, H1, duplicate content, orphan pages, redirect chains — are always guided: the panel shows the steps, never an “Apply” button.

The colours of a fix

Wherever a fix appears (resolution panel, “Fix everything”, history), the same colour tells where it stands:

• To fixFound by the crawl, nothing proposed yet (or the write failed).
• Proposed · to approveA proposal waits for your approval. Nothing changes on your site until you click “Apply”.
• In progress / pull requestApproved, being written, in an open pull request, or written and being checked on the page.
• Fixed and verifiedLive, and NeoRank read it back on the page. Only this status is green.
• Discarded / undoneDiscarded before being written, or undone: the previous value was put back.

Each status, each message and what to do about it is on the Statuses, colours and troubleshooting page.

One fix at a time per field

• While a field (a page's title, an image's alt…) has a fix approved, being written or in an open pull request, a second fix of the same field is refused (“A fix for this field is already in progress”). In “Fix everything” it is simply skipped and the rest of the batch goes through.
• The “Propose a fix” button disappears from a page whose fix is proposed, in progress or done: the page shows its status instead. After a failure or an undo it becomes “Propose again”.
• A pull request closed without merging frees the field: its fix goes back to “proposed”.
• A proposal whose field already has a fix in progress or done is replaced: it is filed in grey under “Replaced proposals”, never counted or applied, and can be discarded.

“Fix everything with your approval”

At the top of the technical audit's Issues & alerts tab, this panel gathers everything the connected platform can fix, by issue type, with colour counters.

1. Prepare the fixes: NeoRank reads each page on your site and drafts the exact fix, by a rule, otherwise by AI. A bar shows the measured percentage (pages prepared ÷ pages to prepare) and the seconds elapsed; up to 20 pages it moves page by page.
2. Review: every proposal shows before and after. Those that need reading (new text, a value changed on your site) can only be selected after “I have read this text”, which selects them at once.
3. Tick what you want, or “Select all”, then “Approve and apply” (or “Approve and open a pull request” on Git). Nothing is written before that click.
4. The panel then follows the batch: queued, applied, verified on the page, pull request open, failures with their reason.

• Closing the page during preparation stops it: proposals already drafted stay (orange), nothing is applied.
• You can approve only a part, and later undo one precise fix of the batch from the history, like a single fix.
• At most 100 fixes per approval, and your plan's batch size (table below); 100 pages per issue type and per preparation.

AI-written text

• One AI call only when the rule is not enough (or when you click “Propose a fix”); it counts against your plan's AI request quota. Without AI in your plan, NeoRank proposes a draft built from the page's own words.
• Page content is treated as untrusted data: sentences that look like instructions are removed before the call.
• Every text is checked: length, the page's language, no HTML, no external link, no template braces, no figure or promise absent from the page. A refused text is not proposed; a “To review” remark shows on a stored text that no longer passes.
• Neo AI can explain a fix but never applies one. See AI help.

Plans and limits

An undo, or a fix restored because its verification failed, does not consume the quota. The quota resets on the 1st of each month (UTC).

Pause and revocation

• “Pause” (connector card › Manage) stops every new write on that site until “Resume”. On Cloudflare the worker then serves your original pages, without the fixes.
• “Revoke” cuts NeoRank's access to the site; each platform page says exactly what is removed.
• The NeoRank team can also suspend writes for an organisation or for the whole platform.

Security

• NeoRank asks only for the rights the catalogue above needs: never users, orders, customers, prices or theme files.
• Keys, tokens and passwords entrusted to NeoRank are encrypted in the connector vault and never shown again.
• Outbound calls only reach public addresses over HTTPS, never follow a redirect, and are bounded in size and time.
• Write caps per site, bounded batches, a pause per site, per organisation and globally.