What changed on the platform, and what we learned building it, from the first line of code onward.
RSSEach specialist agent now says which tasks it picks up, and when one gets stuck a strategist can answer it directly and it finishes the job. Hand-written tasks are read against the task standards before they are saved.
The client report can count the events you name as conversions instead of the property's key events. Every discovery gets a strategist's review before it is ready, and agents read facts but no longer write them.
Assign a teammate to clients in one dialog, see whether every client's data is flowing, and read logins and webhooks as tables. Underneath, what agents remember about a campaign is now typed: facts, notebooks and events.
Agents had two outputs, a task or silence. Asks are the third. Notes & feedback replaces Comments and turns what you write into proposed changes, and the client workspace navigation was consolidated.
A brand groups the clients that belong to one company and carries rules and context every member campaign inherits. Campaign context, citation notes and a daily digest also arrived, and the Google data sync was rebuilt to scale.
Tracked keywords now move with a client's website when it changes. Feedback you send back always puts an agent on the rework, the review page shows the full feedback, and agents read a page in full before they touch it.
Pages built with the newest Divi builder can now be read and edited through our connector without corrupting the page. The comparison view on a review is read-only while it is open.
A content review that has come back for a second look now shows exactly what moved since the version you last read. The testing standard became scripts we run before every change.
Settings gained a Communications tab and partners without a plan land on Start Here. Staff got a record of every edit the team makes to agent work, and the one-off SEO audit became a project on the platform.
The Keywords page names each rank state instead of one catch-all, reports gain two more trend switches, and the branded WordPress plugin gets a share link. Agents read real server response time before recommending speed work and must open a page before writing a task about it.
Each partner gets their own branded build of the WordPress connector from a new Settings tab. Written Content approvals can fall back to approved after a set number of days. Reports gain a Website toggle and per-section comparison switches.
Set once which portal pages and report sections every client gets, and override per client. The portal can show the campaign goal, brief and competitors, and content due dates are now publish dates.
Nothing changed on partner screens. The WordPress connector learned to clone blocks, change heading levels and move sections, and the staff task queue now lists only work that is ready to start.
A connected website no longer hands site edits or publishing to the agent by default; partners opt in per workspace or per client. The WordPress connector now reads pages whose copy lives in custom fields, searches a whole site and places links that know a copy link from a navigation link.
Approval requests arrive as new, named by the client's website, and land on the task. Campaign notifications reach only the team members assigned to that client. Approved plans merge into one month-by-month list.
Every client site is classified by the CMS or builder it runs on and shown on Website Access and the client header. Citations stop ordering the big directories, and competitive gap reviews reach every workspace.
The client page now opens on the campaign plan with goal, brief and competitors editable in place, the agent page becomes Sessions, and content can pause for a draft check on your own site before it goes live.
Approving or sending back a task is open to every member of your team.
Each Business Profile post carries its location and posts spread across the month, website edit approvals split into visible and technical, and the team's task queue reorders by urgency.
Content drafts now come from brief-writer, writer and QA agents. Tasks hand between teams rather than people, published URLs can be recorded from the editor, and cancelling a client winds the campaign down properly.
Partners with a white-label domain use the whole platform there, every campaign gets a Rules tab, content pieces get a featured image, and approving over unread feedback asks first.
Website edit tasks carry a lane, Business Profile edit becomes a task type, work still under our review stays out of your approvals until we release it, and admins get an Operations section.
The client report can be viewed and downloaded by quarter, gains a Work Delivered section, and competitive gap reviews move into Monitoring and Audits.
Page speed monitoring opens one alert when the site itself stops a page being measured, audits that cannot complete wait for their regular slot, and task text reads the same wherever your team sees it.
The discovery report gets a Download PDF button and real competitor heatmaps, and the team can read live Search Console and Analytics data for any campaign from their own tools.
Pausing a client now leaves a record, can be scheduled, and keeps delivering work that was owed. Locations suggest Business Profiles you already manage, and Google data links minutes after activation.
Activation now switches on the standard monitoring set and starts citation scans for every location, team assignments get their own tab, and the onboarding agent starts taking shape.
Activating a client now asks for a start date. Today starts now, a future date schedules the flip, and every locked page offers the same flow.
A discovery on a site with tens of thousands of pages now waits for the crawl to finish, and checks a site blocked us from running read as unchecked rather than failed.
The dashboard opens on Active clients, Prospects and Team members, and the Prospects card opens a filtered client list.
The client portal's home became the campaign plan with phases and a checklist, monitoring copy was rewritten in plain language, brief-only campaigns arrived for partners who write their own content, and on Thursday every change started going through review and automated checks before it ships.
The first partners were on the platform this week, a Monday digest started listing everything waiting on a partner, alerts learned to wait and see, and the agent editor was rebuilt for daily use.
Real billing went live on Monday, screenshots became task evidence, task requests and direct messages to the agent arrived, and Agent Builder v2 rebuilt the agent system so no agent lives in code.
The whole client portal became a single no-login page a partner can embed, arrived inside HighLevel, and reviewing work settled into one shape with explicit decisions and batched feedback.
The platform became Tideworthy, the client portal grew into a set of real pages with approvals inside it, reports learned to chart, and AI Visibility arrived.
The platform began on July 6. Its first week put accounts, clients, monitoring, keyword tracking, reporting, planning, approvals and a daily campaign agent in place, carrying over tooling already built in Workbench and the Portal.
June 2026 into the first days of July. Campaign reporting and monitoring arrived, tasks and initiatives became visible to partners, blog posts learned to link, and citations were reorganised around locations.
Late April 2026. Writing agents for geo, blog, service, location, expanded and ecommerce pages, a Business Profile post writer, citation ordering end to end, and a personal assistant with shared memory for every member of the team.
The first half of April 2026. The campaign plan a partner sees became a live page on a link, on the agency's own domain if they wanted, and the Portal's monthly grid, focus pages and task views followed.
Late February 2026. Packages and scope items were rebuilt as one catalogue that Workbench and the Portal both read from, a campaign strategist agent arrived, and discoveries got a proper workspace.
Early February 2026. Written content got a feedback loop that partners used from a link, Workbench gained a library of playbooks, and the first content-writing agent drafted its first pages.
Late January 2026. The link building tooling moved into Workbench, every campaign got a scope catalogue, and the first shareable campaign plan pages went out.
The first half of January 2026. The last of the campaign record left ClickUp for Workbench, and the first internal agents started working on it.
December 2025 in Workbench: the discovery report became a Workbench deliverable with its own crawler and local scans, the first agents were defined and run under a staff member's eye, planning agents began writing plan items, and a plugin connected client sites.
On December 4, 2025 the billing build that started in September landed: invoices, statements, receipts, payment methods and autopay in the Portal. In the same weeks discovery editing and tasks left the Portal for Workbench, and campaign scope became a timeline.
A short note when something changes on the platform, plus whatever else you pick.
Check your inbox to confirm your subscription.