# Build Guide: “Sell My Structured Settlement” ## 1. Build objective Build this as a long-form service and decision-support page within the existing Genex Capital site. Use the supplied written page verbatim; do not replace its headings with headings from this guide. The page must: - Explain selling structured settlement payments before asking the reader to commit. - Present Genex as the direct purchaser, not a broker, lender, law firm or neutral adviser. - Make the free written offer and published phone number easy to reach. - Keep all substantive answers visible on the page. - Use existing site styles, components, lead routing, analytics and global header/footer. - Avoid hard-sell devices, unsupported promises and invented company data. If a new route is required, use: `/sell-my-structured-settlement/` Otherwise retain the CMS-assigned or existing canonical URL. --- ## 2. Content handling rules - Preserve the supplied copy, heading wording, tables, qualifications and disclaimers. - Maintain the supplied section order. - Use one H1 only. Subsequent major sections are H2s; subsections are H3s. - Do not convert substantive content into accordions, tabs, carousels or tooltips. - Do not add a generic FAQ section or FAQ schema. - Do not create a calculator or estimate widget. - Do not add competitor profiles, rankings, comparison logos or outbound competitor links. - Do not invent or independently update: - Discount-rate ranges - Transaction costs - Processing timelines - Cash-advance limits - Approval rates - Client counts - Transaction volume - Company start date - Worker’s compensation eligibility - Testimonials - Use the values in the supplied copy. If a value is held in a verified global site field, use that same field everywhere so repeated facts remain consistent. - Never publish TODOs, bracketed placeholders or unsupported claims. If a value is missing, use an approved existing site value; if none exists, omit that individual fact rather than estimating it. --- ## 3. Page shell and visual system Use the existing site’s: - Header and primary navigation - Footer - Breadcrumb component, if standard on other service pages - Typography - Color tokens - Buttons - Form controls - Card and callout styles - Legal/privacy components - Analytics and consent framework Recommended layout: - Maximum content width: the site’s standard wide container, approximately 1120–1200px. - Normal prose measure: approximately 720–820px. - Tables, comparison blocks and the hero may use the full container. - Desktop section spacing: 64–88px. - Mobile section spacing: 40–56px. - Use restrained neutral backgrounds to separate major sections. Do not alternate every paragraph or create excessive cards. Do not use: - A stock photo of a smiling couple or family - Cash, check or oversized dollar imagery - Countdown timers - Pop-ups triggered on entry or exit - Fake chat notifications - Star ratings not supported by visible, verified review data - “Instant cash” styling or language Omit hero imagery. The headline, explanation and form should be the first-screen focus. --- ## 4. Page assembly ### A. Hero: meaning, eligibility and written offer Build the opening as a two-column hero. #### Desktop - Left column: approximately 58–62%. - Right column: approximately 38–42%. - Vertically align the form card near the top of the text column. #### Left column Place, in this order: 1. Breadcrumb, if the site normally displays one. 2. H1. 3. Opening definition explaining what selling the payments means. 4. The short eligibility/can-you-sell passage. 5. The three short facts as a visible list: - Selling part or all - Availability nationwide - Required court approval 6. Published phone number as a prominent `tel:` link. Use the exact language from the supplied copy. Do not add “guaranteed,” “approved today,” “same-day” or similar claims. #### Right column Use the site’s existing production lead-form component in a bordered or lightly elevated card. Give the form wrapper this anchor: `id="written-offer-form"` The form heading and submit label must clearly refer to requesting a free written offer. #### Mobile order 1. H1 and opening copy 2. Eligibility list 3. Phone link 4. Offer form 5. Trust strip Do not place the form before the H1 on mobile. --- ### B. Trust strip Place one compact proof strip immediately below the hero, outside the two-column grid. Display the facts in this order: 1. Direct purchaser 2. Year purchasing began 3. Clients served 4. Total payments transacted 5. Court-approval success rate 6. BBB rating Requirements: - Use only values provided in the written page or verified global site data. - Include a visible, concise “company-reported” attribution applying to the company statistics. - Do not imply that approval is guaranteed. - Render as a semantic list, not a decorative image. - On desktop, display in one compact row when space permits. - On smaller screens, wrap into two columns or a single stacked list; do not reduce text until unreadable. --- ### C. Eligibility and payment types Build the section covering who can sell and what payment types are considered as a standard text section. Structure: 1. H2 and introductory paragraph. 2. Payment types as a two-column list on desktop and one column on mobile. 3. Separate short paragraph for life-contingent payments. 4. State-law paragraph with an inline link to the site’s state page hub or relevant state directory. Do not add state-by-state legal details here. Link to existing state resources rather than reproducing statutes. If the copy discusses guardians, conservators, minors, inherited payments or payment ownership, keep those qualifications in normal body text where supplied. --- ### D. Partial sale options Use the section about selling some payments or all payments as a distinct full-width content block. Build: 1. Introductory paragraph. 2. Semantic comparison table for the three partial-sale structures: - A block of scheduled payments or years - A share of each payment - One or more future lump sums 3. Paragraph explaining how nearer and later payments affect price. 4. The short line about how payees commonly structure a sale, styled as a restrained note rather than a quotation. The table must use real table markup with headers. Do not recreate it as an image. If the supplied content includes a payment-timeline illustration, render it as a simple accessible HTML/CSS figure. Any visual shading is supplementary; all meaning must remain in the adjacent text and table. Do not invent payment amounts or dates for a decorative graphic. --- ### E. Pricing and worked example This is the page’s main information section. Give it a subtle background change or stronger section divider, but retain the site’s normal visual language. Build the subsections in the supplied order: 1. Discount-rate explanation 2. Factors affecting the rate 3. Worked numerical example 4. Fees and costs 5. Offer-quality checklist 6. Best-price promise 7. Sale-versus-loan explanation #### Factors list Render each pricing factor as a short list item. A two-column list is acceptable on desktop, but keep the reading order logical. #### Worked-example box Place the example in a clearly labeled neutral card. Include: - A visible “illustrative example” label - The payment schedule - Total face value - Illustrative discount rate - Resulting lump sum - Difference between the face value and current lump sum - Partial-sale comparison, if included in the supplied copy - The supplied qualification that it is not an offer and remains subject to underwriting and court approval Use semantic table markup. Preserve the writer’s figures exactly; do not recalculate or substitute numbers. #### Fees Keep the explanation in prose. Make the distinction between the discount and any separately itemized fees easy to scan. Do not add “no fees” language unless the supplied copy expressly supports it. #### Offer checklist Render as a checked list, not a form. Each item must remain visible, including: - Payments being sold - Gross purchase price - Net amount received - Discount rate - Itemized fees - Conditions under which the amount might change #### Best-price promise Use a bordered informational callout directly after the offer checklist. Requirements: - Keep every qualification from the supplied copy next to the claim. - Link “terms,” “published terms” or equivalent wording to the site’s live best-price-promise terms page. - Do not shorten the promise into an unqualified badge or headline. - Do not display the promise without its terms link. #### Sale, not a loan Keep this as body copy, not a promotional banner. Do not use loan-related schema or label the offer form as a loan application. --- ### F. Process section Render the transaction process as an ordered vertical stepper. Use a semantic `
    ` with one step per supplied stage. Each step must contain its full explanatory text, not merely a title. The order should follow the written content from sharing payment information through insurer acknowledgment and funding. #### Desktop - Vertical line and numbered markers may be added decoratively. - Text remains in the DOM as normal headings or bold step labels plus paragraphs. #### Mobile - Use a simple stacked numbered list. - Do not place essential wording inside SVGs or background graphics. #### Disclosure-statement block Following the steps, render the disclosure terms in a boxed definition list: ```html
    Term
    Plain-language meaning
    ``` Include all terms supplied by the writer. Do not hide definitions behind tooltips. #### Timeline Render the realistic timing explanation as normal prose. Any stated range must retain the adjacent court-dependent qualification. #### Cash advance Use a visually quiet callout, not a promotional banner. Keep the following qualifications immediately adjacent to the advance statement: - Availability is not guaranteed - Subject to eligibility and underwriting - Subject to documentation and individual circumstances - Deducted from the final lump sum, where the supplied copy says so Do not use “instant cash,” “cash today” or an unqualified amount in a button. #### Changing one’s mind Keep this as a visible paragraph after the advance callout. Do not convert it into fine print. --- ### G. Court approval section Build this as one H2 section with the supplied H3 subsections. The section must visibly include: - Why protection laws require court review - The judge’s best-interest determination - Factors the judge considers - Reasons commonly accepted or questioned - Hearing location and appearance logistics - What the reader may need to bring - Whether independent counsel is required or advisable - Clarification that the buyer’s lawyer represents the buyer Render the judge’s factors as a short bullet list inside the relevant subsection. If the approval success rate appears here, preserve its “company-reported” attribution and the statement that approval is the judge’s decision and is never guaranteed. Do not add statute numbers or state-specific filing instructions. --- ### H. Decision section Build the “keep versus sell” content as a comparison section. #### Comparison table Use a two-column semantic table with headings equivalent to the two choices in the supplied copy. Preserve all comparison rows. On mobile: - Allow horizontal scrolling within a labeled table wrapper, or - Stack rows with both column labels repeated visually. Do not remove either side of a comparison to make it fit. #### Decision test Keep the practical comparison between the offer’s discount rate and the cost or realistic return of the intended use in body copy immediately after the table. Do not turn it into personalized financial advice or an automated calculator. #### Common reasons Render the reasons for selling as a compact bullet list. #### Lump-sum plan, taxes and benefits Keep these as separate visible subsections or paragraphs: - Planning the use of the lump sum - Tax treatment - SSI, Medicaid, SNAP or other need-based benefits Preserve all “generally,” “may,” professional-advice and individual-circumstance qualifications. Do not add tax or legal guarantees. --- ### I. Choosing a buyer Build the buyer-selection section in this order: 1. Explanation of direct purchasers versus brokers 2. Red-flag list 3. Questions-and-answers table 4. Genex proof block #### Red flags Use a restrained warning treatment with an icon from the existing design system. Keep every red flag visible as a list item. Do not use sensational “scam alert” graphics. #### Questions and answers Use a two-column table: - First column: question to ask - Second column: Genex’s supplied answer Do not turn the table into an accordion. Keep qualifications about changing offers, timing, fees and the best-price promise intact. #### Proof block Use a concise card or bordered panel containing the supplied company facts. - Use the same shared fact values as the hero trust strip. - Include the A+ BBB rating in text. - Use the existing approved BBB asset if one already exists in the site library. - If using the BBB image, give it descriptive alt text and link it to the verified BBB profile. - If no approved BBB asset exists, use text only. - Include client quotations only when they are in the supplied page or an approved CMS testimonial record. Preserve attribution. - Do not manufacture quotations, initials, locations, star scores or review counts. --- ### J. Final action section Finish with a visually distinct but restrained CTA section. Include: 1. Final H2. 2. Supplied paragraph explaining why an individual schedule is needed for an accurate written offer. 3. Primary button linking to: `#written-offer-form` 4. Published phone number as a `tel:` link. 5. The supplied invitation to compare a qualifying written competitor offer. 6. Reminder about court review and the right to independent advice, where included in the written copy. Do not create a second independently coded form. The final primary CTA should return focus to the production form at the top. Use smooth scrolling only when the visitor has not enabled reduced-motion preferences. After activation, move keyboard focus to the form heading or first invalid/empty field. --- ## 5. Offer form requirements Reuse the existing live lead-form component and its existing: - Submission endpoint - CRM integration - Lead routing - Spam protection - Consent language - Privacy link - UTM and source capture - Error handling - Success state - Analytics conventions Do not create a mailto form or a disconnected front-end-only form. The form must collect the information represented in the supplied page: - Type of payments - Payment amount - Number of payments or remaining payment term - Start date or next due date - State - Full name - Phone - Email Use the existing approved option lists for payment type and state. Do not add an unsupported payment category. Implementation details: - Every control needs a persistent visible label. - Use `inputmode="decimal"` for payment amount where appropriate. - Use an appropriate date input or the site’s accessible date component. - Allow “not sure” where the existing production form supports it; do not force visitors to invent payment details. - Use autocomplete attributes for name, telephone and email. - Validation errors must appear beside the relevant field and in an accessible summary. - The error summary should receive focus after an unsuccessful submission. - The success message must confirm receipt without implying a guaranteed offer, transaction or court approval. - Do not request a Social Security number, bank details or document upload in this initial form. - Submit-button language must refer to a free written offer. Use the exact CTA from the supplied copy; otherwise use “Request My Free Written Offer.” - Keep the supplied no-cost, no-obligation and follow-up explanation directly beneath the button. - Retain any required TCPA or communications consent language from the existing live form. Do not pre-check consent boxes. --- ## 6. Links and anchors Use real site URLs; do not leave placeholder links. Required links where the corresponding words appear: - Published phone number → `tel:` URL - State-law passage → existing state page hub or state directory - Best-price promise → full published terms - Form privacy language → privacy policy - BBB proof, if linked → verified BBB profile - Final CTA → `#written-offer-form` Internal section anchors may be generated from the writer’s final headings, but do not add a separate table of contents unless the site already uses one for comparable long-form service pages. All anchored headings need sufficient `scroll-margin-top` to clear the sticky site header. --- ## 7. Responsive behavior ### Hero - Two columns at the site’s desktop breakpoint. - Stack at tablet/mobile widths. - Do not squeeze the form beside the text below approximately 900px. ### Lists - Two-column lists may collapse to one column. - Preserve DOM reading order. ### Tables - Keep native table semantics. - Wrap wide tables in a region with horizontal overflow. - Provide a visible or screen-reader caption identifying each table. - Do not reduce table text below the site’s normal readable body size. - Ensure the shadow or border indicates when more columns can be scrolled into view. ### Trust strip - One row on wide screens. - Two-column wrap or single-column stack on small screens. ### Stepper - Vertical at all sizes. - Remove decorative connector lines if they create crowding on mobile. ### Calls to action - Keep buttons full-width inside the form on mobile. - Do not add a fixed bottom bar if the site does not already have an approved one. - Never obscure form controls, legal copy or table content with sticky elements. --- ## 8. Accessibility Meet WCAG 2.2 AA using existing site standards. Required: - One H1 and logical heading nesting - Semantic lists, tables, ordered steps and definition lists - Keyboard-operable forms and links - Clearly visible focus states - Form labels not dependent on placeholders - Accessible error and success announcements - Minimum target sizes consistent with site standards - Sufficient text and control contrast - Descriptive link wording; avoid repeated unlabeled “learn more” - `tel:` links that expose the readable phone number - Decorative icons marked `aria-hidden="true"` - Meaningful alt text for the BBB asset or any non-decorative image - No essential information contained only in color - Respect for `prefers-reduced-motion` - No automatic focus movement except after an initiated anchor action or form validation/submission event All legal, pricing, court and qualification text must be available to screen readers and visible to sighted users. --- ## 9. SEO and metadata Use the writer-supplied SEO title and meta description if present. If no dedicated SEO title is supplied, use: **Sell My Structured Settlement | Free Written Offer From the Buyer, Not a Broker** Technical requirements: - Self-referencing canonical URL - Index/follow unless the existing environment specifies otherwise - H1 rendered as text, not an image - Open Graph and social title/description based on the approved SEO metadata - No keyword tag - No hidden keyword blocks - No duplicate H1 in the hero form or header - Preserve the exact search-relevant wording naturally present in the written copy ### Structured data Use JSON-LD consistent with existing site entities: - `WebPage` - `BreadcrumbList`, if breadcrumbs are visible - `Service` For `Service`: - Reference the site’s existing `Organization`/Genex entity as `provider` - Use a visible service description - Use `areaServed` for the United States only if the page visibly states nationwide service - Do not add a fixed price or `Offer` amount - Do not use `LoanOrCredit` - Do not use review or aggregate-rating properties unless identical verified information is visibly shown - Do not add FAQ schema --- ## 10. Analytics Use the site’s existing event names and data layer where available. Track at minimum: - Hero form view - Form start - Form validation error - Successful form submission - Primary CTA click - Final CTA anchor click - Phone-link click - Best-price terms click - State-page link click Pass the page path and CTA location, such as `hero`, `pricing_callout` or `final_cta`, without sending payment amounts or other form-entered personal information into analytics. Preserve UTM parameters and the original landing-page value through submission. --- ## 11. Performance - Do not add a large hero image or video. - Use existing SVG icons rather than icon libraries loaded only for this page. - Keep the form’s required JavaScript in the initial page load, but defer unrelated scripts. - Reserve space for the form and any BBB image to avoid layout shift. - Use the site’s existing optimized font setup. - Do not embed third-party review widgets if the same proof can be rendered from approved site content. - Keep decorative effects CSS-based and lightweight. --- ## 12. Compliance and publication checks Before publishing, verify: - Genex is consistently described as the direct purchaser. - No language describes the transaction as a loan. - The discount rate, fees and net amount are discussed as written. - No approval or funding date is guaranteed. - Court approval is clearly required. - The approval success rate is attributed and paired with a non-guarantee. - The best-price promise links to its full terms. - The cash-advance qualification appears immediately with the advance claim. - Tax and benefits language retains its qualifications. - State-law differences are linked out rather than expanded into unsupported state advice. - The buyer’s lawyer is not presented as the reader’s lawyer. - Every company statistic matches the approved source. - The same phone number appears in the hero and final CTA. - The top form submits to the production lead workflow. - No placeholder links, data or testimonials remain. - All tables and process answers are visible without interaction. - There is no calculator, competitor ranking, collapsed FAQ or intrusive promotional overlay.