Search Engine News — January 2022 Recap

Every month our team clips the search news that will change how you work, and drops the rest. Here is the January 2022 edition.

Top Moves This Period

The January 2022 cycle brought the usual mix of ranking updates, AI Overviews expansions, and quieter algorithm shifts. We only surface items that changed a real client site.

What to Change This Week

Nothing on this list is emergency work — but pushing it now will keep you ahead when the next quarter's changes stack.

• Re-check canonicals on paginated archives.
• Refresh JSON-LD Article authors for E-E-A-T.
• Audit AI-Overview candidate pages against the current answer format.

What We're Watching Next

Signal quality across AI surfaces is still the dominant story. Model-specific citation patterns are stabilizing enough to design for.

{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Search Engine News — January 2022 Recap",
  "speakable": {
    "@type": "SpeakableSpecification",
    "cssSelector": ["h1", ".tldr", ".key-takeaway"]
  }
}

Speakable JSON-LD — voice + AI answer surfaces

• Install WBP Omni SEO Pro on staging and run the scanner against one silo.
• Approve the first 10 low-risk fixes (missing alt text, canonical, breadcrumbs, schema).
• Roll one fix back on purpose to feel the safety net before you scale.
• Verify with Bot Tracker that GPTBot, ClaudeBot and PerplexityBot have re-crawled the fixed URLs.
• Promote the workflow to production and schedule the weekly per-silo run.
• Add /llms.txt and /llms-full.txt at the site root — they are read by ChatGPT and Claude.

Inside WBP Omni SEO Pro: Guided Onboarding & Wizards

Why this matters for "Search Engine News — January 2022 Recap": Most SEO plugins ship with a config screen — WBP ships with a coach.

Best practices worth stealing

• Ship the fix as a diff, not a screenshot — reviewers can approve in seconds.
• Log every applied change with user, timestamp and before/after payload.
• Cap batch sizes at 250 URLs so rollback stays surgical.
• Re-crawl within 24h of any apply so attribution stays clean.

Manual vs. audit-tool vs. agentic

References & further reading

• Google Search Central — Structured data guidelines
• web.dev — Core Web Vitals field data
• Search Engine Journal — AI Overviews coverage
• Wikipedia — Semantic search, entity linking, schema.org
• YouTube: WP Bulk Publishing channel — walkthroughs of the agentic loop
• Reddit — r/SEO, r/bigseo threads on GEO measurement

Paired module: SEO Error Monitor

A rolling scan of indexability, canonical drift, meta length, duplicate H1s, image weight, mixed content and schema validity — with severity and one-click fixes. Errors are cheap to introduce (a theme update, a plugin conflict) and expensive to find without a monitor watching every publish.

• Enable Error Monitor in SEO Features
• Set severity thresholds per environment
• Route P1 issues to Slack/Email via the reports channel
• Approve suggested fixes in bulk or per-URL

Real-world examples

Three shapes this problem takes in the wild — and what the fix looked like when a team applied the GEO, AEO & AIO playbook end-to-end.

The workflow at a glance

Final thoughts

The teams that pull ahead in 2026 are the ones that made geo, aeo & aio boring — repeatable, auditable, reversible. That's exactly what the WBP Omni-Agent is built to run.