Central generates a product FAQ that grows from the verified record. New questions surface from review themes, support tickets, and search behavior. Every answer is grounded in a source — and ships as a PDP section, Schema.org FAQPage, JSON-LD payload, and widget layer.
Static FAQs freeze at launch. A Living FAQ updates as new review themes surface, as support tickets repeat, and as buyers search the page for words it does not yet cover.
The Living FAQ is not a copy block. Every answer references the verified product fields, the review themes that surfaced the question, and the support or manual passages that confirm the answer.
Edit the source, and the answer updates. Re-mine reviews, and new themes surface as candidate questions. Sources stay attached to the answer wherever it ships — PDP, FAQPage, JSON-LD, widget.
every answer cites its sourcesDoes the Smeg TSF01 fit a bagel or thick slice of sourdough?
Yes for most sourdough loaves and standard bagel halves. The toaster has 38 mm wide slots with a self-centering rack, and the slot length accepts standard 12 cm bread. Very tall artisan loaves may need to be turned mid-toast.
How do I clean the chrome body without scratching the finish?
Wipe the chrome with a damp microfiber cloth and dry immediately to prevent water spots. Smeg's manual warns against abrasive cleaners, citrus-based sprays, and steel wool — they pit the chrome plating. For fingerprints, a small amount of distilled white vinegar on the cloth works.
Is the cord long enough to reach across a kitchen island?
The Smeg TSF01 has a 96 cm (3 ft 2 in) cord with a UK/EU/US-specific plug variant. For typical 90 cm-wide island counters with a recessed outlet, that reaches with about 6 cm of slack. For wider islands or counters without a flush outlet, an inline 1.5 m extension is the most common solution.
How loud is the lever and the pop-up — will it wake someone in the next room?
The lever has a soft mechanical click on press and a spring-assisted pop-up that buyers describe as quieter than a typical pop-up toaster. In sentiment analysis, only 4 of 847 reviews flagged the pop-up as too loud, and most attribute the lever press as quieter than the previous-generation Smeg.
Is the heating element replaceable if it burns out?
The heating element is not user-replaceable. Authorized Smeg service centers can replace it during the 2-year warranty period, and out-of-warranty repair is offered in most regions for a flat service fee. The merchant should confirm the regional service partner before this answer is auto-published.
What does the Smeg warranty actually cover, and for how long?
Smeg offers a 2-year manufacturer warranty on the TSF01 from the original purchase date. The warranty covers manufacturing defects in materials and workmanship, including the heating element, lever mechanism, and electronic controls. Cosmetic chrome wear, accidental damage, and misuse are excluded.
Central does not invent buyer intent. Each candidate question is mined from a real signal — a review theme, a recurring support topic, a search query the page does not yet answer, or a verified field with no buyer-facing explanation.
Buyer reviews are mined for repeated intent themes — sizing, fit, noise, finish, durability. A theme becomes a candidate question once enough reviewers mention it.
Recurring topics in support email, chat logs, and chatbot transcripts surface questions buyers were too unsure to ask on the PDP. Deflection is the goal.
Site-search misses, Google "people also ask" data, and PDP scroll-depth signals reveal what buyers searched the page for and didn't find.
Verified custom fields that have no buyer-facing explanation. The Living FAQ can narrate the spec in plain language and link to the field underneath.
Google rich results, ChatGPT, Perplexity, and Claude all consume Schema.org FAQPage data when it's published correctly. Central emits the exact FAQPage payload for every supported question — with merchant-friendly x-central provenance fields the agents can use to weight trust.
If an answer is held or in review, it does not enter the schema. Held questions never appear in rich results.
Google's rich result guidelines require self-contained, factually grounded answers. Central's FAQPage payload passes the rich-results test because every emitted answer is backed by a source the merchant can show under audit.
ChatGPT, Perplexity, and Claude consume Schema.org but also reward provenance metadata. The non-standard x-central block exposes source count, confidence, basis fields, and a verified timestamp — agents weight your PDP higher when they can trust it.
basislastVerified shows the answer is currentThe same Smeg TSF01 product page — before, then after Central. Before: a thin PDP with a product description and a review average. After: an answered FAQ section, an eligible rich result, and the same questions surfacing in the widget.
A static FAQ is written once and forgotten. The Living FAQ grows from real signals — review themes, support tickets, search queries, and verified field gaps. New questions surface as the catalog accumulates buyer behavior, and answers are refined as more sources verify them. Low-traffic questions can retire, high-traffic questions stay prominent.
Four signals. Review themes mined from buyer reviews, support tickets and chatbot logs, search queries from site-search and Google's "people also ask", and spec gaps where a verified field has no buyer-facing explanation. Every candidate question keeps its source attached for audit.
No. Central's anti-hallucination principle applies to every answer. If a question has no verifiable basis, it stays in held state and does not publish — not to the PDP, not to FAQPage schema, not to the widget. Held questions are visible to the merchant so the team can decide whether to add a missing source.
Yes, where Google's policy allows. Central emits a Schema.org FAQPage payload that passes the rich-results test for every supported question. Each Q&A also carries an x-central provenance block (sources, confidence, basis fields, last-verified timestamp) that AI shopping agents reward but Google ignores.
Yes. Every answer is editable. Merchant edits become a brand-authored source at confidence 1.00 — they outweigh scraped sources and persist through re-enrichment. Held or in-review answers are routed into the merchant queue first, so risky claims never auto-publish.
Agents read Schema.org FAQPage data directly. When the PDP also exposes the llms.txt data layer Central publishes, the agents get a machine-readable copy of every verified Q&A — including the basis fields the answer cites. Trustworthy provenance is how an agent decides whether to surface your product over a competitor's.