Every month our team clips the search news that will change how you work, and drops the rest. Here is the January 2023 edition.
- Top three Google / AI-search moves in January 2023.
- What to change on your site this week.
- What we're watching next.
Top Moves This Period
The January 2023 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.
Inside WBP Omni SEO Pro: Cloudflare Edge Integration
Push redirects, security rules and cache rules to the Cloudflare edge, and read edge analytics back into WBP.
Why this matters for "Search Engine News — January 2023 Recap": Redirects and rules at the edge are 10× faster than at the origin and remove the origin as a bottleneck for SEO plumbing.
- 1Step 1
Integrations → Connect Cloudflare
- 2Step 2
Choose which rules push to edge (redirects, security, cache)
- 3Step 3
Watch edge hit rate and rule performance
- 4Step 4
Rollback pushes zone-side without touching Cloudflare UI
"The edge is where SEO plumbing belongs — the origin should be free to serve content."
— WBP Omni SEO Pro
Ship reversible fixes weekly. Measure citations, not just clicks. Keep one authoritative schema emitter. Everything else is a distraction.
Manual vs. audit-tool vs. agentic
| Trait | Manual | Audit tool | Agentic (WBP) |
|---|---|---|---|
| Output | Spreadsheet | PDF report | Approvable diffs |
| Reversibility | Manual DB fix | None | One-click rollback |
| Speed to fix | Days | Weeks | Minutes |
| Scale | ≤ 200 URLs | Any (read-only) | Any (write + rollback) |
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.
Paired module: Tag Manager & Taxonomy Guard
Merges near-duplicate tags, enforces a controlled vocabulary, prevents thin tag-archive pages and rewrites internal links when tags are merged. Uncontrolled tagging creates thousands of thin archive pages that dilute topical authority and confuse the LLM entity graph.
- Analytics → Taxonomy Guard → Run duplicate scan
- Review suggested merges with post counts and overlap %
- Merge with automatic redirect + internal-link rewrite
- Set a minimum-post threshold before a tag archive is indexable
Do I need to change my strategy based on January 2023?
Rarely. Monthly recaps are for calibration, not pivots. Pivots come from your own analytics.
Where do you source this?
Google's official communications, Search Central posts, first-party AI-surface changelogs, and our own client dashboards.
Do I need Cloudflare to use WBP?
No — every feature works origin-only; Cloudflare is a performance and reach upgrade, not a requirement.
Can I noindex thin tag archives without breaking navigation?
Yes — Taxonomy Guard keeps the archive reachable for users but noindexes and removes it from sitemaps until it crosses the post threshold you set.
Ship this workflow inside WordPress
WBP Omni SEO Pro turns every playbook on this blog into an approvable, reversible diff.
Get WBP Omni SEO ProAffiliate — this link goes to the official WBP Omni SEO Pro product page.
