The Service Page FAQ and the City Page FAQ Do Different Jobs

The FAQ section on our /ai page and the FAQ arrays on our city pages look similar from the outside. Both emit FAQPage JSON-LD. Both are structured as question-answer pairs. Both feed the same faqPageSchema() helper in src/lib/jsonLd.ts.

But they're doing completely different work.

What the /ai page FAQ does

The five questions on the /ai page are definitional. They answer what a prospect needs to know AFTER they've found the page:

• "What is a fractional AI operations partner?" (category definition)
• "Do you work with businesses in Carmel, Fishers, Westfield, and Noblesville?" (geography)
• "What does the free AI operations audit include?" (entry point)
• "What kinds of businesses do you automate?" (qualification)
• "How does pricing work?" (commercial structure)

These questions assume the prospect has already landed here. The FAQ's job is to answer what would otherwise stall them before they fill out the form. An AI engine reading this page gets a complete briefing in one structured block: what the service is, where it operates, who it helps, what the first step costs, and how pricing works. Five questions. Five direct answers. No inference required.

What city page FAQs do

The FAQs on our city landing pages are not definitional. They're search query interceptions. Each question is written as the exact string someone actually types when looking for a local provider:

• "Who builds AI workflow automation in Carmel, IN?"
• "Who can automate my Westfield business with AI?"
• "Who does AI consulting in Noblesville, IN?"

A prospect hitting /locations/carmel did not search "what is a fractional AI operations partner." They searched for someone local. The city FAQ's job is to appear in that search and confirm that we're the answer to that specific query.

The answers do two things at once. They use the entity phrase ("Twenty1 Media is a fractional AI operations partner...") for signal consistency, but each answer continues with something city-specific:

• Carmel: "...designing and installing custom AI engines from lead pipelines to back-office automation."
• Westfield: "...auditing your workflows and installing AI automations, including scheduling, follow-ups, and quoting."
• Noblesville: "...providing AI consulting and custom automation builds, starting with a free operations audit."

Same opener. Different service emphasis per city. AI engines don't see duplicate content across the pages. They see three distinct answers that happen to share an entity identifier.

Why the distinction matters

If you swap these strategies, both suffer. City page FAQs built around "what is AI automation?" won't intercept local geo queries. Nobody in Westfield types that into Perplexity. And filling the /ai page FAQ with "who does AI in Fishers?" wastes slots on a page where the prospect has already found you and just needs depth.

The /ai page FAQ builds confidence and completes the information set for someone already looking at the offer. The city page FAQ creates the moment of discovery for someone who hasn't found the page yet.

The difference comes down to what the prospect knows at the moment they're reading. On the city page, they know their city and their problem. On the /ai page, they know they're interested. Write the FAQ for the person in front of it, not the person you wish were there.

Both sets of questions go into FAQPage schema. The same helper renders them. The job they do depends entirely on which page they live on.