Short answer
Arcline scans your pages automatically, every 5 hours on Premium and every week on Free, scores what it finds and ranks the problems by how much a fix should help against its effort and risk. Safe fixes then go out through the connection you allow: a GitHub pull request, or WordPress or Ghost. Each change is checked on the live page and undone if the check fails. Bigger changes wait for your approval.
What happens, step by step?
- Scan
It reads your sitemap, follows your links and reads up to 200 pages, politely and within your robots.txt rules. It repeats this every week on Free and every 5 hours on Premium.
- Score
It turns the findings into thirteen scores and one health score out of 100, with the reasons behind each.
- Rank
It works out which fixes help most for their effort and risk, and skips fixes that would not move a score.
- Decide
For each problem it chooses: fix it now, ask you first, or hand you exact steps.
- Change
It sends the fix through GitHub as a pull request, or saves it in WordPress or Ghost.
- Check
It waits for your host to publish, reads the live page and compares it with the page before.
- Learn
The next scan shows whether the problem is gone. A change that was undone is not repeated.
How does it choose what to fix first?
Each possible fix gets a number from 0 to 100. Impact counts most (35%), then urgency (25%) and the business value of the page (15%), with smaller shares for how sure Arcline is, how little effort the fix needs and how solid the evidence is. The result is reduced by the fix's risk, and a broken page is never buried by its own risk.
The number sorts the work into now, next and later. It is a ranking of jobs and not a prediction of where Google will place you, and Arcline writes down the pros and cons of each decision.
What can it fix by itself?
| Fix | GitHub | WordPress | Ghost |
|---|---|---|---|
| Page titles | Yes | Yes | Yes |
| Search descriptions and social previews | Yes | No, you get wording to copy | Yes |
| Links between your pages | No, they would need code edits | Yes | Yes |
| Search markup, llms.txt, robots.txt | Yes (robots.txt always asks you) | No | No |
| New pages and articles | FAQ and landing pages on Next.js App Router | Article drafts | Article drafts |
Everything else, such as page speed, broken links and redirects, arrives as exact steps with a Copy text button. The platforms answer explains each connection. Fixes that wait for your OK are on the Free plan (up to 10 a month) and are unlimited on Premium, and the autopilot that applies small ones by itself is part of Premium.
Who writes the new wording?
Simple rules come first, using your own page text. An AI model steps in only where rules are not enough. For one problem there are at most three approaches: rules, then an AI draft, then a second AI draft told what failed. Every draft is checked for length, format and unsafe content such as script code. If no trustworthy wording can be drafted, Arcline asks you to type what it should say, up to 600 characters. The Activity page records how each piece of wording was written, so you can judge a draft before you trust the next one.
How does it avoid loops and pile-ups?
- By default it makes at most 20 changes a day and 6 in one check, and touches a page at most once every 24 hours.
- After a change goes live, that place on that page is left alone for 7 days. A really broken page and a change you approve yourself are the exceptions.
- After a failed try it rests 1 day, then 3 days. After 3 failed tries in a row it stops and hands the job to you.
- New wording must differ from everything recently written to that place.
- If your host never publishes a change, later changes are held back instead of stacked on a stuck build.
How does it know a fix worked?
Two checks decide. The live check confirms the new wording is on your public page and that nothing else on it changed. A later scan confirms the problem is gone and no new one appeared. If someone edited the page in the meantime, Arcline never overwrites that edit: it says it could not confirm the change and checks again at the next scan. Arcline does not connect to Google Search Console today, so it cannot measure rankings or clicks and does not claim that a fix moved them. Search engines also take time: see how long SEO takes.
What should not be automated?
Repetitive on-page work such as titles, descriptions, markup and internal links suits automation. Mass-produced content does not. Google's spam policy on scaled content abuse targets pages made in bulk mainly to manipulate rankings, however they are produced, while AI-written text is not penalized for being AI-written. See whether Google penalizes AI content.
So the content studio plans at most 2 new articles a week by default (Premium includes 8 article drafts a month), writes from a brief, leaves blanks instead of inventing facts and publishes only when you confirm. For the full feature list, see Features. The page on SEO automation lists what can and cannot be automated safely.