Elementor's Overview widget — shortcuts, tutorials, news — clutters the dashboard of every subsite that has Elementor active. On a single site you'd just ignore it; across a multisite network you want it gone everywhere at once, without touching the subsites where Elementor isn't even installed.
Not every page is for public eyes — internal SOPs, server notes, draft policies. WordPress can lock content so only administrators see it, and the right method depends on whether you're hiding a whole page, a whole category, or just one secret line inside an otherwise public post.
A vector graphic is just math, so it stays razor-sharp at any size and weighs a fraction of a photo. That makes SVG the right choice for logos, icons, and diagrams — but only if you embed it the right way, strip the bloat, and sidestep the handful of traps that make a "sharp" format look fuzzy.
WordPress turns on a lot of things by default. Some of them quietly work against your SEO — spawning thin, near-duplicate pages, or loading scripts you never use. You don't need to disable everything, but a handful of defaults are worth switching off on most sites. Here's the shortlist, grouped by why.
Every time you upload an image, WordPress quietly creates a whole separate page for it — a near-empty page with just the image and its caption. Most site owners never notice, but search engines do, and they're rarely a good look. Here's what attachment pages are, why they usually hurt, and how to switch them off cleanly.
You're mapping a messy source vocabulary onto a clean target taxonomy. The target has about 5,600 slots, so the job must be roughly 5,600 decisions — right? The backlog is already past 8,900, and still climbing.
You shipped a fix to how one field is computed, re-ran the pipeline across everything, and it reported a clean run. Then the consistency check still flags those records as wrong. The fix is in the code, the rebuild "ran" — and the records never changed. Your own optimisation skipped them.
The report said 80 duplicate groups still to resolve. You'd been resolving them for days. You run it again after a big batch and it *still* says 80-ish. The backlog isn't stubborn — the scan is counting work you already finished.
You hardened a skill in the repo, shipped the PR, and the agent kept loading the old one. Or you fixed the live skill by hand, and the versioned copy quietly stayed behind. Same root cause: the copy you run and the copy you version are two different files.