Documentation · Pages
Results
Where your approved work lands: pull requests to review and merge, or prompts to paste. Follow each change from approved to shipped and measured.
Open Results from the sidebar, or go to app.ivyl.ink/results. Everything you approve on Approvals shows up here, along with what happened to it.
Two ways work reaches you
Results works in one of two modes. Which one you see depends on your GitHub connection and your How finished work reaches your site setting in Settings.
| Pull requests | Prompts | |
|---|---|---|
| When | GitHub is connected and finished work is set to Pull requests or Pull requests, merged for you | GitHub isn't connected, or finished work is set to Prompts only |
| Line under the heading | "Your approved work, as pull requests on your repository." | "Your approved work, as prompts you can paste into the tool you build your site with." |
| What you do | Review and merge each change, on GitHub or with Merge here | Copy each prompt into your site builder, make the change, then click I made this change |
Pull requests is the default once GitHub is connected. See Connect GitHub and Ship changes.
When GitHub isn't connected
In prompts mode, a notice at the top tells you why and how to change it:
- GitHub not connected: "Connect GitHub and Ivy Link opens these changes as pull requests for you." Click Connect GitHub to go to Settings, Connections.
- GitHub connected, but set to prompts only: "Finished work arrives as prompts because your site is set to prompts only." Click Change it to pick Pull requests instead.
Nothing is lost while you're on prompts. Your approved work still arrives, as prompts.
What's on the page
From top to bottom:
- Your site's address, the heading Results, and the line for your mode.
- A notice, if you just did something here (merged, marked done, moved back), or the GitHub notice above.
- Ready for you: pull requests waiting for your review, and prompts waiting for you to paste.
- Merging on its own: pull requests Ivy Link will merge for you. Only shown when your site is set to Pull requests, merged for you.
- Being worked on: approved work your agents haven't finished yet.
- Done: shipped and measured work, up to 30 items.
Sections only show when they have something in them. If nothing is approved yet, the page says: "Nothing is approved yet. Approve ideas on Approvals and their work shows up here."
Pull request cards
Each open pull request is a card with:
- The title of the change.
- A state pill (see the table below).
- The why: what the change is for. A data update says "The latest data for your pages, updated each day. Merge it when you want the new numbers live."
- A note, when Ivy Link left one explaining why the change is waiting for you.
- Pull request #N · N files (or data files for a data update).
- Buttons: Merge (when Ivy Link may merge it), Review on GitHub, and See the change (for site fixes, not data updates).
| Pill | What it means | What to do |
|---|---|---|
| Waiting for your review | A fix your agents opened, ready for you | Review it, then click Merge or merge it on GitHub |
| New data to merge | The daily data update for your pages | Merge it when you want the new numbers live |
| Waiting for you | Ivy Link left a note on it | Read the note, then sort it out on GitHub or merge |
| Merging once checks pass | Under Merging on its own; Ivy Link merges it for you | Nothing. Close it on GitHub if you don't want it |
If Merge isn't offered, the card says "Merge it on GitHub. To merge here, let Ivy Link open pull requests." The link takes you to the setting.
Merge a pull request from Results
- Find the pull request under Ready for you.
- If you want, click Review on GitHub or See the change first.
- Click Merge.
Before it merges, Ivy Link checks again that the pull request hasn't changed, doesn't conflict with your main branch, and that every check on it passed. If a pull request has no checks at all, Ivy Link won't merge it here; merge it on GitHub instead.
When it works you see: "Merged. Your site goes live with it on its next build." The card leaves the page.
When it doesn't, the notice tells you why:
| Notice | What to do |
|---|---|
| "Its checks haven't all passed yet. Try again once they have, or merge it on GitHub." | Wait for the checks, then click Merge again |
| "It conflicts with newer changes on your main branch. Sort that out on GitHub, then merge it there." | Resolve the conflict on GitHub |
| "Your repo needs a review, or the change brought up to date, before it can merge. Merge it on GitHub." | Your repo's rules need a step only GitHub can do |
| "It changed since Ivy Link last checked it. Review it on GitHub." | Someone changed it; look at it on GitHub |
| "Ivy Link hasn't finished checking how this change looks on your site. Try again later, or merge it on GitHub." | Wait and try again, or merge on GitHub |
| "That pull request isn't open anymore, or Ivy Link can't reach your repo." | Check it on GitHub and your connection in Settings |
| "Ivy Link can't merge it while your site is set to prompts only or GitHub isn't connected. Merge it on GitHub, or change that in Settings, Connections." | Merge on GitHub, or change the setting |
| "GitHub didn't merge it. Try again in a minute, or merge it on GitHub." | Try again shortly |
You can always merge on GitHub instead. Ivy Link notices either way.
A merged pull request doesn't ship instantly. Your site goes live with the change on its next build. A change only counts as shipped once Ivy Link confirms it on your live site.
Merging on its own
With Pull requests, merged for you, the section reads: "Ivy Link merges these once every check on them passes, because your site is set to pull requests merged for you." Each merged change stays on GitHub, so you can revert it there.
Ivy Link leaves a pull request for you instead, with a note saying why, when:
- it conflicts with your main branch,
- your repo requires a review or a required check before it can merge,
- its checks haven't passed within an hour,
- its build checks are missing, unfinished or unsuccessful,
- your repo requires it to be up to date with your main branch first,
- someone added commits to it,
- the branch it merges into changed,
- GitHub wouldn't let Ivy Link merge it,
- your access setting or GitHub connection changed, or
- it touches a page ("This change touches a page, so it waits for your review."). For now, every change that touches a page waits for you.
Those move to Ready for you with the Waiting for you pill.
See the change
See the change opens a page for that change, with an Open pull request button and a Publishing: line (Automatic, Your review, Paused, Merged or Closed).
Ivy Link doesn't take screenshots of changes yet. So the page shows Preview unavailable and says: "Ivy Link doesn't take screenshots of changes yet. Open the pull request on GitHub to check its preview build." Use Open pull request to do that.
Prompt cards
In prompts mode, each change comes as a prompt you paste into whatever you build your site with.
A prompt card shows the title, a status pill, the why, a Because line with the evidence when there is some, and:
- Done when: what the finished change looks like, when the prompt doesn't already say it.
- Copy prompt: copies the whole prompt.
- I made this change: tells Ivy Link you've done it.
- Show the prompt: opens the full prompt to read.
Use a prompt
- Under Ready for you, click Copy prompt (or Show the prompt to read it first).
- Paste it into the tool you build your site with and make the change.
- Publish your site as usual.
- Click I made this change. You see: "Marked done. Ivy Link checks the change on your site and measures what it does."
The card moves to Done as Shipped. While a prompt is still being written, the card says "Its prompt is being written."
Work being worked on
Approved work that hasn't reached you yet sits under Being worked on. In prompts mode, the card says "Its prompt is being written." With pull requests, the card says what it's waiting for:
| Card text | What it means |
|---|---|
| "Queued for the builder." | It's in line for an agent |
| A wait reason | Something is holding it, such as your balance |
| "Agents are off. Pick a plan in Settings and the builder starts on it." | Turn your agents on in Settings |
| "Your agents are working on it." | An agent has started |
| "Your agent stopped without making a change. Its notes say what it found and what it needs. Move it back and approve it again to have it try again." | The agent looked and stopped safely; read its notes on Agents |
| "Your agent's attempt failed. Move it back and approve it again to retry." | The attempt didn't finish |
| "Not available yet: Ivy Link can't collect data for a page yet. This stays approved, and we'll email you when it can start." | A data item; nothing to do, we'll email you |
With pull requests, agents make one attempt per approval. To have them try again, click Move back, then approve it again on Approvals.
Take back an approval
Until an agent starts, an approved card has two buttons:
- Move back: returns it to Waiting for your OK on Approvals. Notice: "Moved back to waiting for your OK."
- Drop: your agents leave it. It stays under Dropped on Approvals.
Once an agent starts, the buttons go away. If the work is in line for an agent, the card says "Your agents are working on it." If you press a button on a page that's out of date, you see "Your agents have already started on it, so it stays approved."
Status pills
| Pill | Meaning |
|---|---|
| Approved | You approved it; not started or not finished yet |
| In progress | Your agents are building it |
| Shipped | Live on your site: confirmed after a merge, or you clicked I made this change |
| Measured | Your agents have measured what it did |
A work card with a pull request shows a link like Pull request #12 · Open, Merged or Closed. If a pull request is closed without merging, the work goes back to where it was before: Approved, or Waiting for your OK on Approvals.
How shipped work is measured
When a shipped change came from a problem with a search or a page, Pip measures it twice: 7 days and 28 days after it shipped. Each measurement compares that search or page with how it was when the change shipped. For a search, it uses clicks and average position over the last 7 days of Search Console data. You see the results in Done lately on Home and in the feed on Agents. A search line looks like this (example numbers):
"running shoes", 7 days after the fix: 42 clicks a week, from 30 (+40%), position 8.2 → 6.9. Recovered.
For a page fix, the line says whether the checks still see a problem on that page, for example "the checks see no problem."
| Verdict | When |
|---|---|
| Recovered | Clicks up 10% or more, or position up by 1 or more. For a page fix: the checks see no problem |
| Regressed | Clicks down 10% or more, or position down by 1 or more. For a page fix: the checks still see a problem |
| Too early to call | For a search at day 7, when the change is smaller than that. At day 28, Pip calls it by the direction it moved |
Home says it plainly: while agents are off, Pip still measures the work that shipped.
These are before-and-after observations. They don't prove the change caused the difference, and Ivy Link doesn't guarantee rankings.
Who can act here
Only the account owner can merge, mark work done, move it back or drop it.
Related
- Approvals: approve the ideas that become Results.
- Ship changes: the full path from idea to live change.
- Connect GitHub: get pull requests instead of prompts.
- Weekly reports: a weekly record of merged work and search data.
Last updated October 31, 2026
Something here not match what you see? Email hello@ivyl.ink and we'll fix the page.