Sell My Structured Settlement” provider page

Part 1Page type and route

• Preferred new-page slug: /sell-my-structured-settlement/
• If the site already has a canonical page for this service, update that page instead of creating a duplicate.
• Use the site’s standard header, navigation, breadcrumb and footer.
• Do not add article furniture such as author, publication date, reading time, comments, blog sidebar or related-post cards.
• Use the SEO title, meta description, H1 and headings supplied with the written page. There must be one H1.
• Set a self-referencing canonical URL and allow indexing.

Use the client’s existing theme, spacing, typography, form system, buttons and design tokens. The page should feel calm and advisory, not promotional or urgent.

Part 2Content handling

Use the supplied written page as the source of truth.

• Preserve its final wording, headings, figures, qualifications and legal disclosures.
• Do not turn the page into one long rich-text field. Place the copy into the components specified below.
• Do not invent pricing, discount rates, turnaround times, advance limits, review counts, ratings, years in business, registrations, addresses or guarantees.
• Use only verified site data or values supplied in the written page.
• Do not add competitor names, buyer directories, “best company” rankings or comparison logos.
• Do not introduce pre-settlement funding content.
• Annuity and lottery payments may appear only where the supplied copy or quote-form options mention them.
• Do not use “loan,” “borrow” or “apply for financing” in UI labels. This page offers a sale and a quote, not a loan.
• Keep all substantive content server-rendered and present in the HTML.

Part 3Page structure

Use this exact content order:

1. Offer hero and quote form
2. What selling the payments means
3. Payment value, discount and costs
4. Partial versus full sale
5. Quote-to-funds process
6. Whether selling makes sense
7. Choosing and checking the buyer
8. Transfer questions
9. Final quote CTA

Do not insert unrelated promotional sections between these modules.

Part 4Hero: offer and quote form

Use a two-column hero on desktop.

Left/content column

Place:

1. Breadcrumb
2. H1
3. Short opening answer explaining the offer
4. The supplied compact offer bullets
5. The passage answering whether the visitor can sell or cash out all or part of the payments

Keep the main answer visible without requiring an accordion or modal.

Right/form column

Place the production quote form in a visually distinct card. Use the existing live lead form and submission integration if one exists; do not create a non-functional mockup.

Configure these fields in this order:

1. What the visitor wants to sell
   • Structured settlement, selected by default
   • Annuity
   • Lottery payments
2. Payment amount
3. Number of payments
4. When the payments begin
5. Name
6. Phone number

Retain any additional field, consent checkbox or disclosure required by the site’s production form or applicable lead-capture rules. Do not request sensitive documents, a Social Security number or bank information in this initial form.

Form requirements:

• Use visible labels; placeholders cannot be the only labels.
• Use appropriate mobile input modes and autocomplete attributes.
• Apply inline validation and an accessible error summary.
• Preserve values after a validation error.
• Submit to the existing CRM or lead endpoint.
• Show a clear success state and the stated next step.
• Use the supplied quote-button wording.
• Add the click-to-call phone number and business hours.
• Under the button, show the supplied no-obligation, no-upfront-fee and written-quote line.
• Use existing spam protection without introducing a visible challenge unless required.

On desktop, make the form card sticky with an offset below the site header. Keep it within the hero or its assigned grid rail; it must not cover the footer or follow the visitor across the entire page. On mobile, render it in normal document flow.

For mobile ordering, use:

1. H1 and short offer
2. Offer bullets
3. Quote form
4. Longer qualification/cash-out explanation

Give the form wrapper the stable anchor quote-form. Every “get a quote” CTA on the page should link to this anchor and move focus to the first field where appropriate.

Do not add a countdown, limited-time message, intrusive popup or automatic chat takeover.

Part 5What selling the payments means

Build this as a compact explanatory section, not as multiple oversized cards.

Place the supplied content in this order:

1. One-line structured settlement definition
2. A short definition list for legal terms, including transfer and life-contingent payments
3. The “this is not a loan” explanation
4. The statement identifying the company as the direct buyer/factoring company

Use a semantic definition list where it fits. A restrained icon row is optional, but icons must be decorative and must not replace labels.

Do not use a stock photograph in this section.

Part 6Payment value, discount and costs

This section should make the financial comparison easy to scan.

Worked-example card

Create one card containing the exact example supplied by the writer. Show three clearly labelled figures:

• Face value of the payments being sold
• Lump sum paid
• Difference between them

Follow the figures with the supplied explanation of the payment schedule and the factors that affect value.

Treat the figures as an example, not a guaranteed offer. Do not calculate or substitute values. If values are dynamically sourced, display a timestamp or other qualification only if the existing site already does so.

Explanatory content

After the card, place:

1. The discount-rate explanation
2. The cost and fee explanation
3. A three-item “how to read an offer” list covering the face value, discount rate and net lump sum
4. Any supplied written-quote comparison or price-match language

Do not visually minimize the discount, deductions or net proceeds.

Calculator callout

Add a compact calculator callout after the offer-reading list.

• Link to the site’s existing structured settlement calculator.
• Make clear through the supplied copy that it gives an estimate and the written quote controls.
• Include a secondary “get a written quote” button linking to #quote-form.
• Do not build a new calculator unless the site already has a tested calculator component and calculation rules.

Part 7Partial versus full sale

Begin with the supplied introduction explaining that the visitor may sell only the amount needed.

Build the options as a semantic three-column table:

Create one row for every option in the written page, such as a block of years, part of each payment, a future lump sum, part of a lump sum or a blended structure.

Requirements:

• Use <table>, <thead>, <tbody> and header scopes on desktop.
• On narrow screens, transform each row into a stacked card with all column labels repeated.
• Do not allow horizontal page scrolling.
• Keep the supplied “most common” note close to the table.
• Follow the table with the court-treatment paragraph and then the repeat-sale paragraph.

Do not add an interactive option selector unless it connects to the real quote flow and has been tested.

Part 8Quote-to-funds process

Numbered steps

Use a numbered step component for the complete process from quote through funding. Each step must include its supplied explanatory sentence, not merely a short label.

The sequence should cover:

1. Written quote from the payment schedule
2. Choosing how much and which payments to sell
3. Reviewing and signing the agreement and disclosure
4. Court petition and notices
5. Required waiting or notice period
6. Hearing and judge’s review
7. Court order, payment redirection and lump-sum funding

Place the supplied explanation of an advance at the step where it becomes available.

Small step icons are optional. If used, mark them aria-hidden="true".

Add a quote CTA immediately after the numbered steps.

Documents checklist

Render the documents passage as a proper checklist beside or directly below the steps. Use the writer’s exact list. This is informational, not an upload form.

On desktop, the checklist may sit in a side card. On mobile, place it after the process steps.

Court approval

Place the court-approval explanation in a full-width text block. Follow it with a short visible list of what the judge considers.

Do not place this information behind a tooltip or legal-disclaimer link.

Timeline, advance and independent advice

Use three compact subsections in this order:

1. Typical timeline and causes of delay
2. “If you need cash now” advance callout
3. Lawyer or independent-advice explanation

The advance callout must display all supplied conditions, including how it affects the final lump sum and what happens if the court denies the sale. Do not style an advance as instant approval or a way to avoid court.

Make clear that the buyer’s lawyer does not represent the seller.

Part 9Whether selling makes sense

This section should be visually neutral and credible.

Decision test

Present the writer’s three-question test in a highlighted but restrained panel. Use either numbered questions or a checklist. Do not turn it into an automated result quiz.

Reasons list

Render the common reasons to sell as a concise list. Keep the supplied explanation beside each reason rather than showing only category names.

Pros and cons

Use a balanced two-column comparison:

• Reasons selling can help
• Costs and risks of selling

Both columns should have equal visual weight. On mobile, stack them with the benefits first and risks immediately after.

When not to sell

End the section with the supplied “keep your payments if” content. Style this as ordinary advisory content, not a warning modal. Keep the partial-sale alternative in the same block.

Place a quote CTA after this section, linking to #quote-form.

Part 10Choosing and checking the buyer

Comparison criteria

Build the buyer-selection criteria as a visible checklist or compact list. Each criterion should be paired with the company’s supplied answer where the copy provides one.

Do not add a competitor table or claim that the company is “best” unless that exact, supportable language is in the approved copy.

Legitimacy checks

Create a second list showing how to verify any buyer. Include the client’s verified details inline where supplied:

• Legal business name
• Physical address
• Years in business
• Relevant state registration
• BBB record
• Third-party review source
• Consumer-protection or attorney-general resource

Make outbound verification links identifiable and open them according to the site’s existing external-link policy.

Use badges and logos only when the client is entitled to display them. Link verification badges to their source where possible.

Reviews

Use the site’s existing review component or verified review data.

Display:

• Three or four short reviews
• Reviewer first name and state, if supplied and approved
• Rating and total review count
• Named third-party review platform
• Link to the full reviews page or source

Use exact approved review excerpts. Do not fabricate, rewrite or combine reviews. Do not use an auto-rotating carousel; use a static grid or manually controlled component. On mobile, stack the reviews.

If the site has a live review feed, ensure its rendered content remains readable without waiting for a heavy third-party widget. Do not show stale aggregate numbers that conflict with the source.

Part 11Transfer questions

Use the written page’s four questions:

1. Whether a judge must approve the sale
2. Whether the sale is taxable
3. Selling payments established for a minor
4. What the purchase agreement contains and when the seller can cancel

Use native <details> elements or the site’s accessible accordion component.

Requirements:

• All answers must be present in the server-rendered HTML.
• Render all four answers open on first paint. They may be collapsed by the visitor afterward.
• Question controls must be keyboard operable and expose their expanded state.
• Do not duplicate large passages from earlier sections; preserve the concise answers and their links back to relevant sections.
• Do not add unrelated FAQs merely to increase the count.

Part 12Final CTA band

End the page with a full-width CTA band containing:

• The supplied final heading
• One sentence restating the free written quote, no obligation and no upfront fees
• Primary quote button linking to #quote-form
• Click-to-call phone number
• Business hours

Use the site’s normal high-contrast CTA treatment. Do not introduce new promises in this band.

Part 13Visual and responsive rules

• Use the site’s standard content width, approximately 1100–1200px if no token exists.
• Use a roughly 60/40 hero split on desktop.
• Maintain comfortable reading width for paragraphs.
• Prefer whitespace, borders and subtle background changes over heavy gradients.
• Avoid stock images of courtrooms, checks, cash or distressed consumers.
• Do not add a table of contents or blog sidebar.
• Do not hide core sections in tabs.
• Keep sticky elements clear of the header and cookie banner.
• Test tables, phone numbers, figures and form fields at 320px width.
• Respect reduced-motion settings.
• Meet the site’s WCAG contrast standard and maintain visible keyboard focus.

Part 14SEO and structured data

• Use the supplied SEO title and meta description.
• Use one H1 and a logical H2/H3 hierarchy based on the supplied headings.
• Keep headings descriptive; do not replace them with vague labels such as “Learn More.”
• Add BreadcrumbList structured data if breadcrumbs are displayed.
• Add Service and WebPage structured data using the client’s existing organization entity.
• FAQPage structured data may be added only when the four visible questions and answers exactly match the markup.
• Do not add Review or AggregateRating schema unless the site already has a compliant implementation and the displayed data meets Google’s eligibility rules.
• Do not mark this service up as a loan or credit product.

Part 15Links and interactions

Verify these links:

• Every quote CTA → #quote-form
• Phone numbers → the existing tracked tel: number
• Calculator callout → live calculator page
• Full reviews link → live review page or verified third-party profile
• Any legal or consumer-protection links → correct destination
• Internal references to court, pricing or partial-sale sections → stable section IDs if the writer includes them

Preserve the site’s existing dynamic number insertion and tracking. Never place personal form data into analytics events or URLs.

Part 16Analytics

Use the site’s existing analytics conventions to track:

• Quote-form view
• Form start
• Validation failure
• Successful submission
• Quote CTA clicks
• Phone clicks
• Calculator clicks
• Review-source clicks
• FAQ opens

Send field names or event states only, never names, phone numbers, payment amounts or other lead data.

Part 17Final acceptance checks

Before publishing, confirm:

• The page immediately identifies the company as a buyer of structured settlement payments.
• The quote form is visible near the top and submits successfully.
• Structured settlement is preselected in the form.
• The page explains all-or-part sales, court approval, discounting, fees and timeline.
• The worked example uses only approved figures.
• Partial-sale options remain understandable on mobile.
• The process, document checklist and court criteria are visible without interaction.
• Pros and cons receive equal visual treatment.
• Reviews, rating, address, registrations and business-history claims are verified.
• FAQ answers exist in the initial HTML.
• All quote buttons reach and focus the live form.
• No competitor directory, pre-settlement funding section, fake urgency or loan language has been added.
• No placeholders, dead links, horizontal scrolling or unsupported claims remain.
• The page passes keyboard, form-validation, mobile, performance and structured-data checks.