The platform now knows what every client site is built on

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.

A day about knowing the client’s website before touching it, plus a long pass over the staff inbox and the task view.

For our partners

1. The platform now detects the CMS or site builder each client site runs on and shows it on the Website Access page and in the client header.
2. The citation scan now lists the Google, Apple Maps and Bing profiles it finds for a location, so a location whose only listing is its Google profile no longer reads as having none.
3. “Choose sites for me” is now the platform’s pick, ranked by directory authority, and it never orders Google, Apple Maps, Bing or Yelp listings; a hand pick naming one of those is refused with the reason.
4. Competitive gap reviews are on for every workspace, and the setup checklist folds the gap step into the monitoring step.
5. The draft checkpoint added yesterday is now called Newly published content on the approval rules and in the Approvals queue.
6. Activation start dates skip weekends.

1. Site detection

Managers can correct it or ask for a fresh detection, and the connect picker opens on the detected platform when it is one the platform pairs with.

Behind the scenes

1. Site detection no longer asks an AI model about the sites it cannot recognise on its own; unknown now means a human reads it.
2. The staff task view grew up: the campaign’s website in the header, the campaign’s rules in the rail, site logins on the task, and a CMS row.
3. My Inbox got category tabs, a Cleared tab with undo, and paging.
4. Team activity gained a list behind every count, a people picker, a columns picker and totals in the footer, and it now counts a task completed once however many times it was closed.

1. Rules written by hand

Detection started the day asking the model about the sites it could not recognise, and the model kept naming platforms the evidence did not support. So the model is gone. We read every unresolved site by hand (response headers, cookies, where its files are served from, stored logins) and turned each into a rule: fifteen platforms detection had never heard of, sites hiding behind security plugins, parked domains behind redirects. Sites that are code rather than a CMS are named for what they are.