Introduction
In early 2025, the seoplus+ web team began exploring ways to improve how client-provided content was collected for website projects. Historically, this process relied on a lengthy Google Doc template that was difficult to create, overwhelming for clients to navigate, and prone to technical issues like browser crashes.
To address these challenges, I launched a pilot using Content Snare, a structured content collection tool, during a redesign project for Aetna Pest Control. Working alongside our Project Manager, we configured and deployed a customized Content Snare template built directly from approved wireframes. This initiative aimed to streamline content handoff between clients, designers, and developers, and ultimately reduce friction across departments.
Download Case StudyThe pilot ran from March to April 2025, gathering more than 20 pages of content and client-provided images.
Goals
The primary goal of this initiative was to replace the cumbersome Google Doc–based content collection process with a more efficient, structured, and user-friendly solution.
More specifically, the objectives included:
- Improving efficiency for designers when creating and implementing content templates.
- Providing a significantly better and more intuitive client experience.
- Reducing the number of content revisions and ensuring content no longer broke approved design sections.
- Standardizing the content handoff process across web projects.
- Increasing accuracy and clarity of client-provided content.
- Addressing recurring internal pain points identified by designers, developers, PMs, and clients.
- Supporting a larger, ongoing effort to refine and modernize the seoplus+ web process.
Challenges
Before adopting Content Snare, the team relied on a large Google Doc template that presented several major obstacles across departments:
User and team pain points
- Difficult and time-consuming for designers to customize for each project.
- The size of the document often caused browser lag or crashes for both team members and clients.
- Hard for clients to navigate, leading to confusion and frustration.
- Challenging for PMs to track progress, updates, or completed sections.
- Difficult for designers to identify what content has been updated or still needs revision.
Impact on projects
These issues contributed to slower implementation of client-provided content, increased follow-up time, and frequent back-and-forth for clarification. As a result, project timelines often experienced delays and a less-than-ideal experience for both clients and internal teams.
Initial barriers
Moving to Content Snare required upfront testing, a small client learning curve, and internal alignment to adopt a new tool. It also required team buy-in to deviate from the long-established Google Doc workflow.
Preview of solutions
I created standardized Content Snare templates, embedded detailed instructions, and introduced a structured content vetting workflow to ensure content aligned with approved wireframes.
Approach
The solution involved replacing the traditional Google Doc content template with a fully-configured Content Snare setup.
Research & selection
After evaluating the recurring issues with the Google Doc system, Content Snare stood out for its:
- Structured, user-friendly interface
- Built-in guidance and field validation
- Real-time progress tracking
- Strong alignment with client usability needs
Building the template
Using the approved wireframes for Aetna Pest Control as a foundation, I developed a detailed Content Snare template that:
- Organized content requests by page and section, including fields for copy, CTAs, and client-provided images.
- Added character limits, visual examples, and clear instructions to ensure content matched design requirements.
Client enablement
To support adoption and ease-of-use:
- A walkthrough video was recorded to guide the client through the process.
- Conducted internal testing before sending it to the client to ensure clarity and functionality.
Workflow integration
To align the process with project delivery:
- Coordinated with our Project Manager to assess client readiness and monitor submission progress.
- Reviewed content as it was submitted to ensure it aligned with design needs.
- Designers were able to begin content implementation shortly after submission without major revisions.
Iteration
Throughout the test, I refined the template by adjusting character limits, updating field instructions, and adding visuals to make sections even easier to understand.
Results
The Content Snare pilot produced clear and measurable benefits across the entire web process.
Key outcomes
- Client completed all content within one week of beginning the process — significantly faster than typical timelines using Google Docs.
- The clearer structure resulted in fewer revisions and far fewer content-related design issues.
- Client feedback indicated they found the tool easy to use once they got started.
Quantitative improvements
- 8+ hours saved for the designer during content implementation into mockups.
- Reduced PM follow-ups due to clearer progress tracking.
- Designers saved time previously spent reformatting or resizing client-provided images
- Content adhered to character limits and section structures, resulting in near-perfect compatibility with the design.
Team-level impact
- Designers: Faster, cleaner, more efficient content workflow with minimal rework.
- PMs: Clearer tracking and drastically fewer follow-ups.
- Developers: Received well-formatted, accurate content that matched design specifications, improving build efficiency.
Game-changer doesn’t even cover it. Content Snare has tightened up the handoff between writers and designers, cutting the back-and-forth and making it easier for both teams to do their best work.
Organizational impact
Based on the success of this pilot, Content Snare is now being incorporated into the standard seoplus+ web process and is being considered for broader use in future projects.
Conclusion
This case study demonstrates the significant impact that thoughtful process improvements and tool adoption can have on both internal workflows and client experience. Implementing Content Snare reduced friction across teams, accelerated timelines, and increased the accuracy and quality of client-provided content.
By modernizing a longstanding pain point in the web process, this initiative sets a strong precedent for future website projects. It highlights the importance of testing new tools, embracing designer-led innovation, and prioritizing both internal efficiency and client usability. As we continue to refine the template and expand the tool into more projects, this improved workflow is positioned to deliver consistent, scalable benefits across the entire web department.
