FAQPage、HowTo 與 LocalBusiness：小型 WordPress 網站的結構化資料整理

FAQ blocks, HowTo toggles, and LocalBusiness cards in Rank Math or Yoast feel like free rich results. On small WordPress sites they more often create invisible FAQPage spam, the same FAQ JSON-LD on every URL, HowTo markup on pages that are not procedures, and LocalBusiness NAP that disagrees with the footer. That is schema hygiene — not a Schema.org encyclopedia, not title/meta SERP copy, and not image/Open Graph cards. It is how you stop wasting structured-data credibility (and, where Google still shows enhancements, rich-result eligibility) on markup nobody can see or trust.

Honest 2026 note up front: Google no longer shows FAQ or HowTo rich results for ordinary sites (HowTo deprecated earlier; FAQ rich results fully wound down in 2026). Leaving broken FAQ/HowTo on the page does not magically restore stars. Cleaning it still matters: GSC noise, other consumers, AI/answer surfaces that read markup, and the same plugin habits that spam FAQPage usually break LocalBusiness — which still matters for local visibility. Fix the mistakes; do not chase dead SERP chrome.

What each type is for (no textbook)

FAQPage: a page whose primary content is a list of questions and answers visible to users. Markup should mirror visible Q&A — not a hidden accordion injected sitewide by a block.

HowTo: a page that teaches a real, ordered procedure with steps a human can follow. A service landing page (“We fix leaks in Austin”) is not a HowTo just because the plugin has a toggle.

LocalBusiness (and subtypes): who you are, where you operate, how to contact you. Name, address, phone (NAP), url, and often openingHours / geo need to match what humans see. Wrong NAP is worse than sparse NAP.

You do not need every Schema.org type enabled. You need visible FAQ only where the page is FAQ, HowTo only on real procedures, and one accurate LocalBusiness that matches the site.

Myth: “Turn on the FAQ block everywhere for rich results”

Rank Math FAQ blocks, Yoast FAQ blocks, and theme “SEO FAQ” widgets often emit FAQPage JSON-LD even when the questions are collapsed, duplicated in a sidebar, or pasted into a reusable block that lands on Home, every service URL, and the blog index.

Problems:

Invisible or near-invisible FAQ (markup without matching visible content) fails Google’s own structured-data expectations and reads as spammy.
The same five questions on thirty URLs create duplicate FAQ entities across the site.
Editors keep adding keyword-stuffed “questions” nobody asks.

Prefer: one dedicated FAQ URL (or a short visible FAQ section on a money page) with Q&A a human can read without opening DevTools. If the block is only there for JSON-LD, delete it.

When the same FAQ copy appears on overlapping URLs, settle which URL owns the topic with canonical tags — then keep FAQ markup on the canonical page only.

Duplicate FAQ on every page

Sitewide footer FAQs, “global” Rank Math snippets, and copied Gutenberg patterns are the usual source. View source (or the plugin’s schema preview) on Home, a service URL, and a blog post. If FAQPage appears on all three with the same @graph questions, that is not helpful coverage — it is duplication.

Fix: remove global FAQ schema. Keep FAQ markup on pages whose main content is Q&A. For a short on-page FAQ under a service guide, mark it up once on that URL; do not also emit it from the footer.

HowTo for non-howto pages

“How we work” marketing copy, pricing tables, and “3 reasons to hire us” are not HowTo. Plugins that auto-wrap numbered lists as HowTo create invalid or misleading graph nodes: missing HowToStep text, steps that are slogans, or a single step that is the whole sales pitch.

Prefer: HowTo only when the page is literally instructional (replace a filter, submit a claim, configure a plugin). Otherwise leave the list as HTML. Do not enable HowTo sitewide “just in case.”

LocalBusiness NAP mismatches

This is the type that still earns real attention for local businesses. Common small-site failures:

Symptom	What breaks
Plugin Name ≠ footer / GBP name	Trust / entity confusion
Address in schema, “serving Greater X” only in copy	Inconsistent NAP
Old phone in JSON-LD after a number change	Call tracking / GBP mismatch
Multiple LocalBusiness nodes (theme + Rank Math + directory plugin)	Conflicting entities
`url` pointing at a campaign short link	Wrong canonical home

Campaign tracking can use a URL shortener; LocalBusiness url should be the stable homepage (or primary location URL), not a tagged short link. Align schema NAP with Google Business Profile and the visible footer before you chase more properties.

Missing required / expected properties

FAQ without visible answers, HowTo without steps, LocalBusiness without name + address (and usually telephone / url) — validators complain for a reason. Adding twenty optional properties while streetAddress is empty does not help. Fill the basics that match the page; skip vanity fields you cannot stand behind.

Test with Rich Results Test (and friends)

Pick money URLs: Home, top service/location page, real FAQ page (if any), one blog post.
Run Google Rich Results Test (and Search Console → Enhancements / structured data where reports still exist for types you use).
For FAQ/HowTo: treat “detected” as a hygiene signal, not a promise of FAQ stars in 2026. Remove spammy or invisible nodes anyway.
For LocalBusiness / Organization: fix errors and NAP mismatches until the graph matches the footer.
After plugin changes, re-test — caches and combined @graph from two SEO plugins are common.

One schema writer in <head> beats Rank Math + Yoast + a theme “local SEO” pack racing the same types.

40-minute practical pass

List money URLs + any dedicated FAQ.
Search source for FAQPage / HowTo / LocalBusiness — note which URLs emit them.
Kill invisible or sitewide duplicate FAQ blocks.
Strip HowTo from non-procedure pages.
Align LocalBusiness NAP with footer + GBP; one node.
Fill missing required basics; delete vanity junk.
Re-run Rich Results Test on what you changed.

Closing

Small WordPress sites lose schema trust from FAQ blocks that spam invisible FAQPage, duplicate FAQ on every URL, HowTo on sales pages, LocalBusiness NAP mismatches, and missing required properties — not from failing to enable every Schema.org type. Clean the graph so it describes visible content; put effort into LocalBusiness accuracy; stop expecting FAQ/HowTo SERP chrome that Google already retired.

More practical technical notes: blog. Free utilities when you need them: tools.

— Riichi Mirza