It publishes to your site, on a calendar that knows about Google's updates
An article that lives in another tool's dashboard is not published. Aeoly puts it on your site, on the schedule you set, and shows the whole month on one grid.
Straight onto your own site
WordPress, Webflow, Shopify, Ghost, Wix, Notion and more, with your credentials stored per site. For anything not on the list there is a webhook, which is how a developer connects a stack nobody else has.
- Your CMS keeps being the source of truth. Aeoly writes into it, it does not host your blog.
- Each connection is tested before the first publish, so a broken credential surfaces then and not on a Sunday
One grid for publishes, changes and scans
The calendar puts the articles going out, the page changes being made and the site scans being run on the same month view, with the days Google was rolling out a ranking update drawn underneath. When traffic moves, the first question is always what else moved that week.
One change at a time, on purpose
Every change gets 28 days on its own before the result is judged. Two edits to the same page in the same week means neither of them can be credited with what happened, and that is how a content programme ends up with opinions instead of evidence.
Questions
- What if my platform is not supported yet?
- The webhook covers it: Aeoly posts the article and its metadata to an endpoint you control, and you write it wherever it needs to go.
- Do you host the content?
- No. It goes to your site, under your domain, in your CMS. If you stop using Aeoly the articles stay where they are.
The rest of the loop
See what is wrong with your site in about a minute
The scan is free, needs no account, and reads your pages without changing them.