You're reading the ForegroundWeb Newsletter, all about photography websites. First time reading? Sign up here.
ForegroundWeb Newsletter
YOUR WEEKLY DOSE OF PHOTO WEBSITE ADVICE & INSPIRATION.
IN TODAY’S EMAIL:
⚡️ 3 Quick tips: newsletters, platforms, ad traffic
🧠 Really deep dive: How to use FAQ sections to boost your SEO and AI visibility
QUICK TIPS
You post. You blog. But is your email list obvious on your site?
Most photographers hide the subscribe box—no incentive, no visibility. Add a homepage opt-in (inline, slide-in, or tasteful pop-up) with a concrete lead magnet (prep guide, wardrobe tips, mini-session early access).
Then email consistently, segment by service, and sell seasonal offers to the right people. This fills calendars faster than hoping for DMs.
2. 💡 Is your website platform holding you back?
Most photographers choose a website builder for simplicity, but often hit a wall when their business grows. Don't let your platform dictate your business's future.
Dedicated photography platforms like PhotoDeck, SmugMug, Pixietset, etc. are great for e-commerce and file delivery, but they often can't match the design flexibility and power of WordPress. If your goal is a custom, detailed site that brings in clients, you need a flexible foundation.
I consistently recommend WordPress for its SEO control and design power, even though it requires some maintenance. Choosing your builder is a game of compromises, but WordPress offers the most room to grow.
Reach out if you need an expert review on whether your current platform is right for your goals.
3. 🚫 Stop sending ad traffic to your homepageQuick tip
Most paid campaigns fail for one simple reason: the click lands on a generic page. That’s money leaking. Create a specific offer (mini-sessions, seasonal shoots, limited promos) and send people to a focused landing page with one clear CTA. Generic “Services” pages aren’t built for cold traffic.
Add urgency, social proof, and a short form. Run separate campaigns per offer (newborn vs. maternity) and measure bookings, not clicks.
DEEP DIVE
How to use FAQ sections to boost your photography website’s SEO and AI visibility
If your photography website doesn’t include an FAQ section with structured data, you’re leaving clicks (and bookings) on the table. A simple, well-placed FAQ block can improve visitor experience and help search engines “get” what your site is about.
Let’s walk through how to do this the right way, as I’ve done for dozens of photographers in my own website audits.
Why you should care about FAQ sections and structured data
Because you want more traffic, more informed visitors, more bookings; and this helps.
Here’s what I’ve seen working after 100+ website audits for photographers:
1. Lower visitor friction
If someone lands on your site and immediately sees “How long will it take to get my photos?” or “Do I need to bring outfits?” you answer them before they ask. Fewer questions = fewer drop-outs.
2. Signals clarity to search engines
When you mark up FAQs correctly (with the Schema.org “FAQPage” schema), you’re telling Google & co: “Hey this page has direct Q&A content.” This boosts the semantic clarity of your page.
3. Potential for rich snippets (more click-attracting listings)
If the markup is eligible, Google may show your FAQ content right in the search results (under your link) which increases real estate and attractiveness. One case study saw an over 50% increase in CTR after implementing FAQ schema.
4. Future-proofing for AI/voice search
Search engines are increasingly AI-powered. Structured data helps them parse your content better and get you in the “answer boxes” or voice assistant responses.
Which pages should have FAQ sections (and why)
You don’t want FAQ content randomly thrown everywhere. Here’s how I recommend structuring it for a photography site.
Home page
Yes, your homepage can benefit from a “mini-FAQ” section. Think of 3–5 very common questions (pricing, location, style). It immediately builds trust and clarity.
Just ensure the answers remain concise and not duplicate in full across many pages.
Service pages (portraits, weddings, commercial, etc.)
This is where FAQ schema shines. Each service page has unique questions: “How many images will I receive for a wedding?”, “Do you travel internationally?”, “What’s your backup plan if it rains?”
Add a richer FAQ section here and corresponding markup.
Gallery or portfolio pages
Optionally, if visitors have distinct questions about print options, licensing, file delivery. If you do this, keep it relevant (don’t dilute).
Dedicated FAQ page
If you have many questions (>10-15), you may build a full-page FAQ. Then you may choose to mark up both the page and perhaps not repeat the same schema on every other page (to avoid duplication issues).
What to include in your FAQ section (content & schema)
Here’s a step-by-step of what I do when coaching a photographer site.
Step 1: Research the right questions
Walk through your inbox: what do clients ask repeatedly?
Use tools like “People Also Ask” in Google by searching e.g. “wedding photographer Bucharest cost”, “what to wear family shoot”.
Focus on questions your ideal clients ask.
Step 2: Write crisp, helpful answers
Keep answers direct, 50-100 words is often enough.
Avoid vague fluff. Give actual value.
But don’t spoil your site’s conversion funnel by giving away everything; e.g., you might answer “Yes, I travel” rather than “Here’s the full price list, see page X”.
Step 3: Display visibly on the page
Use a toggling accordion or simple list of questions + answers. (Your screenshot example is great: a UI that expands the answer when clicked.)
Make sure the content in the visible FAQ matches exactly the questions & answers in your schema.
Step 4: Add the JSON-LD markup
Use the FAQPage schema format. Here’s a simple example (you’ll adapt it):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What style of photography do you offer?",
"acceptedAnswer": {
"@type": "Answer",
"text": "My style is natural, timeless, and focused on connection..."
}
},
{
"@type": "Question",
"name": "How long will it take to receive the images?",
"acceptedAnswer": {
"@type": "Answer",
"text": "For weddings I deliver an online gallery within 4-6 weeks..."
}
}
// Add more Q&A pairs here
]
}
</script>Key things:
Use
"@type": "FAQPage"at top.Each question is an object with
@type: Question,namefor the question text.acceptedAnswerobject has@type: Answerandtextfor the answer.The visible content on the page must match the schema, as Google recommends.
You don’t need to hand-code this if you don’t want to. There are free online FAQ schema generators (just Google “FAQ schema generator” and you’ll find several tools where you paste your questions and answers, and it outputs valid JSON-LD code). You can also ask AI chatbots to create it for you, just feed them your Q&A list and ask for properly formatted FAQPage schema. And if your site runs on WordPress, many plugins or builders (like RankMath, Yoast, or Elementor) already have this built in. Often it’s literally a checkbox or a field labeled “FAQ schema,” and you’re done.
Step 5: Validate and monitor
Use the Google Rich Results Test tool or the Schema Validator tool to ensure the markup is error-free.
After implementing, request indexing via Google Search Console and monitor in the Enhancements > FAQ report.
Keep an eye on your click-through rate (CTR) for pages where FAQ schema is live.
Best practices & things to watch out for
From 15 years of building photography websites I’ve learned a few caveats:
Don’t duplicate FAQ content across many pages. Google advises that identical Q&A markup repeated on multiple pages may reduce value.
Only one answer per question (so don’t use FAQ schema on pages where there are multiple community answers). If your page allows many answers, it’s a QAPage not FAQPage.
Avoid using FAQ schema purely for promotional fluff. The questions should be genuine. If it’s marketing talk, it could get ignored.
Visible to user: ensure the FAQ content is on the page (not hidden behind login or loaded dynamically in a way search bots can’t see), as recommended by Google’s guidelines.
Rich snippet isn’t guaranteed: Even with correct markup you may or may not get the extra SERP listing. Still worth doing for the semantic clarity and potential.
Keep it up to date: If your business changes (new policy, pricing, service area), update the FAQ. Out-of-date answers undermine trust.
How this drives results (and what you should expect)
When you implement a well-crafted FAQ section with schema, here’s what you often see (based on my projects):
More pages from your site qualify for rich snippets or enhanced listings → higher visibility.
Better alignment with “question”-style search queries (which are increasing thanks to voice search and natural-language search).
Improved CTR (click-through rate) from search results because you’re giving the user more value before they click.
Lower bounce rate (users stay longer because they got answers immediately).
More trust built, new visitors feel your site is authoritative because FAQs show you anticipate their questions.
Now, you’re not going to flip a switch and go from page 3 to page 1 overnight just because you added FAQ schema. But you will strengthen your foundation, improve site architecture, enhance semantic clarity for AI/SE bots, and that compounds.
"I've been Google AdWords (now Google Ads) certified since 2007 and have taught SEO courses since 2011 and your advice is 100% spot on. Really good work and advice! You are a great example to follow."
Next step (your action list)
Here’s your mini-roadmap:
✅ Audit your main pages (home + service pages) and list 5–8 real questions your clients ask.
✅ Write concise, useful answers for each question.
✅ Add the FAQ section visibly on the page (expandable accordion or simple list).
✅ Add matching JSON-LD FAQPage markup in the page header or just before
</body>. You can use any free online generator or AI chatbots for this conversion.✅ Run Google’s Rich Results Test to validate.
✅ Submit the URL in Google Search Console for re-indexing.
✅ Monitor clicks & impressions for the page, see if your snippet changes or improved performance.
✅ Periodically review and refresh the FAQ content every 3-6 months.
If you’d like help choosing optimal questions, writing the markup, or integrating it into your custom site build, I’d love to help. We can set up a quick audit call or I can show you how I’d do it on one of my recent client sites (with real examples). Just let me know when you’re ready.
Want all of this done for you? Check out my complete SEO service for photographers.
QUOTE OF THE WEEK
"If at first you don't succeed, failure may be your style."
How was today's newsletter?
When you’re ready, here’s how I can help:
Website audit for photographers: I’ll manually review every aspect of your site—design, SEO, speed, UX, and backend—and walk you through my findings live on a Zoom call. You’ll get a personalized action plan, the full recording, and practical steps to turn your site into a client-converting machine. Book your site audit »
Private 1:1 consulting call: get specific, actionable advice, answering your most pressing questions questions on how to improve your photography website. Book a call »
Bespoke photography website or makeover: Your photos matter most. My web-design services just make them shine. Whether you want a custom website from scratch, or just looking to freshen up what you already have, I got you covered. Let’s build a new site or do an existing site makeover
