Working on Wordpress and Gutenberg — In Production

Working on Wordpress and Gutenberg is one of the small levers that pays back at scale. Here's the version we run in client work, tuned for AI-search visibility without breaking existing rankings.

Why This Keeps Coming Back

Working on Wordpress and Gutenberg shows up in every WordPress audit because teams treat it as a launch task. It isn't — it's a recurring loop.

The Loop That Works

Detect → Explain → Fix → Approve → Apply → Track → Rollback. The loop is the product, not the report.

What to Stop Doing

Stop shipping PDF audits nobody reads. Ship diffs a human can approve.

# nginx.conf — rewrite legacy URLs at the edge
location ~ ^/old/(.+)$ {
  return 301 https://$host/new/$1;
}

Edge-evaluated 301 rewrite — faster than PHP origin

• 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.
• Log-file check: confirm the fix reached Googlebot AND the AI crawlers, not just the frontend.

Inside WBP Omni SEO Pro: Google Search Console Deep Integration

Why this matters for "Working on Wordpress and Gutenberg — In Production": GSC in the browser is a research tool; GSC inside the CMS is a workflow.

Manual vs. audit-tool vs. agentic

Common mistakes to avoid

Glossary — plain-English definitions

Paired module: SEO Task List & Reminders

A to-do system that surfaces issues, suggested fixes, upcoming audits and personal reminders — with iteration tracking per URL. SEO work fragments across dashboards, docs and Slack; a task list inside the CMS is where it stops being forgotten.

• Task List → Auto-populates from Error Monitor and Agents
• Assign tasks to roles or users
• Iterate on the same URL with linked history
• Snooze or dismiss with a required reason

Real-world examples

Three shapes this problem takes in the wild — and what the fix looked like when a team applied the Technical SEO playbook end-to-end.

The workflow at a glance

Final thoughts

The playbook above is the same one WBP Omni SEO Pro runs every night on production sites — Detect, Explain, Fix, Approve, Apply, Track, Rollback. Ship the workflow once and technical seo becomes a background process, not a fire drill.