Crowdfunding Campaign Stack
Crowdfunding/pledge pages with Organization + Offer context, FAQs, and breadcrumb navigation.
When to use this stack
- Crowdfunding/pledge campaign landing pages
- Fundraising pages that need clear offer tiers and org context
- Pages where FAQs clarify eligibility, timelines, and fulfillment
What is included
Anchors the campaign’s organization with logo and URL.
Expresses the pledge/offer tier with pricing and URL.
Answers campaign timing, fulfillment, and eligibility questions.
Provides navigation context to the campaign page.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- availability
- itemListElement[].name
- logo
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- price
- priceCurrency
- url
Recommended properties
- address.addressCountry
- category
- description
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- priceValidUntil
- sameAs
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/crowdfunding/clean-water#org",
"name": "Clean Water Initiative",
"url": "https://www.example.com",
"logo": "https://www.example.com/assets/logo.svg",
"sameAs": [
"https://www.linkedin.com/company/clean-water-initiative"
]
},
{
"@context": "https://schema.org",
"@type": "Offer",
"@id": "https://www.example.com/crowdfunding/clean-water#offer",
"name": "Pledge — Provide Clean Water",
"description": "Fund a household water filtration kit.",
"price": "50.00",
"priceCurrency": "USD",
"availability": "https://schema.org/PreOrder",
"url": "https://www.example.com/crowdfunding/clean-water#donate",
"priceValidUntil": "2025-12-31"
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "When will funds be deployed?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Projects deploy quarterly. We publish impact updates after each deployment."
}
},
{
"@type": "Question",
"name": "Is my pledge tax-deductible?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes, if applicable in your country. You’ll receive a receipt after donating."
}
},
{
"@type": "Question",
"name": "What happens if the campaign is underfunded?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We reallocate to the next highest-priority clean water projects or refund upon request."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Campaigns", "item": "https://www.example.com/crowdfunding" },
{ "@type": "ListItem", "position": 3, "name": "Clean Water Initiative", "item": "https://www.example.com/crowdfunding/clean-water" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Should I list multiple tiers?
Include one Offer per tier shown on the page with distinct @id and URLs matching the visible buttons.
Can I include stretch goals?
Mention them in the Article body; keep Offer objects focused on pledge tiers that can be selected.