Tideworthy gets its name, and the client portal gets its pages

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 product got its name this week, the client portal became a set of real pages, and reports learned to chart.

For our partners

1. The platform became Tideworthy on Monday: new name across the app, a new mark, one official address, and email that sends from a Tideworthy account domain.
2. The client portal went from one plan page to a set of pages: Content, Link building, Google Business posts, Website map, Activity, Approvals and Reports.
3. Reporting grew charts, and Configure Report saves on every change.
4. On Saturday, AI Visibility arrived for discoveries and reporting: sampled mention rates for a client and its competitors across the major AI assistants, on location-pinned buyer prompts, reported as rates rather than a single day’s check.
5. A shield in the top bar holds two account-wide trust controls, pause all client communication and force safe mode across every campaign, with per-client safe mode underneath.
6. Partners choose per client who implements website changes, their own team or ours.
7. Google Business posts moved to a model where the plan is the written posts and the partner approves finished units, and citations became something the agent sets up and runs as recurring rounds.
8. Elsewhere: tasks got a page of their own with comments and inline editing, keyword mapping got a page-first view, planning stacks the soonest months on top, alerts read “All clear” when quiet, and a Help Center opened.

1. Tideworthy

Partners send client email from a subdomain of their own domain, managed for them, instead of setting up their own email service. Branding settings split into Client Portal and Email Sending tabs, and a partner’s own logo replaces ours at the top of their sidebar.

2. The client portal

Each page shows only when the partner turns it on and there is something to show. Clients approve plans and content from the portal itself, not only from an emailed link, and pending decisions lead their dashboard. Client comments with mentions arrived, with an inbox on the client workspace.

3. Reporting charts

The charts are six-month monthly trends with the year prior overlaid, stat cards with sparklines, a crawl score gauge, crawl history as a stacked bar by severity, keyword tables split into Priority and Other, and a Link Profile section.

Behind the scenes

1. What sets an agent going is now something the team edits rather than code: each agent has a written list of what starts it (a critical alert, a finished gap review, a partner message, a schedule), each with its own instructions and background, editable from an admin page. Its skills are documents too.
2. Agent Labs keeps a replayable record of everything an agent did and lets staff fix an instruction side by side with the work that exposed the problem.
3. An agent working a task can now pause, wait for rankings to arrive, and pick up where it left off knowing everything it already knew, so research, waiting and mapping happen in one head.
4. Moving our book of agencies onto the platform began on Wednesday: a partner-by-partner script carries clients, keywords with rank history, tasks, notes, locations, Business Profiles, competitors, Google connections and past discoveries, then each agreement onto the new scope model. A written procedure lets anyone on the team move a partner.
5. A Monday retrospective reviews shipped work on two horizons, a two-week pulse for harm and a month for verdicts, so the week’s plan acts on findings the same morning.
6. A shared Task Queue pools implementation work for specialists, and a task can only ever be picked up by one person.
7. A public API opened for staff.