Sell My Structured Settlement” Service Page

Part 1Build objective

1. Confirm that selling payments is possible.
2. Request a free quote immediately.
3. Understand how the lump sum, discount and fees are calculated.
4. Decide whether to sell all, part or none of the payments.
5. Understand eligibility, court approval, timing, taxes and benefit implications.
6. Evaluate the company and take action.

Use the supplied written page verbatim wherever possible. Match content blocks by meaning rather than expecting the headings in this guide to match the writer’s headings.

Do not turn this into a blog post, buyer comparison, state-law guide or FAQ page.

Part 2Site and theme integration

• Use the site’s existing header, footer, navigation, breadcrumb system, typography, color tokens, spacing, buttons, form controls and card styles.
• Reuse the site’s existing quote form, phone-number component, CRM integration, consent language, privacy link, validation, analytics and spam protection.
• Do not create a disconnected landing-page design or introduce a second visual system.
• Use the current page URL if this replaces an existing page. If no route has been assigned and no equivalent live page exists, use /sell-structured-settlement/.
• Preserve any existing global legal notices, accessibility widgets and tracking scripts.
• Use the site’s standard content container. Keep ordinary prose to approximately 65–75 characters per line; tables, grids and forms may use the full container width.

Part 3Content handling rules

• Render all substantive content in the written page. Do not shorten, summarize or hide important explanations.
• Keep the major sections in the order specified below.
• Use exactly one H1, in the hero.
• Use H2s for the eight main informational sections and the closing CTA if its copy includes a heading.
• Use H3s for named subtopics within sections, such as the disclosure statement, court approval and legal advice.
• Preserve the writer’s headings rather than replacing them with headings from this guide.
• Do not create an FAQ section or place content in accordions. The reader must be able to see the answers while scrolling.
• Do not invent rates, ranges, examples, fees, timelines, ratings, years in business, review counts, licensing claims or other company facts.
• Do not strengthen timing language into claims such as “cash today,” “instant cash” or “funding in days.”
• Do not add competitor names, ranked buyer lists, detailed state statutes or post-sale reversal advice.
• Do not leave unresolved placeholders on a published page.

Part 4Page structure and component map

Build the page in this exact semantic order.

A. Hero: opening explanation and quote request

Use a two-column hero on desktop:

• Left column, approximately 55–60%
  • Breadcrumb, if the site normally uses one.
  • H1.
  • The short opening passages explaining:
    • That some or all payments can be sold for a lump sum.
    • That the transfer is court approved.
    • That the quote is free and carries no obligation.
    • What a structured settlement is and why buyers exist.
  • Clickable phone number.
  • Business hours.
  • Spanish-language phone note only if the company actually provides that service.
• Right column, approximately 40–45%
  • Quote form in a visually distinct card.
  • Brief reassurance or privacy text supplied with the written page.
  • A compact trust line below the form.

Do not place a photograph or illustration in the hero. The form is the hero’s primary visual element.

On mobile:

1. H1 and opening explanation.
2. Phone contact.
3. Quote form.
4. Trust line.

The form should appear before the first informational H2.

Hero quote form

Use the existing production form and submission flow. It must not be a mock form or a mailto: action.

The form should collect the supplied equivalents of:

• Whether the person wants to sell all payments, some payments or is unsure.
• Payment amount.
• Number of payments or remaining payment term.
• Next payment date.
• Payment issuer, if requested by the company.
• State.
• Name.
• Phone.
• Email.
• Existing required consent and privacy fields.

Use persistent visible labels, not placeholder-only labels. Use appropriate input types, input modes and autocomplete attributes.

Primary submit label: “Get my free quote”, unless the site has an approved equivalent already used for the same quote flow.

Form behavior must include:

• Inline, programmatically associated validation.
• Clear required-field indicators.
• A disabled/loading state during submission.
• A clear success state and next-step explanation.
• Preservation of entered data after a validation or server error.
• Existing CRM, lead-routing, UTM capture, analytics and spam controls.
• Existing TCPA or communication consent language without modification.

Give the hero form a stable anchor such as id="quote-form" so later CTA buttons can return to it.

Hero trust line

Display only supplied, verified facts, such as:

• Years purchasing payments.
• Direct-buyer status.
• BBB rating or accreditation.
• Industry association standing.

Use text or approved site assets. Do not download or recreate a BBB or association badge. Omit any proof point not supported by the written content or approved site data.

B. Amount and pricing section

This is the most visually developed informational section. It must contain, in the order presented by the writer:

1. Explanation of present value and what determines the lump sum.
2. Explanation of the discount rate and how buyers earn money.
3. A compact list of the main rate drivers.
4. The worked sale example.
5. A CTA under the example.
6. Explanation of the gap between face value and the amount received.
7. Fee information.
8. A checklist for comparing offers.

Rate-driver list

Render the rate drivers as a three-item list or three compact cards on desktop and a stacked list on mobile. Do not add decorative claims or figures.

Worked example table

Use a real semantic HTML table, not an image.

Recommended structure:

Adapt the columns to the written page if its example is structured differently, but retain all supplied figures and the comparison between sale structures.

Requirements:

• Include the writer’s illustrative-example caption.
• Use <caption>, <th> and appropriate scope attributes.
• Align numeric values consistently.
• Do not calculate or infer missing values.
• On narrow screens, place the table in a keyboard-accessible horizontal scroll wrapper. Do not shrink the type until it becomes difficult to read.
• Keep the illustrative disclaimer visibly adjacent to the table.

Place a “Get my number” or equivalent supplied CTA directly below the table. It should scroll to the hero form or launch the site’s established quote flow.

Cost-of-time callout

Place the passage comparing the discount to the value or interest saved in a highlighted callout box. It should be visually prominent but not styled as a warning or error.

Fee list

Use a short list that makes each fee and who pays it easy to scan. Preserve any distinction between:

• Court filing costs.
• Buyer legal costs.
• Processing costs.
• Servicing costs.

Do not imply a fee is paid by the company unless the written content explicitly says so.

Offer-comparison checklist

Render the advice on written quotes, net proceeds, changing offers, partial sales and pressure tactics as an open checklist. Do not place it in an accordion.

C. Partial versus full sale section

Render the explanation of selling only part of the payment stream as:

• Introductory prose.
• A four-item list covering the partial-sale structures provided in the copy.
• A short paragraph about which payments to sell and how pricing changes.
• The supplied closing line or statistic.

The four sale structures can be displayed as a two-by-two grid of compact cards on desktop and a single stacked list on mobile.

Do not create an interactive calculator or selector.

An image is not required. If the written package contains an approved diagram, place it after the introductory paragraph with descriptive alt text. Otherwise, let the list carry the section.

D. Decision section

This section should contain the following distinct components in the writer’s order:

1. Common reasons for selling.
2. The central “sell when the money now does more than the discount costs” test.
3. Pros and cons.
4. Alternatives to selling.
5. A prominent “not a loan” explanation.
6. Guidance on planning the use of the lump sum.

Common reasons

Use a concise bulleted list followed by the writer’s explanation of how the court views the proposed use.

Decision-test callout

Pull the one-line decision test into a highlighted quotation or callout. Keep its supporting prose immediately before or after it.

Pros and cons

Use two side-by-side panels on desktop:

• Benefits or reasons in favor.
• Costs or reasons against.

Stack the panels on mobile. Use semantic lists, not a table. Do not style the “pros” side so aggressively that the “cons” become visually subordinate.

Not-a-loan box

Render the sale-versus-loan explanation in a bordered or tinted information box. It must remain in the normal reading flow and should not resemble a promotional banner.

E. Eligibility and state differences section

Build this section from:

1. The list of qualifying settlement or payment types.
2. Special eligibility notes, including prior sales, inherited rights, minors and any company position on workers’ compensation.
3. The explanation of life-contingent payments.
4. The explanation of state-by-state process differences.

Use a standard list for eligible payment types and prose for the special cases.

For the state-law portion:

• Use a short three-item list for the aspects that vary by state.
• Link to existing state pages or the existing state-page directory where URLs are supplied or already available on the site.
• Do not add a fifty-state statute summary to this page.
• Do not create links to nonexistent state pages.
• Link the separate annuity-payment page where the written content calls for it and an existing route is available.

F. Process section

This section must visually communicate the process in sequence.

Numbered process

Use an ordered list or the site’s accessible step component for the complete quote-to-funding process. Each step should contain:

• A short step name.
• One or two lines explaining what the seller does and what the company handles.

The process must include all supplied stages from quote request through funding. Do not combine stages if doing so removes the disclosure period, petition, hearing or court order.

On desktop, the step component may use a vertical line or numbered timeline. On mobile, use a single vertical ordered list.

Supporting subsections

Following the numbered process, use separate H3 subsections for the content covering:

• The disclosure statement.
• Court approval and the hearing.
• Whether the seller needs a lawyer or other independent advice.

After the court-approval passage, include the supplied “questions about the hearing” phone CTA. Use a tel: link.

Timeline graphic

After the process explanations, render a small timeline using the phases and time ranges stated in the written content. Typical phase labels should be taken from the supplied copy, such as:

• Disclosure or waiting period.
• Filing and notice.
• Hearing and order.
• Funding.

The timeline must not introduce a duration not present in the writing.

Implement it as an accessible list first. Any connecting line, arrows or decorative graphic should be CSS and aria-hidden="true". The information cannot exist only in an image.

Keep the explanation of “cash in days” or advances immediately adjacent to this timeline.

G. Taxes and public benefits section

Use two clearly separated H3 subsections:

1. Tax treatment.
2. SSI, Medicaid and other needs-based benefits.

Place the supplied tax, legal or benefits-advice disclaimer after both passages in a subdued note style.

Do not rewrite the content as a guarantee of tax treatment. Do not add a calculator or eligibility tool.

H. Buyer selection and company proof section

Build this section in three parts.

Questions and warning signs

Render two open checklists:

• Questions to ask every buyer.
• Warning signs or red flags.

These may be side by side on desktop and stacked on mobile. Keep the final standard for comparing buyers—the written net amount and stable terms—visually associated with these lists.

Do not introduce competitor profiles or name competing companies.

Company proof

Use an H3 followed by a compact proof grid or list. Possible items include only the verified facts supplied in the written page:

• Years and transaction volume.
• Direct-buyer status.
• States served.
• BBB or association standing.
• Offer-lock policy.
• Court or legal costs paid by the company.
• Named case specialist.
• Spanish-speaking support.

Where a named specialist is supplied with an approved headshot, use the existing image asset. Otherwise, use text only. Do not source an unapproved portrait.

Seller reviews

Use three or four static review cards, not an auto-rotating carousel. Each card should use the information actually supplied:

• Review quotation.
• Seller name or approved display name.
• State.
• What was sold.
• What the proceeds were used for.

Use <blockquote> and <cite> where appropriate.

Include the supplied link to the third-party review profile. Do not invent review text, identities, ratings or transaction details.

Do not add Review or AggregateRating schema by default, particularly for testimonials displayed by the company about itself.

I. Closing CTA band

End the page with a full-width band using the writer’s closing heading and two-line reassurance.

Include:

• Primary quote CTA linking back to #quote-form, or the site’s established quote modal.
• Clickable phone number.
• Business hours or Spanish-language note if supplied.

Prefer a button back to the hero form over embedding a second full form. If the site’s established conversion pattern requires a repeated form, reuse the production form component with unique IDs and identical validation and consent behavior.

Do not place new informational sections after this band.

Part 5Responsive behavior

Desktop

• Hero: two columns.
• Rate drivers: three columns.
• Partial-sale types: two-by-two or four compact columns if the site’s content width supports it.
• Pros and cons: two columns.
• Buyer questions and red flags: two columns.
• Review cards: three or four columns depending on available width.

Tablet

• Hero may remain two columns only if the form stays at least approximately 360 px wide.
• Collapse multi-column content to two columns where necessary.
• Keep table horizontally scrollable.

Mobile

• Use a single-column flow.
• Do not place an image above the hero form.
• Use full-width form fields and primary buttons.
• Stack all cards and checklists.
• Maintain at least 44 × 44 px touch targets.
• Prevent horizontal page overflow; only the example table’s wrapper may scroll horizontally.
• Keep the phone number easy to tap.
• Do not use sticky overlays that cover content or form controls.

Part 6Visual hierarchy

• The hero form and worked example are the two strongest visual elements.
• Use restrained section-background changes to separate major topics.
• Use callouts for:
  • The cost-versus-benefit decision test.
  • The explanation of the face-value gap.
  • The fact that a sale is not a loan.
• Use icons only when the site has an existing icon set. Mark decorative icons as hidden from assistive technology.
• Avoid generic stock imagery, money imagery, gavels and oversized courthouse photos.
• Avoid excessive card treatment. Ordinary explanatory prose should remain prose.
• Do not hide caveats in tiny text. Disclosures and example captions must use the site’s normal secondary-text size and meet contrast requirements.

Part 7Accessibility requirements

• One H1 and a logical heading hierarchy.
• Proper landmarks: header, main, sections and footer.
• Associate every form input with a visible <label>.
• Associate errors using aria-describedby or the site’s established accessible form pattern.
• Ensure keyboard access to all controls and horizontal table scrolling.
• Provide visible focus styles.
• Meet WCAG AA contrast requirements.
• Use semantic ordered and unordered lists.
• Use a semantic table with caption and header scopes.
• Do not use color alone to distinguish pros from cons or successful from invalid form states.
• Respect reduced-motion preferences.
• Add useful alt text only to informative images. Use empty alt text for decorative images.
• Do not make phone numbers or links depend on icon-only labels.

Part 8SEO and document setup

• Use the SEO title supplied with the written page. Do not put multiple title options into the page.
• Use the writer’s selected H1; it may differ from the SEO title.
• Use the supplied meta description. If none is supplied, create a concise description from the existing opening and CTA language without adding unsupported claims.
• Set a self-referencing canonical URL.
• Allow indexing unless the page is intentionally in staging.
• Use the site’s Open Graph and social-sharing defaults. If no approved page image exists, use the sitewide default rather than sourcing a stock image.
• Preserve or generate breadcrumbs through the site’s existing breadcrumb system.
• Keep the state, annuity and other internal links contextual.
• Do not add FAQPage schema.
• Preserve the site’s existing Organization and WebSite schema.
• BreadcrumbList schema may be generated by the existing breadcrumb component.
• Add Service schema only if the site already uses a validated service-page schema component. Do not add fixed prices, ratings or unsupported offer data.

Part 9Conversion and analytics

Use existing analytics conventions rather than inventing a parallel event system. Confirm tracking for:

lightspark- Hero quote submission.

• Hero quote validation failure.
• Quote CTA clicks below the pricing example.
• Phone clicks.
• Hearing-question phone clicks.
• Final quote CTA clicks.
• Third-party review-profile clicks.

If the site captures campaign parameters, preserve them through form submission using its existing implementation.

Do not fire a successful-lead event until the form backend confirms submission.

Part 10Performance requirements

• Do not add a large hero image or background video.
• Use the existing icon set and CSS rather than loading a new visual library.
• Lazy-load any below-the-fold review or specialist images.
• Set image dimensions to prevent layout shift.
• Keep custom JavaScript minimal.
• Use server-rendered or statically rendered primary copy so all explanatory content is present without interaction.
• Do not make the quote form dependent on an unnecessary third-party script if the site already has a native form component.

Part 11Factual and compliance guardrails

Before publishing, verify that the build has not:

• Invented or changed an industry range, discount rate or worked-example figure.
• Described the example as an actual guaranteed quote.
• Hidden fees or the example disclaimer.
• Promised approval or guaranteed a judge’s decision.
• Claimed the process takes only days where the written timeline says otherwise.
• Called the transaction a loan.
• Stated that credit checking, tax treatment or benefit effects work differently from the supplied content.
• Added unsupported “best,” “highest payout” or “lowest rate” claims.
• Added unsupported BBB, association, licensing, volume or review claims.
• Added a Spanish service line where none exists.
• Presented the buyer’s lawyer as the seller’s lawyer.
• Added new competitor, state-statute or reversal content.
• Collapsed substantive answers into accordions.

Part 12Pre-publish acceptance checklist

The page is complete only when:

• [ ] Existing site header, footer and navigation remain intact.
• [ ] There is exactly one H1.
• [ ] The quote form is visible in the hero and works through the production backend.
• [ ] The hero has no competing image.
• [ ] Phone links work and display the correct number and hours.
• [ ] All main sections appear in the prescribed order.
• [ ] The pricing example is a semantic table with the exact supplied figures and caption.
• [ ] The pricing CTA links to the quote form.
• [ ] Partial-sale options are easy to scan.
• [ ] Pros and cons receive comparable visual weight.
• [ ] The process is an accessible numbered sequence.
• [ ] Disclosure, court approval and independent-advice content remain visible.
• [ ] The timeline uses only supplied durations.
• [ ] Tax and benefits caveats are visible.
• [ ] Buyer questions and red flags are open, not collapsed.
• [ ] Company proof and reviews use verified content only.
• [ ] The final CTA returns to a working quote path.
• [ ] No FAQ section or FAQ schema has been added.
• [ ] No dead state or annuity links exist.
• [ ] Mobile layout has no page-level horizontal overflow.
• [ ] Forms, table, links and interactive controls pass keyboard testing.
• [ ] Metadata, canonical URL and index settings are correct.
• [ ] No unresolved placeholders, editorial notes or unsupported claims remain.