Looking for more on SEO? This collection on the Acme blog brings together related articles, guides, and insights. Browse all 12 posts below.
The gtag.js snippet was installed correctly and the page loaded fine, but GA4's real-time report stayed empty — because the CMS's Content-Security-Policy was silently blocking every request to Google's domains.
Opening the sitemap directly in a browser rendered a wall of broken-looking markup — but the file itself was perfectly valid XML the whole time.
Taxonomy terms and author bylines copy automatically to a translated post — the SEO Open Graph image doesn't, and the gap is easy to miss until a share card renders blank.
We created a translated post with the wrong slug, corrected it with an update call, and accidentally 301'd our own live article to the new URL.
Only 1 in 10 website migrations improve SEO rankings — most lose ground. These are documented failures, and the specific mistakes behind each one.
Rankings don't belong to your CMS — they belong to your URLs, content, and signals. What actually transfers in a migration, what's genuinely at risk, and the realistic timeline for both.
EmDash generates your sitemap, robots.txt, and JSON-LD structured data automatically — but only correctly if one config value is set. Here's the full SEO surface: site-wide defaults, per-page metadata via plugin hooks, and the one setting that silently breaks all of it if skipped.
Rankings aren't lost because you changed CMS platforms — they're lost because search engines temporarily can't tell your new URLs are the same content as your old, already-trusted ones. Understanding that mechanism is what actually prevents the drop.
301 redirects need to stay live for a minimum of 12 months, not until launch day passes. This is the scannable, platform-agnostic checklist for before, during, and after a CMS migration — the specific items that actually determine whether you keep your rankings.
JSON-LD is the format Google recommends, and it's trivial to generate from a CMS's own content fields — no separate plugin required if your platform lets templates emit it directly. Here's what to actually implement, and how the mechanics differ from a plugin-based approach.
Headless architecture doesn't make a site fast by branding alone — it removes specific bottlenecks: CDN-served pre-built pages instead of per-request server rendering, more crawl budget spent discovering pages instead of waiting on them, and metadata generated programmatically instead of set by hand.
Your CMS determines whether updating metadata takes 30 seconds or a developer ticket, whether pages load in 2 seconds or 8, and whether search engines can crawl your content efficiently. Yes, it affects SEO — here's exactly how.