How Findem migrated 500 pages in a week and now runs SEO and AEO overnight

Findem’s marketing team has 10 to 15 people across content, customer marketing, product marketing, and operations. Their website carries a lot of that work: about 300 blog posts, 27 customer stories, 20 guides, 20 webinars, and 50 to 60 static pages, plus campaign pages. Around the turn of 2026, Findem refreshed its brand, and a developer rebuilt the whole site on a new design system in Webflow.

Findem’s business moves fast, and its website had to keep up.

On Webflow, fixing a bug, building a new page, or running a CRO test meant a developer request and an Asana task. Those changes took weeks, if not months, and new Webflow features meant learning another tool or paying extra.

Ideas such as AEO tracking, ongoing SEO work, and campaigns to drive Studio signups and demo requests stayed on the list because there was no way to scale them. Findem had two options: keep filing developer requests and wait, or add more point tools, each with its own setup and cost.

Then Liv Anderman, Findem’s CMO, asked whether Webflow was still the right home for the site. Findem had experimented with Lovable and other web design tools the year before. After conversations with Ploy, Austin started a trial to see what Ploy could do with Findem’s own site.

Findem had always had a healthy site for SEO, and the team did not want to lose that visibility or the new design. Austin gave Ploy the sitemap and source code and asked it to start building. Ploy recreated the site one to one, new design system included, and three months of experimentation turned into about a week of migration.

Before the cutover, Austin checked the server settings, Google tags, cookie consent, and every form. Ploy told him exactly which tags to fix, which URL to open, and which steps to take, then tested each fix. The next day, his colleagues could not tell what had changed. Every page on the Findem site is now served by Ploy, and Austin rates site health as “even better than when we were on Webflow.”

Finding pages to improve used to mean exporting a Google Analytics report and cross-referencing it against Webflow. Now Ploy queues recommendations every night. When Austin wakes up, chats are waiting for his approval or input.

Some recommendations come from changes on the site, such as updated content that other pages should reflect. Others come from visitors. When someone requests a demo, Ploy suggests how to improve the experience for other prospects on the same path.

In one session, Ploy used traffic and Semrush data to find high-traffic blog posts with no clear CTA. Austin added links, CTAs, and buttons to those posts and pushed them live in about 15 minutes.

Austin runs always-on projects in Ploy, each with its own job. One tracks AEO: the prompts Findem shows up for, where it is cited, its mention rate, and how competitors compare. Another handles ongoing SEO optimization and content. Others focus on driving Findem Studio signups and demo requests.

Plenty of point tools sell AEO tracking on its own. Findem runs that tracking in Ploy, where it already edits the site, without a second tool. Ploy connects to Google Analytics, Semrush, HubSpot, Slack, Google Drive, and Gmail, so Austin asks for the data he needs in a prompt.

On Webflow these projects stayed ideas because there was no way to scale them. Now Ploy proposes each change, and Austin approves it or asks for another pass. “Ploy is telling me how I can do that, and I’m just saying, ‘Looks good’ or ‘no, needs a change,’” he said.

As Studio changes, the paths into it have to change too. Austin prompts new pages directly against Findem’s design system. In a single week, he created two versions of one landing page and two more landing pages for individual Studio agents.

Austin gives Ploy a draft and asks it to get the post live. Ploy adds the internal links, includes the post in the sitemap, and makes it visible to Google. “It’s done in about five minutes, and it saves us so much time,” he said.

Sales wanted prospects to filter Findem’s customer stories by industry and company size. Austin connected Ploy to the Findem MCP, the same connection Findem customers use to bring Findem’s people and company data into their own AI tools. Ploy pulled each customer’s industry and headcount directly from Findem, and Austin built the filters in 20 minutes. He called it “a really quick win that would’ve taken us weeks to implement otherwise.”

Ploy surfaces account-level intent signals and ties site activity to Google Analytics. A weekly Slack digest lists those signals with follow-up recommendations that Austin shares with sales.