Skip to main content Scroll Top

FAQ Schema Generator: Valid JSON-LD for FAQs, Local Business, Service and Jobs

Updated September 2026 · Written and maintained by the Progression Agency strategy team

A schema generator that checks its own output. Pick a type, fill in what you have, and get JSON-LD with every required property verified against Google’s documentation — including the ones you left blank.

On this page · 10 sections
  1. What a schema generator actually does
  2. Why FAQ schema still matters after the rich result went away
  3. Local business schema, and the one mistake that breaks most of them
  4. Service schema: no rich result, and worth doing anyway
  5. Job posting schema, and why it carries the highest cost per click here
  6. The rule that decides whether markup helps or hurts
  7. How to add the block once you have generated it
  8. What this generator will not tell you
  9. Making the same page work for AI assistants
  10. Where this sits in a wider programme

The short answerGenerating JSON-LD is the easy part; any tool can wrap text in braces. Blocks fail for two reasons that templates never check: a required property is missing, which makes Google read the block as absent rather than partial, and the marked-up content is not visible on the page, which is a policy violation. This generator reports both, refuses to invent ratings, and tells you plainly which properties you left out and whether Google’s documentation calls them required or merely recommended.

Google’s structured data requirements change. Each type below links to the documentation it is built from, which is the source of truth rather than this page. Search volumes and cost-per-click figures quoted are Ubersuggest, United States, September 2026.

What a schema generator actually does

A schema generator turns what you know about a page into JSON-LD, the format Google and the AI assistants read to understand what a page is about rather than guessing from prose.

The generating part is trivial. Any tool can wrap your text in braces. What separates a block that earns a result from one that is quietly ignored is whether every property the documentation marks as required is actually present, and whether the marked-up content matches what a visitor sees. Those are the two gates this generator checks and most free templates do not.

Schema markup generator

Pick a type, fill what you have, and get JSON-LD with every required property checked against Google’s own documentation — including the ones you left out.

Results appear here.

Runs entirely in your browser. Nothing you paste is uploaded, logged or stored — which is also why it takes pasted text rather than a URL: a browser cannot read another site’s files without that site’s permission.

How a markup block earns a result
Most free generators stop at the first gate. The failures that actually cost traffic happen at the second and third.

Why FAQ schema still matters after the rich result went away

In 2023 Google restricted FAQ rich results to well-known government and health sites. The visible blue-link enhancement is gone for almost everybody, and a lot of advice concluded that FAQPage markup was therefore dead.

That conclusion confuses one consumer of the markup with all of them. FAQPage is a question paired with an explicit, self-contained answer — which is the exact shape a retrieval system wants when it assembles a response. The enhancement disappeared; the structure did not stop being the most machine-legible thing on your page.

What changed and what did not

  • The rich result: restricted to authoritative government and health sites.
  • The markup: still valid, still parsed, still in Google’s structured data documentation.
  • The content shape: a direct answer under a question heading, which is what gets quoted.
  • The practical effect: you stopped competing for a SERP enhancement and started competing to be the source of an answer.

Why the answer text is the part that matters

An assistant assembling a response needs a passage it can lift without editing. A forty-word answer that resolves the question on its own is liftable. A ten-word answer that depends on the paragraph above it is not. The generator flags answers under forty characters for that reason, and it is the single most useful warning it produces.

Where FAQ markup is worth adding

  • Service pages, where the same five objections come up in every sales call.
  • Pricing pages, where the honest answer is a range and a list of what moves it.
  • Location pages, where the questions differ by area in ways a template cannot fake.
  • Process pages, where the question is genuinely about sequence and timing.

Local business schema, and the one mistake that breaks most of them

LocalBusiness markup is what lets a machine state your name, where you are and when you are open without inferring it from a footer.

The failure is almost always the same: address supplied as a single string rather than a PostalAddress object with streetAddress, addressLocality and addressRegion as separate properties. It looks correct to a human reading the code and is unusable to a parser, so nothing errors and nothing works.

Choosing the right subtype

LocalBusiness has dozens of subtypes — Plumber, Dentist, Electrician, Restaurant, HomeAndConstructionBusiness. Using the specific subtype tells a machine what category you compete in, which is exactly the judgement an assistant has to make when somebody asks for a kind of business rather than a named one. Use the narrowest subtype that is honestly accurate.

Hours are a structure, not a sentence

Opening hours belong in openingHoursSpecification objects with a day, an opening time and a closing time. “Mon-Fri 9-5” in a paragraph is invisible. The generator takes a day, an open and a close per line and builds the objects for you.

One block per location, not one for the company

  • A business with three locations needs three LocalBusiness blocks on three pages, not one block listing three addresses.
  • Each block sits on the page that describes that location.
  • The telephone should be the number that rings at that location.
  • Sharing one block across locations is the reason multi-location sites under-perform in local results.
What each schema type is worth per click
Cost per click is a proxy for commercial intent. The developer-intent terms carry volume but sit in a different market.
Required and recommended properties by type, per Google’s documentation
TypeRequiredRecommendedMost common omission
FAQPagemainEntityinLanguageAnswers too short to quote
LocalBusinessname, addresstelephone, openingHoursSpecification, url, priceRange, geo, imageaddress sent as a string, not a PostalAddress
Servicename, providerareaServed, serviceType, description, offersareaServed left blank
JobPostingtitle, description, datePosted, hiringOrganization, jobLocationbaseSalary, employmentType, validThroughvalidThrough
Productnameimage, description, brand, offers, aggregateRating, reviewoffers, or an invented aggregateRating

Service schema: no rich result, and worth doing anyway

Service has no rich result of its own, which is why most tools skip it and most sites have none. It is also the type that answers the question an assistant is actually asked.

When somebody asks an assistant who does a particular job in a particular place, the machine needs two facts: what you do, and where you do it. Service with serviceType and areaServed states both explicitly. Nothing else on a typical page does.

areaServed is the field that decides near-me questions

A service page that never names its area is asking a machine to infer geography from an address in the footer. Naming the counties, boroughs or cities you actually serve, as separate entries, is the difference between being a candidate answer and not.

Do not claim an area you do not serve

Listing forty towns you would technically drive to is the structured-data version of a doorway page. It produces leads you cannot service profitably and it is trivially contradicted by your own reviews and directory listings.

Job posting schema, and why it carries the highest cost per click here

“Job posting schema generator” is a small term — roughly forty searches a month in the US — carrying a cost per click of $95.23, the highest in this entire keyword set.

That number is a signal about who searches it. Nobody idly looks up JobPosting markup. The people searching are staffing firms and employers with an open role and a budget, which is why the auction is expensive and why the term is worth serving properly even at low volume.

validThrough is the property everybody omits

It is not required, so most generators leave it out. Google drops postings that go stale, and a posting with no declared end date has no way to prove it is current. Omitting it is the most common reason a correctly-marked-up role stops appearing.

Salary data changes performance

  • Postings with baseSalary are shown more often than those without.
  • The value belongs in a QuantitativeValue with minValue, maxValue and unitText.
  • unitText is HOUR, DAY, WEEK, MONTH or YEAR, and getting it wrong misstates the offer by orders of magnitude.
  • A range is fine; an invented range that contradicts your offer letter is not.
What this generator checks that a template does not
The last row matters. Any tool promising a rich result is selling something it does not control.

Want this done for your site?We build and maintain the search, content and paid programmes described on this page.

Get a free proposal

The rule that decides whether markup helps or hurts

Structured data must describe content that is visible on the page. This is the line between markup and misrepresentation, and it is enforced.

Marking up questions that do not appear on the page, prices you do not display, or ratings you never collected is a policy violation, and the penalty is applied to the site rather than to the block. The generator refuses to help with the ratings case specifically because it is the one people ask for most.

What counts as visible

  • Content a visitor can read without authenticating.
  • Content inside an accordion the visitor can open counts as visible.
  • Content rendered only to a crawler does not.
  • Content that contradicts the visible text is worse than no markup at all.

Ratings deserve a specific warning

aggregateRating is the most abused property in schema. It must come from reviews you collected, about the thing being marked up, displayed on the same page. A rating pulled from a different platform, or averaged across your whole company and attached to one product, is the pattern manual actions are written for.

How to add the block once you have generated it

The output is a JSON-LD object. It goes inside a script tag with the type application/ld+json, in the head of the page it describes.

One page, one set of blocks, each describing something genuinely on that page. Multiple types on one page is normal and correct — a service page can legitimately carry Service, FAQPage and Organization at once.

Where it goes by platform

  • WordPress: a header snippet plugin, or your SEO plugin’s schema field if it accepts raw JSON-LD.
  • Shopify: theme.liquid, inside the head, guarded so it only renders on the intended template.
  • Webflow: page settings, custom code, head.
  • Squarespace: page settings, advanced, code injection.
  • Static sites: directly in the template for that route.

Then check it against the parser, not against your eyes

Paste the finished page into Google’s Rich Results Test and the Schema Markup Validator. They answer different questions: one tells you whether a rich result is possible, the other whether the markup is valid schema.org at all. Both are free and neither is optional.

FAQPage — Questions and answers. Still read by assistants.
LocalBusiness — Name, address, hours. The near-me foundation.
Service — What you do, where. No rich result, real value.
JobPosting — A role you are filling. Highest CPC in the set.
Product — A thing at a price. Offers or nothing.
Organization — Who you are. The entity spine.
Where the JSON-LD goes, by platform
PlatformWhere to paste itWatch out for
WordPressHeader snippet plugin, or the SEO plugin’s schema field if it takes raw JSON-LDContent filters can mangle raw code in post bodies
Shopifytheme.liquid, inside the headGuard it so it renders only on the intended template
WebflowPage settings, custom code, headPer page, not site-wide, unless it truly applies everywhere
SquarespacePage settings, advanced, code injectionSite-wide injection puts one block on every page
Static siteDirectly in the template for that routeOne template can serve many pages; vary the values

What this generator will not tell you

It will not tell you whether Google shows a rich result for your page, because nothing can.

Eligibility is decided by your markup. Display is decided per query by a system nobody outside Google observes. Any tool that promises the second is describing the first and hoping you do not notice the difference.

Three honest limits

  • It validates structure and required properties, not truthfulness — it cannot know whether your hours are right.
  • It checks the block, not the page, so it cannot see whether the content is actually visible.
  • It reflects Google’s documented requirements at the time of writing; those requirements change and the documentation is the source.
Required — Missing one. Block reads as absent.
Recommended — Missing many. Eligible but thin.
PostalAddress — A string instead. Silent failure.
Visible match — Marked not shown. Policy violation.
validThrough — Never set. Dropped when stale.
aggregateRating — Invented. Manual action.
What the 2023 FAQ change did and did not alter
AspectBeforeAfterStill true today
Rich result in searchShown broadlyRestricted to government and health sitesGone for most sites
Markup validityValidValidStill in Google’s documentation
Parsed by GoogleYesYesYes
Useful to AI assistantsYesYesA question with a self-contained answer is the ideal shape
Worth addingFor the enhancementFor machine legibilityThe reason changed, not the answer

Making the same page work for AI assistants

Schema is one half. The other half is whether the prose around it can be lifted as an answer without editing.

Assistants quote passages, not pages. A page that answers its own question in the first sentence under a heading shaped like the question gets quoted; a page that builds to its answer in paragraph six does not, however good the markup is.

The structural checklist

  • Answer the heading’s question in the first sentence beneath it.
  • Shape headings as the question a person would actually type or say.
  • Keep the answering paragraph self-contained, so it survives being lifted out of context.
  • Define your terms in plain language rather than assuming the jargon.
  • Attach one citable source per factual claim.
  • Keep the URL stable, because a citation to a moved page is a citation lost.

Check the result rather than trusting it

Whether a page is extractable is testable. Read it with JavaScript disabled, and see what survives when the page is reduced to plain text. Both of those are separate free tools on this site and both take under a minute.

Direct answer — First sentence. What gets quoted.
Question heading — Shaped as asked. Retrieval handle.
Defined terms — Stated plainly. Entity clarity.
One source — Per claim. Citable.
Short paragraphs — Extractable. Lift-friendly.
Stable URL — Unchanged. Worth citing.
Failure modes, and the symptom each produces
FailureWhat you seeWhy it happens
Missing a required propertyNothing at all; no errorGoogle reads the block as absent rather than partial
Address as a plain stringMarkup validates, local results do not improveA parser cannot split it into locality and region
Marked-up content not visibleWorks, then stops workingPolicy violation; the penalty lands on the site
No validThrough on a jobPosting appears, then disappearsStale postings are dropped once they cannot prove currency
Invented aggregateRatingRich result, then a manual actionRatings must be real, on-page and about the marked-up thing
One block for several locationsWeak multi-location performanceEach location needs its own block on its own page

Where this sits in a wider programme

Markup is plumbing. It makes a page legible to machines; it does not make the page worth citing.

The order that works is: have something specific to say, say it in a shape that can be lifted, then mark it up so nothing is ambiguous. Sites that invert that order end up with immaculate structured data describing content nobody has a reason to quote.

Want this done across the site?

We build and maintain the structured data, the content shape and the measurement together, rather than shipping markup and calling it a strategy.

Get a free proposal

Not sure which of these applies to you?Tell us the situation and we will say plainly what we would do first, and what we would not.

Talk it through

Getting found in search

AI, AEO and what is changing

Paid media and lead generation

Websites and design

Choosing and working with an agency

Social, content and brand

By industry and by situation

Frequently asked questions

What is a FAQ schema generator?
A tool that turns a list of questions and answers into FAQPage JSON-LD, the structured format Google and AI assistants read. This one also checks that each answer is long enough to stand on its own when quoted, and that every property the documentation requires is present.
Is FAQ schema still worth adding in 2026?
Yes, for a different reason than before. Google restricted the FAQ rich result to authoritative government and health sites in 2023, so the visible enhancement is gone for most sites. The markup is still parsed, and a question paired with a self-contained answer is the exact structure a retrieval system wants when assembling a response.
Does FAQ schema still produce a rich result?
Not for most sites. Google limited FAQ rich results to well-known government and health sites. Adding the markup is now about machine legibility rather than a SERP enhancement.
Why does my LocalBusiness markup not work?
The most common cause by far is supplying the address as a single string instead of a PostalAddress object with streetAddress, addressLocality and addressRegion as separate properties. It reads correctly to a human and is unusable to a parser, so nothing errors.
Which LocalBusiness subtype should I use?
The narrowest one that is honestly accurate — Plumber, Dentist, Electrician, HomeAndConstructionBusiness rather than the generic LocalBusiness. The subtype tells a machine what category you compete in, which is the judgement an assistant makes when somebody asks for a kind of business rather than a named one.
Can I put one LocalBusiness block for all my locations?
No. Each location needs its own block on its own page, with the phone number that rings at that location. A single block listing several addresses is a common reason multi-location sites under-perform in local results.
What is Service schema for if it has no rich result?
It states what you do and where you do it, explicitly. When somebody asks an assistant who performs a particular job in a particular area, those are the two facts the machine needs, and nothing else on a typical page states them unambiguously.
What does areaServed actually affect?
It is the property that makes you a candidate for questions framed by location. Without it, a machine has to infer your geography from an address in the footer.
Should I list every town I could possibly serve?
No. That is the structured-data equivalent of a doorway page, it generates leads you cannot service profitably, and it is contradicted by your own reviews and directory listings.
Why is job posting schema so expensive per click?
Because nobody researches JobPosting markup idly. At roughly forty US searches a month it carries a $95.23 cost per click, which tells you the searchers are staffing firms and employers with an open role and a budget.
What is validThrough and why does it matter?
It is the date a job posting stops being valid. It is not a required property, so most generators omit it, and Google drops stale postings. A posting with no declared end date has no way to prove it is still current.
Do I have to include salary in a job posting?
It is not required, but postings carrying baseSalary are shown more often. The value belongs in a QuantitativeValue with minValue, maxValue and a unitText of HOUR, DAY, WEEK, MONTH or YEAR — getting unitText wrong misstates the offer by orders of magnitude.
Can I mark up content that is not visible on the page?
No. Structured data must describe content a visitor can see. Marking up invisible content is a policy violation and the consequence lands on the site, not on the individual block.
Does content inside an accordion count as visible?
Yes, provided the visitor can open it. Content rendered only for a crawler does not count.
Can I add aggregateRating to look more credible?
Only if the ratings are real, collected from customers, about the thing being marked up, and displayed on the same page. Averaging company-wide ratings onto one product, or importing them from another platform, is precisely the pattern manual actions exist for.
Where do I paste the generated JSON-LD?
Inside a script tag with type=”application/ld+json”, in the head of the page it describes. In WordPress that is a header snippet or your SEO plugin’s schema field; in Shopify, theme.liquid; in Webflow and Squarespace, the page’s custom code or code injection panel.
Can one page carry several schema types?
Yes, and it is normal. A service page can legitimately carry Service, FAQPage and Organization at once, as long as each describes something genuinely on that page.
How do I check the markup after I add it?
Use Google’s Rich Results Test and the Schema Markup Validator. They answer different questions — whether a rich result is possible, and whether the markup is valid schema.org at all. Both are free.
Will this guarantee a rich result?
No, and no tool can. Your markup decides eligibility; Google decides display, per query. Any tool promising the second is describing the first.
Is anything I paste into this tool uploaded?
No. The analysis runs entirely in your browser and nothing you paste is stored. The only thing sent to us is the contact detail you enter to unlock the full findings.

Want this done for your site?We build and maintain the search, content and paid programmes described on this page.

Get a free proposal

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Our website uses cookies from third party services to improve your browsing experience. Read more about this and how you can control cookies by clicking "Privacy Preferences".
Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Privacy Policy
You have read and agreed to our privacy policy
Required
Contact Us
0