Alix programmatic SEO pages
Build the probate search engine, not just another content batch.
A repeatable publishing system that turns official probate research into state pages, Webflow CMS fields, internal links, and performance feedback.
Turning probate demand into a reusable page system.
Build around the questions families already search.
State probate cost, filing fees, small estate thresholds, executor responsibilities, and whether legal support is needed.
Separate source facts from page copy.
The page pulls from a clean source table, not raw research notes. Each fact has scope, source, date, and page-safe language.
Use cost education to show where Alix belongs.
Alix manages estate settlement from start to finish and includes legal support. Attorneys handle legal work; Alix specialists handle the operational estate workload.
The relevant Alix V2 page types are already developed. Now we connect them.
The current work is not a blank-page build. The relevant programmatic page types already exist on Alix V2. The next layer is connecting those developed pages to the research table, Webflow CMS fields, internal links, publishing rules, and performance tracking.
| Page type | Alix V2 staging page | Asana record | Role in the page system |
|---|---|---|---|
| Probate Hub | alix-v2.webflow.io/probate-hub-v2 | CMS template-system ticket | Central hub that routes readers into state, city, cost, executor, glossary, and legal-support pages. |
| Probate State Guide — New York | alix-v2.webflow.io/probate-state-guide-v2 | Direct ticket | State-guide model for jurisdiction-specific probate explanation and service routing. |
| State Cost — California | alix-v2.webflow.io/probate/california/cost | Direct ticket | First state cost model for filing-fee explanation, cost buckets, sources, and Alix support path. |
| City Cost — Los Angeles | alix-v2.webflow.io/probate/california/los-angeles/cost | Direct ticket | City/county layer for local intent when the search and source data justify a local page. |
The page engine has six parts.
Source the state fact
Start from court, statute, fee schedule, or government sources. Capture what the number means and where it applies.
Turn it into fields
State, slug, fee type, source URL, source scope, cost bucket, checked date, page status, and page-safe language.
Assemble page modules
Direct answer, cost breakdown, source section, Alix support section, FAQs, related pages, and schema.
Route the reader
Connect each page to the probate hub, related state/city content, glossary definitions, and service pages.
Push through Webflow
Populate CMS fields, check page rendering, index status, canonical, schema, and source links before launch.
Feed results back
Use search and conversion data to update pages, add sections, adjust internal links, and expand the next cluster.
Research connects to the Alix V2 page layer through CMS fields.
Webflow CMS architecture to connect the developed pages
The internal link system is part of the product.
Probate hub
The entry point. Explains the overall probate journey and routes readers into state, cost, executor, and legal-support topics.
State cost page
Answers the state-specific cost question and separates the court fee from broader estate work.
City or county page
Used when local fee examples, court paths, or local search demand justify a more specific page.
Supporting education pages
Used only when they help the reader understand the state page, such as executor responsibilities, court documents, creditor notices, and settlement steps.
Alix conversion path
Shows how Alix handles the estate settlement workload and includes legal support without overstating the legal role.
The Sheet is the source of truth for page production.
| Production field | What it controls | Client-safe explanation |
|---|---|---|
| State, Abbreviation, URL, Slug, Page Type | Page identity | Creates the state page path and keeps Webflow, the sitemap, and reporting aligned. |
| Primary Keyword, Page H1, SEO Title, Meta Description | Search targeting | Defines the exact query each page is built to answer and how it appears in search. |
| Small Estate Procedure, Small Estate Threshold, Threshold Conditions, Waiting Period | Eligibility context | Explains whether a simpler state procedure may exist, without making the filing-fee page sound like legal advice. |
| Threshold Source URL, Threshold Source Type, Threshold Validation Status | Threshold evidence | Shows where the small-estate information came from and whether it is cleared for page use. |
| Court Fee Type, Probate Filing / Court Fee Summary, Exact Fee Amount, Fee Formula | Court-cost answer | Separates the probate filing fee from the broader cost of probate or estate settlement. |
| County Example, County Example Fee, Fee Source URL, Fee Source Type, Fee Validation Status | Source confidence | Prevents a county example from being presented as a statewide fact unless the source supports that scope. |
| Geographic Scope, Preferred Replacement Source Needed | Publishing control | Flags whether the page can use the current source or needs a better statewide court/government source. |
| Probate Tax Summary, Publication / Notice Cost Summary, Documentation Cost Summary | Cost buckets | Names the other costs families may need to plan for when the data is sourced. |
| Executor Compensation Summary, Attorney / Legal Fee Summary, Bond Summary | Additional cost context | Explains additional possible costs without pretending every estate pays the same amount. |
| Page-Safe Fee Language, Alix Positioning Note, Publish Status, Blocked / Missing Reason, Reviewer Notes | Client-ready page control | Keeps raw research from going live until the source, language, legal boundary, and review status are clear. |
| Field group | Examples | Use on page |
|---|---|---|
| URL and page identity | State, abbreviation, URL slug, page type, canonical URL | Creates the Webflow CMS item and page path. |
| Cost intelligence | Fee type, court fee summary, formula, county example, cost bucket | Builds the state-specific answer and cost explanation. |
| Source support | Official source URL, source type, checked date, geographic scope | Supports claims and tells us when a page needs review. |
| Publishing control | Research status, copy status, Webflow status, index status | Prevents raw research from becoming live content. |
| Connection layer | Hub link, related pages, service path | Turns each page into part of the Alix content network. |
| Content area | Current readiness | Publishing rule |
|---|---|---|
| Court or filing fee section | Ready as a controlled page module | Use with official source and clear scope. |
| Publication and notice costs | Collect before exact claims | Mention conditionally until state-specific support exists. |
| Executor compensation | Collect before exact claims | Use only after the state rule is checked. |
| Bond, appraisal, tax, property work | Collect before exact claims | Explain as possible cost buckets unless sourced. |
| Alix positioning | Ready as page guidance | Lead with Alix as estate settlement service with legal support. |
Publishing is the start of the feedback loop.
Indexation
- Submitted in sitemap
- Indexed or not indexed
- Canonical accepted
- Source date still current
Search movement
- Impressions by query group
- Clicks by page type
- Ranking movement by state
- AI answer visibility prompts
Page quality
- Engagement depth
- FAQ expansion opportunities
- Internal link coverage
- Duplicate or thin-section risk
Business signal
- Consultation path clicks
- Form starts and completions
- Assisted conversions
- Topic clusters creating qualified estate inquiries
We expand by page family, not by dumping pages.
What we need approval to connect next.
Use the developed Alix V2 page types as the presentation layer, connect the research table to Webflow CMS fields, and make the state probate cost system the first scalable page family.