Photography Booking Stack
Photography booking pages with LocalBusiness + Service + FAQs and breadcrumb navigation.
When to use this stack
- Photography service pages with packages and booking CTA
- Studios or freelancers listing service tiers and locations
- Pages needing clarity on inclusions, delivery, and scheduling
What is included
Anchors NAP, URL, and brand identity for the photographer or studio.
Describes the photography service/package and provider.
Answers questions about scheduling, delivery, and rights.
Provides navigation context to the booking 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
- address.addressCountry
- address.addressLocality
- address.addressRegion
- address.postalCode
- address.streetAddress
- itemListElement[].name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- offers.price
- offers.priceCurrency
- provider.@id
- serviceType
- telephone
- url
Recommended properties
- areaServed.name
- description
- geo.latitude
- geo.longitude
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- offers.availability
- offers.url
- priceRange
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": "LocalBusiness",
"@id": "https://www.example.com/photography#business",
"name": "Sunrise Photography",
"url": "https://www.example.com/photography",
"telephone": "+1-917-555-0199",
"image": "https://www.example.com/images/studio.webp",
"address": {
"@type": "PostalAddress",
"streetAddress": "45 Broadway",
"addressLocality": "New York",
"addressRegion": "NY",
"postalCode": "10006",
"addressCountry": "US"
},
"priceRange": "$$"
},
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/photography#service",
"name": "Portrait Session",
"serviceType": "Photography",
"description": "60-minute portrait session with 20 edited photos delivered within 5 business days.",
"provider": { "@id": "https://www.example.com/photography#business" },
"offers": {
"@type": "Offer",
"price": "350.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/photography#book"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How do I book?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Use the booking link to choose your date/time. A 25% deposit confirms your slot."
}
},
{
"@type": "Question",
"name": "What is included?",
"acceptedAnswer": {
"@type": "Answer",
"text": "20 edited photos in high resolution. Additional edits available for a fee."
}
},
{
"@type": "Question",
"name": "When do I get the photos?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Within 5 business days via an online gallery with download access."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Services", "item": "https://www.example.com/services" },
{ "@type": "ListItem", "position": 3, "name": "Photography", "item": "https://www.example.com/photography" }
]
}
]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
Can I list multiple packages?
Yes. Add one Service per package, each with its own @id and Offer aligned to the visible CTA.
What if pricing is custom?
If no price is shown, omit price fields and keep offers.url/availability aligned to the booking flow.