Features
Fix statuses, colours and troubleshooting
Coming soon — Everything the screen can tell you about a fix, in one place: what each colour means, why a fix fails or waits, and what to do.
The five colours
- To fix (red)The finding is on the page and no fix is proposed, or the last one failed. Action: “Propose a fix” (or “Propose again”).
- Proposed · to approve (orange)A proposal waits for a site manager. Nothing is changed. Action: read it, edit the after if needed, then “Apply” or “Discard”.
- In progress / pull request (blue)Approved · queued, being written, pull request open · to merge, or written · checking the page. Action: wait (or merge the pull request on Git).
- Fixed and verified (green)Live and read back on the page. Nothing to do; “Undo” stays possible for 30 days (except Git).
- Discarded / undone (grey)Discarded before being written, or undone: the previous value was put back. Propose again if needed.
A colour bar sums up each issue: “X / Y page(s) fixed”, then how many are in progress, to approve and to fix. A legend recalls the colours under each list.
Each status in detail
| Status shown | What it means |
|---|---|
| Proposed · to approve | A proposal only: nothing changes until you click “Apply”. |
| Approved · queued | Approved; NeoRank will write it (a work queue picks it up automatically). |
| Being written | NeoRank is writing the value to your site. |
| Pull request open · to merge | Not live yet: the fix goes live when you merge the pull request in your repository. |
| Written · checking the page | Written to your site: NeoRank is reading the live page back to confirm it. |
| Fixed and verified | Done: live and read back on the page. |
| Failed · nothing changed | The write failed: your site was left as it was. You can propose again. |
| Discarded | Discarded: nothing was written. |
| Undone | The previous value was put back on your site. |
Replaced proposals and “one at a time”
- A proposal whose field already has a fix in progress or done is replaced: it shows in grey under “Proposals replaced by a fix already done or in progress”, is never counted or applied; “Discard” removes it.
- Two fixes of the same field cannot be in progress at once: the second is refused with “A fix for this field is already in progress (approved or in an open pull request): wait until it is live, merged or closed”.
- “Changed on your site since the proposal — to review: nothing was written”: someone changed the value after the proposal. Read it, tick “I have read this text”, then approve again (or discard).
Verification: timing and failures
- Verification happens a few minutes after the write; on Git, after the merge and your site's deployment.
- “The check on the live page failed: the original value was restored”: the served page does not show the new value (cache, a theme rewriting the title, a redirected page). Clear the page's or the CDN's cache, check the theme, then propose again.
- “Not verifiable yet (site unreachable)”: NeoRank could not read the page; the fix is kept and will be checked later.
- “Not verifiable: the store is password-protected”: enter the store's password on the Shopify card.
- On Git: “The live page does not show the merged fix yet: it will be checked again on the next deployment”.
Undo
- “Undo” (fix history) is offered for a fix written or verified, not restored, for 30 days after it was written.
- It is missing beyond 30 days, for a fix already restored, for a member who is not a site manager, and on Git: there, undoing is a revert pull request in your repository.
- Undo puts the previous value back at once; the live page follows as soon as your cache serves it again. If someone changed the value after NeoRank, the undo is refused: NeoRank never overwrites a change made after it.
- Each fix of a batch is undone on its own, from the history.
Error messages and solutions
| Message | What to do |
|---|---|
| Your plan's monthly fix quota is used up. | Wait for the 1st of the month (UTC) or change plan. |
| This selection exceeds your plan's batch size. | Approve fewer fixes at once. |
| Your plan includes the preview: applying fixes automatically is included in the Pro plan. | See the plans. |
| Automatic fixes are paused for this site. | Connector card › Manage › Resume. |
| Tick “I have read this text” before applying. | New text or a changed value: read it, then tick. |
| The value is refused (length, HTML or external link). Edit it. | Edit the after to fit the length, with no HTML or external link. |
| Redirect refused: its target is already redirected… | NeoRank creates no redirect chain: pick another target. |
| Connect your site on the connectors page first. | See Automatic fixes. |
| The site was re-connected since this proposal: propose it again. | Propose again on the new connection. |
| On this platform, this fix is done by following the guide. | Follow the panel's steps. |
| Nothing on this page can be fixed automatically. | A page with no editable object (Shopify home, cart…): follow the guide. |
| Only site managers can apply fixes. | Administrator or Strategist role required. |
| Too many requests. Try again in a minute. | Wait a minute. |
| The connector is no longer authorised: reconnect… | Access was withdrawn: reconnect the platform. |
| The item no longer exists or is not published on the site | Publish it or ignore the fix. |
| The site did not answer correctly / did not confirm the write | Retry; check the site is online. |
| The page no longer answers 404 | No redirect needed any more: nothing to do. |
| No valid fix could be drafted: open the issue to write it | Write the after yourself in the panel. |
| Too little text on the page, and AI drafting is not included in your plan | Write the fix yourself, or see the plans. |
| AI drafting unavailable (AI quota reached / too many requests) | Wait a few minutes or until next month. |
| Not a safe code edit: added as a checklist item in the pull request | Make that edit by hand in the repository. |
| No bulk fix for this type: open the issue | Fix it from its resolution panel. |
If the connection drops during a batch
Each fix of a batch is written and verified separately. If the platform stops answering, the fixes concerned fail with their reason (nothing is written for them, or the original value is restored); those already verified stay green. Reconnect, then propose the failures again.
Google connector statuses
| Status | What to do |
|---|---|
| Connected | Nothing: the sync keeps its pace. |
| Sync interrupted | Data already imported stays shown, dated; reconnect to resume. |
| Google access expired — reconnect | Google no longer accepts the grant: “Reconnect” and give a new consent. |
| Sync failed | Try again later; if it persists, reconnect. |
| Access revoked / Disconnected | Connect again from the connectors page. |