The starting point

The association’s site carries a lot: annual conferences, courses and workshops, membership and fellowship forms, a partners directory, photo galleries and a page for each regional chapter. The new build had gone live, but many of those pages didn’t hold up on a phone.

Grid pages didn’t match the approved HTML and CSS, mobile fonts were too small to read, the registration form and its OTP popup broke on mobile, and long gallery titles were stuck inside image sliders. Search titles were generic too. 27 pages carried titles with the site name tacked on twice, the way “Contact Us | Society | Society” reads.

What we did

  1. Logged every issue in one tracker Each task got an ID, priority, page or section, reference links, a screen recording or screenshot, and links to the matching Figma frames. The developer marked status, completion date and what was fixed.
  2. Fixed the layouts first Between March 20 and March 24, 2025, the developer closed the first 17 high-priority tasks: conference, course, event and chapter grids, team card hover effects, gallery and chapter detail pages, the fellowship table (now scrolls sideways instead of squeezing), and membership and partner pages.
  3. Fixed forms and registration The tracker logged fixes for the conference and course registration forms: required and optional field markers, an option to remove a profile photo, a designed error page and a responsive OTP popup. The developer marked each one done.
  4. Logged the remaining items Later rows covered a partner logos section on the 2025 conference registration page and video carousels that looped during playback, then a member dashboard, blog templates, a certificate PDF design and a program details page. The tracker shows these closed, though the dashboard row notes two pages still needed HTML design.
  5. Rewrote titles and meta descriptions We wrote titles and meta descriptions for 127 URLs, with character counts. Most were built from a template, and the 4 main pages got hand-refined versions. The sheet covers chapter pages (26), events and academics (24), conferences (19), workshops (14), event galleries (13), courses (8) and the main pages.

Delivered

  • Front-end QA tracker with 25 tasks marked completed
  • Tracked responsive fixes across conference, course, event, chapter, fellowship, membership and partner pages
  • Tracked registration form and OTP popup fixes
  • Tracker items for a partner logos section, member dashboard, blog templates, certificate PDF and program details
  • On-page SEO sheet: templated titles and meta descriptions for 127 URLs, hand-refined for the 4 main pages

Why the tracker mattered

A society site has many stakeholders and a lot of near-identical pages. Logging each fix against a live URL, a recording of the bug and the matching Figma frame meant nobody had to describe a problem twice. The first 17 high-priority tasks were assigned on March 20 and 21 and closed within two to three days.

The SEO pass came after the layout fixes for the same reason. There’s little point sharpening a chapter page’s title while the page itself breaks on a phone. Our website design and development work usually runs in that order.

What we’d point out

This study reports work completed, not search results. We don’t have before-and-after ranking or traffic data for this project. The title and meta sheet shows what we wrote; it doesn’t by itself show when each change went live.

The tracker also held 8 empty placeholder rows marked not started, which aren’t in the count of 25. One of the 25 completed rows has a blank description, and three have no dates. For organizations with large page counts, a sheet-driven SEO pass like this one is usually the quickest way to fix titles at scale, though templated titles still need a human check.