Documentation · Pages
Settings
Set your agents' plan, turn them on or off, connect GitHub and Search Console, choose what agents may do on your site, and manage Enterprise.
Open Settings from the sidebar, or go to app.ivyl.ink/settings. The page shows your site's address at the top, the heading Settings, and two tabs:
| Tab | Address | What it covers |
|---|---|---|
| Agents | app.ivyl.ink/settings | Your agents' plan, the on/off switch, and Enterprise |
| Connections | app.ivyl.ink/settings/connections | GitHub, Search Console, and what agents may do on your site |
Settings apply to the site you have chosen in the Site menu. If you have several sites, switch sites first. See Sites.
Agents tab
The lead line reads: "Your agents, what they may spend, and how they reach your site." The tab has three sections: Agents, Enterprise and Your site.
The Agents section
Next to the Agents heading is a pill that reads On or Off.
Under it you see one of these:
- First visit. A card headed Start your agents and Pick a plan and they start. It explains that agents check your site every day, research keywords, content gaps and competitors, find technical problems, and write up fixes for you to approve. It names the plan that is already selected. Pick another if it suits you better.
- Agents on. "Agents are working at the plan below: daily checks, reviews that research new keywords and content, and the fixes they write up for you to approve."
- Agents off. "Agents are off. Nothing runs or spends. Pick a plan below and they start. Reports still run."
- Agents off, on an Enterprise site. "Agents are off. Nothing runs. Turn them on below and they run on Canopy. Reports still run."
Below that is a line about your balance. It says how many credits you have and either what auto top-up adds and when, or that "with auto top-up off, agents pause when it runs out." The Billing link takes you to Billing. If you have more than one site, the line also tells you that each site has its own plan and all your sites share one balance.
Plan cards
The plan is how fast your agents may spend from your balance. A bigger plan buys more frequent and more careful work. It never buys cheaper work. Pick one card:
| Card | Budget | Quality | What it promises |
|---|---|---|---|
| Off | 0 | — | "Nothing runs or spends. Reports still run." |
| Seedling | 10 credits a month | Basic | Quick checks and short reviews. Fine for keeping an eye on a small site. |
| Sprout | 30 credits a month | Standard | Careful reviews and clear fixes, at a steady pace. |
| Climb | 100 credits a month | High | Deeper reviews that read more of your site each run. |
| Canopy | 300 credits a month | Best | The most thorough work we do, at maximum effort, as often as your site needs. |
| Custom | Any whole number of credits an hour, day, week or month | Set by the budget | Your own pace. |
Each plan card (except Off) shows:
- The credits a month and the quality.
- A picture of the agent crew, with how many agents are busy on a typical day.
- Estimates worked out for your site's size, including:
- Reviews: how many review runs you get.
- Pages per run: how many pages each review reads.
- Whole site: how often the agents get through your whole site.
- Research: how widely the content review looks for new pages to add, Usual or wider.
- Credits used: a typical month's use, as "About X of Y" credits.
- A Current pill on the plan you have saved, while agents are on.
These numbers are estimates. They change with the size of your site.
On a small site, a bigger plan may do no more than the one below it. That card then says it's More than a site this size needs and names the cheaper plan that covers your site as often and as widely. Pick the cheaper plan unless you want room to grow. On a very small site, a card may instead say how many credits of useful work your site has a month: the rest stays in your balance.
Some deeper whole-site work, such as checks that inspect your pages with screenshots, needs a budget of at least 100 credits a month (Climb or above). On a smaller plan that work doesn't start, and it waits with the reason "This work needs a budget of at least 100 credits a month."
Custom budgets
On the Custom card, type a whole number of credits from 0 to 100,000 and pick an hour, a day, a week or a month. The quality follows the monthly amount your budget adds up to. For example, 10 credits a day is about 300 credits a month, so it gets Best.
| Monthly amount | Quality |
|---|---|
| 300 credits or more | Best |
| 100 up to 300 | High |
| 30 up to 100 | Standard |
| Under 30 | Basic |
If the number isn't valid you see: "That budget didn't save. Enter whole credits from 0 to 100,000, then pick a window."
Save or start
The button under the cards reads Start agents when agents are off and Save when they are on.
- Pick a plan card. For Custom, fill in the credits and the window.
- Click Start agents or Save.
- You see "Saved. Agents follow the new settings from their next job."
Any budget above zero turns agents on. Choosing Off and saving turns them off: nothing runs or spends on that site, including the free daily checks. Reports still run.
For how budgets pace work and what happens when your balance runs low, see Budgets and Credits. To start for the first time, see Turn agents on.
On an Enterprise site
When a site is on Enterprise, the plan is fixed at Canopy and the plan cards are greyed out. You see: "This site is on Enterprise: its agents run on Canopy and Ivy Link pays for their work. Ivy Link changes the plan if Enterprise ends."
You get a single button instead, Turn agents on or Turn agents off. After you click it you see one of these:
- "Your agents are on. They run on Canopy and Ivy Link pays for their work."
- "Your agents are off. Nothing runs until you turn them on again."
The balance line reads "Ivy Link pays for this site, so its agents never wait for credits."
Your site
The last section has one row, Connections and permissions. It sums up your setup in a line, for example whether GitHub is connected and how finished work arrives, whether Search Console is connected, and your New ideas setting. Click Connect (nothing connected yet) or Manage to open the Connections tab.
Enterprise card
The Enterprise section on the Agents tab lets you put this one site on Enterprise. Enterprise costs $1,000 a month for the site. Ivy Link pays for all of the site's agent work and reports, the agents run on Canopy, and an SEO expert checks every idea before it reaches you. Your credits stay for your other sites. You can cancel any time.
A pill next to the heading shows the state: Active, Payment due or Requested.
| State | What you see | What you can do |
|---|---|---|
| Not on Enterprise | The price and what's included | Start Enterprise to pay in Stripe Checkout, or write in the box and click Talk to us |
| Requested | "We have your request and will email you within one business day." | Wait for our email, or click Start Enterprise to begin now |
| Confirming payment | "Confirming your payment with Stripe…" The page refreshes on its own. | Wait. Enterprise starts the moment Stripe confirms. |
| Active | Price ($1,000 a month), Billing ("Renews" and the date) and Started | Cancel Enterprise |
| Active, cancelling | Billing shows "Ends" and the end date | Keep Enterprise to undo the cancel |
| Payment due | "Your last Enterprise payment didn't go through." Stripe tries your card again, and your agents keep running meanwhile. | Update card |
| Arranged with Ivy Link | Billing reads Arranged with Ivy Link | Email hello@ivyl.ink to change it |
Cancel Enterprise, Keep Enterprise and Update card open Stripe's billing page. When you come back, the card shows what Stripe now says.
The Talk to us box holds up to 2,000 characters. If Enterprise can't be bought online for your account, there is no Start Enterprise button: you write in the box and click Talk to us, and we set it up with you.
When Enterprise ends, your agents switch off and go back to the plan you had before. Once you turn them on, their work is paid from your credits again.
For the full story, see Enterprise.
Connections tab
Go to app.ivyl.ink/settings/connections. The lead line reads: "Where Ivy Link connects to your site, and what it may do there." The tab has two sections: Connections and Permissions.
GitHub
The GitHub card shows one of these pills:
| Pill | What it means | What to do |
|---|---|---|
| Not connected | No repo is linked. | Click Install on GitHub. |
| Pick your repo | The app is installed but no repo is chosen yet. | Choose a repo and click Use this repo. |
| Connected | Ivy Link can reach your repo. | Nothing. Use the buttons below to change it. |
| Access removed | "Ivy Link can't reach" your repo "anymore." The app or repo was removed on GitHub. | Install the app again to reconnect. |
| Not open yet | GitHub connections aren't open yet. | We'll email you when they are. |
To connect:
- Click Install on GitHub.
- On GitHub, install the Ivy Link SEO app and choose which repos it can see. Finish within 15 minutes, or the link expires and you start again.
- Back in Ivy Link, under Repos the Ivy Link SEO app can see, choose your site's repo. Private repos are marked Private.
- Click Use this repo. You see "Connected. Ivy Link will open pull requests on this repo."
If the app can't see any repos yet, the card says so. If your repo isn't listed, click Change which repos the app can see, give the app access on GitHub, then reload the page. If you installed on an organization you don't own, GitHub sends the request to an owner. Once they approve it, come back and pick the repo.
When connected, the card says what Ivy Link does with the repo, based on your finished-work setting. It has two buttons:
- Use a different repo: pick another repo, then Use this repo.
- Manage access on GitHub: opens your GitHub installation settings in a new tab, where you can change which repos the app sees or remove it.
Site not on GitHub? Email hello@ivyl.ink with how it's hosted. For more, see GitHub.
Search Console
The Search Console card shows one of three pills:
- Not connected: "Reports and checks use public ranking data." Click Connect.
- Connected: shows your property, and whether Ivy Link reads your search data and sends Google your sitemaps, or reads your search data only. Click Manage.
- Access removed: Ivy Link can't read your property anymore. Click Reconnect.
Each button opens the Search Console page, where you connect, change access or disconnect. See Search Console.
New ideas
Under Permissions, the New ideas card sets what happens "When an agent has an idea for your site."
| Choice | What happens |
|---|---|
| Ask me first (default) | Each idea waits until you approve it on Approvals. |
| Start without asking | Agents start their ideas on their own: fixes, page changes, new pages and data updates. You can still pause or drop any of them. Agents only spend within your budget. |
Click Save new ideas. You see "Saved. New ideas:" and your choice. This setting works without GitHub.
How finished work reaches your site
This card sets what Ivy Link does with fixes, page changes and new pages.
| Choice | What happens |
|---|---|
| Prompts only | Ivy Link reads your repo to find what causes each issue but never changes your site's code. Writes to data/ follow the Data updates setting below. Each change arrives as a prompt on Results for you to paste. |
| Pull requests (default) | Ivy Link opens a pull request for each change, from a branch named ivylink/…. It never pushes code to your main branch. You review it, then merge it on GitHub or with Merge on Results. |
| Pull requests, merged for you | Ivy Link opens a pull request and merges it once your repo's checks pass. Each change stays on GitHub, where you can revert it. Choosing this also merges fix pull requests already waiting for you. |
Click Save finished work. You see "Saved. Finished work:" and your choice.
Without a connected repo, this card is greyed out with Prompts only selected: "Connect GitHub to choose pull requests. Until then, finished work arrives as prompts on Results."
With Pull requests, merged for you, Ivy Link leaves a pull request for you to merge when the change touches a page (a template, stylesheet or page file), when someone else adds commits to it, when its destination branch changes, when it conflicts, when your repo requires a review or a check, when it must be brought up to date with your main branch, or when checks haven't passed within an hour. Results shows why it is waiting for you, for example This change touches a page, so it waits for your review.
For more, see Ship changes.
Data updates
This card only shows when your site has a dataset. It covers the daily data files in data/ that your pages are built from.
| Choice | What happens |
|---|---|
| Automatic (default) | Ivy Link commits the day's data to your repo each day, and your site rebuilds with it. It only changes files in data/. |
| Pull request | Ivy Link keeps one pull request with the latest data, updated each day. Merge it when you want the new numbers live. |
| Paused | Ivy Link keeps collecting but doesn't write to your repo. Turn it back on and the next update brings everything in. |
Click Save data updates. You see "Saved. Data updates:" and your choice. See Data.
An approved new page, including one built from your dataset, is built like any other approved work: a pull request under either Pull requests setting, or a prompt with Prompts only or without GitHub. A new page waits for your review even under Pull requests, merged for you. Ivy Link only collects new data for a page when data updates are set to Automatic. See Ship changes.
Other settings
- Weekly report email is set under Email delivery on Weekly reports, not here.
- Credits, auto top-up and payment are on Billing.
Questions? Email hello@ivyl.ink.
Last updated October 31, 2026
Something here not match what you see? Email hello@ivyl.ink and we'll fix the page.