Our engagement ran six workstreams over twelve months. The order was deliberate: foundation first, authority content as the engine, links and entity work as reinforcement.
1. Technical SEO and indexation cleanup (months 1 to 3)
Before writing anything, our team ran crawl and indexation triage, cleaned up canonicals and redirects, fixed template-level duplication, and validated Core Web Vitals, renderability, schema, and internal status codes. The goal was a cleaner indexed-page ratio and less crawl waste on low-value URLs, so that authority we built later would flow to the right pages rather than leak away.
2. Authority content and intent alignment (months 2 to 4)
This is the core of the program and the flagship service. We mapped the SERP intent behind each target query, wrote rewrite briefs for the money pages, and planned a support-page cluster structure around them. The commercial pages were matched cleanly to commercial and transactional intent; the informational content was built to surround and reinforce them.
Over the twelve months the content program produced 63 articles across 8 topic clusters. For a family law practice those clusters map to the real decision journey: divorce and separation, child custody and parenting arrangements, financial settlements and property division, spousal and child support, domestic violence and protection orders, prenuptial and cohabitation agreements, the court process and timelines, and cost, fees and what to expect from a consultation. By month twelve the site was picking up an estimated 1,159 informational keywords, and our internal topical authority index rose from 23 to 71.
The mechanism matters more than the counts. A large, well-structured body of informational content earns topical authority and generates internal-link equity. That equity is what lifts the money pages. The informational articles are the cause; the money-page rankings are the effect. Volume alone would not do it, and depth alone across too few topics would not do it either. It takes both: coverage across the clusters a real prospect researches, and enough depth in each that the content is genuinely useful.
3. Information architecture and internal linking (months 2, 3, 5)
We mapped a hub-and-spoke structure, distributed anchor text sensibly, consolidated cannibalizing pages, shortened the path to conversion pages, and pruned orphaned or weak pages. This is where the fragmented intent from the audit got resolved: duplicate pages were merged or redirected into a single authoritative URL.
4. Entity, schema and LLM presence (months 3 to 5)
We cleaned up Organization and Service schema, aligned author and reviewer entities, checked citation consistency, and built answer-ready summary blocks written to be quotable by AI assistants without making claims the pages could not support. As AI Overviews and assistants like ChatGPT, Claude and Perplexity increasingly answer 'best family lawyer' style questions, structured authoritative content raises the odds of being surfaced and cited. Few local competitors are positioned for this yet, which makes it an early-mover advantage rather than a guarantee.
5. Digital PR, citations and link recovery (months 4 to 6)
Our approach here was conservative: recover lost links, clean up relevant citations, pursue unlinked mentions, and do selective industry resource outreach, all behind a quality threshold. Referring domains grew from 42 to 69 and Domain Rating from 15 to 25 across the year, a gradual curve with no unnatural spikes.
6. Brand voice and editorial QA (months 1, 2, 4)
Every page passed through a reviewer checklist that kept claims inside approved evidence boundaries and blocked risky language before publication. For a regulated profession this is not optional polish; it is what keeps the content trustworthy and compliant.
Data sources: Search Console for clicks, impressions, CTR and position; analytics for sessions and conversions; a third-party tool for Domain Rating, referring domains and visibility. Case value is modeled internally. Figures are internally coherent for scenario modeling and should not be read as verified third-party exports.