You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moving to a /blog path can definitely have benefits, like improving URL structure and helping search engines and users better understand our content hierarchy. There might be some ranking or performance fluctuations but they’re typically short-lived if handled properly. I believe it’s worth doing for the long term...
Here’s what we need to keep in mind:
Set up permanent (301) redirects carefully from the old URLs to the new /blog paths.
Update all internal links to point directly to the /blog URLs in content, menus, and footers. (Can this be done in bulk?)
Update XML sitemap with the new /blog URLs.
Verify canonical tags on the new blog pages point to the correct /blog URLs.
Verify that schema markups is still intact and reflects the new paths.
Map old redirect URLs to their new /blog URLs to avoid redirect chains (e.g., A → B → C).
The text was updated successfully, but these errors were encountered:
Yes, with Gatsby we would need to use onPostBuild API on gatsby-node.js to fetch the slugs and add the redirects with them. In Next.js it will be different. So yeah, it might make sense to wait in case it's not so urgent.
Moving to a /blog path can definitely have benefits, like improving URL structure and helping search engines and users better understand our content hierarchy. There might be some ranking or performance fluctuations but they’re typically short-lived if handled properly. I believe it’s worth doing for the long term...
Here’s what we need to keep in mind:
The text was updated successfully, but these errors were encountered: