We make your business the answer AI engines give.

The seven steps above show the agent at work. It is just as useful to know where it stops, because those limits shape what you can expect from it and what still needs a person. Most of these limits are built into the system rather than left to someone's memory.

It does not read your whole site each week. A weekly run reviews up to ten of your pages, taking first the ones it has gone longest without reading, so on a site with many pages a full lap takes a number of weeks. Some pages it leaves alone entirely: any link that carries a password or an access token, and any page marked noindex, is never crawled, analysed or changed.

Not every proposal can be applied by software. Ideas written as advice, such as a suggested new heading, a fuller rewrite of a section or a redirect, are not something the WordPress plugin or our companions can carry out, so approving one sends it to our team's task list for a person to action. Site-wide files are treated as one document for the whole site, so the review of a single page cannot rewrite your llms.txt file or your robots rules. On WordPress and companion script sites, approval is the last step a person takes: the plugin collects approved changes at its next hourly sync, and the script applies them at the next page view.

Who signs off depends on what a change touches. Changes that alter what a visitor reads, such as a reworded heading, a new section or a question-and-answer block, are the only kind we send you for approval, by email, with a button to approve and another to ask for changes. Technical changes, such as titles, descriptions, structured data, canonical tags and image attributes, are signed off on our side and never sent to you.

Two checks can stop a change at the last step, even after it has been approved:

• Business details. Structured data may only state a phone number, street address, postcode, map position, opening hours or email address that matches your business record. Anything that does not match is removed, and a block of markup left with nothing to identify is dropped rather than published.
• Earnings claims. Titles, descriptions, structured data, headings and new copy are scanned for promises about profit, returns or income that nobody could back up. A change that makes one is refused until someone changes the wording; the system never rewrites it quietly.

The live check has limits too. It fetches each page the way a crawler does, without running scripts, and compares what it finds with what was approved. Some changes cannot be checked that way, such as a redirect or a site-wide file, so those are left for a person to confirm. On sites that use our companion script rather than the plugin, changes are made in the visitor's browser as the page loads, which means crawlers that do not run scripts may never see them.

Finally, the agent cannot tell you which single change moved a result. The follow-up taken at least fourteen days after a change sets your site's overall audit score from before it against one from after, so it reflects the direction of the whole site rather than the effect of one edit. Nor can it make an engine name you. A page with every fix in place can still be left out of an answer, because Google and the AI engines decide that for themselves, which is why we never put a date on results.