C12 — Chapter 3 - Schema.org

Criterion C12 : Schema WebSite SearchAction — guide + checklist

PART 1 - Fundamentals Chapter 3 - Schema.org Keyword : schema website searchaction

This criterion seems “simple,” but it creates many discrepancies in production.

The **C12 — Schema WebSite SearchAction** criterion is part of our SEO checklist (335 criteria). Here, you have a **practical** method to verify and fix it — with a concrete example.

What exactly this criterion covers

This criterion seems “simple,” but it creates many discrepancies in production.

**C12 — Schema WebSite SearchAction** (Chapter 3 - Schema.org): potentialAction SearchAction for direct search from Google Sitelinks

Why it matters (SEO + UX)

Why it matters: it is a comprehension signal for the engine. When poorly applied, we often observe: ambiguity (wrong associated query), duplication between pages, or loss of performance on CTR.

On high-volume generated sites, this criterion also serves as a **safeguard**: a stable rule prevents 1,000 errors at once.

How to verify (step by step)

Approach: validation via Search Console (real data). Recommended tool: **Screaming Frog (JSON‑LD extraction)**.

  1. Test the URL in Google Rich Results Test.
  2. Validate the JSON‑LD (types, required properties, consistency with content).
  3. Check Search Console → “Enhancements” (if available) for errors/warnings.

Tip: first isolate 10 “representative” URLs (top pages + generated pages) before scaling the fix.

How to fix properly

Strategy: fix the minimum necessary, then stabilize.

  • Choose **one main type** (Article / FAQPage / LocalBusiness…) that is consistent.
  • Fill only what you can justify in the content (no invented fields).
  • Validate, then monitor errors via Search Console.

Next: re-crawl 50–200 URLs, then monitor Search Console for 7–14 days (impressions/CTR/indexing).

Concrete example (illustrative)

Example (illustrative):

  • **Context**: local page for a law firm in Tunis
  • **Before**: No schema (or an incomplete JSON‑LD).
  • **After**: Added an Organization schema consistent with the content.
  • **Note**: Goal: structure information and reduce ambiguity for the engine.

Checklist to tick

  • [ ] Consistent schema type
  • [ ] Required fields present
  • [ ] No unjustified information
  • [ ] Validation OK (0 errors)
FAQ

Frequently asked questions — C12

What is the most common error on “Schema WebSite SearchAction”?

Applying an overly generic automatic pattern (same logic on all pages) without adding a differentiating element.

Which tool is fastest for large-scale control?

For this type of criterion, a crawl (e.g., Screaming Frog) + targeted verification in Screaming Frog (JSON‑LD extraction) is generally the fastest combo.

How to prevent it from happening again on 10K generated pages?

Freeze an auto-generation rule (title/structure/schema/URLs) + add automatic control (crawl or test) before production import.

Ready to go from theory to action?

Validate this criterion with an audit, then deepen the method in the Academy.

Audit with the tool → Learn in the Academy →