Four community listings were read for this playbook and all four had the same faults: the stray word "testtest" in the Neighborhoods section of the page text, a "Weight Limit (lbs)" pet label with no value, and an FAQ line ending "to reach a resident at (community)..". Two had an FAQ saying the community "offers Studio" while the pricing section on the same page lists more room types. These are the pages families land on from search, and the new VP of Strategic Account Management is being hired to "Drive more complete, accurate, and current community information across the network". With 11K+ communities and 5K+ agencies, nobody can check this by hand.
First action
Open five community listings in a browser, check whether "testtest" is visible under Neighborhoods, and compare each FAQ's room types with its pricing table.
How to measure it
Clean-listing rate (500-page sample)
- Now
- –
- Target
- From baseline to 90%
- By
- 90 days
Steps
Confirm in a browser
Check five listings by eye: is the test text visible or only in the page source, and do the FAQ and pricing table disagree? Record screenshots as the baseline.
Staff Software Engineer, Web 2 hours
Fix the template faults
Remove the test string, hide labels with no value, fix the doubled full stop and the FAQ wording "to reach a resident". One change clears every listing.
Staff Software Engineer, Web 2 days
Audit a 500-listing sample
Inputs: sitemap URLs and the rendered pages. Count each fault type so the team knows which checks matter most.
Staff Software Engineer, Web 1 week
Build the contradiction checks
Compare FAQ room types with pricing rows, review totals across page sections, and amenity pairs that cannot both be true. Each finding stores the page, the two conflicting values and a suggested correction.
Staff Software Engineer, Web 1 week
Route findings to owners
Template faults open one engineering ticket. Data gaps appear in a per-provider queue next to the account record in Salesforce and PartnerCentral, so the account manager sees them before the next call.
Senior Account Manager 1 week
Keep a person on approval
Account managers confirm the correct value with the provider and approve the change; nothing is published unreviewed.
Vice President, Strategic Account Management ongoing
Run nightly and report
Schedule the run, alert on any new sitewide fault within a day, and report the clean-listing rate and median days to fix each month.
Vice President, Strategic Account Management monthly
Why it works
Build a nightly checker for listing pages. Inputs: the three community sitemaps and the home care sitemaps, the rendered page, and the listing record behind it. Checks: (1) template faults that appear on every page (leftover test strings, empty labels, doubled punctuation); (2) contradictions inside one listing (FAQ room types against the pricing table, operator review totals that differ, "Complimentary Transportation" beside "Transportation at Cost"); (3) missing data (no floor plans, no weight limit, truncated description). Outputs: template faults go as one ticket each to the web team; data gaps go to a queue per account manager, grouped by provider, with the exact field to ask for. A person approves every listing change before it is published; the checker never edits a listing itself. The first run is a one-off audit of a sample of 500 listings so the size of each problem is known before anything is automated.
Template faults are fixed once and vanish from thousands of pages, so the first week pays for the build. Contradictions between an FAQ and the pricing table are the kind of error that makes a family doubt the whole listing, and they are easy for software to spot and hard for a person to spot at scale. The data-gap queue gives each account manager a concrete, provider-specific request, which is exactly what the new account leadership role is asked to deliver.
Ready to use
ChecklistListing checker rules, first version
[ ] No test or placeholder strings in page text [ ] No label shown without a value (for example pet weight limit) [ ] FAQ room types match the pricing table [ ] Operator review total is the same everywhere on the page [ ] No amenity pair that cannot both be true [ ] FAQ phone line says who answers the call [ ] Description not cut mid-sentence without a working Read more [ ] Photo and floor plan counts match the gallery [ ] Each finding names the page, both values and the owner
Risks and how to handle them
The test text is hidden from visitors and only in the page source
Still remove it: search engines and AI systems read the source, and the contradiction checks stand on their own.
The queue floods account managers
Cap it at the five highest-traffic listings per provider per month.
The checker flags correct data
Track false positives per check and retire any check above 10%.
Evidence
- Your websiteFour community listings read on November 16, 2026 (Michigan and Alabama, 43 to 116 reviews each): in all four, the page text an automated reader receives has the stray word "testtest" under "Neighborhoods around ..."; all four list a "Weight Limit (lbs)" pet label with no value; and all four FAQs end "Call (number) to reach a resident at (community).." with a doubled full stop. One listing was fetched twice with the same result.Source
- Your websiteListing FAQs that contradict the listing: one Michigan community's FAQ says it "offers Studio" while its own pricing section lists Studio, 1 Bedroom and 2 Bedrooms; an Alabama community's FAQ says "offers Studio" while its pricing lists Studio and Semi-Private and its description mentions "studio and deluxe studio". Operator review totals also differ within one page (27,879 in one place, 27,866 in another), and both "Complimentary Transportation" and "Transportation at Cost" appear on the same listing.Source
- HiringVice President, Strategic Account Management (posted November 5, 2026): leads "approximately 10 account managers focused entirely on APFM's existing senior living provider network"; will "Drive more complete, accurate, and current community information across the network", "Build a provider performance scorecard and account planning process" and "Own provider NPS for the network", connecting "APFM referrals to move-ins, occupancy, and revenue".Source
- HiringStaff Software Engineer, Web (posted November 11, 2026): "Millions of families start their senior care search on our site", "most of them arriving through organic search (SEO) and paid search (SEM)"; the site is "the front door of our business". The role owns "mobile-first performance and Core Web Vitals", technical SEO ("crawlability, indexation, structured data, canonicals"), experimentation, and evolving "our headless CMS (Sanity) so content and marketing teams can ship pages without engineering bottlenecks".Source